Re: Multiple indexes for the same property key with different label constraints
Peter Schwarz <kkup...@...>
toggle quoted message Show quoted text
Thank you, your suggestion provided me with the clues to a solution. This is how I do things now:
1st tx: create any necessary property keys and build the index. Commit
2ndtx: Inspect the status of each key field. If any key is in the INSTALLED state, call updateIndex with the REGISTER_INDEX action. Commit. You only need to do this for one key per index.
Wait for the index to get to the REGISTERED state
Third tx: (or 2nd, if no key was in the INSTALLED state): Call updtaeIndex with the ENABLE_INDEX action. Commit.
Wait for the index to get to the ENABLED state.
What I find is that keys are ENABLED immediately if they have never been used in another index. But if they have been, the registration and enable steps must be explicit, and in separate management transactions. I don't believe a REINDEX is necessary, but to be honest I have not tested that as yet. This whole ting would be a lot simpler if the documentation was more complete and clear.
I'm still on 0.1.1, but I should probably upgrade sometime soon.
On Friday, August 11, 2017 at 3:49:27 PM UTC-7, Robert Dale wrote: