You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have also set the @Id annotation on my entity class MerchantsEntity.
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
However, I am still getting an exception when trying to integrate it with my spring boot application and running a test method which calls the repository method.
The exception is:
com.aerospike.client.AerospikeException: Error 26: Id has not been provided
Furthermore, when I checked the maven repository for latest version(4.8.0) of spring-data-aerospike at
does not appear to have the jar files updated since May 29, 2024. When will be the release with this change happening? Or did I go wrong somewhere?
The text was updated successfully, but these errors were encountered:
pauls-baby
changed the title
Fixed issue not available in maven repository
Fixed issue "Id has not been provided" is not available in maven repository
Jul 30, 2024
Apologies for the delayed reply.
As you correctly noticed, the changes from the mentioned PR have not been released yet.
The current plan is to release new version 5.0.0 of Spring Data Aerospike (with quite a few changes) within 1-3 months.
I could find that an issue
appears to be fixed in the PR #752.
I am already passing "#p0" for key in @Cacheable annotation like:
I have also set the
@Id
annotation on my entity class MerchantsEntity.However, I am still getting an exception when trying to integrate it with my spring boot application and running a test method which calls the repository method.
The exception is:
Furthermore, when I checked the maven repository for latest version(4.8.0) of spring-data-aerospike at
does not appear to have the jar files updated since May 29, 2024. When will be the release with this change happening? Or did I go wrong somewhere?
The text was updated successfully, but these errors were encountered: