|
||||||||
|
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 |
||||||||
I'd be willing to take direction on implementation, but am concerned about the low priority status.
In a pure OGM environment, the only stable path to query is Hibernate Search. I'm good with that .. no named/criteria queries...all lucene. The real kicker is that I cannot seem to get by the chicken/egg situation on re-indexing. MassIndexer fails in an OGM environment because StatelessSession is not implemented and a direct iteration of objects using fulltext.index(entity) fails due to transaction issues (also seen in MassIndex). To compound the problem, HS/lucene must be used to implement the "getAll" query for mass indexing since criteria/named are not available. Seems wrong to rely on a technique that requires using the target index as the source for modifications. Has anyone else encountered this problem and/or resolved it?
I can certainly pull the core implementation and implement, but I'd appreciate any guidance or suggestions.