[
https://issues.apache.org/jira/browse/HIVE-13771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294609#comment-15294609
]
Sergey Shelukhin edited comment on HIVE-13771 at 5/21/16 1:08 AM:
------------------------------------------------------------------
Tiny patch on top of other patches. The patch that introduces coordinator is
the real blocker but I don't remember which one that is. [~jdere] [~sseth] does
this method make sense to you?
Is it ok to generate bogus cluster timestamp, or does it have to be a real
timestamp?
was (Author: sershe):
Tiny patch on top of other patches. The patch that introduces coordinator is
the real blocker but I don't remember which one it is. [~jdere] [~sseth] does
this method make sense to you?
Is it ok to generate bogus cluster timestamp, or does it have to be a real
timestamp?
> LLAPIF: generate app ID
> -----------------------
>
> Key: HIVE-13771
> URL: https://issues.apache.org/jira/browse/HIVE-13771
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-13771.patch
>
>
> See comments in the HIVE-13675 patch. The uniqueness needs to be ensured; the
> user may be allowed to supply a prefix (e.g. his YARN app Id, if any) for
> ease of tracking
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
