carloea2 opened a new issue, #8209: URL: https://github.com/apache/texera/issues/8209
### What happened? ArrowTableTupleProvider tracks row positions using the first column's chunk layout and applies those chunk coordinates to every column. Valid Arrow tables can have different chunk boundaries per column, causing later fields to throw IndexError or read the wrong position. Before: different column chunk boundaries -> second row throws IndexError After: different column chunk boundaries -> rows are read by global index ### How to reproduce? Create a three-row Arrow table whose first column has chunk lengths 2 and 1 while its second column has chunk lengths 1 and 2. Read the second row through ArrowTableTupleProvider. ### Version/Branch 1.3.0-incubating-SNAPSHOT (main) ### Commit Hash 70c21145887920528d7d5540e3fb790b43e8b759 ### What browsers are you seeing the problem on? Not browser-specific. ### Relevant log output ```text chunk_layouts= [2, 2] row1= 1 10 row2_a= 2 IndexError: index out of bounds ``` -- 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]
