JiriOndrusek opened a new issue, #9013:
URL: https://github.com/apache/camel-quarkus/issues/9013
### Describe the feature here
There are two problems in the Quarkus LangChain4j RAG augmentor bridge of
`camel-quarkus-support-langchain4j`:
1. **Ambiguous default augmentor silently disables RAG.** If more
`RetrievalAugmentor`s are configured as
`quarkus.camel.langchain4j.rag.augmentors.<name>`. The deafault search from
`@RegisterAiService` fails and no retrieval is registered at all. The build
should fail with actionable guidance instead, and
`quarkus.camel.langchain4j.rag.augmentors.<name>.default=true` should mark the
designated default
2. **No retrieval-side filter hook.** Segment metadata written at
ingestion time (for example a tenant key) cannot be enforced at query time
without replacing the whole augmentor. A `RagRetrievalFilterSupplier` SPI
should plug a per-request `Filter` into every produced augmentor
(`dynamicFilter`), turning such metadata into actual access control.s
--
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]
