Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

A result cell's download button does nothing off the canvas

Closed
  • Is something wrong?
#8,538 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@yangzhang75 is already working on this.

Since Sep 17, 2026.

Assessment

This issue has not been assessed yet.

Description

What happened?

The download button on a result cell does nothing. Pressing it opens the export dialog; entering a filename, choosing a destination and confirming closes the dialog and nothing else happens — no file, no request, no error, no message. It behaves the same for every destination: export to local, save to an existing dataset, and save to a newly created dataset, which stays empty.

The cause is the scope the export gives itself. WorkflowResultExportService.performExport reads the canvas selection (getCurrentHighlightedOperatorIDs()) unless the caller asked for all operators, and returns at its operatorIds.length === 0 check when that comes back empty. That is the right rule for the two callers that read the canvas — the top menu asks for everything, the context menu exports the selection — but a result cell is neither: a cell belongs to one operator, whoever happens to be selected. On the Form View the selection holds the step the user is configuring, and holds nothing at all until they click one, so a cell's export there finds an empty scope and returns before sending anything. The dialog's own checks read the same empty selection, so a restricted operator goes unreported there too.

Expected: the download button on a result cell exports that cell's operator, wherever the cell is mounted.

How to reproduce?
  1. Open a workflow whose result column holds binary data (a Python UDF source yielding a binary column is enough) and run it.
  2. Open it in the Form View (/user/workflow/<id>/form) and do not click any step, so nothing is selected.
  3. Hover a result row and click the download icon on the binary cell. The export dialog opens.
  4. Enter a filename, choose local, and press Export.
  5. The dialog closes and nothing arrives. DevTools > Network shows no request to /api/executions/result/export/local.

https://github.com/user-attachments/assets/c770a437-7547-4809-a1a6-88cad1013855

Separately, and not covered by this issue: export-execution-result-enabled defaults to false in common/config/src/main/resources/gui.conf, and performExport returns even earlier when it is off, with the same silence. On a default local deployment you have to set GUI_WORKFLOW_WORKSPACE_EXPORT_EXECUTION_RESULT_ENABLED=true before any export works at all. Whether that default should change is a separate question.

Version/Branch

1.4.0-incubating-SNAPSHOT (main)

Commit Hash (Optional)

dcb25efa9e1d4321b7b99459db4ee777f37cbaff

What browsers are you seeing the problem on?

No response

Relevant log output
No request is sent; the export service returns before any HTTP call.
Dominant language
Scala
Stars
316
Forks
192
Avg merge
4d 17h
Merged PRs (30d)
141

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/texera

All issues in apache/texera

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.