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

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

Open

chaofengxia opened this issue Feb 7, 2017 · 0 comments

chaofengxia commented Feb 7, 2017

hi joshsh， ihave some problem on titan，ask for your help .
https://github.com/thinkaurelius/titan/issues/1371
there are many titan 1.0 instances running online now

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

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

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???

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