-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
PR which finishes "respect `size` when splitting `terms` aggregation into buckets" issue. Some example of triple bucketing (terms {terms {terms {} } }) aggregation, like in the testcase I added with this PR, showing that our SQLs seem to be correct (what Clickhouse returns for each query is good) We have such a table <img width="1559" alt="Screenshot 2024-07-07 at 19 54 14" src="https://github.com/QuesmaOrg/quesma/assets/5407146/82b4c21d-c60a-4616-b8b3-791ff69d1334"> Topmost SQL for bucketing by `surname` (top 200 `surname`s) generated by our code is simple: <img width="1720" alt="Screenshot 2024-07-07 at 19 56 26" src="https://github.com/QuesmaOrg/quesma/assets/5407146/67ea6c14-c534-476b-a89d-0188581062f0"> Double nested bucketing (top 20 `limbName`s for each `surname`) is <img width="1718" alt="Screenshot 2024-07-07 at 19 57 36" src="https://github.com/QuesmaOrg/quesma/assets/5407146/937ba2da-a776-4625-a3a4-4598edbf690e"> Triple nested bucketing (top 1 `organName` for each `surname, limbName` pair) <img width="1716" alt="Screenshot 2024-07-07 at 20 00 47" src="https://github.com/QuesmaOrg/quesma/assets/5407146/e1b8caee-fb1c-48fc-bcd0-e85f0d48dce3"> --------- Co-authored-by: Przemek Delewski <[email protected]> Co-authored-by: Jacek Migdal <[email protected]>
- Loading branch information
1 parent
20d4a1e
commit 4871087
Showing
20 changed files
with
2,212 additions
and
192 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.