-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
[Explore]SORT BY metric incorrectly re-added to SELECT clause #13423
Comments
fyi @junlincc |
thanks for reporting! |
@junlincc we were seeing in on the area chart with a Here's a screenshot of the relevant UI controls: |
ah, I see. It does happen when group by is added to area chart and bar and Pivottable. @john-bodley thanks for additional info! cc @maloun96 Victor, could you please take a look, it might related to the sort-by project we recently did? thanks! |
Note this may be related to #13426 which also seems to be a regression. |
#13228 seems to have the same root cause. |
If the metric name/expression is the same as the SORT BY metric, the SORT BY metric is re-added to the SELECT clause (necessary for sorting) which results in selecting the expression twice which then introduces ambiguity resulting in the query engine returning an error.
Expected results
The SORT BY metric should not be re-added to the SELECT clause.
Actual results
Depending on the engine an error may be thrown, i.e., for Presto:
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
METRICS
section (chart dependent) andSORT BY
.GROUP BY
.RUN
.Environment
(please complete the following information):
master
3.7
node -v
Checklist
Make sure to follow these steps before submitting your issue - thank you!
The text was updated successfully, but these errors were encountered: