[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Resolution: Fixed
Fix Version/s: 3.0.0
Status: Resolved (was: Patch Available)
Committed to master branch. Thanks [~xuefuz] and [~asherman] for the review!
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Fix For: 3.0.0
>
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch,
> HIVE-18283.2.patch, HIVE-18283.3.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: HIVE-18283.3.patch
Thanks [~xuefuz] and [~asherman] for the comments! They are very helpful.
Attaching patch v3 to address the comments.
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch,
> HIVE-18283.2.patch, HIVE-18283.3.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: HIVE-18283.2.patch
Patch v2 to fix check style issues.
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch,
> HIVE-18283.2.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: HIVE-18283.1.patch
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: (was: HIVE-18283.1.patch)
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: (was: HIVE-18283.1.patch)
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: HIVE-18283.1.patch
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Status: Patch Available (was: Open)
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: HIVE-18283.1.patch
Attaching patch v1 with a test for {{SparkSessionImpl#getHiveException()}}.
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch, HIVE-18283.1.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HIVE-18283) Better error message and error code for HoS exceptions
[
https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-18283:
Attachment: HIVE-18283.0.patch
Attaching patch v0. cc [~xuefuz].
> Better error message and error code for HoS exceptions
> --
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
>Reporter: Chao Sun
>Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors,
> user will see an error code 1 followed by a lengthy stacktrace. This is not
> ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply
> inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user
> have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which
> user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical
> error messages for different HoS errors. We can take advantage of the
> existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
