[jira] [Commented] (HIVE-13633) LLAP: better handling of container id, attempt number, fragment number for external clients

["Sergey Shelukhin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261324#comment-15261324 ] 

Sergey Shelukhin commented on HIVE-13633:
-----------------------------------------

[~hagleitn] [~sseth] fyi relevant to signing

> LLAP: better handling of container id, attempt number, fragment number for external clients
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13633
>                 URL: https://issues.apache.org/jira/browse/HIVE-13633
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Siddharth Seth
>
> From the API discussion. We want to make sure that fields coming from external clients that are used by LLAP as various kinds of IDs are handled correctly and misbehaving clients do not cause bizarre issues. Some of the fields may not be practically signable (e.g. attempt number, even we implemented some signing scheme it would just be ugly to re-sign to retry), also someone could just submit the same signed split twice. 
> The fields are - fragment number (and various other parts of ID, presumably), attempt number, container id, maybe others.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)