Skip to content
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

[reports] GET chart/<pk>/data api doesn't respect force parameter #22189

Closed
3 tasks
mayurnewase opened this issue Nov 22, 2022 · 0 comments · Fixed by #22196
Closed
3 tasks

[reports] GET chart/<pk>/data api doesn't respect force parameter #22189

mayurnewase opened this issue Nov 22, 2022 · 0 comments · Fixed by #22196
Assignees
Labels
alert-reports Namespace | Anything related to the Alert & Reports feature #bug Bug report v1.5 v2.0

Comments

@mayurnewase
Copy link
Contributor

mayurnewase commented Nov 22, 2022

A clear and concise description of what the bug is.
Api to get data of a saved chart used by reports to send csv data doesn't respect force parameter resulting in reports having stale data.

How to reproduce the bug

  1. setup caching for data and report
  2. create table chart, so it caches the data
  3. change the data in the datasource without busrting cache of the chart
  4. create report with csv and enable Ignore cache when generating screenshot
  5. see the report having stale data.

Expected results

As Ignore cache when generating screenshot is enabled, report should have fresh data from datasource.
Or this option is only for reports with screenshot as its name suggests?

Actual results

Report has stale data.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

(please complete the following information):

  • browser type and version:
  • superset version: 1.5.1 and 2.0
  • python version: python --version
  • node.js version: node -v
  • any feature flags active: ALERT_REPORTS

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@mayurnewase mayurnewase added #bug Bug report v2.0 v1.5 alert-reports Namespace | Anything related to the Alert & Reports feature labels Nov 22, 2022
@mayurnewase mayurnewase self-assigned this Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alert-reports Namespace | Anything related to the Alert & Reports feature #bug Bug report v1.5 v2.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant