Add ability to download Worksheet results (CSV/XLS/Clipboard/Export)

[rbernotas]

Is your idea related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The ability to query datasets through the worksheets is a great feature, making data.all more usable as a single pane of glass for users. While once a user has been granted access to data, they may be able to work more directly with the data from S3 within an AWS account, non-technical or less technical users in an organization may need the ability to download query results directly from data.all, without having to work directly with the AWS account, in order to more easily retrieve result data as reports.

Describe the solution you'd like A clear and concise description of what you want to happen.

P.S. Don't attach files. Please, prefer add code snippets directly in the message body.

Add a feature to the Worksheet result data display, where the user can choose to download the result data they have generated as a CSV formatted file. XLS format, Copy results to clipboard, and other export options will also be useful. The feature could be presented to the user as a menu or button which prompts the user for a local download location, and then processes the output file for the user to download.

[dlpzx]

Hi @rbernotas thank you for adding it :) We will have a look

[mvidhu]

Our organisation users are also interested in this feature.

[anmolsgandhi]

#293

[rbernotas]

Referencing https://github.com/data-dot-all/dataall/issues/293 as well, I do think we will have interest in this feature, as despite the security concerns, it is a use case that we already regularly support with other platforms. One thing we have done in the past is to limit the number of rows that can be downloaded at a given time, so it's not so easy for someone to just select star grab all the data from a table and walk away with it. Ideally the CSV download would be a configurable feature, but also configurable in the maximum number of rows that can be downloaded for a query result. The idea being, that the CSV download would be for more ad-hoc usage / reporting, as opposed to bulk data export and data transfer (which would not be desirable).

We also had another set of use cases for CSV download that could be applied with such export support. It would be nice to be able to CSV export info about all the datasets in the catalog, or even your search result from the catalog (again, for reporting purposes, so teams can pass around the list of onboarded datasets, accounts that have been onboarded, etc.). Same for environments and organizations, and perhaps also available shares. This same functionality could be used in those cases as well. And future auditing feature where we can pull activity data from RDS can also benefit from this.

[SofiaSazonova]

I have several thoughts on this feature:

1. We can do it as another group-permission. So, not everyone will have an opportunity to download the data

2. I see a potential problem in 'download only N rows'. The user can be unnecessary confused, if what they see is not what they get. Considering the download is restricted, maybe we should reconsider restriction on number of rows.

3. On the other hand, if number of rows is too big (much more than in worksheet-preview) and we want to form the file on server side, we will have a trouble with direct download. So, it's much better to store the result in S3 and share pre-signed url when it's ready.