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

[DOCS] Add operation delete under the es.write.operation section #1959

Merged
merged 2 commits into from
May 19, 2022

Conversation

morland96
Copy link
Contributor

Thank you for submitting a pull request!

Please make sure you have signed our Contributor License Agreement (CLA).
We are not asking you to assign copyright to us, but to give us the right to distribute your code without restriction. We ask this of all contributors in order to assure our users of the origin and continuing existence of the code.
You only need to sign the CLA once.

@morland96
Copy link
Contributor Author

morland96 commented May 13, 2022

The delete operation is existing for a while but the current documentation is not representing that. #1324

@masseyke masseyke self-assigned this May 16, 2022
@masseyke
Copy link
Member

@morland96 thanks for the PR! It does look like we just missed this after we added #1324. I've added a minor suggested change to bring it in line with the wording for update, but otherwise looks good.

Co-authored-by: Keith Massey <[email protected]>
Copy link
Member

@masseyke masseyke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@morland96
Copy link
Contributor Author

Looks good to me.

Who will gonna execute the merge? Not sure about the workflow in this project.

@masseyke masseyke merged commit 4681236 into elastic:main May 19, 2022
@@ -159,6 +159,7 @@ The write operation {eh} should perform - can be any of:
`create`;; adds new data - if the data already exists (based on its id), an exception is thrown.
`update`;; updates existing data (based on its id). If no data is found, an exception is thrown.
`upsert`;; known as _merge_ or insert if the data does not exist, updates if the data exists (based on its id).
`delete`;; deletes existing data (based on its id). If no data is found, an exception is thrown.
Copy link

@atomobianco atomobianco Jun 8, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If no data is found, an exception is thrown.

Maybe I am confusing what is meant with "data", but I am not getting an exception when deleting documents that are not in Elasticsearch.
Using "org.elasticsearch" %% "elasticsearch-spark-20" % 7.14.2

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PS: Which to me is preferable (having no exceptions) so that I am not obliged to read ES before

This comment was marked as duplicate.

@@ -159,6 +159,7 @@ The write operation {eh} should perform - can be any of:
`create`;; adds new data - if the data already exists (based on its id), an exception is thrown.
`update`;; updates existing data (based on its id). If no data is found, an exception is thrown.
`upsert`;; known as _merge_ or insert if the data does not exist, updates if the data exists (based on its id).
`delete`;; deletes existing data (based on its id). If no data is found, an exception is thrown.

This comment was marked as outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants