The field variant_count is stored and is not the target of a copyfield.
However I did notice that we were setting the same coreNodeName on both the
shards in core.properties. Removing this property fixed the issue and
updates succeed.
What role does this play in handling updates and why were oth
I can't reproduce this.
I tried starting up a 2 shard cluster and then followed the example here:
http://yonik.com/solr/atomic-updates/
"book1" was on shard2 (port 7574) and everything still worked fine.
> missing required field: variant_count
Perhaps the problem is document specific... What can
curl http://localhost:8983/solr/search/update -H
'Content-type:application/json' -d '
[
{
"id":
"c8cce27c1d8129d733a3df3de68dd675!c8cce27c1d8129d733a3df3de68dd675",
"link_id_45454" : {"set":"abcdegff"}
}
]'
I have two collections search and meta. I want to do an update in the
sea
On Tue, Sep 17, 2013 at 10:47 AM, Sesha Sendhil Subramanian
wrote:
> I am using solr 4.4 in solr cloud configuration. When i try to 'set' a
> field in a document using the update request handler, I get a 'missing
> required field' error.
Can you show the exact error message you get, and the updat
