szehon-ho opened a new pull request, #50793: URL: https://github.com/apache/spark/pull/50793
### What changes were proposed in this pull request? A very small follow up for https://github.com/apache/spark/pull/50523/files In that PR, I had changed some method to use Column... In some environment it may go to this test package's Column (org.apache.spark.sql.Column), when in fact it should go to org.apache.spark.sql.connector.catalog.Column (ie, DSV2 Column) However, there is some ambiguity in the import, so I think its better to have an alias to avoid this import shadow problem, following example of DataSourceV2SQLSuite Changing to use an alias ### Why are the changes needed? Scala import precedence seems a bit not-easily predictable , defined by the compilation unit, which may change based on tool. See: https://www.scala-lang.org/files/archive/spec/2.12/02-identifiers-names-and-scopes.html. I saw this error in another build environment. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Test change, existing test ran. ### Was this patch authored or co-authored using generative AI tooling? No -- 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: reviews-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
