devinjdangelo commented on issue #9465: URL: https://github.com/apache/arrow-datafusion/issues/9465#issuecomment-1986859943
> If we need to break backwards compatibility, I think it should be discussed more widely I think that we either should - break backwards compatibility and throw an error when a column is declared as both a regular column and a partition column - rework internal logic of partitioned ListingTables so they respect the original order the columns were declared in by the user, even if some are partitioned columns I favor the first option and believe it would be much easier to implement. We could perhaps go for a phased approach where we deprecate the existing syntax with a warning of why it is not recommended, though maintaining both syntaxes would be more complex. With all that said if we are against a breaking change, we could simply update documentation to increase visibility into the existing behavior and especially clarify that partition columns must be moved to the end when inserting data. -- 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]
