On Tue, Oct 25, 2011 at 5:08 AM, prasenjit mukherjee <[email protected]> wrote: > Thats exactly I was trying to avoid :( > > I can afford to do that during indexing time, but it will be > time-consuming to do that at search time.
hu? I don't understand, if you provide the terms at indexing time lucene keeps track of the term frequency etc. why would you want to do this at search time? simon > > On Mon, Oct 24, 2011 at 1:05 PM, Simon Willnauer > <[email protected]> wrote: >> so you are saying you got (uniqueTerm, freq) tuples and you want to >> make lucene use this directly? I think the easiest way is to write a >> simple tokenFilter that emit the term X times where X is the term >> frequency. There is no easy way to pass these tuples to lucene >> directly. >> >> simon >> >> On Mon, Oct 24, 2011 at 3:28 AM, prasenjit mukherjee >> <[email protected]> wrote: >>> Can you tell me how I can feed the lucene index by using the term >>> frequency directly ? >>> >>> Actually I am getting the documents along with their term-frequency >>> and don't want to write any additional code to expand them. >>> >>> >>> On 10/23/11, ppp c <[email protected]> wrote: >>>> Of curse, it can be reused. >>>> But from my point of view, it's meaningless, since the analysis process has >>>> to be performed to collect such as prox, offset, or syno, payload and so >>>> on. >>>> >>>> On Sun, Oct 23, 2011 at 11:22 PM, prasenjit mukherjee >>>> <[email protected]>wrote: >>>> >>>>> I already have the term-frequency-count for all the terms in a >>>>> document. Is there a way I can re-use that info while indexing. I >>>>> would like to use solr for this. >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>> >>> -- >>> Sent from my mobile device >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
