HeartSaVioR commented on issue #28026: [SPARK-31257][SQL] Unify create table 
syntax (WIP)
URL: https://github.com/apache/spark/pull/28026#issuecomment-606310697
 
 
   Thanks for the detailed answer. Really appreciated.
   
   I misunderstood something as you commented, but it seems to come from 
something which is not addressed yet and the plan was not shared. Without 
sharing the detailed plan (TODO) I wonder the review can be done correctly. 
Maybe we'd be better to wait for you to make more progress?
   
   Btw, this change doesn't seem to be trivial but PR description has shortage 
of information - one line per a major change. I guess we tend to describe at 
least how it works in high level on the PR description so that commit message 
itself becomes informative. We may want to get it once the PR is ready to merge.
   
   Back to the comment, your plan looks promising to me, but I'm not an expert 
of DSv2 (what I originally pointed out was ambiguous parser syntaxes, not about 
DSv2) so I feel I'm not qualified.
   
   > Speaking of well-formed, I think it might be reasonable to ensure that 
either a provider or serde info is present, but not both. That would raise an 
exception if both USING and STORED AS or SERDE clauses were used. I think 
that's probably reasonable. In that case, we could skip the checks above. What 
do you think?
   
   Would we like to disallow STORED AS/SERDE clauses if the provider is 
specified to Hive via USING clause? That would be still OK if we provide good 
error message and guide alternatives (either doc or error message).

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

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

Reply via email to