JiriOndrusek opened a new pull request, #9229: URL: https://github.com/apache/camel-quarkus/pull/9229
Fixes #9225 The RAG bridge decides whether to produce the default `RetrievalAugmentor` through a bean census over `BeanDiscoveryFinishedBuildItem`, which lists class-based beans only. A store or model registered by a Quarkus LangChain4j extension (e.g. pgvector) is a synthetic bean, so the census never saw it and no augmentor was produced. This change gives the census a second input; augmentor registration, explicit configuration and runtime resolution are unchanged: - new core `AnnouncedSyntheticBeanBuildItem`: an extension announces a bean it registers synthetically, with the name qualifier of a named bean - `support-langchain4j-ql4j`, active only when Quarkus LangChain4j is present, produces it from `EmbeddingStoreBuildItem`, `SelectedEmbeddingModelCandidateBuildItem` and `InProcessEmbeddingBuildItem`; a model of a named configuration is announced by name - `BeanCensus` counts the announced default beans next to the discovered ones - a store item carries no name, so the default augmentor's `@Default` store and model are verified at startup, failing fast with a hint to `quarkus.camel.langchain4j.rag.augmentors.<name>.embedding-store-name` - migration guide: applications with a Quarkus LangChain4j store now get retrieval without a configuration change, with the opt-out - deployment test with a synthetic store; the rag-bridge IT and the `langchain4j-ingest-rag` example without its explicit augmentor pass locally _Claude Code on behalf of @JiriOndrusek_ 🤖 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]
