Optimize common-prefix across all terms in a field [LUCENE-5667]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
I tested different UUID sources in Lucene
http://blog.mikemccandless.com/2014/05/choosing-fast-unique-identifier-uuid.html
and I was surprised to see that Flake IDs were slower than UUID V1.
They use the same raw sources of info (timestamp, node id, sequence
counter) but Flake ID preserves total order by keeping the timestamp
"intact" in the leading 64 bits.
I think the reason might be because a Flake ID will typically have a
longish common prefix for all docs, and I think we might be able to
optimize this in block-tree by storing that common prefix outside of
the FST, or maybe just pre-computing the common prefix on init and
storing the "effective" start node for the FST.
---
Migrated from [LUCENE-5667](https://issues.apache.org/jira/browse/LUCENE-5667) by Michael McCandless (@mikemccand), updated May 09 2016
Contributor guide
Assessment
This issue has not been assessed yet.