[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552414#comment-13552414
]
Commit Tag Bot commented on SOLR-4127:
--
[trunk commit] Erik Hatcher
http://svn.apache.org/viewvc?view=revisionrevision=1432794
SOLR-4127: post.jar ignores -Dparams when -Durl is used
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1, 5.0
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552415#comment-13552415
]
Commit Tag Bot commented on SOLR-4127:
--
[branch_4x commit] Erik Hatcher
http://svn.apache.org/viewvc?view=revisionrevision=1432795
SOLR-4127: post.jar ignores -Dparams when -Durl is used (merged from trunk)
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1, 5.0
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13531217#comment-13531217
]
Lukas Graf commented on SOLR-4127:
--
Gave this a test with current trunk (r1421381) - works like a charm.
Thanks for fixing this so quickly Hoss!
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1, 5.0
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528822#comment-13528822
]
Markus Jelsma commented on SOLR-4127:
-
We have seen this too on a very recent trunk cluster. It has updateLog enabled
and the distributed processor is in the chain. I could not successfully
reproduce it when i disabled the langid processor in the chain, nor could i
reliably reproduce this problem with the langid enabled.
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529127#comment-13529127
]
Hoss Man commented on SOLR-4127:
marjus...
bq. We have seen this too on a very recent trunk cluster. It has updateLog
enabled and the distributed processor is in the chain...
that sounds like it must be a differnet bug with similar symptoms -- the next
time you reproduce, can you please file a bug with your configs and the
specifics of hte document you tried to updated (ie: it's current state, and
what atomic update you attempted)
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529134#comment-13529134
]
Lukas Graf commented on SOLR-4127:
--
In my experience, the same symptoms could possibly be caused by either
* using the wrong syntax for the atomic update instructions
* or using the atomic add update instruction in an XML update message, which
apparently isn't implemented (only in JSON).
If nobody beats me to it, I will add two separate issues for those.
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529143#comment-13529143
]
Commit Tag Bot commented on SOLR-4127:
--
[trunk commit] Chris M. Hostetter
http://svn.apache.org/viewvc?view=revisionrevision=1420297
SOLR-4127: Added explicit error message if users attempt Atomic document
updates with either updateLog or DistribUpdateProcessor
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
[
https://issues.apache.org/jira/browse/SOLR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529174#comment-13529174
]
Commit Tag Bot commented on SOLR-4127:
--
[branch_4x commit] Chris M. Hostetter
http://svn.apache.org/viewvc?view=revisionrevision=1420305
SOLR-4127: Added explicit error message if users attempt Atomic document
updates with either updateLog or DistribUpdateProcessor (merge r1420297)
Atomic updates used w/o updateLog should throw an error
---
Key: SOLR-4127
URL: https://issues.apache.org/jira/browse/SOLR-4127
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 4.0
Reporter: Lukas Graf
Assignee: Hoss Man
Fix For: 4.1, 5.0
Attachments: SOLR-4127.patch
The atomic update feature described in
[SOLR-139|https://issues.apache.org/jira/browse/SOLR-139] seems to depend on
having an {{updateLog /}} configured in {{solrconfig.xml}}.
When used without an update log, the update commands like {{set}} or {{add}}
don't result in an error and the transaction being aborted, but produce
garbled documents instead. This is the case for both the XML and JSON formats
for the update message.
Example:
I initially created some content like this:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:My original Title, Creator: John Doe}]'
{code}
Which resulted in this document:
{code:xml}
doc
str name=id7cb8a43c/str
str name=TitleMy original Title/str
str name=CreatorJohn Doe/str
/doc
{code}
Then I attempted to update that document with this statement:
{code}
$ curl 'localhost:8983/solr/update?commit=true' -H
'Content-type:application/json' -d '
[{id:7cb8a43c,Title:{set:My new title}}]'
{code}
Which resulted in this garbled document, with the fields that weren't updated
missing:
{code:xml}
doc
str name=id7cb8a43c/str
str name=Title{set=My new title}/str
/doc
{code}
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
