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

Add CLR error message from ElasticSearch #46

Merged
merged 2 commits into from
Nov 21, 2022
Merged

Conversation

dvs39
Copy link
Contributor

@dvs39 dvs39 commented Nov 10, 2022

Description

Currently there is no message if any CLR exception occurs during Indexation create/update.

UI:
image

However, perhaps better aproach would be enable .ThrowExceptions() options for Provider, but this need proper testsing.

References

elastic/elasticsearch-net#1793

QA-test:

Jira-link:

Artifact URL: https://vc3prerelease.blob.core.windows.net/packages/VirtoCommerce.ElasticSearch_3.210.0-pr-46-172f.zip

@vc-ci
Copy link
Contributor

vc-ci commented Nov 10, 2022

Reveiw task created: https://virtocommerce.atlassian.net/browse/PT-9590

@sonarcloud
Copy link

sonarcloud bot commented Nov 14, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@dvs39
Copy link
Contributor Author

dvs39 commented Nov 14, 2022

@OlegoO elastic/elasticsearch-net#1793 (comment)
I guess you need to consider to use wrap ConnectionSettings.ThrowExceptions() for NEST Client as ElasticProvider setting.

@OlegoO OlegoO merged commit cff9b8d into dev Nov 21, 2022
@OlegoO OlegoO deleted the feature/add-clr-exception branch November 21, 2022 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants