It seems like by-design
https://issues.apache.org/jira/browse/SOLR-5211
you can't update a parent doc from the block.
On Tue, Oct 7, 2014 at 9:44 AM, Ali Nazemian wrote:
> The list of docs before do partial update:
>
> product01
> car
> product
>
The list of docs before do partial update:
product01
car
product
part01
wheels
part
part02
engine
part
Can you upload the update documents then (into a Gist or similar).
Just so that people didn't have to re-imagine exact steps. Because, if
it fully checks out, it might be a bug and the next step would be
creating a JIRA ticket.
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalo
Dear Alex,
Hi,
LOL, yeah I am sure. You can test it yourself. I did that on default schema
too. The results are same!
Regards.
On Mon, Oct 6, 2014 at 4:20 PM, Alexandre Rafalovitch
wrote:
> A stupid question: Are you sure that what schema thinks your uniqueId
> is - is the uniqueId in your setup
A stupid question: Are you sure that what schema thinks your uniqueId
is - is the uniqueId in your setup? Also, that you are not somehow
using the flags to tell Solr to ignore duplicates?
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources and newsletter: http://
Dear all,
Hi,
I am going to do partial update on a field that has not any value. Suppose
I have a document with document id (unique key) '12345' and field
"read_flag" which does not index at the first place. So the read_flag field
for this document has not any value. After I did partial update to t
in
database, it will raise a flag so that I may do something before getting
complaints.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Duplicate-Unique-Key-tp4129651p4129894.html
Sent from the Solr - User mailing list archive at Nabble.com.
It's indeed quite odd. And after I trigger re-indexing all documents
>> (via
>> > the normal process of existing program). The duplication is gone. It can
>> > not be reproduced easily. But it did occur occasionally and that makes
>> it a
>> > frustrating
rogram). The duplication is gone. It can
> > not be reproduced easily. But it did occur occasionally and that makes
> it a
> > frustrating task to troubleshoot.
> >
> > Thanks,
> > Simon
> >
> >
> >
> > --
> > View this message in context:
> http://lucene.472066.n3.nabble.com/Duplicate-Unique-Key-tp4129651p4129701.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
>
ge in context:
> http://lucene.472066.n3.nabble.com/Duplicate-Unique-Key-tp4129651p4129701.html
> Sent from the Solr - User mailing list archive at Nabble.com.
View this message in context:
http://lucene.472066.n3.nabble.com/Duplicate-Unique-Key-tp4129651p4129701.html
Sent from the Solr - User mailing list archive at Nabble.com.
"id$": "1",
> "_version_": 1464236728284872700,
> "_root_": 1
> }
>
> I use SolrJ api to add documents. My understanding solr uniqueKey is like a
> database primary key. I am wondering how could I end up with two docume
derstanding solr uniqueKey is like a
database primary key. I am wondering how could I end up with two documents
with same uniqueKey in the index.
Thanks,
Simon
--
View this message in context:
http://lucene.472066.n3.nabble.com/Duplicate-Unique-Key-tp4129651.html
Sent from the Solr - User mailing list archive at Nabble.com.
13 matches
Mail list logo