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

Add a button to download query results #211

Closed
brianok-aws opened this issue Oct 22, 2021 · 1 comment · Fixed by #602
Closed

Add a button to download query results #211

brianok-aws opened this issue Oct 22, 2021 · 1 comment · Fixed by #602
Assignees
Labels
enhancement New feature or request
Projects

Comments

@brianok-aws
Copy link

Is your feature request related to a problem? Please describe.
When I run a SPARQL query in the notebook, I am frustrated there’s no option to download the data as a CSV or other file format.

Describe the solution you'd like
I would like to have a "download" button to download the result set in my browser.

Describe alternatives you've considered
I can issue HTTP requests or write code to save the results to a file and write the file to my Neptune instance, but that is not friendly to my data scientist team and will likely add a lot of small files to my notebook instance file system.

@michaelnchin michaelnchin added this to New issues/Needs triage or review in Planning via automation Oct 22, 2021
@michaelnchin michaelnchin added the enhancement New feature or request label Oct 22, 2021
@joywa joywa moved this from New issues/Needs triage or review to Low priority in Planning Jan 18, 2023
@richraid21
Copy link

I ran into this problem yesterday where I was doing some exploration of the graph and needed some quick results, but the result set was large enough that printing it as CSV via Pandas was too taxing on the browser. I ended up needed to rewrite the query in Java and run it to save the results.

@michaelnchin michaelnchin moved this from Low priority to In progress in Planning May 30, 2024
@michaelnchin michaelnchin self-assigned this May 30, 2024
@michaelnchin michaelnchin linked a pull request May 30, 2024 that will close this issue
Planning automation moved this from In progress to Resolved May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Planning
Resolved
Development

Successfully merging a pull request may close this issue.

3 participants