Hi Wojciech,
The code isn't ready, it is a major project and I am trying to also
complete the realtime indexing patches and look for a job. I believe
that the tag indexing stuff is of interest to many people so if there
is someone who can pay to get it completed feel free to contact me as
I am av
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
My strong reqirement is that search server runs on different machine then
client - so I think I have two options: SOLR or Lucene via RMI
(RemoteSearchable)
So by now it looks like I have several options:
1. TagIndex - like described here
http://issues.apache.org/jira/browse/
If you search the archive, this very topic has been
discussed many times. You'e find a wealth of
discussion and more than a few options
outlined there
Best
Erick
2008/9/12 Wojciech Strzałka <[EMAIL PROTECTED]>
>
> The most changing fields will be I think:
> Status (read/unread): in fact I'm af
The most changing fields will be I think:
Status (read/unread): in fact I'm affraid of this at most - any
mail incoming to the system will need to be indexed at
least twice
Flags: 0..n values from enum
Tags:0..n values from enum
Of course all the other field
Thanks for reply.
Generally good idea and I like it - almost :) We just need to tweak
it a little more.
What if I have to search for both fields at the same time?
Is there any way to do something similiar to SQL JOIN on the two
documents / indexes? (I don't think so)
I think ca
