On Wed, Jun 10, 2009 at 3:07 PM, Uwe Schindler <u...@thetaphi.de> wrote: > My problem with all this is how to optimize after which shift value to > switch between terms and payloads.
Just make it a configurable number of bits at the end that are "stored" instead of indexed. People will want to select different tradeoffs anyway. What about using the position (as opposed to a payload) to encode the last bits? Should be faster, no? > And this information about the trie > structure and where payloads are should be stored in FieldInfos. As is the case today, the info is encoded in the class you use (and it's settings)... no need to add it to the index structure. In any case, it's a completely different issue and shouldn't be tied to TrieRange improvements. -Yonik http://www.lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
