Just saw this:
https://issues.apache.org/jira/browse/SOLR-4134
so I don't think you can do what you want currently without the patch.
Erick
On Fri, Dec 21, 2012 at 7:58 AM, Erick Erickson wrote:
> Hmmm, looks like it might be a bug, but I don't know that code at all.
> Wonder what Yonik would
Hmmm, looks like it might be a bug, but I don't know that code at all.
Wonder what Yonik would have to say
On Wed, Dec 19, 2012 at 9:52 AM, Dikchant Sahi wrote:
> Hi Erick,
>
> The name field is stored. I experience problem only when I update
> multiValued field with multiple values like,
>
Hi Erick,
The name field is stored. I experience problem only when I update
multiValued field with multiple values like,
* solr*
* lucene*
*
*
It works perfect, when I set single value for multiValued field like,
*solr*
Thanks,
Dikchant
On Wed, Dec 19, 2012 at 6:25 PM, Erick Erickson wrote:
> F
FIrst question: Is the "name" field stored (stored="true")? If it isn't,
that would explain your problems with that field. _all_ relevant fields
(i.e. everything not a destination of a copyField) need to be stored for
atomic updates to work.
Your second problem I'm not sure about. I remember some
Hi,
Does Solr 4.0 allows to update the values of multi-valued field? Say I have
list of values for skills field like java, j2ee and i want to change it
to solr, lucene.
I was trying to play with atomic updates and below is my observation:
I have following document in my index:
1
Dikchant
softwa
