Payloads only make sense in terms of specific positions in the index, so I don't think there is a way to hack Lucene for it. You could, I suppose, just store the payload for the first instance of the term.
Also, what's the use case you are trying to solve here? Why store term frequency as a payload when Lucene already does it (and it probably does it more efficiently) -Grant On Feb 2, 2011, at 2:35 PM, Alex vB wrote: > > Hello everybody, > > I am currently using Lucene 3.0.2 with payloads. I store extra information > in the payloads about the term like frequencies and therefore I don't need > frequencies and term positions stored normally by Lucene. I would like to > set f.setOmitTermFreqAndPositions(true) but then I am not able to retrieve > payloads. Would it be hard to "hack" Lucene for my requests? Anymore I only > store one payload per term if that information makes it easier. > > Best regards > Alex > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Storing-payloads-without-term-position-and-frequency-tp2408094p2408094.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 > -------------------------- Grant Ingersoll http://www.lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
