> If you understood that, you'd be able to look > at the actual token value if you were interested in what shift was > used. So it's redundant, has a runtime cost, it's not currently used > anywhere, and it's not useful to fields other than Trie. Perhaps it > shouldn't exist (yet)?
You are right, you could also decode the shift value from the first char of the token... I think, I will remove the ShiftAttribute and only set the TermType to highest, lower precisions. By this, one could easily add a payload to the real numeric value using a TokenFilter. Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org