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

Add support for the multi_terms aggregation #1512

Closed
bralbral opened this issue Jun 30, 2021 · 10 comments · Fixed by #1543
Closed

Add support for the multi_terms aggregation #1512

bralbral opened this issue Jun 30, 2021 · 10 comments · Fixed by #1543

Comments

@bralbral
Copy link

bralbral commented Jun 30, 2021

Good day!

How can i use multu-terms aggregation ?

I have got : elasticsearch_dsl.exceptions.UnknownDslObject: DSL class multi_terms does not exist in agg.
Is there a method implemented?

@sethmlarson
Copy link
Contributor

This aggregation is new in Elasticsearch 7.12 and hasn't been implemented in Elasticsearch-DSL natively yet.

@bralbral bralbral closed this as completed Jul 7, 2021
@sethmlarson sethmlarson reopened this Jul 7, 2021
@sethmlarson
Copy link
Contributor

No need to close this until it's implemented.

@sethmlarson sethmlarson changed the title Multi Terms aggregation Add support for the multi_terms aggregation Jul 7, 2021
@robindierckx
Copy link

robindierckx commented Aug 16, 2021

same problem with combined_fields (new in elastic_search 7.13):

elasticsearch_dsl.exceptions.UnknownDslObject: DSL class `combined_fields` does not exist in query.

While waiting for it to be implemented, is there a workaround to tell DSL "don't bother if you don't understand it, just add the parameter in the elastic search request"

robindierckx added a commit to robindierckx/elasticsearch-dsl-py that referenced this issue Sep 27, 2021
Aims to tackle second issue described here: elastic#1512
@snowwhitehat
Copy link

Any idea on timeline for the 'multi_terms' aggregation being natively supported in the elasticsearch dsl? Cheers!

@Telomeraz
Copy link
Contributor

Telomeraz commented Oct 30, 2021

I've just sent a pr for this issue, could you review it please? @sethmlarson

Also, should i create a new issue to implement "combined_fields" query?

@EvieGillie
Copy link

Is there a workaround in the meantime?

@Telomeraz
Copy link
Contributor

I think there isn't. You can write it natively. @EvieGillie

@vipulg13
Copy link

vipulg13 commented Jan 5, 2022

could you please consider adding support to the "combined_fields" query? @Telomeraz

@vipulg13
Copy link

vipulg13 commented Jan 6, 2022

@Telomeraz should I create a new issue for combined_fields, as this one is closed?

@Telomeraz
Copy link
Contributor

@vipulg13 Yes, you can create a new one.

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 a pull request may close this issue.

7 participants