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.

Sign up for GitHub

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

Jump to bottom

Eliminate the anti-discovery pattern in Elasticsearch #15133

Closed
MikeAlhayek opened this issue Jan 19, 2024 · 0 comments · Fixed by #15134
Closed

Eliminate the anti-discovery pattern in Elasticsearch #15133

MikeAlhayek opened this issue Jan 19, 2024 · 0 comments · Fixed by #15134
Assignees
@MikeAlhayek
Labels
enhancement
Milestone
2.0

Comments

@MikeAlhayek
Copy link
Member

Currently, Elasticsearch module follows an anti-dicovery pattern where if ES is not configured, none of it's services is registers. This cause exceptions in some services that needs it.

I'll submit a PR to fix this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MikeAlhayek MikeAlhayek

Labels
enhancement
Projects
None yet
Milestone
2.0
Development

Successfully merging a pull request may close this issue.

Eliminate the anti-discovery pattern in Elasticsearch OrchardCMS/OrchardCore
1 participant
@MikeAlhayek