I saw your comments on JIRA. You mentioned about rework and I'm wondering if the currently available patch is production ready (functionally complete)? Will the code after rework work with the index build with the current version?
I'm quite new to SOLR/Lucene but I hope I could write custom SearchComponent to SOLR based on yours Tag Index and this way get exactly what I need. And one more question: I don't really get now how could I setup field to be indexed by TagIndexWriter instead of TagWriter. I know it's somehow handled by ParallelIndexWriter but how can I setup it? > Yes Tag Index will work. I have not had time to complete it however > if you are interested in working on it please feel free to contact me. > On Fri, Sep 12, 2008 at 3:48 PM, Mark Miller <[EMAIL PROTECTED]> wrote: >> You might check out the tagindex issue in jira as well. Havn't looked at it >> myself, but I believe its supposed to be an option for this. >> >> Gerardo Segura wrote: >>> >>> I think the important question is: in general how to cope with frequently >>> changing fields. >>> >>> >>> Karl Wettin wrote: >>>> >>>> Hi Wojciech, >>>> >>>> can you please give us a bit more specific information about the meta >>>> data fields that will change? I would recommend you looking at creating >>>> filters from your primary persistency for query clauses such as >>>> unread/read, >>>> mailbox folders, et c. >>>> >>>> karl >>>> >>>> 12 sep 2008 kl. 13.57 skrev Wojciech Strza?ka: >>>> >>>>> Hi. >>>>> >>>>> I'm new to Lucene and I would like to get a few answers (they can >>>>> be lame) >>>>> >>>>> I want to index large amount of emails using Lucene (maybe SOLR), not >>>>> only >>>>> the contents but also some metadata like state or flags. The >>>>> problem is that the metadata will change during mail lifecycle, >>>>> although much smaller updating this information will require >>>>> reindex the whole mail content which I see performance bottleneck. >>>>> >>>>> I have the data in DB also so my first question is: >>>>> >>>>> - are there any best practices to implement my needs (querying both >>>>> lucene & DB and then merging in memory?, close one eye and re-index >>>>> the whole content on every metadata change? others?) >>>>> >>>>> - is at all Lucene good solution for my problem? >>>>> >>>>> - are there any plans to implement field updates in more efficient way >>>>> then >>>>> delete/insert the whole document? if yes what's the time horizon? >>>>> >>>>> >>>>> Best regards >>>>> Wojtek >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Pozdrowienia, Wojciech Strzalka --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
