suyashj1231 commented on PR #5607: URL: https://github.com/apache/texera/pull/5607#issuecomment-4675684086
Hi, yes tested it locally to be sure. Ran the file-service from this branch inside the full single-node docker stack (everything else same), then just used the app normally in the browser: Workflow: - created a dataset + uploaded a csv = multipart upload went through fine, committed as v1, file renders in the viewer - downloaded the single file and the version zip = both match the original exactly - pointed a CSV File Scan operator at the dataset file and ran the workflow = completed, all 3 rows came through also tried hitting a missing file and got a clean 404 with the new "LakeFS resource not found" message instead of a raw 500, so the handler is doing its thing outside the failure-injection tests too. <img width="1440" height="900" alt="08-dataset-created" src="https://github.com/user-attachments/assets/dcb5bc38-3740-4822-bca4-b38ff2b458ab"; /> <img width="1440" height="900" alt="11-version-created" src="https://github.com/user-attachments/assets/5dc58691-d213-40c5-8483-ae59bac3ff07"; /> <img width="1440" height="900" alt="22-file-picked" src="https://github.com/user-attachments/assets/e9061525-81aa-4edc-812a-9fc4398046b3"; /> <img width="1440" height="900" alt="42-run-done" src="https://github.com/user-attachments/assets/6d32ca39-cfd6-4b80-902d-0c8e13691cc5"; /> -- 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]
