[BUGFIX/REGRESSION] Fix wrong elastic client setup when use custom URL #1381
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ah my mistake, forgot to move to the new node. thanks @tirongi ! |
HenryHengZJ
approved these changes
Dec 13, 2023
hemati
pushed a commit
to hemati/Flowise
that referenced
this pull request
Dec 27, 2023
…stomURL [BUGFIX/REGRESSION] Fix wrong elastic client setup when use custom URL
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the new Elastic node, there is the same connection error that was solved in the deprecated nodes whenever connecting to a custom server URL.
The bug was previously solved in #1262