[
https://issues.apache.org/jira/browse/LENS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048541#comment-15048541
]
Puneet Gupta commented on LENS-743:
-----------------------------------
*Different IDs Approach*
*Pros*
1. Clean separation between runs with separate log files/DB entry for each run
*Cons*
We have to add extra functionality that user has to be aware of. May be retry
option should be switched of by default so that existing users are not affected.
1. Api to access all linked ids.
2. Existing apis may need option to show the status/details/result/etc for the
latest retry by passing the original handle ( for convenience sake ) ?
Please add to the list ..
> Query failure retries for transient errors
> ------------------------------------------
>
> Key: LENS-743
> URL: https://issues.apache.org/jira/browse/LENS-743
> Project: Apache Lens
> Issue Type: Improvement
> Components: server
> Reporter: Amareshwari Sriramadasu
> Assignee: Rajat Khandelwal
> Labels: newbie
>
> There have to be retries for query failures for transient errors like network
> errors (Hive server not reachable/ Metastore not reachable/ DB not
> reachable). Retries should be available for each phase - submission,
> execution, updating status, fetching results and formatting.
> Right now, any such failure results in marking query as failed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
