tv42 commented on issue #13190: URL: https://github.com/apache/datafusion/issues/13190#issuecomment-2638095485
And a debugging hint for others, because this might not be a Datafusion bug in all cases: I refactored my TableProvider and forgot to apply the given Projection to the schema it returns. This caused "column index 1" to not mean what it was supposed to mean. This same bug on my part also caused ``` query failed: Internal error: Physical input schema should be the same as the one converted from logical input schema. Differences: - Different number of fields: (physical) 2 vs (logical) 0. This was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker ``` ``` Internal error: Input field name a does not match with the projection expression b. This was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker [SQL] UPDATE kanto.myschema.mytable SET a=41 WHERE b=7; ``` ``` test panicked: index out of bounds: the len is 1 but the index is 1 ``` (backtrace said it was a `.column(idx)` deep in the guts of Datafusion, async meant backtrace didn't refer to my code at all) -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
