-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
[Aera/line chart] Zero imputation resample returns error when combined with Group By #19157
Comments
@EBoisseauSierra I have posted a new PR for refactoring AA in this scenario. |
@EBoisseauSierra I have merged that PR. Let me know if any following up is needed. |
@zhaoyongjie thanks! I finally managed to have a go at it, and can confirm ( However, my particular example uses cumulative sum, and the graphs doesn't seem to resample: (with
|
@EBoisseauSierra Could you share the dataset so that I reproduce this case? |
@EBoisseauSierra it seems that this issue has gone cold... are you still seeing an issue here, and if so are you able to provide a reproduction case with sample data? Otherwise, we should probably close this one out. |
This is likely fixed by now, and is pretty out of date if not. If people are still encountering this in current versions (3.x) please open a new Issue or a PR to address the problem. |
I am getting an Unexpected error when trying to use the Advanced analytics/Resample/Fill Method = Zero imputation feature of the Time-series {Line, Area} Chart.
How to reproduce the bug
sum(numeric)
,str
(categorical variable, with or withoutNULL
values),Note that removing the metric in Group By allows to generate a graph as expected.
Expected results
A chart is generated.
Actual results
The Explore Panel returns an Unexpected error:
The following can be found in the logs:
Screenshots
Environment
(please complete the following information):
1.4.1
3.9.10
14.19.0
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
This seems linked to #18045.
The text was updated successfully, but these errors were encountered: