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

Jaeger-cassandra-schema compatibility with cassandra #189

Closed
princeop opened this issue May 31, 2017 · 8 comments
Closed

Jaeger-cassandra-schema compatibility with cassandra #189

princeop opened this issue May 31, 2017 · 8 comments

Comments

@princeop
Copy link

Using jaeger-cassandra-schema docker with cassandra 3.0.12 causes this exception

<stdin>:156:ConfigurationException: Unable to find custom indexer class 'org.apache.cassandra.index.sasi.SASIIndex' on this line:

CREATE CUSTOM INDEX ON ${keyspace}.dependencies (ts_index) USING 'org.apache.cassandra.index.sasi.SASIIndex' WITH OPTIONS = {'mode': 'SPARSE'};

This in turn causes to dependency functionality not working on jaeger-query docker:

"Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING"

SASIIndex in available in cassandra since version 3.4+

@black-adder
Copy link
Contributor

Thanks for catching this, we removed SASI indexes but forgot to do it for the dependencies table, we'll get rid of it.

@omeid
Copy link

omeid commented Jun 23, 2017

Any update on this?

@black-adder
Copy link
Contributor

It's a breaking change as of this moment so we're gonna cut a release and then fix it for the upcoming release

@jpkrohling
Copy link
Contributor

This should have been fixed by #278 .

@yurishkuro
Copy link
Member

@jpkrohling it won't be - the request in this issue is to support older versions of Cassandra, specifically pre-3.4 when SASI indices were not available. The Dependencies table is the only one still using a SASI index.

@rajatparida86
Copy link

Any updates on this fix?

@yurishkuro
Copy link
Member

I expect it to happen within a month.

@jpkrohling
Copy link
Contributor

Took a bit more than a month, but I think this is now fixed :-)

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

No branches or pull requests

6 participants