Skip to content

Deprecate ascending sort for terms aggregations#8167

Merged
epixa merged 1 commit intoelastic:masterfrom
epixa:8059-ascsortterms
Sep 6, 2016
Merged

Deprecate ascending sort for terms aggregations#8167
epixa merged 1 commit intoelastic:masterfrom
epixa:8059-ascsortterms

Conversation

@epixa
Copy link
Copy Markdown
Contributor

@epixa epixa commented Sep 6, 2016

Elasticsearch is deprecating the ability to use ascending sort for terms
aggregations, so we render a deprecation notice whenever a user views a
visualization that uses a terms aggregation with ascending sort by
count. We only render this error message once per route so it does not
spam the users constantly when they have things like auto-refresh
enabled on a dashboard.

Closes #8059

Elasticsearch is deprecating the ability to use ascending sort for terms
aggregations, so we render a deprecation notice whenever a user views a
visualization that uses a terms aggregation with ascending sort by
count. We only render this error message once per route so it does not
spam the users constantly when they have things like auto-refresh
enabled on a dashboard.
@ycombinator
Copy link
Copy Markdown
Contributor

ycombinator commented Sep 6, 2016

@epixa I just re-read the Elasticsearch issue that triggered this PR (and the ones for 4.6): elastic/elasticsearch#17614. My current (possibly incorrect) interpretation of the discussion in that issue is that Elasticsearch isn't going to deprecate this capability for future removal, but is going to leave it in and add warnings in documentation and such about its inaccuracy. If this is your understanding as well, should the warning in Kibana be updated accordingly?

@ycombinator
Copy link
Copy Markdown
Contributor

BTW, the code looks good as a forward port of #8050 and #8056. Just wanted to raise the question in my previous comment about whether we want to tweak the warning message before giving a final LGTM.

@epixa
Copy link
Copy Markdown
Contributor Author

epixa commented Sep 6, 2016

It doesn't look like a final decision has been made yet, but since we've already shipped this deprecation in 4.6, I want to make sure it is at least in master as well. We can always tweak or remove it entirely if such a decision is made on the ES side of things.

@ycombinator
Copy link
Copy Markdown
Contributor

Yeah, fair point. We'll have more 5.x releases so we'll have the opportunity to amend things when a final decision is made in ES-land. Thanks. This PR LGTM!

@epixa epixa merged commit 7a1745c into elastic:master Sep 6, 2016
@epixa epixa deleted the 8059-ascsortterms branch September 6, 2016 21:07
@tbragin
Copy link
Copy Markdown
Contributor

tbragin commented Oct 11, 2016

For anyone curious what the notice looks like, you can see it at the time you select this option the first time you create the visualization, but not afterwards.

screen shot 2016-10-11 at 4 28 49 pm

@epixa
Copy link
Copy Markdown
Contributor Author

epixa commented Oct 11, 2016

@tbragin You should see that whenever there's a fresh page load that includes that visualization rather than only when it's first created. This way a user wouldn't constantly be spammed with the notice if they're navigating around Kibana, but if they were to do a page refresh or close their browser and come back later or something, they'd see it again.

@tbragin
Copy link
Copy Markdown
Contributor

tbragin commented Oct 12, 2016

Great! Yeah, i see that now. Thanks for the clarification.

airow pushed a commit to airow/kibana that referenced this pull request Feb 16, 2017
Deprecate ascending sort for terms aggregations

Former-commit-id: 7a1745c
@PhaedrusTheGreek
Copy link
Copy Markdown
Contributor

@tbragin / @epixa , being that the deprecation was backed out - the warning is somewhat of a nuisance on dashboards that are using this feature. Do we have a way to disable it in 5.x?

@epixa
Copy link
Copy Markdown
Contributor Author

epixa commented Jul 19, 2017

@PhaedrusTheGreek There's no way to disable it, but if ES isn't going to proceed with its removal, then we should remove the deprecation notice in Kibana. Once I get confirmation that it will stick around for awhile in ES, we can proceed with removing it (the notice) in Kibana.

@PhaedrusTheGreek
Copy link
Copy Markdown
Contributor

@epixa Did this warning ever get backed out? I'm hitting this issue again with another dashboard.

@epixa
Copy link
Copy Markdown
Contributor Author

epixa commented Sep 21, 2018

@PhaedrusTheGreek It wasn't backed out, sorry about that. I created #23409 to track that so it doesn't get lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants