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 @arafalov
Solr resources and newsletter: http://www.solr-start.com/ and @solrstart
Solr popularizers community: https://www.linkedin.com/groups?gid=6713853


On 6 October 2014 11:23, Ali Nazemian <alinazem...@gmail.com> wrote:
> 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 <arafa...@gmail.com>
> wrote:
>
>> 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://www.solr-start.com/ and @solrstart
>> Solr popularizers community: https://www.linkedin.com/groups?gid=6713853
>>
>>
>> On 6 October 2014 03:40, Ali Nazemian <alinazem...@gmail.com> wrote:
>> > 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 this
>> > document to set "read_flag"="true", I faced strange problem. Next time I
>> > indexed same document with same values I saw two different version of
>> > document with id '12345' in solr. One of them with read_flag=true and
>> > another one without read_flag field! I dont want to have duplicate
>> > documents (as it should not to be because of unique_key id). Would you
>> > please tell me what caused such problem?
>> > Best regards.
>> >
>> > --
>> > A.Nazemian
>>
>
>
>
> --
> A.Nazemian

Reply via email to