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.

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

Allow Terms aggregations to define exact excludes and includes #1766

Merged
merged 1 commit into from
Mar 12, 2020

Conversation

thePanz
Copy link
Collaborator

@thePanz thePanz commented Mar 11, 2020

Allow Terms aggregations to define:

  • exact excludes
  • exact includes
  • include-partitions

Removed the $flags from the setInclude() as not supported by ES anymore

Closes #1764

@thePanz thePanz force-pushed the fix-terms-aggratations-include branch from 8ab6508 to 1c6ae73 Compare March 11, 2020 16:54
@thePanz thePanz requested a review from ruflin March 11, 2020 16:55
@thePanz thePanz force-pushed the fix-terms-aggratations-include branch from 1c6ae73 to 2ec6466 Compare March 12, 2020 08:10
@ruflin
Copy link
Owner

ruflin commented Mar 12, 2020

The only part I'm worried is that we need to add more functions if ES decides to add something new here. But at the same time, this is kind of how Elastica works ...

@thePanz
Copy link
Collaborator Author

thePanz commented Mar 12, 2020

@ruflin the functions here are helping to not memorize the ES endpoints. if something new comes up: , we can add a new method, but in the meanwhile the ->setParam() will work fine as a temporary solution :)

@thePanz thePanz merged commit 62d1800 into ruflin:master Mar 12, 2020
@thePanz thePanz deleted the fix-terms-aggratations-include branch March 12, 2020 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Terms aggregation with exact values in include
2 participants