You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/12/23 12:33:57 UTC
[GitHub] [superset] pratikgera123 opened a new issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
pratikgera123 opened a new issue #17861:
URL: https://github.com/apache/superset/issues/17861
When multiple pages are present in a report and user clicks on export CSV , only the data from first page is getting exported in CSV even when any other page is selected.
#### How to reproduce the bug
1. Open any report
2. Navigate to any other page using pagination
3. Click on export CSV
### Expected results- Csv file with entries of current page should get downloaded
### Actual results- CSV file with entries of first page getting downloaded
#### Screenshots
### Environment
- browser :Chrome
- superset version: `1.3.1`
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with the combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore changes to "show <n> entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] ankuraga2022 edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
ankuraga2022 edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1033566464
While downloading the CSV file irrespective of pagination i.e. 10/20/50 items or "All" items in the list, the downloaded file consists first 10/20 records as they were set for pagination for display.
Validated on multiple reports and different datasets.
Expected -
"Export CSV" option should be extracting records displayed on the view with respect to no. of records set to display on single page
"Export full CSV" option should extract all records.
Actual -
Fixed number of records are extracted from both the options .
<img width="81" alt="Pagination" src="https://user-images.githubusercontent.com/99324676/153170672-61603a53-1b77-49de-91e0-e1eed8f924ee.png">
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with the combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore changes to "show n entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way. We had to suggest to them to go via "view chart in explore", disable server pagination, and download from there. Not the best user experience, especially given that we have quite some users.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] noobyogi0010 commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
noobyogi0010 commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1010257143
Hi @amitmiran137 !
I would like to work on this issue if nobody has already taken it up.
Thanks.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with ne combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore "show <n> entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with ne combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore "show <n> entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] ajaysharma202 commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
ajaysharma202 commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1033587573
> When multiple pages are present in a report and user clicks on export CSV , only the data from first page is getting exported in CSV even when any other page is selected.
>
> #### How to reproduce the bug
> 1. Open any report
> 2. Navigate to any other page using pagination
> 3. Click on export CSV
>
> ### Expected results- Csv file with entries of current page should get downloaded
> ### Actual results- CSV file with entries of first page getting downloaded
> #### Screenshots
> 
>
> ### Environment
> * browser :Chrome
> * superset version: `1.3.1`
I am also getting the same issue.
Can anyone suggest if we can expect this fix in near future?
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with the combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore changes to "show n entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way. We had to suggest to our users to go via "view chart in explore", disable server pagination, and download from there. Not the best user experience, especially given that we have quite some users.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all pages" vs. "download current page", override for limit, etc.).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with the combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore "show <n> entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with the combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore changes to "show n entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] amitmiran137 commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
amitmiran137 commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1003648980
@villebro could you think of a possible solution for this one ?
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] ankuraga2022 edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
ankuraga2022 edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1033566464
While downloading the CSV file irrespective of pagination i.e. 10/20/50 items or "All" items in the list, the downloaded file consists first 10/20 records as they were set for pagination for display.
Validated on multiple reports and different datasets.
Expected -
"Export CSV" option should be extracting records displayed on the view with respect to no. of records set to display on single page
"Export full CSV" option should extract all records.
Actual -
Fixed number of records are extracted from both the options .
<img width="240" alt="Pagination" src="https://user-images.githubusercontent.com/99324676/153172853-e12b78fb-f66a-4122-b5b6-d9d3abbb644a.png">
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] nijcap01 commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
nijcap01 commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1075888048
Hi Team,
Any update on this item, our client is following us regularly on this, Please let us which version we are targeting this so that we can respond accordingly.
Thanks
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with ne combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore "show <n> entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with the combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore changes to "show n entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way. We had to suggest to our users to go via "view chart in explore", disable server pagination, and download from there. Not the best user experience, especially given that we have quite some users.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all pages" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with ne combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore "show <n> entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with ne combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore "show <n> entries" (always use the default "server page length"
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] hosswald edited a comment on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
hosswald edited a comment on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020094798
@noobyogi0010 @geido
Our customer also has issues with the combination of server pagination & csv export.
The behaviour is different from exporting from a chart without server pagination.
In a "normal" chart, all pages would be downloaded (e.g. 10 pages a 10 entries = 100 row csv).
In a "server paged" chart, the "export CSV" function will
- download the first page only
- ignore changes to "show n entries" (always use the default "server page length")
I would suggest not necessarily going @pratikgera123's proposed way (download the current instead of the first page) but instead harmonizing "server paged" CSV export with normal CSV export, e.g. they should behave the same. The user of a dashboard does not necessarily even know what server paging is and whether it's used, so they expect csv to behave the same either way. We had to suggest to our users to go via "view chart in explore", disable server pagination, and download from there. Not the best user experience, especially given that we have quite some users.
Ideally, the CSV export option should offer a pop-up where such things can be selected before downloading ("download all" vs. "download current page", for instance).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] geido commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
geido commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1020087211
Hello @noobyogi0010 that would be great! Let me know if you are still interested in working on this issue
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] ankuraga2022 commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
ankuraga2022 commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1033566464
While downloading the CSV file irrespective of pagination i.e. 10/20/50 items or "All" items in the list, the downloaded file consists first 20 records. Validated on multiple reports and different datasets.
<img width="81" alt="Pagination" src="https://user-images.githubusercontent.com/99324676/153170672-61603a53-1b77-49de-91e0-e1eed8f924ee.png">
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] nijcap01 commented on issue #17861: While exporting CSV , only the entries on first page are getting downloaded even when user is on other pages
Posted by GitBox <gi...@apache.org>.
nijcap01 commented on issue #17861:
URL: https://github.com/apache/superset/issues/17861#issuecomment-1012005523
Any update on which version can we expect this, also in the above we are using sql templating in datasets.
> Hi @amitmiran137 ! I would like to work on this issue if nobody has already taken it up. Thanks.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org