[ 
https://issues.apache.org/jira/browse/SPARK-24268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marco Gaido updated SPARK-24268:
--------------------------------
    Description: 
In SPARK-22893 there was a tentative to unify the way dataTypes are reported in 
error messages. There, we decided to use always {{dataType.simpleString}}. 
Unfortunately, we missed many places where this still needed to be fixed. 
Moreover, it turns out that the right method to use is not {{simpleString}}, 
but we should use {{catalogString}} instead (for further details please check 
the discussion in the PR ).

So we should update all the missing places in order to provide error messages 
coherently throughout the project.

  was:
In SPARK-22893 there was a tentative to unify the way dataTypes are reported in 
error messages. There, we decided to use always {{dataType.simpleString}}. 
Unfortunately, we missed many places where this still needed to be fixed. 
Moreover, it turns out that the right method to use is not {{simpleString}}, 
but we should use {{catalogString}} instead.

So we should update all the missing places in order to provide error messages 
coherently throughout the project.


> DataType in error messages are not coherent
> -------------------------------------------
>
>                 Key: SPARK-24268
>                 URL: https://issues.apache.org/jira/browse/SPARK-24268
>             Project: Spark
>          Issue Type: Improvement
>          Components: ML, SQL
>    Affects Versions: 2.3.0
>            Reporter: Marco Gaido
>            Assignee: Marco Gaido
>            Priority: Minor
>
> In SPARK-22893 there was a tentative to unify the way dataTypes are reported 
> in error messages. There, we decided to use always {{dataType.simpleString}}. 
> Unfortunately, we missed many places where this still needed to be fixed. 
> Moreover, it turns out that the right method to use is not {{simpleString}}, 
> but we should use {{catalogString}} instead (for further details please check 
> the discussion in the PR ).
> So we should update all the missing places in order to provide error messages 
> coherently throughout the project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to