kz930 opened a new issue, #8735: URL: https://github.com/apache/texera/issues/8735
### Feature Summary When a port finishes with no rows, a Python table operator gets a DataFrame with no columns. Any operator that names a column then fails, so a Sort after a Filter that matched nothing fails the whole run. #8487 has the reproduction. #8487 was closed so it would not hold up unrelated work, and the question itself was left open. One view is that a table with no rows carries no schema by design. Another is that a table with no data can still be a real table, like a filter that matched nothing or a file with only a header, and its schema is information worth saving. This choice decides what every table operator sees on an empty input, so I'd like to hear from others before writing any code. ### Proposed Solution or Design Three options, none picked yet: 1. Keep today's behavior. A port with no rows reaches the operator with no columns, and an operator that names a column fails. 2. The engine skips `process_table` for a port with no rows and finishes it quietly. 3. The operator gets the port's declared columns with no rows under them. #8488 did this and was closed. ### Affected Area Workflow Engine (Amber) -- 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]
