[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

The tests from "TestOperationLoggingAPIWithMr" and 
"TestOperationLoggingAPIWithTez" would fail without this fix. However looks 
like we are seeing some issues with the test itself (see below). Given that 
there is no active development for hive1, I will mark this JIRA "won't fix".

TestOperationLoggingAPIWithMr - did not produce a TEST-*.xml file (likely timed 
out) (batchId=384)
TestOperationLoggingAPIWithTez - did not produce a TEST-*.xml file (likely 
timed out) (batchId=385)

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


I don't have an answer for that. We haven't been too active on adding more 
fixes on the branch-1, so I believe we would need to improve the tests from it. 
Have you investigating the type of errors happening there?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

[~spena], [~thejas] Do you know why there are still 130+ test failures for 
branch-1?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-14476:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835870/HIVE-14476.1-branch-1.2.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 134 failed/errored test(s), 7899 tests 
executed
*Failed tests:*
{noformat}
TestAdminUser - did not produce a TEST-*.xml file (likely timed out) 
(batchId=340)
TestAuthorizationPreEventListener - did not produce a TEST-*.xml file (likely 
timed out) (batchId=371)
TestAuthzApiEmbedAuthorizerInEmbed - did not produce a TEST-*.xml file (likely 
timed out) (batchId=350)
TestAuthzApiEmbedAuthorizerInRemote - did not produce a TEST-*.xml file (likely 
timed out) (batchId=356)
TestBeeLineWithArgs - did not produce a TEST-*.xml file (likely timed out) 
(batchId=378)
TestCLIAuthzSessionContext - did not produce a TEST-*.xml file (likely timed 
out) (batchId=394)
TestClientSideAuthorizationProvider - did not produce a TEST-*.xml file (likely 
timed out) (batchId=370)
TestCompactor - did not produce a TEST-*.xml file (likely timed out) 
(batchId=360)
TestCreateUdfEntities - did not produce a TEST-*.xml file (likely timed out) 
(batchId=359)
TestCustomAuthentication - did not produce a TEST-*.xml file (likely timed out) 
(batchId=379)
TestDBTokenStore - did not produce a TEST-*.xml file (likely timed out) 
(batchId=325)
TestDDLWithRemoteMetastoreSecondNamenode - did not produce a TEST-*.xml file 
(likely timed out) (batchId=358)
TestDynamicSerDe - did not produce a TEST-*.xml file (likely timed out) 
(batchId=328)
TestEmbeddedHiveMetaStore - did not produce a TEST-*.xml file (likely timed 
out) (batchId=337)
TestEmbeddedThriftBinaryCLIService - did not produce a TEST-*.xml file (likely 
timed out) (batchId=382)
TestFilterHooks - did not produce a TEST-*.xml file (likely timed out) 
(batchId=332)
TestFolderPermissions - did not produce a TEST-*.xml file (likely timed out) 
(batchId=365)
TestHS2AuthzContext - did not produce a TEST-*.xml file (likely timed out) 
(batchId=397)
TestHS2AuthzSessionContext - did not produce a TEST-*.xml file (likely timed 
out) (batchId=398)
TestHS2ImpersonationWithRemoteMS - did not produce a TEST-*.xml file (likely 
timed out) (batchId=386)
TestHiveAuthorizerCheckInvocation - did not produce a TEST-*.xml file (likely 
timed out) (batchId=374)
TestHiveAuthorizerShowFilters - did not produce a TEST-*.xml file (likely timed 
out) (batchId=373)
TestHiveHistory - did not produce a TEST-*.xml file (likely timed out) 
(batchId=376)
TestHiveMetaStoreTxns - did not produce a TEST-*.xml file (likely timed out) 
(batchId=352)
TestHiveMetaStoreWithEnvironmentContext - did not produce a TEST-*.xml file 
(likely timed out) (batchId=342)
TestHiveMetaTool - did not produce a TEST-*.xml file (likely timed out) 
(batchId=355)
TestHiveServer2 - did not produce a TEST-*.xml file (likely timed out) 
(batchId=400)
TestHiveServer2SessionTimeout - did not produce a TEST-*.xml file (likely timed 
out) (batchId=401)
TestHiveSessionImpl - did not produce a TEST-*.xml file (likely timed out) 
(batchId=383)
TestHs2Hooks - did not produce a TEST-*.xml file (likely timed out) 
(batchId=357)
TestHs2HooksWithMiniKdc - did not produce a TEST-*.xml file (likely timed out) 
(batchId=429)
TestJdbcDriver2 - did not produce a TEST-*.xml file (likely timed out) 
(batchId=388)
TestJdbcMetadataApiAuth - did not produce a TEST-*.xml file (likely timed out) 
(batchId=399)
TestJdbcWithLocalClusterSpark - did not produce a TEST-*.xml file (likely timed 
out) (batchId=393)
TestJdbcWithMiniHS2 - did not produce a TEST-*.xml file (likely timed out) 
(batchId=390)
TestJdbcWithMiniKdc - did not produce a TEST-*.xml file (likely timed out) 
(batchId=426)
TestJdbcWithMiniKdcCookie - did not produce a TEST-*.xml file (likely timed 
out) (batchId=425)
TestJdbcWithMiniKdcSQLAuthBinary - did not produce a TEST-*.xml file (likely 
timed out) (batchId=423)
TestJdbcWithMiniKdcSQLAuthHttp - did not produce a TEST-*.xml file (likely 
timed out) (batchId=428)
TestJdbcWithMiniMr - did not produce a TEST-*.xml file (likely timed out) 
(batchId=389)
TestJdbcWithSQLAuthUDFBlacklist - did not produce a TEST-*.xml file (likely 
timed out) (batchId=395)
TestJdbcWithSQLAuthorization - did not produce a TEST-*.xml file (likely timed 
out) (batchId=396)
TestLocationQueries - did not produce a TEST-*.xml file (likely timed out) 
(batchId=363)
TestMTQueries - did not produce a TEST-*.xml file (likely timed out) 
(batchId=361)
TestMarkPartition - did not produce a TEST-*.xml file (likely timed out) 
(batchId=349)
TestMarkPartitionRemote - did not produce a TEST-*.xml file (likely timed out) 
(batchId=353)
TestMetaStoreAuthorization - did not produce a TEST-*.xml file (likely timed 
out) 

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


These 3 tests may be fixed with HIVE-13587
{noformat}
org.apache.hive.minikdc.TestHiveAuthFactory.testStartTokenManagerForDBTokenStore
 (batchId=426)
org.apache.hive.minikdc.TestHiveAuthFactory.testStartTokenManagerForMemoryTokenStore
 (batchId=426)
org.apache.hive.minikdc.TestMiniHiveKdc.testLogin (batchId=423)
{noformat}

These 3 tests are also failing on master
{noformat}
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJarWithoutAddDriverClazz[0]
 (batchId=250)
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[0] (batchId=250)
org.apache.hive.beeline.TestBeelineArgParsing.testAddLocalJar[1] (batchId=250
{noformat}

I don't know what could be causing the failures on the other tests. Are they 
also failing locally?
If they do fail locally, I usually try to search for the commit that is causing 
those failures. That commit can give you a better idea how to fix it. I use 
'git bisect' to investigate the commit.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

We are seeing test failures in branch-1 as well: 
https://issues.apache.org/jira/browse/HIVE-15049
[~spena] Do you have quick thoughts on how to fix these failures?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-14476:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835870/HIVE-14476.1-branch-1.2.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 137 failed/errored test(s), 7897 tests 
executed
*Failed tests:*
{noformat}
TestAdminUser - did not produce a TEST-*.xml file (likely timed out) 
(batchId=339)
TestAuthorizationPreEventListener - did not produce a TEST-*.xml file (likely 
timed out) (batchId=370)
TestAuthzApiEmbedAuthorizerInEmbed - did not produce a TEST-*.xml file (likely 
timed out) (batchId=349)
TestAuthzApiEmbedAuthorizerInRemote - did not produce a TEST-*.xml file (likely 
timed out) (batchId=355)
TestBeeLineWithArgs - did not produce a TEST-*.xml file (likely timed out) 
(batchId=377)
TestCLIAuthzSessionContext - did not produce a TEST-*.xml file (likely timed 
out) (batchId=393)
TestClientSideAuthorizationProvider - did not produce a TEST-*.xml file (likely 
timed out) (batchId=369)
TestCompactor - did not produce a TEST-*.xml file (likely timed out) 
(batchId=359)
TestCreateUdfEntities - did not produce a TEST-*.xml file (likely timed out) 
(batchId=358)
TestCustomAuthentication - did not produce a TEST-*.xml file (likely timed out) 
(batchId=378)
TestDBTokenStore - did not produce a TEST-*.xml file (likely timed out) 
(batchId=324)
TestDDLWithRemoteMetastoreSecondNamenode - did not produce a TEST-*.xml file 
(likely timed out) (batchId=357)
TestDynamicSerDe - did not produce a TEST-*.xml file (likely timed out) 
(batchId=327)
TestEmbeddedHiveMetaStore - did not produce a TEST-*.xml file (likely timed 
out) (batchId=336)
TestEmbeddedThriftBinaryCLIService - did not produce a TEST-*.xml file (likely 
timed out) (batchId=381)
TestFilterHooks - did not produce a TEST-*.xml file (likely timed out) 
(batchId=331)
TestFolderPermissions - did not produce a TEST-*.xml file (likely timed out) 
(batchId=364)
TestHS2AuthzContext - did not produce a TEST-*.xml file (likely timed out) 
(batchId=396)
TestHS2AuthzSessionContext - did not produce a TEST-*.xml file (likely timed 
out) (batchId=397)
TestHS2ImpersonationWithRemoteMS - did not produce a TEST-*.xml file (likely 
timed out) (batchId=385)
TestHiveAuthorizerCheckInvocation - did not produce a TEST-*.xml file (likely 
timed out) (batchId=373)
TestHiveAuthorizerShowFilters - did not produce a TEST-*.xml file (likely timed 
out) (batchId=372)
TestHiveHistory - did not produce a TEST-*.xml file (likely timed out) 
(batchId=375)
TestHiveMetaStoreTxns - did not produce a TEST-*.xml file (likely timed out) 
(batchId=351)
TestHiveMetaStoreWithEnvironmentContext - did not produce a TEST-*.xml file 
(likely timed out) (batchId=341)
TestHiveMetaTool - did not produce a TEST-*.xml file (likely timed out) 
(batchId=354)
TestHiveServer2 - did not produce a TEST-*.xml file (likely timed out) 
(batchId=399)
TestHiveServer2SessionTimeout - did not produce a TEST-*.xml file (likely timed 
out) (batchId=400)
TestHiveSessionImpl - did not produce a TEST-*.xml file (likely timed out) 
(batchId=382)
TestHs2Hooks - did not produce a TEST-*.xml file (likely timed out) 
(batchId=356)
TestHs2HooksWithMiniKdc - did not produce a TEST-*.xml file (likely timed out) 
(batchId=428)
TestJdbcDriver2 - did not produce a TEST-*.xml file (likely timed out) 
(batchId=387)
TestJdbcMetadataApiAuth - did not produce a TEST-*.xml file (likely timed out) 
(batchId=398)
TestJdbcWithLocalClusterSpark - did not produce a TEST-*.xml file (likely timed 
out) (batchId=392)
TestJdbcWithMiniHS2 - did not produce a TEST-*.xml file (likely timed out) 
(batchId=389)
TestJdbcWithMiniKdc - did not produce a TEST-*.xml file (likely timed out) 
(batchId=425)
TestJdbcWithMiniKdcCookie - did not produce a TEST-*.xml file (likely timed 
out) (batchId=424)
TestJdbcWithMiniKdcSQLAuthBinary - did not produce a TEST-*.xml file (likely 
timed out) (batchId=422)
TestJdbcWithMiniKdcSQLAuthHttp - did not produce a TEST-*.xml file (likely 
timed out) (batchId=427)
TestJdbcWithMiniMr - did not produce a TEST-*.xml file (likely timed out) 
(batchId=388)
TestJdbcWithSQLAuthUDFBlacklist - did not produce a TEST-*.xml file (likely 
timed out) (batchId=394)
TestJdbcWithSQLAuthorization - did not produce a TEST-*.xml file (likely timed 
out) (batchId=395)
TestLocationQueries - did not produce a TEST-*.xml file (likely timed out) 
(batchId=362)
TestMTQueries - did not produce a TEST-*.xml file (likely timed out) 
(batchId=360)
TestMarkPartition - did not produce a TEST-*.xml file (likely timed out) 
(batchId=348)
TestMarkPartitionRemote - did not produce a TEST-*.xml file (likely timed out) 
(batchId=352)
TestMetaStoreAuthorization - did not produce a TEST-*.xml file (likely timed 
out) 

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


Correct.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

Thanks [~spena]. I removed the original patch file to avoid confusion.

Based on my patch name, the test should be against branch-1.2, right?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


I will delete the HiveQA to retrigger the testing. There was an issue on the 
ptest server where the 'master' classes were left on the source code directory, 
and ptest was attempting to run them on branch-1 even if they didn't or never 
exist there.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Thejas M Nair (JIRA)]

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

Thejas M Nair commented on HIVE-14476:
--

Unfortunately, the failures are too many in branch-1. Its hard to tell if there 
could be a related failure or not.


> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

Test failures seem unrelated.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.2.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-14476:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12835190/HIVE-14476.1-branch-1.2.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 197 failed/errored test(s), 7897 tests 
executed
*Failed tests:*
{noformat}
TestAdminUser - did not produce a TEST-*.xml file (likely timed out) 
(batchId=347)
TestAuthorizationPreEventListener - did not produce a TEST-*.xml file (likely 
timed out) (batchId=378)
TestAuthzApiEmbedAuthorizerInEmbed - did not produce a TEST-*.xml file (likely 
timed out) (batchId=357)
TestAuthzApiEmbedAuthorizerInRemote - did not produce a TEST-*.xml file (likely 
timed out) (batchId=363)
TestBeeLineWithArgs - did not produce a TEST-*.xml file (likely timed out) 
(batchId=385)
TestBitFieldReader - did not produce a TEST-*.xml file (likely timed out) 
(batchId=467)
TestBitPack - did not produce a TEST-*.xml file (likely timed out) (batchId=463)
TestBuddyAllocator - did not produce a TEST-*.xml file (likely timed out) 
(batchId=777)
TestCLIAuthzSessionContext - did not produce a TEST-*.xml file (likely timed 
out) (batchId=401)
TestClientSideAuthorizationProvider - did not produce a TEST-*.xml file (likely 
timed out) (batchId=377)
TestColumnStatistics - did not produce a TEST-*.xml file (likely timed out) 
(batchId=443)
TestColumnStatisticsImpl - did not produce a TEST-*.xml file (likely timed out) 
(batchId=457)
TestCompactor - did not produce a TEST-*.xml file (likely timed out) 
(batchId=367)
TestConverters - did not produce a TEST-*.xml file (likely timed out) 
(batchId=723)
TestCreateUdfEntities - did not produce a TEST-*.xml file (likely timed out) 
(batchId=366)
TestCustomAuthentication - did not produce a TEST-*.xml file (likely timed out) 
(batchId=386)
TestDBTokenStore - did not produce a TEST-*.xml file (likely timed out) 
(batchId=332)
TestDDLWithRemoteMetastoreSecondNamenode - did not produce a TEST-*.xml file 
(likely timed out) (batchId=365)
TestDataReaderProperties - did not produce a TEST-*.xml file (likely timed out) 
(batchId=461)
TestDruidSerDe - did not produce a TEST-*.xml file (likely timed out) 
(batchId=441)
TestDynamicArray - did not produce a TEST-*.xml file (likely timed out) 
(batchId=459)
TestDynamicSerDe - did not produce a TEST-*.xml file (likely timed out) 
(batchId=335)
TestEmbeddedHiveMetaStore - did not produce a TEST-*.xml file (likely timed 
out) (batchId=344)
TestEmbeddedThriftBinaryCLIService - did not produce a TEST-*.xml file (likely 
timed out) (batchId=389)
TestFileDump - did not produce a TEST-*.xml file (likely timed out) 
(batchId=445)
TestFilterHooks - did not produce a TEST-*.xml file (likely timed out) 
(batchId=339)
TestFirstInFirstOutComparator - did not produce a TEST-*.xml file (likely timed 
out) (batchId=786)
TestFolderPermissions - did not produce a TEST-*.xml file (likely timed out) 
(batchId=372)
TestHS2AuthzContext - did not produce a TEST-*.xml file (likely timed out) 
(batchId=404)
TestHS2AuthzSessionContext - did not produce a TEST-*.xml file (likely timed 
out) (batchId=405)
TestHS2ImpersonationWithRemoteMS - did not produce a TEST-*.xml file (likely 
timed out) (batchId=393)
TestHiveAuthorizerCheckInvocation - did not produce a TEST-*.xml file (likely 
timed out) (batchId=381)
TestHiveAuthorizerShowFilters - did not produce a TEST-*.xml file (likely timed 
out) (batchId=380)
TestHiveDruidQueryBasedInputFormat - did not produce a TEST-*.xml file (likely 
timed out) (batchId=440)
TestHiveHistory - did not produce a TEST-*.xml file (likely timed out) 
(batchId=383)
TestHiveMetaStoreTxns - did not produce a TEST-*.xml file (likely timed out) 
(batchId=359)
TestHiveMetaStoreWithEnvironmentContext - did not produce a TEST-*.xml file 
(likely timed out) (batchId=349)
TestHiveMetaTool - did not produce a TEST-*.xml file (likely timed out) 
(batchId=362)
TestHiveServer2 - did not produce a TEST-*.xml file (likely timed out) 
(batchId=407)
TestHiveServer2SessionTimeout - did not produce a TEST-*.xml file (likely timed 
out) (batchId=408)
TestHiveSessionImpl - did not produce a TEST-*.xml file (likely timed out) 
(batchId=390)
TestHplsqlLocal - did not produce a TEST-*.xml file (likely timed out) 
(batchId=475)
TestHplsqlOffline - did not produce a TEST-*.xml file (likely timed out) 
(batchId=474)
TestHs2Hooks - did not produce a TEST-*.xml file (likely timed out) 
(batchId=364)
TestHs2HooksWithMiniKdc - did not produce a TEST-*.xml file (likely timed out) 
(batchId=436)
TestInStream - did not produce a TEST-*.xml file (likely timed out) 
(batchId=453)
TestIncrementalObjectSizeEstimator - did not produce a TEST-*.xml file (likely 
timed out) (batchId=779)
TestIntegerCompressionReader - did not produce a 

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Daniel Dai (JIRA)]

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

Daniel Dai commented on HIVE-14476:
---

Created HIVE-14968 for that.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

Did a "git bisect" against branch-1 and this is the first bad commit below. 
[~daijy] Can you take a look?

20908265e2b3e303125f03623e6018f28806d65a is the first bad commit
commit 20908265e2b3e303125f03623e6018f28806d65a
Author: Daniel Dai 
Date:   Tue Aug 9 22:57:30 2016 -0700

HIVE-14436: Hive 1.2.1/Hitting "ql.Driver: FAILED: IllegalArgumentException 
Error: , expected at the end of 'decimal(9'" after enabling 
hive.optimize.skewjoin and with MR engine (Daniel Dai, reviewed by Ashutosh 
Chauhan)


> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Thejas M Nair (JIRA)]

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

Thejas M Nair commented on HIVE-14476:
--

If a fix goes into branch-1.2, it should go into branch-1 as well (as long as 
its applicable there).
It looks like we need to fix branch-1 before we can commit this.


> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


branch-1.2 works fine. Are you trying to add the patch to branch-1.2 instead of 
branch-1? If so, then your file attached should have 
'HIVE-14476-branch-1.2.patch' instead.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

I ran into the same issue with branch-1. Can you try "branch-1.2"? That branch 
should build fine.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


I get this error:

{noformat}
⟫ git log | head -n 6
commit edb6a40a56cd994c44426731a3620cc6fb5f8c76
Author: Daniel Dai 
Date:   Tue Oct 11 15:54:04 2016 -0700

HIVE-14690: Query fail when hive.exec.parallel=true, with conflicting 
session dir (Daniel Dai, reviewed by Thejas Nair)

⟫ git status
On branch branch-1
Your branch is up-to-date with 'apache/branch-1'.
nothing to commit, working directory clean

⟫ mvn clean install -Phadoop-2 -DskipTests
...
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/home/sergio/Development/Apache/hive/ql/src/java/org/apache/hadoop/hive/ql/io/orc/TreeReaderFactory.java:[1490,17]
 no suitable method found for ensureSize(long,boolean)
method 
org.apache.hadoop.hive.ql.exec.vector.ColumnVector.ensureSize(int,boolean) is 
not applicable
  (argument mismatch; possible lossy conversion from long to int)
method 
org.apache.hadoop.hive.ql.exec.vector.LongColumnVector.ensureSize(int,boolean) 
is not applicable
  (argument mismatch; possible lossy conversion from long to int)
[ERROR] 
/home/sergio/Development/Apache/hive/ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java:[2512,15]
 cannot find symbol
  symbol:   class TypeInfo
  location: class org.apache.hadoop.hive.ql.exec.Utilities
[ERROR] 
/home/sergio/Development/Apache/hive/ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java:[2512,32]
 cannot find symbol
  symbol:   variable TypeInfoUtils
  location: class org.apache.hadoop.hive.ql.exec.Utilities
[ERROR] 
/home/sergio/Development/Apache/hive/ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java:[2513,10]
 cannot find symbol
  symbol:   class TypeInfo
  location: class org.apache.hadoop.hive.ql.exec.Utilities
[INFO] 4 errors
[INFO] -
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Hive ... SUCCESS [  2.080 s]
[INFO] Hive Shims Common .. SUCCESS [  2.389 s]
[INFO] Hive Shims 0.20S ... SUCCESS [  0.666 s]
[INFO] Hive Shims 0.23  SUCCESS [  2.257 s]
[INFO] Hive Shims Scheduler ... SUCCESS [  0.573 s]
[INFO] Hive Shims . SUCCESS [  0.688 s]
[INFO] Hive Common  SUCCESS [  3.325 s]
[INFO] Hive Serde . SUCCESS [  3.852 s]
[INFO] Hive Metastore . SUCCESS [ 10.470 s]
[INFO] Hive Ant Utilities . SUCCESS [  0.337 s]
[INFO] Spark Remote Client  SUCCESS [  3.739 s]
[INFO] Hive Query Language  FAILURE [ 18.944 s]
{noformat}

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

[~spena] What issues are you seeing locally?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

Sorry, I forgot "-Phadoop-2". Now it builds fine for me.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


Nop, I got the same ones from ptest.
Use this {{mvn clean install -DskipTests -Phadoop-2}}

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

The build was against branch-1.2. I saw the same errors even without my change.






> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

I ran into the build errors below. Are you seeing the same errors?

[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 9.873 s
[INFO] Finished at: 2016-10-13T15:15:01-07:00
[INFO] Final Memory: 58M/626M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project hive-common: Compilation failure: Compilation failure:
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/common/ServerUtils.java:[23,28]
 cannot find symbol
[ERROR] symbol:   class FileSystem
[ERROR] location: package org.apache.hadoop.fs
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/common/ServerUtils.java:[24,28]
 cannot find symbol
[ERROR] symbol:   class Path
[ERROR] location: package org.apache.hadoop.fs
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[45,30]
 package org.apache.hadoop.conf does not exist
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[54,32]
 package org.apache.hadoop.mapred does not exist
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[55,34]
 package org.apache.hadoop.security does not exist
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[56,30]
 package org.apache.hadoop.util does not exist
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[64,31]
 cannot find symbol
[ERROR] symbol: class Configuration
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[2453,31]
 cannot find symbol
[ERROR] symbol:   class Configuration
[ERROR] location: class org.apache.hadoop.hive.conf.HiveConf
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[2458,32]
 cannot find symbol
[ERROR] symbol:   class Configuration
[ERROR] location: class org.apache.hadoop.hive.conf.HiveConf
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[2471,33]
 cannot find symbol
[ERROR] symbol:   class Configuration
[ERROR] location: class org.apache.hadoop.hive.conf.HiveConf
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[2475,33]
 cannot find symbol
[ERROR] symbol:   class Configuration
[ERROR] location: class org.apache.hadoop.hive.conf.HiveConf
[ERROR] 
/Users/tli/dev2/hive/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java:[2547,33]
 cannot find symbol
[ERROR] symbol:   class Configuration
[ERROR] location: class org.apache.hadoop.hive.conf.HiveConf


 







> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[JIRA]

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

Sergio Peña commented on HIVE-14476:


[~taoli-hwx] I tried compiling the branch-1 with JDK7, and it does not compile. 
It might be broken by another commit, and that's why ptest fails too.
Does it compile for you?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-14476:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12832801/HIVE-14476.1-branch-1.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1502/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1502/console
Test logs: 
http://ec2-204-236-174-241.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-Build-1502/

Messages:
{noformat}
 This message was trimmed, see log for full details 
[INFO] 
[INFO] 
[INFO] Building Hive Query Language 1.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hive-exec ---
[INFO] Deleting /data/hive-ptest/working/apache-github-source-source/ql/target
[INFO] Deleting /data/hive-ptest/working/apache-github-source-source/ql 
(includes = [datanucleus.log, derby.log], excludes = [])
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-no-snapshots) @ 
hive-exec ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (generate-sources) @ hive-exec ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-sources/java/org/apache/hadoop/hive/ql/exec/vector/expressions/gen
[mkdir] Created dir: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-sources/java/org/apache/hadoop/hive/ql/exec/vector/expressions/aggregates/gen
[mkdir] Created dir: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-test-sources/java/org/apache/hadoop/hive/ql/exec/vector/expressions/gen
Generating vector expression code
Generating vector expression test code
[INFO] Executed tasks
[INFO] 
[INFO] --- build-helper-maven-plugin:1.8:add-source (add-source) @ hive-exec ---
[INFO] Source directory: 
/data/hive-ptest/working/apache-github-source-source/ql/src/gen/protobuf/gen-java
 added.
[INFO] Source directory: 
/data/hive-ptest/working/apache-github-source-source/ql/src/gen/thrift/gen-javabean
 added.
[INFO] Source directory: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-sources/java
 added.
[INFO] 
[INFO] --- antlr3-maven-plugin:3.4:antlr (default) @ hive-exec ---
[INFO] ANTLR: Processing source directory 
/data/hive-ptest/working/apache-github-source-source/ql/src/java
ANTLR Parser Generator  Version 3.4
org/apache/hadoop/hive/ql/parse/HiveLexer.g
org/apache/hadoop/hive/ql/parse/HiveParser.g
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_ORDER KW_BY" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_FROM" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_ALL" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_SORT KW_BY" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_INSERT KW_INTO" 
using multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_SELECT" 
using multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_INSERT KW_OVERWRITE" 
using multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_MAP" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_MAP LPAREN" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_GROUP KW_BY" using 
multiple alternatives: 2, 9

As a result, 

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-14476:




Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12832519/HIVE-14476-branch-1.patch

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1460/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1460/console
Test logs: 
http://ec2-204-236-174-241.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-Build-1460/

Messages:
{noformat}
 This message was trimmed, see log for full details 
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/calcite/calcite-core/1.2.0-incubating/calcite-core-1.2.0-incubating.jar
 (3437 KB at 59254.8 KB/sec)
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/tez/tez-runtime-internals/0.5.4/tez-runtime-internals-0.5.4.jar
 (115 KB at 8184.5 KB/sec)
Downloaded: 
http://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy-all/2.1.6/groovy-all-2.1.6.jar
 (6228 KB at 60465.8 KB/sec)
Downloaded: 
http://repo.maven.apache.org/maven2/org/apache/parquet/parquet-column/1.7.0/parquet-column-1.7.0-tests.jar
 (162 KB at 1526.5 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hive-exec ---
[INFO] Deleting /data/hive-ptest/working/apache-github-source-source/ql/target
[INFO] Deleting /data/hive-ptest/working/apache-github-source-source/ql 
(includes = [datanucleus.log, derby.log], excludes = [])
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-no-snapshots) @ 
hive-exec ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (generate-sources) @ hive-exec ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-sources/java/org/apache/hadoop/hive/ql/exec/vector/expressions/gen
[mkdir] Created dir: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-sources/java/org/apache/hadoop/hive/ql/exec/vector/expressions/aggregates/gen
[mkdir] Created dir: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-test-sources/java/org/apache/hadoop/hive/ql/exec/vector/expressions/gen
Generating vector expression code
Generating vector expression test code
[INFO] Executed tasks
[INFO] 
[INFO] --- build-helper-maven-plugin:1.8:add-source (add-source) @ hive-exec ---
[INFO] Source directory: 
/data/hive-ptest/working/apache-github-source-source/ql/src/gen/protobuf/gen-java
 added.
[INFO] Source directory: 
/data/hive-ptest/working/apache-github-source-source/ql/src/gen/thrift/gen-javabean
 added.
[INFO] Source directory: 
/data/hive-ptest/working/apache-github-source-source/ql/target/generated-sources/java
 added.
[INFO] 
[INFO] --- antlr3-maven-plugin:3.4:antlr (default) @ hive-exec ---
[INFO] ANTLR: Processing source directory 
/data/hive-ptest/working/apache-github-source-source/ql/src/java
ANTLR Parser Generator  Version 3.4
org/apache/hadoop/hive/ql/parse/HiveLexer.g
org/apache/hadoop/hive/ql/parse/HiveParser.g
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_ORDER KW_BY" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_FROM" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_ALL" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_SORT KW_BY" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_INSERT KW_INTO" 
using multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_SELECT" 
using multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_INSERT KW_OVERWRITE" 
using multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as "{KW_REGEXP, KW_RLIKE} KW_UNION KW_MAP" using 
multiple alternatives: 2, 9

As a result, alternative(s) 9 were disabled for that input
warning(200): IdentifiersParser.g:455:5: 
Decision can match input such as 

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

Renamed the patch and submitted again.

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476-branch-1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-14476:




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

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1429/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1429/console
Test logs: 
http://ec2-204-236-174-241.us-west-1.compute.amazonaws.com/logs/PreCommit-HIVE-Build-1429/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hive-ptest/working/scratch/source-prep.sh' failed with exit 
status 1 and output '+ date '+%Y-%m-%d %T.%3N'
2016-10-07 22:54:15.052
+ [[ -n /usr/java/jdk1.8.0_25 ]]
+ export JAVA_HOME=/usr/java/jdk1.8.0_25
+ JAVA_HOME=/usr/java/jdk1.8.0_25
+ export 
PATH=/usr/java/jdk1.8.0_25/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+ 
PATH=/usr/java/jdk1.8.0_25/bin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost 
-Dhttp.proxyPort=3128'
+ cd /data/hive-ptest/working/
+ tee /data/hive-ptest/logs/PreCommit-HIVE-Build-1429/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z master ]]
+ [[ -d apache-github-source-source ]]
+ [[ ! -d apache-github-source-source/.git ]]
+ [[ ! -d apache-github-source-source ]]
+ date '+%Y-%m-%d %T.%3N'
2016-10-07 22:54:15.054
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 2435e70 HIVE-14861: Support precedence for set operator using 
parentheses (Pengcheng Xiong, reviewed by Ashutosh Chauhan)
+ git clean -f -d
Removing b/
Removing ql/src/test/results/clientpositive/llap/autoColumnStats_1.q.out
Removing ql/src/test/results/clientpositive/llap/autoColumnStats_2.q.out
Removing ql/src/test/results/clientpositive/llap/bucket_groupby.q.out
Removing 
ql/src/test/results/clientpositive/llap/bucketsortoptimize_insert_2.q.out
Removing ql/src/test/results/clientpositive/llap/cbo_rp_gby.q.out
Removing ql/src/test/results/clientpositive/llap/cbo_rp_join.q.out
Removing ql/src/test/results/clientpositive/llap/cbo_rp_lineage2.q.out
Removing ql/src/test/results/clientpositive/llap/cbo_rp_semijoin.q.out
Removing ql/src/test/results/clientpositive/llap/cbo_rp_subq_not_in.q.out
Removing ql/src/test/results/clientpositive/llap/cbo_rp_unionDistinct_2.q.out
Removing ql/src/test/results/clientpositive/llap/cbo_rp_windowing_2.q.out
Removing ql/src/test/results/clientpositive/llap/correlationoptimizer2.q.out
Removing ql/src/test/results/clientpositive/llap/correlationoptimizer4.q.out
Removing ql/src/test/results/clientpositive/llap/correlationoptimizer6.q.out
Removing 
ql/src/test/results/clientpositive/llap/dynpart_sort_optimization_acid.q.out
Removing ql/src/test/results/clientpositive/llap/escape1.q.out
Removing ql/src/test/results/clientpositive/llap/escape2.q.out
Removing ql/src/test/results/clientpositive/llap/global_limit.q.out
Removing ql/src/test/results/clientpositive/llap/groupby_sort_1_23.q.out
Removing ql/src/test/results/clientpositive/llap/groupby_sort_skew_1_23.q.out
Removing ql/src/test/results/clientpositive/llap/insert_into_with_schema.q.out
Removing ql/src/test/results/clientpositive/llap/join43.q.out
Removing ql/src/test/results/clientpositive/llap/join_filters.q.out
Removing ql/src/test/results/clientpositive/llap/join_nulls.q.out
Removing ql/src/test/results/clientpositive/llap/limit_join_transpose.q.out
Removing ql/src/test/results/clientpositive/llap/lineage2.q.out
Removing ql/src/test/results/clientpositive/llap/lineage3.q.out
Removing ql/src/test/results/clientpositive/llap/llap_partitioned.q.out
Removing ql/src/test/results/clientpositive/llap/load_dyn_part5.q.out
Removing ql/src/test/results/clientpositive/llap/multiMapJoin1.q.out
Removing ql/src/test/results/clientpositive/llap/multiMapJoin2.q.out
Removing 
ql/src/test/results/clientpositive/llap/multi_insert_move_tasks_share_dependencies.q.out
Removing ql/src/test/results/clientpositive/llap/orc_ppd_date.q.out
Removing ql/src/test/results/clientpositive/llap/orc_ppd_decimal.q.out
Removing ql/src/test/results/clientpositive/llap/orc_ppd_timestamp.q.out
Removing ql/src/test/results/clientpositive/llap/parquet_ppd_decimal.q.out
Removing ql/src/test/results/clientpositive/llap/partition_multilevels.q.out
Removing ql/src/test/results/clientpositive/llap/rcfile_createas1.q.out
Removing 

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Thejas M Nair (JIRA)]

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

Thejas M Nair commented on HIVE-14476:
--

Can you click on submit patch to get it run via unit test ?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Thejas M Nair (JIRA)]

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

Thejas M Nair commented on HIVE-14476:
--

+1

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1.patch
>
>
> This issue is from branch-1 code when we decide if a log entry is an 
> operational log or not (the operational logs are visible to the client). The 
> problem is that the code is checking the logging mode at the beginning of the 
> decide() method, while the logging mode is updated after that check. Due to 
> this issue, we ran into an issue that an operational log could be filtered 
> out if it's the very first log being checked from the this method. As a 
> result, that particular log is not showing up for the end user.



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

[jira] [Commented] (HIVE-14476) Fix logging issue for branch-1

[Tao Li (JIRA)]

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

Tao Li commented on HIVE-14476:
---

[~thejas] Can you please take a look at this change?

> Fix logging issue for branch-1
> --
>
> Key: HIVE-14476
> URL: https://issues.apache.org/jira/browse/HIVE-14476
> Project: Hive
>  Issue Type: Bug
>Reporter: Tao Li
>Assignee: Tao Li
> Attachments: HIVE-14476.1.patch
>
>




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