spring-data-cassandra

问题 Is @UDT (http://docs.datastax.com/en/developer/java-driver/2.1/java-driver/reference/mappingUdts.html) supported by Spring-data-Cassandra 1.3.2.RELEASE? If not, how can I add workaround for this Thanks 回答1: See the details here: https://jira.spring.io/browse/DATACASS-172 I faced with the same issue and it sounds like it does not( debug process shows me that spring data cassandra check for @Table, @Persistent or @PrimaryKeyClass Annotation only and raise exception in other case > Invocation of

问题 I try to use spring data cassandra 1.5.0 but when i update my pom by adding <dependency> <groupId>org.springframework.data</groupId> <artifactId>spring-data-cassandra</artifactId> <version>1.5.0.M1</version> </dependency> <repositories> <repository> <id>spring-milestones</id> <name>Spring Milestones</name> <url>https://repo.spring.io/libs-milestone</url> <snapshots> <enabled>false</enabled> </snapshots> </repository> But i got error Missing artifact org.springframework.data:spring-data

问题 This question already has answers here : User Defined Type with spring-data-cassandra (2 answers) Closed 2 years ago . How does springdatacassandra support user defined data types provided by Cassandra in POJO? I am looking for annotation for UDT. 回答1: Spring data cassandra latest version (1.2.0.BUILD-SNAPSHOT) depends on datastax driver 2.0.4 , where as UDT is supported since datastax driver 2.1.x. You can try overriding the datastax driver to 2.1.x to consume the latest features provided by

问题 based on the tutorial spring-data-cassandra-tutorial I'm experimenting with the UserDefinedType annotation. I upgraded the project to use spring-data-cassandra:1.5.0.BUILD-SNAPSHOT, added the attribute price to the book, implemented the corresponding UserDefinedType and added setInitialEntitySet and setUserTypeResolver to the configuration. When I then execute the BookRepositoryIntegrationTest against a cassandra 3.9, I get the following error: org.springframework.data.mapping.model

问题 I am trying to integrate cassandra with Spring boot using spring-data-cassandra. Application.java package hello; import org.springframework.boot.autoconfigure.EnableAutoConfiguration; import org.springframework.boot.SpringApplication; import org.springframework.context.annotation.ComponentScan; @ComponentScan @EnableAutoConfiguration public class Application { public static void main(String[] args) { SpringApplication.run(Application.class, args); } } CassandraConfiguration.java package conf;

问题 I'm using Spring Data Cassandra 1.3.4.RELEASE to persist instances of a class that I have. The class is written in Groovy, but I don't think that really matters. I have implemented a CrudRepository, and I'm injecting an instance of CassandraOperations into the repo implementation class. I can insert, delete, and do most of the other operations successfully. However, there's a scenario I'm running into which breaks my test case. My entity class looks something like this: @Table("foo") class

问题 In my application logs I've seen that, by default, after running create/alter table statements, cassandra driver seems to do processing to bring schema into agreement for up to 10 seconds. Can I (and should I) set a consistency level for example 'quorum' while executing DDL statements like 'Create Table .. IF NOT EXISTS' to make sure my table gets created and propagated to all nodes? 回答1: Schema changes (data definition) in Cassandra since 1.1+ are done via gossip. Since it uses Gossip, it is

问题 I'm working on a project where we have an entity we want to persist with a field of type LocalDateTime, we know cassandra does not have native support for this type conversion, we've created our own custom converter using Spring's support for converters, however it seems Spring-Data-Cassandra is unable to either recognise them or understand that the field should be mapped to a column. This is how we've registered our converters with Spring's conversion service. <bean id="conversionService"

问题 Picture the following senario: A Spark application (Java implementation) is using Cassandra database to load, convert to RDD and process the data. Also the application is steaming new data from the database which are also processed by a custom receiver. The output of the streaming process is stored in the database. The implementation is using Spring Data Cassandra from the integration with the database. CassandraConfig: @Configuration @ComponentScan(basePackages = {"org.foo"}) @PropertySource

问题 It seems underlying cassandra version has been upgraded to 3.0.5. Wanted to find if our current spring-data-casssandra version is compatible with new cassandra 3.0.5 version? Any takes to point to compatibility matrix for the version check (spring-data-cassandra version to cassandra version) 回答1: Looking into dependencies for it, it looks like it won't be compatible - it's based on Cassandra 2.1 that won't work with 3.x. You need to upgrade to latest 1.5.x to be compatible with Cassandra 3.x