|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hi Adrian,
sorry I didn't work on this anymore, many other priorities jumped in. Did you see the new "Conditional indexing" feature on http://docs.jboss.org/hibernate/search/4.2/reference/en-US/html_single/#search-mapping-indexinginterceptor ?
If you enable that on your entities, since version 4.2.0.Beta2 we apply it on the MassIndexer as well. It won't be as fast as what you would get from this feature as it will still initially load the entity, but could still save you a lot of processing and all the loading of @ContainedIn & @IndexedEmbedded relations.
I'd appreciate if you could run some experiments and share some stats to define how urgent this feature still is in practice. I guess you could hack a dirty solution on the current MassIndexer implementation using the #limitIndexedObjectsTo(long) method to simulate the indexing of only the number of entities you would have if you had this feature, and compare it with the effect of an EntityIndexingInterceptor.