hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13131) TezWork queryName can be null after HIVE-12523
Date Wed, 24 Feb 2016 18:56:18 GMT

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

Jason Dere commented on HIVE-13131:
-----------------------------------

It looks like the previous behavior was to always set it to the dagId.  I'm not too familiar
with the usage here - if you think it should be an error then we can do that too.  However
if the conf passed in is null I think we should still default to dagId.

> TezWork queryName can be null after HIVE-12523
> ----------------------------------------------
>
>                 Key: HIVE-13131
>                 URL: https://issues.apache.org/jira/browse/HIVE-13131
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>         Attachments: HIVE-13131.1.patch
>
>
> Looks like after HIVE-12523, the queryName field can be null, either if the conf passed
in is null, or if the conf does not contain the necessary settings.



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

Mime
View raw message