yangzhang75 opened a new issue, #8538: URL: https://github.com/apache/texera/issues/8538
### What happened? On a default local deployment (bin/local-dev.sh or bin/single-node), results cannot be downloaded, and nothing tells the user why. The download icon on every result cell renders regardless of configuration. Clicking it opens the export dialog; choosing Destination = local and confirming does nothing: no request is sent and no message is shown. The cause is `export-execution-result-enabled`, which defaults to `false` in `common/config/src/main/resources/gui.conf`. `WorkflowResultExportService.performExport` returns early on that flag without any notification. The rest of the UI already honours the switch: the top-menu Export entry is disabled and the context-menu entry is hidden. Only the per-cell download button was left out, so it looks like a broken feature rather than a disabled one. The k8s chart turns the switch on explicitly; single-node and local-dev do not, so those deployments lose the feature silently. Expected: either downloading works out of the box, or the UI says clearly that result export is disabled on this deployment. Proposal: 1. Make the per-cell download button honour the switch the same way the menu does (disabled, with a tooltip saying why). I have a small frontend fix with tests ready and can open a PR. 2. Consider defaulting the switch to true, since every interactive deployment already turns it on. ### How to reproduce? 1. Start Texera with the default gui.conf (bin/local-dev.sh up, or bin/single-node), so export-execution-result-enabled is false. 2. Run any workflow and open the result panel. 3. Click the cloud-download icon on any cell. The export dialog opens. 4. Keep the filename, choose Destination = local, click Export. 5. Nothing happens. DevTools > Network shows no request. Meanwhile the top-menu Export entry is greyed out, which is the behaviour the cell button should share. Setting GUI_WORKFLOW_WORKSPACE_EXPORT_EXECUTION_RESULT_ENABLED=true and restarting makes the same button work, which confirms the switch is the only cause. ### 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 ```shell No request is sent; the export service returns before any HTTP call. ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
