Skip to content
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

Upgrade to Cassandra 3.0.0 [DATACASS-271] #444

spring-projects-issues opened this issue Apr 12, 2016 · 1 comment

Upgrade to Cassandra 3.0.0 [DATACASS-271] #444

spring-projects-issues opened this issue Apr 12, 2016 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented Apr 12, 2016

Mark Paluch opened DATACASS-271 and commented

Upgrade Cassandra driver to 3.0

  • Reduce driver dependency to cassandra-driver-core
  • Add support for new data types: short and byte, see
  • Fix timestamp/date mixup, see getTimestamp returns Date and getDate returns Cassandra's com.datastax.driver.core.LocalDate
  • Migrate deserialization to CodecRegistry using the default instance
  • Specify QueryOptions with a zero schema refresh to skip background schema refresh and the required synchronization
  • Support NettyOptions, mainly because the newer drivers add a sleep time on shutdown
  • Simplify ColumnReader
  • Use bigint as default CQL type for long properties (instead of counter) as counter columns are not supported by Spring Data Cassandra
  • Remove log4j dependencies as they are not needed anymore

Issue Links:

  • DATACASS-274 Provide support to Cassandra java driver 3.0 and server 3.X
    ("is duplicated by")

  • DATACASS-128 Improve mapping specifications between Cassandra & Java

  • DATACASS-306 Add support SSTable Attached Secondary Index (SASI) creation

  • DATACASS-169 Deal with breaking changes introduced in cassandra-driver-dse 2.1.0 & later

Referenced from: pull request #56

Copy link

@spring-projects-issues spring-projects-issues commented May 13, 2016

John Blum commented

Code review for PR #56 complete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants