Skip to content

Conversation

@ddey2
Copy link
Member

@ddey2 ddey2 commented Dec 13, 2022

No description provided.

@ddey2 ddey2 requested a review from max-zilla as a code owner December 13, 2022 00:20
@ddey2 ddey2 linked an issue Dec 13, 2022 that may be closed by this pull request
Copy link
Contributor

@tcnichol tcnichol left a comment

Choose a reason for hiding this comment

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

Tested and everything seems to be working. Marking approved.

es_client.delete_by_query(index=index_name, query=query)
except BadRequestError as ex:
logger.error(str(ex))

Copy link
Member

Choose a reason for hiding this comment

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

Do you want to catch more errors other than badrequestError?
Maybe add another except: logger.error(str(e))?

Also not throwing this error?

Copy link
Member

Choose a reason for hiding this comment

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

@ddey2 was this resolved?

Copy link
Member Author

Choose a reason for hiding this comment

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

@lmarini Not resolved. @longshuicy We don't perform the action if the service is unavailable. In this scenario, I think BadRequestError is sufficient. I am all ears to suggestion. Lmk if you think I am missing any scenario

Do we want to throw the exception? We show a message if the Elasticsearch service is not available.

@lmarini lmarini merged commit 354b904 into main Jan 17, 2023
@lmarini lmarini deleted the 237-deleting-datasetfile-doesnt-delete-associated-metadata branch January 17, 2023 19:19
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.

Deleting dataset/file doesn't delete associated metadata

5 participants