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

Unable to use multiple indexes on same table #49

Open
adkhare opened this issue Jan 12, 2015 · 3 comments
Open

Unable to use multiple indexes on same table #49

adkhare opened this issue Jan 12, 2015 · 3 comments

Comments

@adkhare
Copy link
Contributor

adkhare commented Jan 12, 2015

I am trying to create multiple indices on multiple columns and i am unable to do the same. As soon as i create a new index, it always references the first index.

@kadiyams
Copy link

There is a basic mis understanding on how you would use this feature adkhare.
If you want to use the regular indexes on CASSANDRA columns you can just use them. This would not stop you from defining multiple cassandra secondary indexes on multiple columns on a single table.

But if you are using STARGATE index, you can use it only on one column per table. You have to use all the columns in the table that you would query upon into this index.
You have to create your filter query which could span on conditions to evaluate multiple columns at a time.

So this is not an issue, but lack of proper understanding on the user part.

@adkhare
Copy link
Contributor Author

adkhare commented Feb 23, 2015

Well, I brought this point as I thought it might help to index additional columns as and when new columns are added to the schema.

This will help to move away from re-indexing whole data whenever new columns are to the table and need them to be indexed. This is an issue with the Datastax Enterprise Solr integration as well wherein, we need to drop the configuration and reload the configuration XML.

@trulite
Copy link
Member

trulite commented Mar 26, 2015

One way we could achieve what you want is to have additional per column indices for each new row added (this was available in the early implementations btw) and also use that while searching the single row index. It is possible to do this efficiently. Let me know if it works for you.

P.S. When you add a new column to a row index, because of the way row indexing works in Cassandra the whole data is played back to the index. So this may not be what you are looking for.

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

3 participants