[
https://issues.apache.org/jira/browse/SOLR-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495280#comment-13495280
]
Mark Miller commented on SOLR-3831:
-----------------------------------
This should be in trunk.
You may be confused by the above commit bot message?
New tool I'm working on, and yesterday I accidentally triggered it for my name
in the last 400 or so commits, but only for 4x - I stopped it before it did 5x.
So if you know something is not on 5x that is on 4x, we need to fix it. But
don't go by the commit bot messages for these past issues - hoping that's
something you can count on in the future, but it's in development at the moment.
> atomic updates do not distribute correctly to other nodes
> ---------------------------------------------------------
>
> Key: SOLR-3831
> URL: https://issues.apache.org/jira/browse/SOLR-3831
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0-BETA
> Environment: linux
> Reporter: Jim Musil
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3831.patch
>
>
> After setting up two independent solr nodes using the SolrCloud tutorial,
> atomic updates to a field of type "payloads" gives an error when updating the
> destination node.
> The error is:
> SEVERE: java.lang.NumberFormatException: For input string: "100}"
> The input sent to the first node is in the expected default format for a
> payload field (eg "foo|100") and that update succeeds. I've found that the
> update always works for the first node, but never the second.
> I've tested each server running independently and found that this update
> works as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
