cloud-fan commented on issue #28026: [SPARK-31257][SQL] Unify create table syntax URL: https://github.com/apache/spark/pull/28026#issuecomment-613498890 @rdblue Let's also think about the end-users. For example, currently we can say: "the EXTERNAL keyword means the table is external, and if the LOCATION is specified, it implicitly indicates EXTERNAL". If we add the "PROP_EXTERNAL", then it becomes: "the meaning of EXTERNAL depends on the catalog implementation". I think that makes Spark less user-friendly, as the behavior is less clear. The same thing applies to SERDEPROPERTIES, TBLPROPERTIES, and OPTIONS. I understand that we need to distinguish them by adding the "option." prefix, but what's the story for end-users? What they should put as OPTIONS and what for TBLPROPERTIES?
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
