Re: [hibernate-dev] Search: paging over deleted entries [ISPN-2206]

Let's split the problem in two ## Infinispan In the ORM case we do filter null results. The logic is in `QueryLoader.executeLoader` and more precisely `ObjectLoaderHelper.returnAlreadyLoadedObjectsInCorrectOrder`. So it looks like a mistake of the Infinipsan Query module to not reproduce this behavior. Of course when you paginate, you will get smaller windows. Note however that iterate() is expected to return nulls in this situation AFAIR ## Return queries inlined with the current transaction I have to admit I did not spend time thinking hard about how to do avoid the problem. As you said we need an in memory index for the transaction to keep changes and prioritize. I am not fully following you on the update and removal but basically your collector would ignore documents that are planned to be removed or updated and you would index new and updated documents in your in-memory index. Is that correct? I'd love to see an experimental work on that because that's a question we will get more and more often with OGM coming. We will need a way to activate it lazily to not pay the cost unless it's really necessary. That would be a very nice new feature. Hardy, do you think you could work on a prototype? I would rather get Sanne focus on the OGM query parser. Emmanuel On 29 août 2012, at 00:52, Sanne Grinovero wrote: