tanishqgandhi1908 opened a new issue, #8927:
URL: https://github.com/apache/texera/issues/8927

   ### What happened?
   
   In the dataset version picker (File Lister’s Dataset field, and Python UDF 
dataset parameters), switching to another dataset keeps the previously picked 
version and path. The version box still shows the old version name, Select 
stays enabled, and clicking it fills the field with the previous dataset’s path.
   
   Expected: switching datasets clears the version and path until a version of 
the new dataset is picked, as the model picker already does.
   
   Pick dataset A (owner-access-demo) and v1:
   
   <img width="1440" height="900" alt="Image" 
src="https://github.com/user-attachments/assets/9799e9ee-8ef2-4e05-b52c-a57d7de264d9";
 />
   
   Switch to dataset B (weather-readings) without picking a version. “v1” is 
still shown and Select is enabled:
   
   <img width="1440" height="900" alt="Image" 
src="https://github.com/user-attachments/assets/9d955c47-1696-4bc9-9126-d3157a1939e8";
 />
   
   After clicking Select, the field holds A’s path, 
/dataset/[email protected]/owner-access-demo/v1:
   
   <img width="1440" height="900" alt="Image" 
src="https://github.com/user-attachments/assets/d4248410-d9e4-42b5-b85c-b2db58611d27";
 />
   
   ### How to reproduce?
   
   1. Add a File Lister operator and click “Select Dataset”.
   2. Pick a dataset and a version.
   3. Switch to a different dataset without touching the version box.
   4. Click Select. The field gets the first dataset’s path.
   
   ### 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]

Reply via email to