Hi,
I think this is more a problem of the data model.
You should not link a message to a group by the group name. Instead use
a GroupID (which is unique) to refer to the group. The GroupID is a
'non-analyzed' and 'not-stored' field in your lucene document.
Then, when you want to search for all messages assigned to groups the
user is member of, first search for the groups where the user is member
to get the id, and next search all messages with that ids.
So there should no need to reindex.
===
Ralph
On 30.08.2016 08:38, Kumaran Ramasubramanian wrote:
Hi All,
Am building a sample application, where a group of members can interact as
a chat room. i am trying to enable search for message level search...
If i denormalize group_name & group_members in every lucene document, then
below cases will reindex more number of lucene documents...
1. editing group name
2. adding / deleting a member
So am trying to index group_name, group_members(member ids as csv) as
parent and every text message & message_id as child.
By using parent & child, i am trying to solve 1 * m cases...
If there are 1 lakh messages under one parent, how to delete a member id or
edit a group name without reindexing of its children??
is it possible to avoid reindexing? Which lucene class is best fit for
this?
Related Article:
http://blog.mikemccandless.com/2012/01/searching-relational-content-with.html
--
Kumaran R
--
*Imixs*...extends the way people work together
We are an open source company, read more at: www.imixs.org
<http://www.imixs.org>
------------------------------------------------------------------------
Imixs Software Solutions GmbH
Agnes-Pockels-Bogen 1, 80992 München
*Web:* www.imixs.com <http://www.imixs.com>
*Office:* +49 (0)89-452136 16 *Mobil:* +49-177-4128245
Registergericht: Amtsgericht Muenchen, HRB 136045
Geschaeftsfuehrer: Gaby Heinle u. Ralph Soika
