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 i
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
Yes indeed... Thx!
On 05/27/2013 09:33 AM, Gora Mohanty wrote:
On 27 May 2013 12:58, Arkadi Colson 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 th
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
kin
On 27 May 2013 12:58, Arkadi Colson 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 b
