Implement StatelessSession

Description

low priority to me

Environment

None

Activity

Show:
Emmanuel Bernard
June 17, 2011, 5:28 PM

forcontributor

Jonathan Wood
September 10, 2012, 2:35 AM
Edited

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.

Sanne Grinovero
September 10, 2012, 5:19 PM

Hi Jonathan,
that's a great point, I've opened to track it; I don't think I'll implement it using a StatelessSession as it's likely going to be more appropriate to use a different iteration form than what we do for RDBMS systems - depending on the NoSQL store type.

Assignee

Unassigned

Reporter

Emmanuel Bernard

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

Yes, likely

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Priority

Minor
Configure