rscarborough1996 opened a new issue, #25782:
URL: https://github.com/apache/superset/issues/25782
I believe I may have found a bug in the /api/v1/chart/{pk} endpoint on
version 3.0.0.
I make use of Supersets api to retrieve chart data for other applications. I
start by making a get request to /api/v1/chart/{pk}, obtain the query context,
add "time_range" under "queries", and finally post that to /api/v1/chart/data.
This worked until I upgraded to 3.0.0, then the time range would
occasionally be ignored.
From what I have found, time range has no effect unless this is under the
filters key:
```
{
"col": "My Time Column",
"op": "TEMPORAL_RANGE",
"val": "No filter"
}
```
If the chart was created BEFORE upgrading then the following behavior can be
observed:
If the chart does not contain the temporal column, then this filter is
included and the time range is respected.
If the chart DOES contain the temporal column, then this filter IS NOT
included, and the time range is ignored.
This does not happen on charts created after upgrading, and it can be fixed.
After deleting the temporal column, saving, re-adding it, and saving again,
the query context returns the correct filters.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
