Related community bug at https://hibernate.atlassian.net/browse/HSEARCH-1623 When using put/remove via HotRod, some objects might not be indexed if the system is under heavy load. These object will not be returned by Remote Query or returned based on their previous state. This also affects embedded querying when the cache is NOT transactional. The workaround is to mark the cache transactional, regardless of the cache being accessed over HotRod (note that then every single operation is enclosed in a transaction) or locally as an embedded cache.
Thanks Martin. to add a clarification: It also affects loss of update and delete operations, so while it's true that subsequent queries might miss results of newly inserted objects, they might also contain results which aren't supposed to be returned. The problem on missed delete operations only affects usage of projection, as when the user asks to return the object from the grid we remove the missing ones from the results. Another possible workaround is the rebuild the index periodically, assuming it's acceptable to have some period of time in which the index could be inconsistent with the data: in many full-text search related use cases (human queries) that's usually acceptable. Probably not acceptable if this is the query strategy used for a system or record.
I've attached a link to customer portal's casew where customer also wants this to be backported to the next EAP release. Could this backport be considered for the next release? Thanks.
Fedor, did you mean WFK release? EAP doesn't include this component.
(In reply to Fedor Gavrilov from comment #3) > I've attached a link to customer portal's casew where customer also wants > this to be backported to the next EAP release. > Could this backport be considered for the next release? > Thanks. Fedor the customer case you attached this to is a problem with WFK on EAP, but this bugzilla is for JDG. Could you please create a different bugzilla to track this for the next WFK? thanks in advance
(In reply to Sanne Grinovero from comment #5) > (In reply to Fedor Gavrilov from comment #3) > > I've attached a link to customer portal's casew where customer also wants > > this to be backported to the next EAP release. > > Could this backport be considered for the next release? > > Thanks. > > Fedor the customer case you attached this to is a problem with WFK on EAP, > but this bugzilla is for JDG. Could you please create a different bugzilla > to track this for the next WFK? > thanks in advance please use https://issues.jboss.org/browse/WFK2 JIRA instead of Bugzilla
Sanne, Marek, sure, thanks for the explanation! I will copy this to JIRA.
Hi all, I think we'll solve the problem for JDG 6.4 so there should be no need to add this limitation in the release notes for version 6.4 (if any we might want to make sure it gets removed).
Removing the requires_doc_text flag is all that is needed. This is now excluded from the release notes unless the flag is added again (possibly as a resolved issue in the future). :)