Add PPL query editor #3
Merged
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
ahlaw
force-pushed
the
ppl-query-editor
branch
from
9a44571
to
161eaf5
Compare
alexanderzobnin
approved these changes
Dec 16, 2020
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.
What this PR does / why we need it:
This PR contains the addition of a dropdown menu in the Elasticsearch query editor where query syntax can be chosen.
If Lucene (default) is selected, the query editor should function as before. If PPL is selected, a different query editor interface should appear. The PPL query editor contains a main query input field and an additional dropdown that will be used to determine the visualization format.
PPL is only available in the dropdown if
pplEnabledis set in theElasticDatasourceclass.