Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The behavior of doc_as_upsert is incorrect #3265

Closed
Paikan opened this issue Jun 30, 2013 · 4 comments
Closed

The behavior of doc_as_upsert is incorrect #3265

Paikan opened this issue Jun 30, 2013 · 4 comments

Comments

@Paikan
Copy link
Contributor

Paikan commented Jun 30, 2013

Here is the gist recreation

  • First some cleaning
$ curl -XDELETE 'localhost:9200/index1'
  • This insert the document where it shouldn't
$ curl -XPOST 'localhost:9200/index1/test1/1/_update' -d '
{
  doc : { field : "value" },
  doc_as_upsert : false 
}'
  • Changing the order change the behavior of the param
$ curl -XPOST 'localhost:9200/index1/test1/2/_update' -d '
{
  doc_as_upsert : false,
  doc : { field : "value" }
}'
@martijnvg
Copy link
Member

@Paikan Thanks for fixing this!

@Paikan
Copy link
Contributor Author

Paikan commented Jun 30, 2013

@martijnvg wow thanks it was fast! Shouldn't we push the fix in 0.90 branch too as I think the doc_as_upsert feature has been added in 0.90.2?

@martijnvg
Copy link
Member

@Paikan Just pushed it also to the 0.90 branch. Took a while, the wifi on the train is a bit dodgy.

@Paikan
Copy link
Contributor Author

Paikan commented Jun 30, 2013

@martijnvg cool thanks and have a good end of trip then :)

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants