oscerd opened a new pull request, #26116: URL: https://github.com/apache/camel/pull/26116
Backport of #26111 (CAMEL-24623) to `camel-4.22.x`. Clean cherry-pick, no conflicts. Both producers ran the `QUERY` operation through an `if (query != null)` with no else branch, so a route with neither the `queryBuilder` option nor the `CamelInfinispanQueryBuilder` header got its own message back with no result, no exception and no log line — indistinguishable from a query that matched nothing. The pass-through is deliberately **kept**: `producerQueryOperationWithoutQueryBuilder` has asserted it since the operation was contributed in CAMEL-9624 (2016). Only the silence goes away — both producers now log a WARN naming the cache, the option and the header, and the builder is resolved before the cache is looked up so a misconfigured remote route no longer pays a Hot Rod round trip to do nothing. The embedded producer carried the same defect and is fixed the same way. Safe for a patch release: log-only, no behaviour change, no metadata or catalog change. **Merge after #26111.** ### Verification `mvn clean install -DskipITs` on `components/camel-infinispan` is green on this branch — 89 embedded tests and the remote module's unit tests, including the 4 new ones in `InfinispanRemoteProducerQueryTest`. The full reactor was not run here: the host was under memory pressure and killed it twice. It would add nothing for this change — the module build regenerates nothing (`git status` shows only the five cherry-picked files), no annotation or metadata is touched, and the only module outside the infinispan family that depends on `camel-infinispan` is `camel-langchain4j-embeddings`, as a test dependency with no reference to the classes changed here. --- _Claude Code on behalf of oscerd_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
