Camel-Qdrant: collect processors to be used as ref beans

[smongiar]

Description

Need to collect processors and beans for more comfortable usage in route DSL definitions. Some changes involve JBang as well to make it work with camel CLI

Target

• [ X] I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

• [ X] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[davsclaus]

There are uncommitted changes
HEAD detached at pull/21705/merge
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/qdrant.json
modified: dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/QdrantEndpointBuilderFactory.java

[apupier]

I do not understand the link between the commit message and all the modifications.

the different modifications that would worth different commits/PR) that I understood are:

• In the component, a parameter has been added for max results
• some changes in jbang to look to src/main/resources for application.properties
• specific Qdrant Processors

[apupier]

What about using RAGCreateCollection.valueOf()?
It would allow to work with new unit of distance if added later in the library

[smongiar]

that's a good point. I wrongly assumed it's immutable. Let me try this. Thank you.

[davsclaus]

There are uncommitted changes
HEAD detached at pull/21705/merge
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/qdrant.json
modified: dsl/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/QdrantEndpointBuilderFactory.java

[davsclaus]

you have some commits for camel-jbang, this should not be included here when its about qdrant

[smongiar]

I do not understand the link between the commit message and all the modifications.

the different modifications that would worth different commits/PR) that I understood are:

• In the component, a parameter has been added for max results

Sure not mentioned in commit message, but useful to limit results during a vectorial search. I implemented an example that make use of it

• some changes in jbang to look to src/main/resources for application.properties

Exactly. It was not mentioned in commit message, but it's in the PR description. Basically I tried to export a Qdrant example app with SB and Quarkus. Something like:

camel export --runtime=quarkus --gav=org.apache.camel.example:qdrant-rag-quarkus:1.0.0 --directory=./export-quarkus src/main/resources/camel/qdrant-rag.camel.yaml

I faced some issues, so I need to enforce application.properties check to avoid maven fallback

• specific Qdrant Processors

That's mentioned in commit message

[davsclaus]

please separate this and create a new JIRA about camel-jbang