Skip to content

Quarkus32 solr multicore - #2

Open
Oscar-Lilja-Simonsoft wants to merge 4 commits into
mainfrom
quarkus32-solr-multicore
Open

Quarkus32 solr multicore#2
Oscar-Lilja-Simonsoft wants to merge 4 commits into
mainfrom
quarkus32-solr-multicore

Conversation

@Oscar-Lilja-Simonsoft

Copy link
Copy Markdown

No description provided.

Register synthetic CDI beans for configured Solr client names so consumers can inject core-specific clients with @nAmed("repositem") or @nAmed("reposxml"). The beans are backed by SolrClientRegistry and only created when quarkus.solr.enabled=true.

Make the legacy single-core quarkus.solr.url and quarkus.solr.devservices.core config optional so multi-core-only configuration does not require default single-core settings. The default client and legacy single-core Dev Service still fail clearly if those values are used without being configured.

Also add a QuarkusUnitTest that verifies named SolrClient beans resolve for repositem and reposxml.
Allow Solr Dev Service to create multiple cores in a single Solr container from quarkus.solr.devservices.cores.<core>.config-path. Each core is copied into /var/solr/data/<core>, waited on through /solr/<core>/admin/ping, and exposed to runtime as quarkus.solr.clients.<core>.url.

Keep the legacy single-core Dev Service path intact for
quarkus.solr.devservices.core and quarkus.solr.url.

Add a QuarkusUnitTest that starts repositem and reposxml in the same Dev Service container and verifies both named SolrClient injections by pinging both cores. Document the single-core and multi-core configuration in README.

Also align Testcontainers with docker-java 3.7.1 because Quarkus 3.12 otherwise resolves an older Docker client that fails with current Docker Desktop.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant