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.

Sign up for GitHub

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

Jump to bottom

[question or feature request] CQL: what if additional indexes added after some INSERTs? #2019

Closed
pashinin opened this issue Aug 12, 2019 · 1 comment
Closed

[question or feature request] CQL: what if additional indexes added after some INSERTs? #2019

pashinin opened this issue Aug 12, 2019 · 1 comment
Assignees
@amitanandaiyer
Labels
area/docdb YugabyteDB core features community/request Issues created by external users

Comments

@pashinin
Copy link

I was following this example #919 (comment)

But I created secondary indexes after I inserted some data. And I was like: "ok, I'll wait, it will reindex it, fill it with data". Apparently that was a mistake - cqlsh always gave 0 rows.

Maybe a new index should work on existing data as well, not only on new INSERTs?

By the way thank you for this project!
@yugabyte-ci yugabyte-ci added the community/request Issues created by external users label Aug 12, 2019
@kmuthukk kmuthukk added the area/docdb YugabyteDB core features label Aug 12, 2019
@amitanandaiyer
Copy link
Contributor

@pashinin This feature is currently being worked on.

It is being tracked in #448

I'll mark this as a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amitanandaiyer amitanandaiyer

Labels
area/docdb YugabyteDB core features community/request Issues created by external users
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pashinin @kmuthukk @yugabyte-ci @amitanandaiyer