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

Key: CMP-482
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Shay Banon
Reporter: Ben Dotte
Votes: 0
Watchers: 0
Operations

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

Better exception needed when incorrect transaction management causes Lucene IndexReader or I/O exceptions

Created: 12/Nov/07 09:35 AM   Updated: 02/Feb/09 10:22 AM
Component/s: Compass::Core
Affects Version/s: 1.2 GA
Fix Version/s: 2.3.0 beta1


 Description  « Hide
As discussed on this thread:

http://forums.opensymphony.com/thread.jspa?threadID=156558

If a Compass transaction is committed between running a search and retrieving the hits, for example, any of the following 3 Lucene exceptions might get thrown:

org.apache.lucene.store.AlreadyClosedException: this IndexReader is closed
java.io.IOException: The handle is invalid
java.io.IOException: Read error

It would be nice if Compass could detect invalid transaction management like this and throw an error, something to the effect that the search and hit retrieval must occur in the same transaction, for example.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Ben Dotte added a comment - 12/Nov/07 09:43 AM
Also note the exceptions probably won't get thrown unless the same subindex getting searched is also being updated at the same time. Even then the exceptions are intermittent.