Github user gatorsmile commented on the pull request:

    https://github.com/apache/spark/pull/12801#issuecomment-217070994
  
    Regarding SPARK-15026, my major concern is we might get JIRAs if the 
previous `Drop Partition` command only drops a subset of partitions. If users 
issue the same command, they will get an error message:
    ```
    org.apache.spark.sql.AnalysisException: partition to drop 'Map(ds -> 
2008-04-08)' does not exist in table 'exttable_with_partitions' database 
'default';
    ```
    
    If you do not think this is a big deal, we need to issue a better error 
message. Let users know which partitions have been dropped and which partitions 
have not been dropped. This error message could be pretty long if one partial 
partition spec corresponds a long list of partitions. I am not sure if there 
exists any length limit of an exception message.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to