[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-777?pag...
]
Sanne Grinovero commented on HSEARCH-777:
-----------------------------------------
Hi Nikita,
In Hibernate Search 4 there's no notion any more of
"batch"/"regular" usage: we can now "stream" regular
operations on a single reused opened indexwriter and still make it consistent, so the
separate configuration options are now unified and made simpler.
Could you please elaborate on your requirements so we think about it, especially if
it's still possible under the new design?
The ErrorContext passed into ErrorHandler should include a flag
indicating whether it's running in batch mode
-------------------------------------------------------------------------------------------------------------
Key: HSEARCH-777
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-777
Project: Hibernate Search
Issue Type: Improvement
Components: integration
Affects Versions: 3.4.0.Final
Reporter: Nikita D
Priority: Minor
Hibernate Search allows defining a custom error handler for indexing errors (implements
org.hibernate.search.exception.ErrorHandler). The ErrorHandler receives an ErrorContext
with metadata about the error.
It would be very useful to add the following method to the ErrorContext passed into the
ErrorHandler:
{code}
boolean isBatchMode();
{code}
This way a custom error handler can deal with errors that occur during a batch operation
differently from regular operations.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira