-
Notifications
You must be signed in to change notification settings - Fork 736
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
Accept an options array at Type::updateDocument() #686
Conversation
Makes sense. Can you update the changes.txt file with this change? Strange that it was already used in the tests. Do have an idea how we could write a specific test for this options? |
Done! Updating an existing doc with a non-matching version number parameter will rise a VersionConflictEngineException and won't update the document. Perhaps something like this?:
|
Looks good. Can you add this to the pull request? I made a release yesterday, so make sure to merge in the master branch and please add the pull request id to the changes.txt |
Conflicts: changes.txt
…pull request id to changes.txt
Done, I've added the testUpdateDocumentWithParameter() test, could you take a look?. |
@@ -4,6 +4,9 @@ CHANGES | |||
- Release v1.3.4.0 | |||
- Update to elasticsearch 1.3.4 #691 | |||
|
|||
2014-10-02 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the date here and move it on top of the release. Otherwise it will be missing in the next release notes.
Looks good. Almost ready to merge. See my small comment above. |
Merged. |
Allows setting options when updating Documents with Scripts:
It's even being used at TypeTest::testUpdateDocument():