Re: [Initially posted to users@j.a.o] Problem with read limits & a query using a lucene index with many results (but below setting queryLimitReads)

Hi Thomas, thanks for the quick answer! Yes, I have seen cases where an index is re-opened during query execution. In that case, already returned entries are read again and skipped, so basically counted twice. I think it would be good to fix this (only count entries once). It sounds like this

Re: [Initially posted to users@j.a.o] Problem with read limits & a query using a lucene index with many results (but below setting queryLimitReads)

Hi, > Wouldn't it make sense to introduce a query option ala [1] to disable > read/memory limits for one particular query? It's possible, but my fear is that people would use the option in their queries too often... > OAK-6875 does not always have the desired effect (for sure there is some >

[Initially posted to users@j.a.o] Problem with read limits & a query using a lucene index with many results (but below setting queryLimitReads)

Hi all, sorry for cross-posting, but I didn't get an answer on the users list. I think the change made with OAK-6875 does not always have the desired effect (for sure there is some un-deterministic behaviour for large content being accessed via a lucene index which should at least be determin