-
-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storage-related auto-configurations must be ordered after the auto-configurations they rely upon #51
Comments
Hey @snicoll , thanks for your valuable input. I'm a bit lost of what to do with the Lettuce and Redis related autoconfiguration. I see the |
As you've noticed yourself, we don't export those. If your code is relying on that, users will have to create the bean. |
Jedis and Lettuce drivers use different client implementations ( If we consider an arrangement without Spring Data Redis, then client object beans such as |
This is indeed how it is done for others like the MongoDB driver. Are you guys planning to do it also for the Lettuce/Jedis? |
The team is not planning to do this at this time. |
Part of the rationale is that configuring the right client correctly is tied to a lot of complexity (Pooling vs. non pooling, Standalone, Sentinel, Cluster, Master/Replica operation modes) and that complexity is already encapsulated in Spring Data Redis. |
I completely understand - supporting all the different data stores in JobRunr, also took me quite some time to understand how each client library uses pooling/ non-pooling/ ... . |
I'll then close this issue as the requested change is done for the other providers (ElasticSearch, MongoDB and Sql DataSource) |
Describe the bug
Various auto-configurations are reacting to the fact another bit of infrastructure is present. For instance, the elasticsearch one checks if a
HighLevelClient
is defined. Yet, the auto-configuration does not declare anywhere it should be processed once the auto-configuration for elasticsearch has been processed.See
@AutoConfigureBefore
,@AutoConfigureAfter
for more details.Environment
n/a
The text was updated successfully, but these errors were encountered: