[jira] [Commented] (HIVE-14023) LLAP: Make the Hive query id available in ContainerRunner

2016-11-20 Thread JIRA

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

Sergio Peña commented on HIVE-14023:


I'm moving this JIRA out of 2.1.1 release as it is not a blocker nor critical 
for a 2.1.1 RC version. Feel free to commit it to branch 2.1 if the patch is 
ready before the release.

> LLAP: Make the Hive query id available in ContainerRunner
> -
>
> Key: HIVE-14023
> URL: https://issues.apache.org/jira/browse/HIVE-14023
> Project: Hive
>  Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Fix For: 2.2.0
>
> Attachments: HIVE-14023.01.patch, HIVE-14023.02.patch
>
>
> Needed to generate logs per query.
> We can use the dag identifier for now, but that isn't very useful. (The 
> queryId may not be too useful either if users cannot find it - but that's 
> better than a dagIdentifier)
> The queryId is available right now after the Processor starts, which is too 
> late for log changes.



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


[jira] [Commented] (HIVE-14023) LLAP: Make the Hive query id available in ContainerRunner

2016-06-21 Thread Siddharth Seth (JIRA)

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

Siddharth Seth commented on HIVE-14023:
---

Test failures are unrelated. Thanks for the reviews [~sershe]. Committing.

> LLAP: Make the Hive query id available in ContainerRunner
> -
>
> Key: HIVE-14023
> URL: https://issues.apache.org/jira/browse/HIVE-14023
> Project: Hive
>  Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Attachments: HIVE-14023.01.patch, HIVE-14023.02.patch
>
>
> Needed to generate logs per query.
> We can use the dag identifier for now, but that isn't very useful. (The 
> queryId may not be too useful either if users cannot find it - but that's 
> better than a dagIdentifier)
> The queryId is available right now after the Processor starts, which is too 
> late for log changes.



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


[jira] [Commented] (HIVE-14023) LLAP: Make the Hive query id available in ContainerRunner

2016-06-20 Thread Sergey Shelukhin (JIRA)

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

Sergey Shelukhin commented on HIVE-14023:
-

+1

> LLAP: Make the Hive query id available in ContainerRunner
> -
>
> Key: HIVE-14023
> URL: https://issues.apache.org/jira/browse/HIVE-14023
> Project: Hive
>  Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Attachments: HIVE-14023.01.patch, HIVE-14023.02.patch
>
>
> Needed to generate logs per query.
> We can use the dag identifier for now, but that isn't very useful. (The 
> queryId may not be too useful either if users cannot find it - but that's 
> better than a dagIdentifier)
> The queryId is available right now after the Processor starts, which is too 
> late for log changes.



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


[jira] [Commented] (HIVE-14023) LLAP: Make the Hive query id available in ContainerRunner

2016-06-17 Thread Hive QA (JIRA)

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

Hive QA commented on HIVE-14023:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12811293/HIVE-14023.02.patch

{color:green}SUCCESS:{color} +1 due to 4 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 11 failed/errored test(s), 10235 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_acid_globallimit
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_constantPropagateForSubQuery
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_list_bucket_dml_12
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_list_bucket_dml_13
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_repair
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_stats_list_bucket
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_subquery_multiinsert
org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver_index_bitmap3
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_table_nonprintable
org.apache.hadoop.hive.ql.metadata.TestHiveMetaStoreChecker.testPartitionsCheck
org.apache.hadoop.hive.ql.metadata.TestHiveMetaStoreChecker.testTableCheck
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-MASTER-Build/153/testReport
Console output: 
https://builds.apache.org/job/PreCommit-HIVE-MASTER-Build/153/console
Test logs: 
http://ec2-50-18-27-0.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-MASTER-Build-153/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 11 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12811293 - PreCommit-HIVE-MASTER-Build

> LLAP: Make the Hive query id available in ContainerRunner
> -
>
> Key: HIVE-14023
> URL: https://issues.apache.org/jira/browse/HIVE-14023
> Project: Hive
>  Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Attachments: HIVE-14023.01.patch, HIVE-14023.02.patch
>
>
> Needed to generate logs per query.
> We can use the dag identifier for now, but that isn't very useful. (The 
> queryId may not be too useful either if users cannot find it - but that's 
> better than a dagIdentifier)
> The queryId is available right now after the Processor starts, which is too 
> late for log changes.



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


[jira] [Commented] (HIVE-14023) LLAP: Make the Hive query id available in ContainerRunner

2016-06-16 Thread Siddharth Seth (JIRA)

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

Siddharth Seth commented on HIVE-14023:
---

There was a series of bugs around this, and I believe they were resolved.
Any idea on accessing the query string from the conf, is it stored ?

RB: https://reviews.apache.org/r/48818/

> LLAP: Make the Hive query id available in ContainerRunner
> -
>
> Key: HIVE-14023
> URL: https://issues.apache.org/jira/browse/HIVE-14023
> Project: Hive
>  Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Attachments: HIVE-14023.01.patch
>
>
> Needed to generate logs per query.
> We can use the dag identifier for now, but that isn't very useful. (The 
> queryId may not be too useful either if users cannot find it - but that's 
> better than a dagIdentifier)
> The queryId is available right now after the Processor starts, which is too 
> late for log changes.



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


[jira] [Commented] (HIVE-14023) LLAP: Make the Hive query id available in ContainerRunner

2016-06-16 Thread Sergey Shelukhin (JIRA)

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

Sergey Shelukhin commented on HIVE-14023:
-

I think I saw queryID being reused bug somewhere... I thiought that was fixed. 
[~vikram.dixit] and [~hagleitn] might know better... 

Can you post a RB?

> LLAP: Make the Hive query id available in ContainerRunner
> -
>
> Key: HIVE-14023
> URL: https://issues.apache.org/jira/browse/HIVE-14023
> Project: Hive
>  Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Attachments: HIVE-14023.01.patch
>
>
> Needed to generate logs per query.
> We can use the dag identifier for now, but that isn't very useful. (The 
> queryId may not be too useful either if users cannot find it - but that's 
> better than a dagIdentifier)
> The queryId is available right now after the Processor starts, which is too 
> late for log changes.



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