[GitHub] HyukjinKwon edited a comment on issue #23879: [SPARK-26979][SQL] Add missing column name support for SQL functions

[GitBox <gi...@apache.org>]

HyukjinKwon edited a comment on issue #23879: [SPARK-26979][SQL] Add missing column name support for SQL functions
URL: https://github.com/apache/spark/pull/23879#issuecomment-466753983
 
 
   Yes, it costs maintenance overhead - exposed APIs are getting larger. You're not already inventing your a cart by calling `lower(col(...))` that leverages Spark SQL engine.
   
   Not all SQL functions work like this. Spark already has tons of APIs. What kind of attrition does it cause to new learners? Inconsistency? In that case we should rather focus on removing string overridden versions. We should rather focus on reducing APIs rather than adding them. Otherwise, all systems will end up with some APIs like sending an email at the end.
   
   Spark community had a discussion about it before and people tend to think about rather removing string overridden versions.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org