Spring boot + cassandra 3.x - java

Is the way to use cassandra 3.x with Spring boot?
I was trying to use new version of spring-data-cassandra 1.5.0 while cassandra driver 3.0 is supported, but Spring boot change the dependency to 2.1.9.
I also tried to use spring-data-cassandra 1.5.0 without Spring boot, but there is not a reference documentation i i have got some errors.
I've spent whole day for trying to make it works, but there are no effects.
Maybe someone have some samples or information that can help me to run cassandra cluster on Spring boot :)

Related

Camunda BPM - Spring compatibility

I'm trying to migrate application with Camunda BPM 7.14.0 and Spring Boot 2.7.2 dependencies to latest Spring version(3.0.1/3.0.2) and at least Camunda 7.16.
Unfortunately I'm receiving some errors during migration and would like to ask what is the compatible version of Camunda which I can use with Spring 3.0.1?
From the compatibility matrix I can read that Camunda 7.18 is compatible only with version 2.7.x
https://docs.camunda.org/manual/7.18/user-guide/spring-boot-integration/version-compatibility/
Can someone confirm it?
Yes, I can confirm that 7.18 is compatible with 2.7.x
Spring Boot 3.0 requires some change in the autoconfiguration declaration and as far as I understood, the community edition will not support it until 7.20.0.
But the same thread mentions a manual fix that I haven't tried so far.

Spring boot 2.6 incompatible with Cloud Sleuth 3.1.4

I'm using Spring Boot 2.6 and Spring Cloud Sleuth 3.1.4
Whenever I run the app I'm getting this:
Your project setup is incompatible with our requirements due to following reasons:
- Spring Boot [2.6.0] is not compatible with this Spring Cloud release train
Action:
Consider applying the following actions:
- Change Spring Boot version to one of the following versions [2.4.x, 2.5.x] .
You can find the latest Spring Boot versions here [https://spring.io/projects/spring-boot#learn].
If you want to learn more about the Spring Cloud Release train compatibility, you can visit this page [https://spring.io/projects/spring-cloud#overview] and check the [Release Trains] section.
If you want to disable this check, just set the property [spring.cloud.compatibility-verifier.enabled=false]
According to release train 2021.0.x should be compatible with Spring boot 2.6 and sleuth 3.1.4 is a part of it.
Am I missing something here?
In the compatibility matrix, as listed here: https://spring.io/projects/spring-cloud, under 'Release Train' section, this should work.
But, I would recommend you to lower the spring cloud version to 3.1.3 to begin with. If you still get the same error, try with version 3.1.0. as in my project I had no problems using spring-cloud-starter-sleuth 3.1.0 with Spring Boot 2.6.x.
Best regards,
Filip
EDIT: With spring sleuth 3.1.4 you should use spring-cloud-dependencies of version 2021.0.4. Maybe here you got the problem.

Spring boot 2.2.4 release is not compatible with azure spring data cosmos 3.x.x

I'm working on springboot with cosmos api,So if i use #Query that is provided by azure-spring-data-cosmos library(3.x.x) with Springboot 2.5.0 able to get the results from cosmos database. But if i use the same azure-spring-data-cosmos library(3.x.x) with springboot 2.2.4 getting below exception
Field userRepository in com.example.service.UserService required a bean of type 'com.example.repository.UserRepository' that could not be found.The injection point has the following annotations:
- #org.springframework.beans.factory.annotation.Autowired(required=true)
Action:Consider defining a bean of type 'com.example.repository.UserRepository' in your configuration.
I would highly recommend using the latest azure-spring-data-cosmos SDK version 3.19.0 - https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-spring-data-cosmos/CHANGELOG.md#3190-2022-03-10
Since spring boot releases one major version every 6 months, azure spring team supports last 2 versions of Spring Boot. We currently support spring boot 2.5.x and 2.6.x. You should be able to use any one of these versions of spring-boot with latest version of azure-spring-data-cosmos SDK.
The changelog points to the compatible version of spring boot which can be used with azure-spring-data-cosmos SDK.
Also, spring-boot 2.2.4 is more than 2 years old at this point of time. We don't support it anymore.
Not sure which version of cosmos you are using but cosmos change log clearly mentions that 3.5.0 has spring boot support 2.4.3 & above.
Please check if your cosmos version is 3.5.0 which might be causing this issue.
Reference link :
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-spring-data-cosmos/CHANGELOG.md#350-2021-03-11

Migrate Elasticsearch 2.4 to higher version along with Spring Framework 4.2.5 to Springboot 2.x. What will be best approach?

I want to upgrade my elasticsearch version & spring framework to Springboot 2.x version. Which elasticsearch & sprinbboot version should be used considering the spring-data-elasticsearch. I'm new to migrating application, would like to know the things that needs to taken into consideration.
I haven't done any Elasticsearch migration before. But 2.4 is the very old version, I guess you need to rewrite the ingestion logic in the migration.
For your reference, we are using the following tech stack in the project:
Spring boot: 2.3.x
AWS Elasticsearch Service: version 7.1
spring-data-elasticsearch 3.2.10

Spring 4 with Elasticsearch 5

Is it possible to use elasticsearch server version 5 in combination with spring 4 (spring-data-elasticsearch)?
So far if I use spring-data-elasticsearch 2.x, I can load the app, but get error failed to get local cluster state.
If I include 3.x then I cannot start the app with error Initialization of bean failed; nested exception is java.lang.AbstractMethodError...
I suceeded to connect using spring boot 2.x, but this one uses all spring libraries >5 which is currently not an option for me.
For Elasticsearch 5.x you need to use Spring Data 3.x (Kay). Spring Boot 2.x uses that version, so that should work as you described it.
Taking a look at spring-data-parent there is an explicit dependency on Spring 5.x, so I don't think using Spring 4 will work; at least not without a lot of dependency wrangling. IMO the way forward will be to get to Spring 5 and then use Spring Data 3.

Categories

Resources