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

Isolate access to IElasticClient in ElasticIndexManager #16422

Closed

Conversation

AndreySurkov
Copy link
Contributor

Fixes #16421

@MikeAlhayek
Copy link
Member

@AndreySurkov I am seeing too many changes here. I think PR #16424 will fix the issue you are having. Can you please check it out?

Copy link
Contributor

This pull request has merge conflicts. Please resolve those before requesting a review.

@MikeAlhayek
Copy link
Member

@AndreySurkov are you able to verify that this issue no longer exists in 2.0.0-preview? If so, please close this PR.

@AndreySurkov
Copy link
Contributor Author

@MikeAlhayek Thanks. I verified it. My idea was to refactor part of ES related code to avoid similar problems in future, and limit code that make direct to IElasticSearchClient in single place. But if you are prefer to make fix as simple as it can be it works for me.

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.

IndexPrefix setting for ElasticSearch does not work for Queries and ElasticContentPicker
2 participants