kunwp1 opened a new issue, #8873:
URL: https://github.com/apache/texera/issues/8873
### What happened?
After uploading a file to a dataset, I typed a 135-character description
into the "Describe the new version" box and clicked Submit. The page showed
"Version creation failed: There was an error processing your request. It has
been logged (ID 33ec104f33896f01)." After I reloaded the page, it said "No
version is selected" and "No pending changes", so the uploaded file was visible
neither as a staged change nor in any version. The file had already been
committed to LakeFS but no version row was created for it, so the dataset page
and the database no longer agree. The file only showed up again in the next
version I created.
Root cause. createDatasetVersion builds the name v{N} - {description} and
commits to LakeFS first, then inserts the dataset_version row
(DatasetResource.scala:446-481). dataset_version.name is VARCHAR(128), so the
insert fails after the commit, and the commit is outside the DB transaction.
### How to reproduce?
Open a dataset you can write to → drop any file onto "Create New Version" →
enter a description of 124+ characters (the v1 - prefix counts toward 128) →
Submit → reload.
https://github.com/user-attachments/assets/97a22706-45df-48f2-b0ad-18cff70d7903
### Version/Branch
1.4.0-incubating-SNAPSHOT (main)
### Commit Hash (Optional)
_No response_
### What browsers are you seeing the problem on?
_No response_
### Relevant log output
```shell
```
--
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]
