SQL: [Docs] Add example for custom bucketing with CASE #41787
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
Add a TIP on how to use CASE to achieve custom bucketing with GROUP BY. Follows: elastic#41349
matriv
added
>docs
|
Pinging @elastic/es-search |
astefan
approved these changes
May 6, 2019
| =============================== | ||
| CASE can be used as a GROUP BY key in a query to facilitate custom bucketing | ||
| and assign descriptive names to those buckets. If for example the number of | ||
| values for a key are too many or, simply, ranges of those values are more |
There was a problem hiding this comment.
the number ..... is too large. values.... are too many
| [TIP] | ||
| =============================== | ||
| CASE can be used as a GROUP BY key in a query to facilitate custom bucketing | ||
| and assign descriptive names to those buckets. If for example the number of |
There was a problem hiding this comment.
If, for example, the number....
| GROUP BY lang_skills | ||
| ORDER BY lang_skills; | ||
|
|
||
| With this query, we can create normal grouping buckets for values _0, 1, 2, 3_ with |
There was a problem hiding this comment.
With this query, one can create
costin
approved these changes
May 6, 2019
| @@ -98,6 +98,31 @@ an error message would be returned, mentioning that *'foo'* is of data type *key | |||
| which does not match the expected data type *integer* (based on result *10*). | |||
| =============================== | |||
|
|
|||
| [[sql-functions-conditional-case-groupby-custom-buckets]] | |||
| [TIP] | |||
There was a problem hiding this comment.
I would remove the TIP header and promote this to a section (=====) - I think it's big enough to warrant a proper entry.
matriv
added a commit
that referenced
this pull request
May 6, 2019
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
May 7, 2019
* elastic/master: (414 commits) Add tasks to build Docker build context artifacts (elastic#41819) Replace more uses of immutable map builder (elastic#41823) Force selection of calendar or fixed intervals in date histo agg (elastic#33727) Switch run task to use real distro (elastic#41590) Clarify that path_match also considers object fields. (elastic#41658) [DOCS] remove 'es.scripting.update.ctx_in_params' system property for 7.0 (elastic#41643) Clarify _doc is a permanent part of certain document APIs. (elastic#41727) Remove the jdk directory to save space on bwc tests (elastic#41743) Fix full text queries test that start with now (elastic#41854) Remove `nonApplicationWrite` from `SSLDriver` (elastic#41829) SQL: [Docs] Add example for custom bucketing with CASE (elastic#41787) Cleanup Bulk Delete Exception Logging (elastic#41693) [DOCS] Rewrite `term` query docs for new format (elastic#41498) Mute PermissionsIT#testWhen[...]ByILMPolicy (elastic#41858) ReadOnlyEngine assertion fix (elastic#41842) [ML] addresses preview bug, and adds check to PUT (elastic#41803) Fix javadoc in WrapperQueryBuilder Testsclusters use seprate configurations per version (elastic#41504) Skip explain fetch sub phase when request holds only suggestions (elastic#41739) remove unused import ...
gurkankaymak
pushed a commit
to gurkankaymak/elasticsearch
that referenced
this pull request
May 27, 2019
* SQL: [Docs] Add example for custom bucketing with CASE Add a TIP on how to use CASE to achieve custom bucketing with GROUP BY. Follows: elastic#41349 * address comments * address comment
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.
Add a TIP on how to use CASE to achieve custom bucketing
with GROUP BY.
Follows: #41349