You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the druid run_query here a Phase 1 query is created if timeseries_limit == 0, but that can result in an incorrect query if the limit field is not present and there are parts of the Phase 2 query that are necessary (but don't get added).
This causes problems if a viz type does not have a limit but does require a phase 2 query or you remove the limit on a line chart.
@mistercrunch would you suggest having different logic for determining phase = 1 or pulling the necessary logic out of phase 2 and into phase 1?
The text was updated successfully, but these errors were encountered:
@mistercrunch any thoughts on this? If there's no timeseries limit we run a phase 1 query, which isn't always correct. Do you know why this step is necessary?
We are seeing group by line charts that should be 2 phase queries but the query only has a phase 1.
In the druid run_query here a Phase 1 query is created if timeseries_limit == 0, but that can result in an incorrect query if the limit field is not present and there are parts of the Phase 2 query that are necessary (but don't get added).
This causes problems if a viz type does not have a limit but does require a phase 2 query or you remove the limit on a line chart.
@mistercrunch would you suggest having different logic for determining phase = 1 or pulling the necessary logic out of phase 2 and into phase 1?
The text was updated successfully, but these errors were encountered: