A new postings format would be tricky because you have new attributes you want to index.
The DocsAndPositionsEnum does have an attributes source, but this is not well explored, and there are known problems (they can't be easily merged in the composite reader case). So that's why I suggested packing your information into a payload ... Mike McCandless http://blog.mikemccandless.com On Sun, Nov 18, 2012 at 8:33 PM, wgggfiy <wuqiu....@qq.com> wrote: > thx, mike. > about the 3th question, "encode them all into the payload" is better than > "a new postings format with the codec" ?? > I mean replace the orginal posting item (position, startOffset, endOffset, > payload) with my own inverted item such as > class TestPostingItem > { > int termId; > long startOffset; > long endOffset; > float score; > int segId; > long timeStamp; > } > ? > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/what-is-the-offsets-and-payload-in-DocsAndPositionsEnum-for-tp4020933p4020968.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
