Orientdb: Manual index entries not persisted through a server restart
Create a manually created index:
CREATE INDEX md5 UNIQUE_HASH_INDEX;
then manually population the index via inserts with keys and rids.
Then querying the index
e.g. SELECT FROM INDEX:md5 WHERE key = '06700B2BD5AA941B9755B49C129BD66E'
returns the stored rid as expected, but if the server is restarted, nothing is returned.
However
SELECT COUNT(*) FROM INDEX:md5
will return the correct count for the previous inserts...
The type of index does not seem to matter.
fpertl
All 4 comments
Hi, what version do you use ?
laa
on 15 Mar 2016
I'm using 2.1.10 community.
fpertl
on 15 Mar 2016
@fpertl I have investigated the issue and found that automatic key type detection behaviour is unreliable, we have decided to deprecate untyped indexes. As a workaround pease specify an index key type while creating the index, like this:
CREATE INDEX md5 UNIQUE_HASH_INDEX STRING;
taburet
on 16 Mar 2016
Thanks for resolving this :)
fpertl
on 16 Mar 2016
Related issues
saeedtabrizi
·
5Comments
zifnab87
·
4Comments
saeedtabrizi
·
3Comments
f-hashemi
·
4Comments
lightjiao
·
3Comments
Most helpful comment
@fpertl I have investigated the issue and found that automatic key type detection behaviour is unreliable, we have decided to deprecate untyped indexes. As a workaround pease specify an index key type while creating the index, like this:
CREATE INDEX md5 UNIQUE_HASH_INDEX STRING;