nmslib: "Storing non-optimized index is not supported yet" for the bit_hamming space in HNSW
Hi! I ran into an unexpected issue when trying out the bit_hamming
space (and INT
distance type): a Storing non-optimized index is not supported yet
exception when trying to save the index.
During creation skip_optimized_index
is set to 0
The same code works for cosinesimil
space and FLOAT
distance type
Is there an underlying reason why this isn’t expected to work for the hamming space, or is it just not implemented yet/a bug?
A potentially relevant note: when creating index, I get the following message:
hnsw.cc:192 (CreateIndex) [INFO] No appropriate custom distance function for Hamming (bit-storage) space
At the same time, NN search seems to work reasonably. What exactly does that message mean?
Thanks!
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 17 (10 by maintainers)
Commits related to this issue
- Storing non-optimized indices #119 — committed to nmslib/nmslib by searchivarius 7 years ago
- A fix for the broken Build on Windows #119 — committed to nmslib/nmslib by searchivarius 7 years ago
@lsorber I have started working on this, hopefully it won’t take longer than a couple of weeks.