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

Add support SSTable Attached Secondary Index (SASI) creation [DATACASS-306] #420

Closed
spring-projects-issues opened this issue Jun 22, 2016 · 6 comments
Assignees
Labels
type: task
Milestone

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Jun 22, 2016

Yaniv Marom Nachumi opened DATACASS-306 and commented

Cassandra version higher then 3.4 is required in order to use custom index org.apache.cassandra.index.sasi.SASIIndex


Affects: 1.5 M1 (Ingalls)

Issue Links:

  • DATACASS-213 Add index creation to table creation
    ("depends on")
  • DATACASS-377 Take in account the @Indexed attributes when creating a table
    ("is duplicated by")
  • DATACASS-271 Upgrade to Cassandra 3.0.0

Referenced from: pull request #111

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jun 22, 2016

Mark Paluch commented

Spring Data Cassandra 1.5 will be based on the Casandra 3.0 driver (see DATACASS-271). Please help me understand the goal of this ticket

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jun 22, 2016

Yaniv Marom Nachumi commented

In Cassandra 3.4 and later, a new implementation of secondary indexes, SSTable Attached Secondary Indexes (SASI), have greatly improved the performance of secondary indexes and should be used, if possible. https://docs.datastax.com/en/cql/3.3/cql/cql_using/useSASIIndex.html

Including SSTable as this stage might prevent users from implementing an alternative solution (e.g - https://issues.apache.org/jira/browse/CASSANDRA-2915 Lucene based Secondary Indexes).

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jun 22, 2016

Mark Paluch commented

This ticket depends on DATACASS-213 which creates the required infrastructure to create indexes. As of today you can use LIKE with queries (either using CqlTemplate, CassandraTemplate or @Query with repositories) since all queries are string-based

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jun 23, 2016

Yaniv Marom Nachumi commented

Mark thanks for your comments. There is one limitation with your approach:
String data cassandra is tested using cassandra-all 3.0.0, therefor it is unwise to create DAO based unit tests while using different cassandra-all version.

For example: We have several unit test based on AbstractEmbeddedCassandraIntegrationTest; when running using spring-data-cassandra 1.5.0-SNAPSHOT & cassandra-all 3.0.0, all test pass. But when we upgrade to cassandra-all 3.7 the following exception occur:

com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: localhost/127.0.0.1:39667 (com.datastax.driver.core.exceptions.OperationTimedOutException: [localhost/127.0.0.1] Operation timed out))

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jun 26, 2016

Yaniv Marom Nachumi commented

Testing against cassandra-all version 3.5 succeeded while testing using 3.6 fails.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Jul 24, 2017

John Blum commented

Committed to master for the Spring Data Cassandra Kay RC1 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task
Projects
None yet
Development

No branches or pull requests

2 participants