Open chaofengxia opened 7 years ago
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???
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???