SourceForge.net Logo
Main Overview Wiki Issues Forum Build Fisheye
Issue Details (XML | Word | Printable)

Key: CMP-911
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Shay Banon
Reporter: Martin Kovacik
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Compass

PaginationHibernateIndexEntitiesIndexer indexes duplicate DB records

Created: 13/Dec/09 12:28 PM   Updated: 13/Dec/09 12:28 PM
Component/s: Compass::Gps
Affects Version/s: 2.2.0 GA
Fix Version/s: None

Environment: Compass 2.2.0, postgresql 8.4, nativefs index


 Description  « Hide
PaginationHibernateIndexEntitiesIndexer creates duplicate indexes when pagination fetch count is lower than records in DB to index. I encountered this issue using postgresql (8.4). PaginationHibernateIndexEntitiesIndexer uses pagination without explicit order by. However postgresql (and to my knowledge MSSQL) pagination using firstresult and maxresult (which is translated to SQL LIMIT and OFFSET) is not guarenteed to be stable without order by. The easiest solution would be to add explicit "order by primary key" statement.

The possible (ugly) workaround for this issue is to set fetchCount to be greater than rows in DB to index.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.