eugenegujing opened a new issue, #7345: URL: https://github.com/apache/texera/issues/7345
### What happened? `FileScanUtils.createTuplesFromFile` computes the end of its slice as `offset + limit.getOrElse(Int.MaxValue)`. When the user sets an Offset and leaves Limit empty, that addition overflows to a negative number and the operator emits **no rows at all**, silently and with no error, and the workflow reports success. Any Offset ≥ 1 with an empty Limit is affected. **Expected:** Offset = 1 with an empty Limit reads from line 1 to the end of the file. Both `FileScan` and `FileScanOp` are affected, since `FileScanSourceOpExec` and `FileScanOpExec` both delegate to this helper. ### How to reproduce? 1. Upload a five-line text file (`a`, `b`, `c`, `d`, `e` on separate lines) as a dataset. 2. Add a **File Scan** operator and point its **File** property at that file. 3. Leave Attribute Type at its default (`string`, i.e. one tuple per line). 4. Set **Offset (lines)** to `1`. Leave **Limit (lines)** empty. 5. Run the workflow and view the results. Observed: zero rows, with the workflow reporting success. Expected: four rows — `b`, `c`, `d`, `e`. ### Version/Branch 1.3.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]
