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

Remove top level filter parameter #8862

Closed
ppf2 opened this issue Dec 10, 2014 · 7 comments
Closed

Remove top level filter parameter #8862

ppf2 opened this issue Dec 10, 2014 · 7 comments
Assignees
Labels

Comments

@ppf2
Copy link
Member

ppf2 commented Dec 10, 2014

Let's remove top level filter (#4119) from the product. It can be confusing to end users given that we no longer document the top level filter in our guides (we only talk about post_filter now), but Marvel auto-fill still shows it as a valid clause at the top level.

@s1monw
Copy link
Contributor

s1monw commented Dec 10, 2014

+1 @clintongormley what do you think?

@dadoonet
Copy link
Member

+1 as well. Wanna me to work on a PR for this?

@clintongormley
Copy link

Definitely - it's been deprecated since 1.0.

@Mpdreamz
Copy link
Member

Should we do the same for percolator requests:

http://www.elastic.co/guide/en/elasticsearch/reference/current/search-percolate.html

and rename its filter to post_filter? or does its aggs behave slightly different from _search's aggs?

@clintongormley
Copy link

@Mpdreamz the filter on percolators is different - it's essentially just like a filtered query in that case.

@clintongormley clintongormley changed the title Remove top level filter? Remove top level filter parameter Jun 6, 2015
@clintongormley clintongormley added good first issue low hanging fruit and removed :Query DSL labels Jun 6, 2015
@ycombinator ycombinator self-assigned this Jun 11, 2015
ycombinator added a commit that referenced this issue Jun 12, 2015
Removing top-level filter parameter from search API.
ycombinator referenced this issue Jun 12, 2015
Revert "Removing top-level filter parameter from search API."
@ycombinator ycombinator reopened this Jun 12, 2015
@javanna
Copy link
Member

javanna commented Oct 16, 2015

Given that #11600 is in, does this need to stay open? Is there anything left to do?

@clintongormley
Copy link

@javanna that change was reverted, so yes this still needs to be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants