[PR] Fixes #9013. Harden the RAG augmentor bridge [camel-quarkus]

["JiriOndrusek (via GitHub)" <gi...@apache.org>]

JiriOndrusek opened a new pull request, #9014:
URL: https://github.com/apache/camel-quarkus/pull/9014

     Fixes #9013. Harden the RAG augmentor bridge: designated default and retrieval filter hook
       
    Two augmentors with none marked default used to silently disable RAG for every AI service (ambiguous unqualified CDI lookup); the build now fails with the fix in the message, and quarkus.camel.langchain4j.rag.augmentors.<name>.default=true marks the designated default (the @RagAugmentorName qualifier suppresses the implicit Default on the others, keeping them selectable by name).
       
     RagRetrievalFilterSupplier plugs a per-request retrieval Filter into every produced augmentor (dynamicFilter), turning segment metadata like a tenant key into an actual access control. Being an access control, its ways of failing open are closed: more than one implementation, or a @Dependent one, fail the build, and a supplier no produced augmentor will ever consult is reported as a warning. The one bean serves every augmentor, so it is told which augmentor retrieves and over which embedding store, and it takes the Query, so implementations can key on chatMemoryId instead of thread-local state. All three inputs are covered by the tenant isolation tests in the rag-bridge integration module.
   
   
   <!-- Uncomment and fill this section if your PR is not trivial
   [ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
   [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
   [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
   [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
   [ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
   [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
   -->


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Fixes #9013. Harden the RAG augmentor bridge [camel-quarkus]

["JiriOndrusek (via GitHub)" <gi...@apache.org>]

JiriOndrusek merged PR #9014:
URL: https://github.com/apache/camel-quarkus/pull/9014


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org