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

is there any way to create the property key first, commit and then later do indexing? #1371

Open
chaofengxia opened this issue Feb 7, 2017 · 2 comments

Comments

@chaofengxia
Copy link

  1. there are many titan 1.0 instances running online now

  2. i create the property key ( like 'userId' )first, commit .

  3. then i create a CompositeIndex for 'userId' . i found the index status is INSTALLED

  4. when i want to change index status like
    mgmt.updateIndex(scheme_userId, SchemaAction.REGISTER_INDEX);
    i found the index status is always INSTALLED .

I found a similar problem in the Internet like "http://stackoverflow.com/questions/17125181/create-an-index-on-a-vertex-property-that-already-exists-in-titan-cassandra?rq=1"
so is is there any way to create the property key first, commit and then later do indexing???

@chaofengxia
Copy link
Author

@mbroecheler

@chaofengxia
Copy link
Author

@joshsh

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

1 participant