You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Arkadi Colson <ar...@smartbit.be> on 2013/05/27 09:28:25 UTC
Indexing message module
Hi
We would like to index our messages system. We should be able to search
for messages for specific recipients due to performance issues on our
databases. But the message is of course the same for all receipients and
the message text should be saved only once! Is it possible to have some
kind of array field to include in the search query where all the
recipients are stored? Or should we for example use a simple text field
which is filled with the receipients like this:
<field>_434_3432_432_6546_75_8678_</field>
Anybody a good idea?
BR,
Arkadi
Re: Indexing message module
Posted by Arkadi Colson <ar...@smartbit.be>.
Yes indeed... Thx!
On 05/27/2013 09:33 AM, Gora Mohanty wrote:
> On 27 May 2013 12:58, Arkadi Colson <ar...@smartbit.be> wrote:
>> Hi
>>
>> We would like to index our messages system. We should be able to search for
>> messages for specific recipients due to performance issues on our databases.
>> But the message is of course the same for all receipients and the message
>> text should be saved only once! Is it possible to have some kind of array
>> field to include in the search query where all the recipients are stored? Or
>> should we for example use a simple text field which is filled with the
>> receipients like this: <field>_434_3432_432_6546_75_8678_</field>
> [...]
>
> Why couldn't you use a multi-valued string/int field for the
> recipient IDs?
>
> Regards,
> Gora
>
>
Re: Indexing message module
Posted by Upayavira <uv...@odoko.co.uk>.
Switching from single to multivalued shouldn't cause your index to break
(but your app might not like it).
Do you have a deduplication issue, or does each message have a unique
ID? You might be able to use the DedupUpdateProcessorFactory to prevent
updates to an existing message getting into the index.
Upayavira
On Tue, May 28, 2013, at 07:44 AM, Arkadi Colson wrote:
> Is it ok to just change the multivalue attribute to true and reindex the
> message module data? There are also other modules indexed on the same
> schema with multivalued = false. Will it become a problem?
>
> BR,
> Arkadi
>
> On 05/27/2013 09:33 AM, Gora Mohanty wrote:
> > On 27 May 2013 12:58, Arkadi Colson <ar...@smartbit.be> wrote:
> >> Hi
> >>
> >> We would like to index our messages system. We should be able to search for
> >> messages for specific recipients due to performance issues on our databases.
> >> But the message is of course the same for all receipients and the message
> >> text should be saved only once! Is it possible to have some kind of array
> >> field to include in the search query where all the recipients are stored? Or
> >> should we for example use a simple text field which is filled with the
> >> receipients like this: <field>_434_3432_432_6546_75_8678_</field>
> > [...]
> >
> > Why couldn't you use a multi-valued string/int field for the
> > recipient IDs?
> >
> > Regards,
> > Gora
> >
> >
>
Re: Indexing message module
Posted by Arkadi Colson <ar...@smartbit.be>.
Is it ok to just change the multivalue attribute to true and reindex the
message module data? There are also other modules indexed on the same
schema with multivalued = false. Will it become a problem?
BR,
Arkadi
On 05/27/2013 09:33 AM, Gora Mohanty wrote:
> On 27 May 2013 12:58, Arkadi Colson <ar...@smartbit.be> wrote:
>> Hi
>>
>> We would like to index our messages system. We should be able to search for
>> messages for specific recipients due to performance issues on our databases.
>> But the message is of course the same for all receipients and the message
>> text should be saved only once! Is it possible to have some kind of array
>> field to include in the search query where all the recipients are stored? Or
>> should we for example use a simple text field which is filled with the
>> receipients like this: <field>_434_3432_432_6546_75_8678_</field>
> [...]
>
> Why couldn't you use a multi-valued string/int field for the
> recipient IDs?
>
> Regards,
> Gora
>
>
Re: Indexing message module
Posted by Gora Mohanty <go...@mimirtech.com>.
On 27 May 2013 12:58, Arkadi Colson <ar...@smartbit.be> wrote:
> Hi
>
> We would like to index our messages system. We should be able to search for
> messages for specific recipients due to performance issues on our databases.
> But the message is of course the same for all receipients and the message
> text should be saved only once! Is it possible to have some kind of array
> field to include in the search query where all the recipients are stored? Or
> should we for example use a simple text field which is filled with the
> receipients like this: <field>_434_3432_432_6546_75_8678_</field>
[...]
Why couldn't you use a multi-valued string/int field for the
recipient IDs?
Regards,
Gora