[jira] [Commented] (HIVE-18968) LLAP: report guaranteed tasks count in AM registry to check for consistency

[Prasanth Jayachandran (JIRA)]

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

Prasanth Jayachandran commented on HIVE-18968:
--

some minor comments in RB. looks good otherwise. +1

> LLAP: report guaranteed tasks count in AM registry to check for consistency
> ---
>
> Key: HIVE-18968
> URL: https://issues.apache.org/jira/browse/HIVE-18968
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18968.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18718) Integer like types throws error when there is a mismatch

[Vihang Karajgaonkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vihang Karajgaonkar updated HIVE-18718:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Integer like types throws error when there is a mismatch
> 
>
> Key: HIVE-18718
> URL: https://issues.apache.org/jira/browse/HIVE-18718
> Project: Hive
>  Issue Type: Improvement
>Reporter: Janaki Lahorani
>Assignee: Janaki Lahorani
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18718.1.patch, HIVE-18718.2.patch, 
> HIVE-18718.3.patch, HIVE-18718.4.patch, HIVE-18718.4.patch
>
>
> If a value is saved with long type and read as int type it results in
> FAILED: Execution Error, return code 2 from 
> org.apache.hadoop.hive.ql.exec.mr.MapRedTask



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18718) Integer like types throws error when there is a mismatch

[Vihang Karajgaonkar (JIRA)]

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

Vihang Karajgaonkar commented on HIVE-18718:


The test failures look environment related. I think we should reduce the batch 
size of TestNegativeCliDriver. The previous run test failures were mostly 
related to GC related and the patch didn't change any code.

Patch merged to master. Thanks for your contribution [~janulatha]

> Integer like types throws error when there is a mismatch
> 
>
> Key: HIVE-18718
> URL: https://issues.apache.org/jira/browse/HIVE-18718
> Project: Hive
>  Issue Type: Improvement
>Reporter: Janaki Lahorani
>Assignee: Janaki Lahorani
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18718.1.patch, HIVE-18718.2.patch, 
> HIVE-18718.3.patch, HIVE-18718.4.patch, HIVE-18718.4.patch
>
>
> If a value is saved with long type and read as int type it results in
> FAILED: Execution Error, return code 2 from 
> org.apache.hadoop.hive.ql.exec.mr.MapRedTask



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18965) HIVE-17990 didn't update derby SQL scripts

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18965:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
24s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black}  0m 36s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9656/dev-support/hive-personality.sh
 |
| git revision | master / 50e0077 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9656/yetus/patch-asflicense-problems.txt
 |
| modules | C: metastore U: metastore |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9656/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> HIVE-17990 didn't update derby SQL scripts
> --
>
> Key: HIVE-18965
> URL: https://issues.apache.org/jira/browse/HIVE-18965
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18965.patch
>
>
> Owing to HIVE-18775, there are currently two copies of the derby installation 
> and upgrade script.  HIVE-17990 only updated the one in standalone-metastore. 
>  The one in metastore needs to be updated as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline

[Vihang Karajgaonkar (JIRA)]

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

Vihang Karajgaonkar commented on HIVE-18963:


{quote}I think we should have a way to specify the final jdbc url (including 
not just the host:port, but other connection/session/conf params). That would 
be a nice usability add on - what do you think?
{quote}
It does support connection params in the url using the xml file. Check 
[this|https://github.com/apache/hive/blob/master/beeline/src/test/org/apache/hive/beeline/hs2connection/TestUserHS2ConnectionFileParser.java#L101]
 test case for example. This test also has other examples of urls which can be 
supported using the xml file. Is this not want you are looking for here?
{quote}We should also have a way to specify urls (let's call it named urls) for 
different HS2 services. For example, let's say there are 2 different versions 
of the service running on the cluster, the user can connect to a specific 
instance like this: {{beeline -c namedUrl}}. We can keep a default url as well 
which gets picked if no namedUrl switch is provided on command line.
{quote}
This would be a good improvement. I myself had this at the back of my mind but 
I never got around working on it. I think it would be a good addition.

> JDBC: Provide an option to simplify beeline usage by supporting default and 
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection 
> string to use the HS2 instance and set up the jdbc driver. Since we plan to 
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the 
> usability if the user can simply type {{beeline}} and get start the hive 
> session. The jdbc url can be specified in a beeline-site.xml (which can 
> contain other named jdbc urls as well, and they can be accessed by something 
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be 
> potentially expanded later if needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18281) HiveServer2 HA for LLAP and Workload Manager

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18281:




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

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

{color:red}ERROR:{color} -1 due to 29 failed/errored test(s), 13419 tests 
executed
*Failed tests:*
{noformat}
TestNegativeCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=95)

[jira] [Updated] (HIVE-18908) Add support for FULL OUTER JOIN to MapJoin

[Matt McCline (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-18908:

Attachment: HIVE-18908.08.patch

> Add support for FULL OUTER JOIN to MapJoin
> --
>
> Key: HIVE-18908
> URL: https://issues.apache.org/jira/browse/HIVE-18908
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Matt McCline
>Assignee: Matt McCline
>Priority: Critical
> Attachments: FULL OUTER MapJoin Code Changes.docx, 
> HIVE-18908.01.patch, HIVE-18908.02.patch, HIVE-18908.03.patch, 
> HIVE-18908.04.patch, HIVE-18908.05.patch, HIVE-18908.06.patch, 
> HIVE-18908.08.patch, JOIN to MAPJOIN Transformation.pdf, SHARED-MEMORY FULL 
> OUTER MapJoin.pdf
>
>
> Currently, we do not support FULL OUTER JOIN in MapJoin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18908) Add support for FULL OUTER JOIN to MapJoin

[Matt McCline (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-18908:

Attachment: (was: HIVE-18908.07.patch)

> Add support for FULL OUTER JOIN to MapJoin
> --
>
> Key: HIVE-18908
> URL: https://issues.apache.org/jira/browse/HIVE-18908
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Matt McCline
>Assignee: Matt McCline
>Priority: Critical
> Attachments: FULL OUTER MapJoin Code Changes.docx, 
> HIVE-18908.01.patch, HIVE-18908.02.patch, HIVE-18908.03.patch, 
> HIVE-18908.04.patch, HIVE-18908.05.patch, HIVE-18908.06.patch, JOIN to 
> MAPJOIN Transformation.pdf, SHARED-MEMORY FULL OUTER MapJoin.pdf
>
>
> Currently, we do not support FULL OUTER JOIN in MapJoin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18281) HiveServer2 HA for LLAP and Workload Manager

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18281:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
41s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  4m 
19s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  2m 
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  3m  
8s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
7s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
30s{color} | {color:red} hive-unit in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
25s{color} | {color:red} util in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
36s{color} | {color:red} hive-unit in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 36s{color} 
| {color:red} hive-unit in the patch failed. {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
14s{color} | {color:red} itests/hive-unit: The patch generated 4 new + 0 
unchanged - 0 fixed = 4 total (was 0) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m  
9s{color} | {color:red} llap-client: The patch generated 33 new + 74 unchanged 
- 9 fixed = 107 total (was 83) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m  
9s{color} | {color:red} llap-ext-client: The patch generated 1 new + 39 
unchanged - 0 fixed = 40 total (was 39) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
10s{color} | {color:red} llap-tez: The patch generated 6 new + 66 unchanged - 0 
fixed = 72 total (was 66) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
39s{color} | {color:red} ql: The patch generated 5 new + 61 unchanged - 10 
fixed = 66 total (was 71) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
12s{color} | {color:red} service: The patch generated 40 new + 20 unchanged - 2 
fixed = 60 total (was 22) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green}  0m  
3s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
12s{color} | {color:green} common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
16s{color} | {color:green} hive-minikdc in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
22s{color} | {color:green} hive-unit in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
15s{color} | {color:green} hive-unit-hadoop2 in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
17s{color} | {color:green} util in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
10s{color} | {color:green} llap-client generated 0 new + 6 unchanged - 6 fixed 
= 6 total (was 12) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m  
9s{color} | {color:green} llap-ext-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
12s{color} | {color:green} llap-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m  
9s{color} | {color:green} llap-tez in the patch passed. {color} |
| 

[jira] [Commented] (HIVE-18910) Migrate to Murmur hash for shuffle and bucketing

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18910:




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

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

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/9653/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/9653/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-9653/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Tests exited with: ExecutionException: java.util.concurrent.ExecutionException: 
java.io.IOException: Could not create 
/data/hiveptest/logs/PreCommit-HIVE-Build-9653/failed/203_UTBatch_hcatalog__streaming_16_tests
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12914765 - PreCommit-HIVE-Build

> Migrate to Murmur hash for shuffle and bucketing
> 
>
> Key: HIVE-18910
> URL: https://issues.apache.org/jira/browse/HIVE-18910
> Project: Hive
>  Issue Type: Task
>Reporter: Deepak Jaiswal
>Assignee: Deepak Jaiswal
>Priority: Major
> Attachments: HIVE-18910.1.patch, HIVE-18910.2.patch, 
> HIVE-18910.3.patch, HIVE-18910.4.patch, HIVE-18910.5.patch, 
> HIVE-18910.6.patch, HIVE-18910.7.patch, HIVE-18910.8.patch, HIVE-18910.9.patch
>
>
> Hive uses JAVA hash which is not as good as murmur for better distribution 
> and efficiency in bucketing a table.
> Migrate to murmur hash but still keep backward compatibility for existing 
> users so that they dont have to reload the existing tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18910) Migrate to Murmur hash for shuffle and bucketing

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18910:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
34s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  1m 
59s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
44s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
7s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
15s{color} | {color:red} streaming in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
42s{color} | {color:red} ql in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  2m 
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  2m 
55s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} storage-api: The patch generated 3 new + 88 unchanged 
- 3 fixed = 91 total (was 91) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
17s{color} | {color:red} serde: The patch generated 142 new + 214 unchanged - 3 
fixed = 356 total (was 217) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} hcatalog/streaming: The patch generated 1 new + 33 
unchanged - 0 fixed = 34 total (was 33) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
52s{color} | {color:red} ql: The patch generated 26 new + 1242 unchanged - 3 
fixed = 1268 total (was 1245) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
39s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
13s{color} | {color:red} The patch generated 50 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 27m  7s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9653/dev-support/hive-personality.sh
 |
| git revision | master / 50e0077 |
| Default Java | 1.8.0_111 |
| mvninstall | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus/patch-mvninstall-hcatalog_streaming.txt
 |
| mvninstall | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus/patch-mvninstall-ql.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus/diff-checkstyle-storage-api.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus/diff-checkstyle-serde.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus/diff-checkstyle-hcatalog_streaming.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus/diff-checkstyle-ql.txt
 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus/patch-asflicense-problems.txt
 |
| modules | C: storage-api serde hbase-handler hcatalog/streaming 
itests/hive-blobstore ql standalone-metastore U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9653/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This 

[jira] [Commented] (HIVE-18633) Service discovery for Active/Passive HA mode

[Prasanth Jayachandran (JIRA)]

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

Prasanth Jayachandran commented on HIVE-18633:
--

This patch depends on HIVE-18281, will submit patch and upload to RB after 
committing HIVE-18281. 
cc/ [~sershe]

> Service discovery for Active/Passive HA mode
> 
>
> Key: HIVE-18633
> URL: https://issues.apache.org/jira/browse/HIVE-18633
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
>Priority: Major
> Attachments: HIVE-18633.1.patch
>
>
> HIVE-18281 adds Active/Passive HA mode for HS2. This jira is to extend the 
> feature so that clients will connect only to leader instance via JDBC + 
> service discovery. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (HIVE-18633) Service discovery for Active/Passive HA mode

[Prasanth Jayachandran (JIRA)]

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

Prasanth Jayachandran edited comment on HIVE-18633 at 3/16/18 2:45 AM:
---

This patch depends on HIVE-18281, will submit patch and upload to RB after 
committing HIVE-18281. Patch however is ready for review. 
cc/ [~sershe]


was (Author: prasanth_j):
This patch depends on HIVE-18281, will submit patch and upload to RB after 
committing HIVE-18281. 
cc/ [~sershe]

> Service discovery for Active/Passive HA mode
> 
>
> Key: HIVE-18633
> URL: https://issues.apache.org/jira/browse/HIVE-18633
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
>Priority: Major
> Attachments: HIVE-18633.1.patch
>
>
> HIVE-18281 adds Active/Passive HA mode for HS2. This jira is to extend the 
> feature so that clients will connect only to leader instance via JDBC + 
> service discovery. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18783) ALTER TABLE post-commit listener does not include the transactional listener responses

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18783:




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

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

{color:red}ERROR:{color} -1 due to 25 failed/errored test(s), 13022 tests 
executed
*Failed tests:*
{noformat}
TestNegativeCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=94)

[jira] [Assigned] (HIVE-18633) Service discovery for Active/Passive HA mode

[Prasanth Jayachandran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanth Jayachandran reassigned HIVE-18633:


Assignee: Prasanth Jayachandran

> Service discovery for Active/Passive HA mode
> 
>
> Key: HIVE-18633
> URL: https://issues.apache.org/jira/browse/HIVE-18633
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
>Priority: Major
> Attachments: HIVE-18633.1.patch
>
>
> HIVE-18281 adds Active/Passive HA mode for HS2. This jira is to extend the 
> feature so that clients will connect only to leader instance via JDBC + 
> service discovery. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18633) Service discovery for Active/Passive HA mode

[Prasanth Jayachandran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanth Jayachandran updated HIVE-18633:
-
Attachment: HIVE-18633.1.patch

> Service discovery for Active/Passive HA mode
> 
>
> Key: HIVE-18633
> URL: https://issues.apache.org/jira/browse/HIVE-18633
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Prasanth Jayachandran
>Priority: Major
> Attachments: HIVE-18633.1.patch
>
>
> HIVE-18281 adds Active/Passive HA mode for HS2. This jira is to extend the 
> feature so that clients will connect only to leader instance via JDBC + 
> service discovery. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18739) Add support for Export from unpartitioned Acid table

[Eugene Koifman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eugene Koifman updated HIVE-18739:
--
Attachment: HIVE-18739.08.patch

> Add support for Export from unpartitioned Acid table
> 
>
> Key: HIVE-18739
> URL: https://issues.apache.org/jira/browse/HIVE-18739
> Project: Hive
>  Issue Type: Sub-task
>  Components: Transactions
>Reporter: Eugene Koifman
>Assignee: Eugene Koifman
>Priority: Major
> Attachments: HIVE-18739.01.patch, HIVE-18739.04.patch, 
> HIVE-18739.04.patch, HIVE-18739.06.patch, HIVE-18739.08.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18955) HoS: Unable to create Channel from class NioServerSocketChannel

[Rui Li (JIRA)]

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

Rui Li commented on HIVE-18955:
---

Hi [~bslim], both {{netty-all-4.1.17.Final.jar}} and 
{{async-http-client-2.0.37.jar}} contains class 
{{io.netty.channel.DefaultChannelId}}. The two classes have different 
definitions of {{newInstance()}} method.

> HoS: Unable to create Channel from class NioServerSocketChannel
> ---
>
> Key: HIVE-18955
> URL: https://issues.apache.org/jira/browse/HIVE-18955
> Project: Hive
>  Issue Type: Bug
>  Components: Spark
>Reporter: Rui Li
>Priority: Major
>
> Hit the issue when trying launch spark job. Stack trace:
> {noformat}
> Caused by: java.lang.NoSuchMethodError: 
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
> at io.netty.channel.AbstractChannel.newId(AbstractChannel.java:111) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at io.netty.channel.AbstractChannel.(AbstractChannel.java:83) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.nio.AbstractNioChannel.(AbstractNioChannel.java:84) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.nio.AbstractNioMessageChannel.(AbstractNioMessageChannel.java:42)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:86)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:72)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method) ~[?:1.8.0_151]
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  ~[?:1.8.0_151]
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  ~[?:1.8.0_151]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423) 
> ~[?:1.8.0_151]
> at 
> io.netty.channel.ReflectiveChannelFactory.newChannel(ReflectiveChannelFactory.java:38)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> ... 32 more
> {noformat}
> It seems we have conflicts versions of class 
> {{io.netty.channel.DefaultChannelId}} from async-http-client.jar and 
> netty-all.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18783) ALTER TABLE post-commit listener does not include the transactional listener responses

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18783:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
1s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
25s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
57s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
8s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
 6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  1m  
4s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
13s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 13m 41s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9652/dev-support/hive-personality.sh
 |
| git revision | master / 50e0077 |
| Default Java | 1.8.0_111 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9652/yetus/patch-asflicense-problems.txt
 |
| modules | C: itests/hcatalog-unit standalone-metastore U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9652/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> ALTER TABLE post-commit listener does not include the transactional listener 
> responses 
> ---
>
> Key: HIVE-18783
> URL: https://issues.apache.org/jira/browse/HIVE-18783
> Project: Hive
>  Issue Type: Bug
>Reporter: Na Li
>Assignee: Sergio Peña
>Priority: Major
> Attachments: HIVE-18783.1.patch, HIVE-18783.2.patch
>
>
>  in HiveMetaStore, alter_table_core does NOT call transactional listener, and 
> the notification ID corresponding to the alter table event is NOT set in the 
> event parameters.
> {code}
> + alter_table_core
>   
>   try {
> Table oldt = this.get_table_core(dbname, name);
> this.firePreEvent(new PreAlterTableEvent(oldt, newTable, this));
> this.alterHandler.alterTable(this.getMS(), this.wh, dbname, name, 
> newTable, envContext, this);
> success = true;
> if (!this.listeners.isEmpty()) {
>   MetaStoreListenerNotifier.notifyEvent(this.listeners, 
> EventType.ALTER_TABLE, new AlterTableEvent(oldt, newTable, true, this), 
> envContext);
> }
>   } catch (NoSuchObjectException var12) {
> ex = var12;
> throw new InvalidOperationException(var12.getMessage());
>   } catch (Exception var13) {
> ex = var13;
> if (var13 instanceof MetaException) {
>   

[jira] [Commented] (HIVE-18718) Integer like types throws error when there is a mismatch

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18718:




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

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

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/9651/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/9651/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-9651/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Tests exited with: ExecutionException: java.util.concurrent.ExecutionException: 
org.apache.hive.ptest.execution.ssh.SSHExecutionException: RSyncResult 
[localFile=/data/hiveptest/logs/PreCommit-HIVE-Build-9651/succeeded/230_UTBatch_itests__hive-unit_9_tests,
 remoteFile=/home/hiveptest/35.202.147.211-hiveptest-1/logs/, getExitCode()=11, 
getException()=null, getUser()=hiveptest, getHost()=35.202.147.211, 
getInstance()=1]: 'Warning: Permanently added '35.202.147.211' (ECDSA) to the 
list of known hosts.
receiving incremental file list
./
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.TestCreateUdfEntities.xml

  0   0%0.00kB/s0:00:00  
102,270 100%2.50MB/s0:00:00 (xfr#1, to-chk=13/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.TestDDLWithRemoteMetastoreSecondNamenode.xml

  0   0%0.00kB/s0:00:00  
102,371 100%1.24MB/s0:00:00 (xfr#2, to-chk=12/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.metadata.TestSemanticAnalyzerHookLoading.xml

  0   0%0.00kB/s0:00:00  
102,180 100%1.23MB/s0:00:00 (xfr#3, to-chk=11/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.parse.TestCopyUtils.xml

  0   0%0.00kB/s0:00:00  
102,187 100%  845.69kB/s0:00:00 (xfr#4, to-chk=10/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.parse.TestExportImport.xml

  0   0%0.00kB/s0:00:00  
102,442 100%  840.68kB/s0:00:00 (xfr#5, to-chk=9/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.parse.TestReplicationOnHDFSEncryptedZones.xml

  0   0%0.00kB/s0:00:00  
170,041 100%1.35MB/s0:00:00 (xfr#6, to-chk=8/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.parse.TestReplicationScenarios.xml

  0   0%0.00kB/s0:00:00  
108,494 100%  868.45kB/s0:00:00 (xfr#7, to-chk=7/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.parse.TestReplicationScenariosAcrossInstances.xml

  0   0%0.00kB/s0:00:00  
103,606 100%  640.37kB/s0:00:00 (xfr#8, to-chk=6/15)
TEST-230_UTBatch_itests__hive-unit_9_tests-TEST-org.apache.hadoop.hive.ql.txn.compactor.TestCleanerWithReplication.xml

  0   0%0.00kB/s0:00:00  
102,641 100%  630.41kB/s0:00:00 (xfr#9, to-chk=5/15)
maven-test.txt

  0   0%0.00kB/s0:00:00  
  8,357 100%   51.33kB/s0:00:00 (xfr#10, to-chk=4/15)
logs/
logs/derby.log

  0   0%0.00kB/s0:00:00  
  1,016 100%6.24kB/s0:00:00 (xfr#11, to-chk=1/15)
logs/hive.log

  0   0%0.00kB/s0:00:00  
 38,699,008  27%   36.91MB/s0:00:02  
 87,883,776  63%   41.93MB/s0:00:01  
rsync: write failed on 
"/data/hiveptest/logs/PreCommit-HIVE-Build-9651/succeeded/230_UTBatch_itests__hive-unit_9_tests/logs/hive.log":
 No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.1]
Warning: Permanently added '35.202.147.211' (ECDSA) to the list of known hosts.
receiving incremental file list
logs/
logs/hive.log

  0   0%0.00kB/s0:00:00  
rsync: write failed on 
"/data/hiveptest/logs/PreCommit-HIVE-Build-9651/succeeded/230_UTBatch_itests__hive-unit_9_tests/logs/hive.log":
 No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.1]
Warning: Permanently added '35.202.147.211' (ECDSA) to the list of known hosts.
receiving incremental file list
logs/
logs/hive.log

  0   0%0.00kB/s0:00:00  
rsync: write failed on 
"/data/hiveptest/logs/PreCommit-HIVE-Build-9651/succeeded/230_UTBatch_itests__hive-unit_9_tests/logs/hive.log":
 No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.1]
Warning: Permanently added 

[jira] [Updated] (HIVE-18972) beeline command suggestion to kill job deprecated

[Bharathkrishna Guruvayoor Murali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharathkrishna Guruvayoor Murali updated HIVE-18972:

Status: Patch Available  (was: Open)

Adding the path to mapred binary and updating the info message to use this.

> beeline command suggestion to kill job deprecated
> -
>
> Key: HIVE-18972
> URL: https://issues.apache.org/jira/browse/HIVE-18972
> Project: Hive
>  Issue Type: Bug
>Reporter: Bharathkrishna Guruvayoor Murali
>Assignee: Bharathkrishna Guruvayoor Murali
>Priority: Minor
> Attachments: HIVE-18972.1.patch
>
>
> When I run a beeline command that uses YARN:
> {code}
> INFO : The url to track the job: 
> http://vd0514.halxg.cloudera.com:8088/proxy/application_1488996234407_0010/
> INFO : Starting Job = job_1488996234407_0010, Tracking URL = 
> http://vd0514.halxg.cloudera.com:8088/proxy/application_1488996234407_0010/
> INFO : Kill Command = 
> /opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.9/lib/hadoop/bin/hadoop job 
> -kill job_1488996234407_0010
> {code}
> If I then try to kill the job using that command:
> {code}
> [systest@vd0514 ~]$ 
> /opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.9/lib/hadoop/bin/hadoop job 
> -kill job_1488996234407_0010
> DEPRECATED: Use of this script to execute mapred command is deprecated.
> Instead use the mapred command for it.
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18971) add HS2 WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

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

Sergey Shelukhin commented on HIVE-18971:
-

For now the metrics will only reflect HS2 side info and it looks like they will 
use Hadoop metrics directly for metrics per pool, and only output totals to 
Codahale, because codahale has no capacity for tagging the way it's set up as a 
singleton, with a single process wide context and no sessionId or such things. 
We may later rework how codahale works in Hive to support those (in a separate 
JIRA).
Getting runtime information from AM side (e.g. how many guaranteed tasks are 
used per pool) would require either changing tagging to be pool based instead 
of dag based (and removing session ID, meaningless in this context, to be 
replaced with dag ID, I guess), or propagating it via progress (which is 
probably better, but requires changes to Tez).

> add HS2 WM metrics for use in Grafana and such
> --
>
> Key: HIVE-18971
> URL: https://issues.apache.org/jira/browse/HIVE-18971
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>
> HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
> even sets up metrics right now...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-15566) Schema tool upgrade schema fails from 1.2.1 to 2.1.1 because COMPACTION_QUEUE does not exist

[Bharathkrishna Guruvayoor Murali (JIRA)]

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

Bharathkrishna Guruvayoor Murali commented on HIVE-15566:
-

This issue is not reproducible now. Tested in Hive branches for 2.1.1 as well 
as 2.3.0.

I tried : 
{code:java}
./schematool -dbType derby -initSchemaTo 1.2.0
./schematool -dbType derby -upgradeSchema{code}
The upgrade happened successfully.

 

> Schema tool upgrade schema fails from 1.2.1 to 2.1.1 because COMPACTION_QUEUE 
> does not exist
> 
>
> Key: HIVE-15566
> URL: https://issues.apache.org/jira/browse/HIVE-15566
> Project: Hive
>  Issue Type: Bug
>  Components: Hive
>Reporter: Vihang Karajgaonkar
>Assignee: Bharathkrishna Guruvayoor Murali
>Priority: Major
>
> When we use schematool to upgrade metastore schema from 1.2.1 to 2.x* it 
> fails with the error 
> "ALTER TABLE' cannot be performed on 'COMPACTION_QUEUE' because it does not 
> exist"
> The table COMPACTION_QUEUE is created hive-txn-schema-2.1.0.derby.sql but the 
> upgrade script does not seem to call it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18972) beeline command suggestion to kill job deprecated

[Bharathkrishna Guruvayoor Murali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharathkrishna Guruvayoor Murali updated HIVE-18972:

Attachment: HIVE-18972.1.patch

> beeline command suggestion to kill job deprecated
> -
>
> Key: HIVE-18972
> URL: https://issues.apache.org/jira/browse/HIVE-18972
> Project: Hive
>  Issue Type: Bug
>Reporter: Bharathkrishna Guruvayoor Murali
>Assignee: Bharathkrishna Guruvayoor Murali
>Priority: Minor
> Attachments: HIVE-18972.1.patch
>
>
> When I run a beeline command that uses YARN:
> {code}
> INFO : The url to track the job: 
> http://vd0514.halxg.cloudera.com:8088/proxy/application_1488996234407_0010/
> INFO : Starting Job = job_1488996234407_0010, Tracking URL = 
> http://vd0514.halxg.cloudera.com:8088/proxy/application_1488996234407_0010/
> INFO : Kill Command = 
> /opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.9/lib/hadoop/bin/hadoop job 
> -kill job_1488996234407_0010
> {code}
> If I then try to kill the job using that command:
> {code}
> [systest@vd0514 ~]$ 
> /opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.9/lib/hadoop/bin/hadoop job 
> -kill job_1488996234407_0010
> DEPRECATED: Use of this script to execute mapred command is deprecated.
> Instead use the mapred command for it.
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline

[Vaibhav Gumashta (JIRA)]

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

Vaibhav Gumashta commented on HIVE-18963:
-

[~vihangk1] Looked at the patch and a couple things that would be nice to have 
in addition to what the patch adds:
1. I think we should have a way to specify the final jdbc url (including not 
just the host:port, but other connection/session/conf params). That would be a 
nice usability add on - what do you think?
2. We should also have a way to specify urls (let's call it named urls) for 
different HS2 services. For example, let's say there are 2 different versions 
of the service running on the cluster, the user can connect to  a specific 
instance like this: {{beeline -c namedUrl}}. We can keep a default url as well 
which gets picked if no namedUrl switch is provided on command line.

Let me know what you think about these additions - I can create a patch with 
these changes. Thanks!

> JDBC: Provide an option to simplify beeline usage by supporting default and 
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
>  Issue Type: Bug
>  Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection 
> string to use the HS2 instance and set up the jdbc driver. Since we plan to 
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the 
> usability if the user can simply type {{beeline}} and get start the hive 
> session. The jdbc url can be specified in a beeline-site.xml (which can 
> contain other named jdbc urls as well, and they can be accessed by something 
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be 
> potentially expanded later if needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18718) Integer like types throws error when there is a mismatch

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18718:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  1m  
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
55s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  1m 
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
59s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
51s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
12s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 14m 12s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9651/dev-support/hive-personality.sh
 |
| git revision | master / 50e0077 |
| Default Java | 1.8.0_111 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9651/yetus/patch-asflicense-problems.txt
 |
| modules | C: ql U: ql |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9651/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Integer like types throws error when there is a mismatch
> 
>
> Key: HIVE-18718
> URL: https://issues.apache.org/jira/browse/HIVE-18718
> Project: Hive
>  Issue Type: Improvement
>Reporter: Janaki Lahorani
>Assignee: Janaki Lahorani
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18718.1.patch, HIVE-18718.2.patch, 
> HIVE-18718.3.patch, HIVE-18718.4.patch, HIVE-18718.4.patch
>
>
> If a value is saved with long type and read as int type it results in
> FAILED: Execution Error, return code 2 from 
> org.apache.hadoop.hive.ql.exec.mr.MapRedTask



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18755) Modifications to the metastore for catalogs

[Alexander Kolbasov (JIRA)]

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

Alexander Kolbasov commented on HIVE-18755:
---

[~alangates] Can you post a patch against master? Reviewing it from github 
isn't the best option.

> Modifications to the metastore for catalogs
> ---
>
> Key: HIVE-18755
> URL: https://issues.apache.org/jira/browse/HIVE-18755
> Project: Hive
>  Issue Type: Sub-task
>  Components: Metastore
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
>  Labels: pull-request-available
>
> Step 1 of adding catalogs is to add support in the metastore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-16882) Improvements For Avro SerDe Package

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-16882:




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

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

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/9650/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/9650/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-9650/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Tests exited with: ExecutionException: java.util.concurrent.ExecutionException: 
java.io.IOException: Could not create 
/data/hiveptest/logs/PreCommit-HIVE-Build-9650/failed/170-TestMiniLlapLocalCliDriver-smb_mapjoin_15.q-insert_values_partitioned.q-selectDistinctStar.q-and-27-more
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12914715 - PreCommit-HIVE-Build

> Improvements For Avro SerDe Package
> ---
>
> Key: HIVE-16882
> URL: https://issues.apache.org/jira/browse/HIVE-16882
> Project: Hive
>  Issue Type: Improvement
>  Components: Serializers/Deserializers
>Affects Versions: 3.0.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Minor
> Attachments: HIVE-16882.1.patch, HIVE-16882.2.patch, 
> HIVE-16882.3.patch, HIVE-16882.4.patch
>
>
> # Use SLF4J parameter DEBUG logging
> # Use re-usable libraries where appropriate
> # Use enhanced for loops where appropriate
> # Fix several minor check-style error
> # Small performance enhancements in InstanceCache



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-16882) Improvements For Avro SerDe Package

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-16882:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
 8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
14s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
13s{color} | {color:green} serde: The patch generated 0 new + 38 unchanged - 4 
fixed = 38 total (was 42) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
14s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
12s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black}  9m 23s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9650/dev-support/hive-personality.sh
 |
| git revision | master / 50e0077 |
| Default Java | 1.8.0_111 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9650/yetus/patch-asflicense-problems.txt
 |
| modules | C: serde U: serde |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9650/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Improvements For Avro SerDe Package
> ---
>
> Key: HIVE-16882
> URL: https://issues.apache.org/jira/browse/HIVE-16882
> Project: Hive
>  Issue Type: Improvement
>  Components: Serializers/Deserializers
>Affects Versions: 3.0.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Minor
> Attachments: HIVE-16882.1.patch, HIVE-16882.2.patch, 
> HIVE-16882.3.patch, HIVE-16882.4.patch
>
>
> # Use SLF4J parameter DEBUG logging
> # Use re-usable libraries where appropriate
> # Use enhanced for loops where appropriate
> # Fix several minor check-style error
> # Small performance enhancements in InstanceCache



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone

[Piotr Findeisen (JIRA)]

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

Piotr Findeisen commented on HIVE-18925:


[~hiveqa] , 
i think all you're saying is that the test are failing even before my change.

[~sershe] , [~lirui], 

i do not fully understand what are the duties of {{TimestampParser}}, so please 
double check me.
In {{America/Bahia_Banderas}} zone, the first local time observed in 1970 was 
{{1970-01-01 01:00:00}}, so with this patch, 
{{TimestampParser#startingDateValue}} will be set to {{1970-01-01 01:00:00 
America/Bahia_Banderas}}.
If {{TimestampParser}} is used to parse timestamps (as it seems), this is 
alright. If, however, it can be used to parse _dates_ represented as midnights, 
it might return {{ Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
>  Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't  work if started with 
> {{-Duser.timezone=America/Bahia_Banderas}}
>  
> Steps to reproduce
>  # use [https://github.com/big-data-europe/docker-hive]
>  # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to 
> {{hive-server}} docker container environment configuration
>  # {{docker-compose up}}
>  # 
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1 
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with 
> org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000 
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause 
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000 
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with 
> org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000 
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at 
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at 
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at 
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at 
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at 

[jira] [Commented] (HIVE-18755) Modifications to the metastore for catalogs

[Alan Gates (JIRA)]

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

Alan Gates commented on HIVE-18755:
---

The PR is not yet ready for merging, I'm just posting it as preliminary work, 
since the patch is huge.

So, let me begin by apologizing for the enormity of this patch.  I didn't see a 
good way of breaking it up without leaving lots of half baked stuff in there, 
so I did almost all of the metastore work in one pass.

Second, let me say my sincerest thanks to [~pvary] and others who added all the 
client tests.  They were invaluable in helping me test the new code.

A comment where I took a different path than in the doc posted at HIVE-18685.  
Rather than hard wiring all the old calls to the 'hive' catalog I added a 
notion of default catalog in the config file.  This defaults to 'hive'.  This 
allows an admin to set up a metastore server to talk to a non-'hive' catalog 
while still using older clients.  This seems like a useful feature.

While I have included a lot of testing in this patch there is still a fair 
amount to add.  Things I have tested:
 * new catalog calls
 * existing calls without catalog set
 * direct SQL access path for reading data out of the database.

Things I haven't tested yet but plan to before committing the patch:
 * an old client talking to the server; I want to make sure this works even 
though the old client will have no notion of catalogs
 * configuring the default catalog to be something other than 'hive' and making 
sure a client still works
 * the JDO access path for reading data out of the database

> Modifications to the metastore for catalogs
> ---
>
> Key: HIVE-18755
> URL: https://issues.apache.org/jira/browse/HIVE-18755
> Project: Hive
>  Issue Type: Sub-task
>  Components: Metastore
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
>  Labels: pull-request-available
>
> Step 1 of adding catalogs is to add support in the metastore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18973) Make transaction system work with catalogs

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates reassigned HIVE-18973:
-


> Make transaction system work with catalogs
> --
>
> Key: HIVE-18973
> URL: https://issues.apache.org/jira/browse/HIVE-18973
> Project: Hive
>  Issue Type: Sub-task
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
>
> The transaction tables need to understand catalogs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-16882) Improvements For Avro SerDe Package

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-16882:




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

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

{color:red}ERROR:{color} -1 due to 23 failed/errored test(s), 13019 tests 
executed
*Failed tests:*
{noformat}
TestNegativeCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=94)

[jira] [Updated] (HIVE-18846) Query results cache: Allow queries to refer to the pending results of a query that has not finished yet

[Jason Dere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-18846:
--
   Resolution: Fixed
Fix Version/s: 3.0.0
   Status: Resolved  (was: Patch Available)

Committed to master

> Query results cache: Allow queries to refer to the pending results of a query 
> that has not finished yet
> ---
>
> Key: HIVE-18846
> URL: https://issues.apache.org/jira/browse/HIVE-18846
> Project: Hive
>  Issue Type: Sub-task
>  Components: Query Planning
>Reporter: Jason Dere
>Assignee: Jason Dere
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18846.1.patch, HIVE-18846.2.patch, 
> HIVE-18846.3.patch
>
>
> Currently, a query's results can only be looked up in the cache if the query 
> has completely finished execution. Allow new queries to use the results cache 
> to find queries that are still executing so they can re-use the results when 
> the query has finished.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18972) beeline command suggestion to kill job deprecated

[Bharathkrishna Guruvayoor Murali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharathkrishna Guruvayoor Murali reassigned HIVE-18972:
---


> beeline command suggestion to kill job deprecated
> -
>
> Key: HIVE-18972
> URL: https://issues.apache.org/jira/browse/HIVE-18972
> Project: Hive
>  Issue Type: Bug
>Reporter: Bharathkrishna Guruvayoor Murali
>Assignee: Bharathkrishna Guruvayoor Murali
>Priority: Minor
>
> When I run a beeline command that uses YARN:
> {code}
> INFO : The url to track the job: 
> http://vd0514.halxg.cloudera.com:8088/proxy/application_1488996234407_0010/
> INFO : Starting Job = job_1488996234407_0010, Tracking URL = 
> http://vd0514.halxg.cloudera.com:8088/proxy/application_1488996234407_0010/
> INFO : Kill Command = 
> /opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.9/lib/hadoop/bin/hadoop job 
> -kill job_1488996234407_0010
> {code}
> If I then try to kill the job using that command:
> {code}
> [systest@vd0514 ~]$ 
> /opt/cloudera/parcels/CDH-5.11.0-1.cdh5.11.0.p0.9/lib/hadoop/bin/hadoop job 
> -kill job_1488996234407_0010
> DEPRECATED: Use of this script to execute mapred command is deprecated.
> Instead use the mapred command for it.
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18755) Modifications to the metastore for catalogs

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HIVE-18755:
--
Labels: pull-request-available  (was: )

> Modifications to the metastore for catalogs
> ---
>
> Key: HIVE-18755
> URL: https://issues.apache.org/jira/browse/HIVE-18755
> Project: Hive
>  Issue Type: Sub-task
>  Components: Metastore
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
>  Labels: pull-request-available
>
> Step 1 of adding catalogs is to add support in the metastore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18755) Modifications to the metastore for catalogs

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on HIVE-18755:
---

GitHub user alanfgates opened a pull request:

https://github.com/apache/hive/pull/320

HIVE-18755 Modifications to metastore for catalog



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alanfgates/hive hive18755

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/hive/pull/320.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #320


commit 697e0428b4046b0c36d413a74fc46c2cf28d6e67
Author: Alan Gates 
Date:   2018-03-15T22:51:06Z

HIVE-18755 Modifications to metastore for catalog




> Modifications to the metastore for catalogs
> ---
>
> Key: HIVE-18755
> URL: https://issues.apache.org/jira/browse/HIVE-18755
> Project: Hive
>  Issue Type: Sub-task
>  Components: Metastore
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
>  Labels: pull-request-available
>
> Step 1 of adding catalogs is to add support in the metastore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18970) improve AM WM metrics for use in Grafana and such

[Prasanth Jayachandran (JIRA)]

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

Prasanth Jayachandran commented on HIVE-18970:
--

+1
orthogonal question. are this info also available via print summary to console 
or logged at the end of query execution?

> improve AM WM metrics for use in Grafana and such
> -
>
> Key: HIVE-18970
> URL: https://issues.apache.org/jira/browse/HIVE-18970
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18970.patch
>
>
> AM metrics need to be tagged with something like dag ID.
> Also looks like they are not updated correctly in some cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18846) Query results cache: Allow queries to refer to the pending results of a query that has not finished yet

[Jason Dere (JIRA)]

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

Jason Dere commented on HIVE-18846:
---

Minor update to patch, just updating testconfiguration.properties to add the 
test to minillaplocal.shared. This shouldn't affect compilation.

> Query results cache: Allow queries to refer to the pending results of a query 
> that has not finished yet
> ---
>
> Key: HIVE-18846
> URL: https://issues.apache.org/jira/browse/HIVE-18846
> Project: Hive
>  Issue Type: Sub-task
>  Components: Query Planning
>Reporter: Jason Dere
>Assignee: Jason Dere
>Priority: Major
> Attachments: HIVE-18846.1.patch, HIVE-18846.2.patch, 
> HIVE-18846.3.patch
>
>
> Currently, a query's results can only be looked up in the cache if the query 
> has completely finished execution. Allow new queries to use the results cache 
> to find queries that are still executing so they can re-use the results when 
> the query has finished.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18846) Query results cache: Allow queries to refer to the pending results of a query that has not finished yet

[Jason Dere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-18846:
--
Attachment: HIVE-18846.3.patch

> Query results cache: Allow queries to refer to the pending results of a query 
> that has not finished yet
> ---
>
> Key: HIVE-18846
> URL: https://issues.apache.org/jira/browse/HIVE-18846
> Project: Hive
>  Issue Type: Sub-task
>  Components: Query Planning
>Reporter: Jason Dere
>Assignee: Jason Dere
>Priority: Major
> Attachments: HIVE-18846.1.patch, HIVE-18846.2.patch, 
> HIVE-18846.3.patch
>
>
> Currently, a query's results can only be looked up in the cache if the query 
> has completely finished execution. Allow new queries to use the results cache 
> to find queries that are still executing so they can re-use the results when 
> the query has finished.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone

[Ashutosh Chauhan (JIRA)]

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

Ashutosh Chauhan commented on HIVE-18925:
-

+1

> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
>  Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't  work if started with 
> {{-Duser.timezone=America/Bahia_Banderas}}
>  
> Steps to reproduce
>  # use [https://github.com/big-data-europe/docker-hive]
>  # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to 
> {{hive-server}} docker container environment configuration
>  # {{docker-compose up}}
>  # 
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1 
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with 
> org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000 
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause 
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000 
> (America/Bahia_Banderas)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:323)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:253)
> at org.apache.hive.beeline.Commands.executeInternal(Commands.java:997)
> at org.apache.hive.beeline.Commands.execute(Commands.java:1205)
> at org.apache.hive.beeline.Commands.sql(Commands.java:1134)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:1314)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:1178)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:1033)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:519)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:501)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:221)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.IllegalStateException: Can't overwrite cause with 
> org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000 
> (America/Bahia_Banderas)
> at java.lang.Throwable.initCause(Throwable.java:457)
> at 
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at 
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:237)
> at 
> org.apache.hive.service.cli.HiveSQLException.toCause(HiveSQLException.java:198)
> at 
> org.apache.hive.service.cli.HiveSQLException.(HiveSQLException.java:108)
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:267)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:253)
> at org.apache.hive.jdbc.HiveStatement.runAsyncOnServer(HiveStatement.java:313)
> ... 15 more
> Caused by: java.lang.ExceptionInInitializerError: null
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at 
> org.apache.hive.service.cli.HiveSQLException.newInstance(HiveSQLException.java:245)
> at 
> org.apache.hive.service.cli.HiveSQLException.toStackTrace(HiveSQLException.java:211)
> ... 21 more{noformat}
> From the above stacktrace it's not visible what is the cause, but i think 
> it's initialization of 
> {{org.apache.hive.common.util.TimestampParser#startingDateValue}}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18961) Error in results cache when query has identifiers with spaces

[Jason Dere (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-18961:
--
   Resolution: Fixed
Fix Version/s: 3.0.0
   Status: Resolved  (was: Patch Available)

Committed to master

> Error in results cache when query has identifiers with spaces
> -
>
> Key: HIVE-18961
> URL: https://issues.apache.org/jira/browse/HIVE-18961
> Project: Hive
>  Issue Type: Sub-task
>  Components: Query Planning
>Reporter: Jason Dere
>Assignee: Jason Dere
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18961.1.patch
>
>
> Found by [~gopalv]:
> {noformat}
> 2018-03-14T05:08:32,551 ERROR [0c4b7a6c-ed37-428e-ac04-ca38716f211e 
> HiveServer2-HttpHandler-Pool: Thread-8961]: parse.CalcitePlanner (:()) - 
> Unexpected ]
> org.apache.hadoop.hive.ql.parse.ParseException: line 1:100 missing EOF at 
> 'Count' near 'IMSI'
> at 
> org.apache.hadoop.hive.ql.parse.ParseDriver.parse(ParseDriver.java:220) 
> ~[hive-exec-3.0.0.3.0.0.2-132-jdere.jar:3.0.0-SNAPSHOT]
> at 
> org.apache.hadoop.hive.ql.parse.ParseUtils.parse(ParseUtils.java:74) 
> ~[hive-exec-3.0.0.3.0.0.2-132-jdere.jar:3.0.0-SNAPSHOT]
> at 
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.getQueryStringForCache(SemanticAnalyzer.java:14067)
>  ~[hive-exec-3.0.0.3.0.0.2-132-jdere.jar:]
> at 
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.createLookupInfoForQuery(SemanticAnalyzer.java:14080)
>  ~[hive-exec-3.0.0.3.0.0.2-132-jdere.ja]
> at 
> org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:11683)
>  ~[hive-exec-3.0.0.3.0.0.2-132-jdere.jar:3.0.0-S]
> at 
> org.apache.hadoop.hive.ql.parse.CalcitePlanner.analyzeInternal(CalcitePlanner.java:304)
>  ~[hive-exec-3.0.0.3.0.0.2-132-jdere.jar:3.0.0-SNAPSHO]
> at 
> org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:273)
>  ~[hive-exec-3.0.0.3.0.0.2-132-jdere.jar:3.0.0-SNA]
> at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:614) 
> ~[hive-exec-3.0.0.3.0.0.2-132-jdere.jar:3.0.0-SNAPSHOT]
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18970) improve AM WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18970:

Status: Patch Available  (was: Open)

[~prasanth_j] another small patch :)

> improve AM WM metrics for use in Grafana and such
> -
>
> Key: HIVE-18970
> URL: https://issues.apache.org/jira/browse/HIVE-18970
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18970.patch
>
>
> AM metrics need to be tagged with something like dag ID.
> Also looks like they are not updated correctly in some cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18970) improve AM WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18970:

Attachment: HIVE-18970.patch

> improve AM WM metrics for use in Grafana and such
> -
>
> Key: HIVE-18970
> URL: https://issues.apache.org/jira/browse/HIVE-18970
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18970.patch
>
>
> AM metrics need to be tagged with something like dag ID.
> Also looks like they are not updated correctly in some cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-16882) Improvements For Avro SerDe Package

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-16882:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
1s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
17s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
14s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
13s{color} | {color:green} serde: The patch generated 0 new + 38 unchanged - 4 
fixed = 38 total (was 42) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
15s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
13s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black}  9m 32s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9649/dev-support/hive-personality.sh
 |
| git revision | master / 84f7be2 |
| Default Java | 1.8.0_111 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9649/yetus/patch-asflicense-problems.txt
 |
| modules | C: serde U: serde |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9649/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Improvements For Avro SerDe Package
> ---
>
> Key: HIVE-16882
> URL: https://issues.apache.org/jira/browse/HIVE-16882
> Project: Hive
>  Issue Type: Improvement
>  Components: Serializers/Deserializers
>Affects Versions: 3.0.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Minor
> Attachments: HIVE-16882.1.patch, HIVE-16882.2.patch, 
> HIVE-16882.3.patch, HIVE-16882.4.patch
>
>
> # Use SLF4J parameter DEBUG logging
> # Use re-usable libraries where appropriate
> # Use enhanced for loops where appropriate
> # Fix several minor check-style error
> # Small performance enhancements in InstanceCache



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18971) add HS2 WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18971:

Description: HS2 should have metrics added per pool, tagged accordingly. 
Not clear if HS2 even sets up metrics right now...  (was: AM metrics need to be 
tagged with something like dag ID.
HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
even sets up metrics right now...)

> add HS2 WM metrics for use in Grafana and such
> --
>
> Key: HIVE-18971
> URL: https://issues.apache.org/jira/browse/HIVE-18971
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>
> HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
> even sets up metrics right now...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18970) add and improve WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18970:

Description: 
AM metrics need to be tagged with something like dag ID.
Also looks like they are not updated correctly in some cases.

  was:
AM metrics need to be tagged with something like dag ID.
HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
even sets up metrics right now...


> add and improve WM metrics for use in Grafana and such
> --
>
> Key: HIVE-18970
> URL: https://issues.apache.org/jira/browse/HIVE-18970
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>
> AM metrics need to be tagged with something like dag ID.
> Also looks like they are not updated correctly in some cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18970) improve AM WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18970:

Summary: improve AM WM metrics for use in Grafana and such  (was: add and 
improve WM metrics for use in Grafana and such)

> improve AM WM metrics for use in Grafana and such
> -
>
> Key: HIVE-18970
> URL: https://issues.apache.org/jira/browse/HIVE-18970
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>
> AM metrics need to be tagged with something like dag ID.
> Also looks like they are not updated correctly in some cases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18971) add HS2 WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin reassigned HIVE-18971:
---


> add HS2 WM metrics for use in Grafana and such
> --
>
> Key: HIVE-18971
> URL: https://issues.apache.org/jira/browse/HIVE-18971
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>
> AM metrics need to be tagged with something like dag ID.
> HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
> even sets up metrics right now...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18955) HoS: Unable to create Channel from class NioServerSocketChannel

[slim bouguerra (JIRA)]

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

slim bouguerra commented on HIVE-18955:
---

not sure am getting this, where the exception is happening? and what is causing 
the conflict? 

> HoS: Unable to create Channel from class NioServerSocketChannel
> ---
>
> Key: HIVE-18955
> URL: https://issues.apache.org/jira/browse/HIVE-18955
> Project: Hive
>  Issue Type: Bug
>  Components: Spark
>Reporter: Rui Li
>Priority: Major
>
> Hit the issue when trying launch spark job. Stack trace:
> {noformat}
> Caused by: java.lang.NoSuchMethodError: 
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
> at io.netty.channel.AbstractChannel.newId(AbstractChannel.java:111) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at io.netty.channel.AbstractChannel.(AbstractChannel.java:83) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.nio.AbstractNioChannel.(AbstractNioChannel.java:84) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.nio.AbstractNioMessageChannel.(AbstractNioMessageChannel.java:42)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:86)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:72)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method) ~[?:1.8.0_151]
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  ~[?:1.8.0_151]
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  ~[?:1.8.0_151]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423) 
> ~[?:1.8.0_151]
> at 
> io.netty.channel.ReflectiveChannelFactory.newChannel(ReflectiveChannelFactory.java:38)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> ... 32 more
> {noformat}
> It seems we have conflicts versions of class 
> {{io.netty.channel.DefaultChannelId}} from async-http-client.jar and 
> netty-all.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18925:




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

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

{color:red}ERROR:{color} -1 due to 24 failed/errored test(s), 13019 tests 
executed
*Failed tests:*
{noformat}
TestNegativeCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=94)

[jira] [Commented] (HIVE-18955) HoS: Unable to create Channel from class NioServerSocketChannel

[Jesus Camacho Rodriguez (JIRA)]

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

Jesus Camacho Rodriguez commented on HIVE-18955:


[~lirui], thanks for pinging me. I think that would work fine. [~bslim], what 
do you think?

> HoS: Unable to create Channel from class NioServerSocketChannel
> ---
>
> Key: HIVE-18955
> URL: https://issues.apache.org/jira/browse/HIVE-18955
> Project: Hive
>  Issue Type: Bug
>  Components: Spark
>Reporter: Rui Li
>Priority: Major
>
> Hit the issue when trying launch spark job. Stack trace:
> {noformat}
> Caused by: java.lang.NoSuchMethodError: 
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
> at io.netty.channel.AbstractChannel.newId(AbstractChannel.java:111) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at io.netty.channel.AbstractChannel.(AbstractChannel.java:83) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.nio.AbstractNioChannel.(AbstractNioChannel.java:84) 
> ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.nio.AbstractNioMessageChannel.(AbstractNioMessageChannel.java:42)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:86)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at 
> io.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:72)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method) ~[?:1.8.0_151]
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  ~[?:1.8.0_151]
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  ~[?:1.8.0_151]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423) 
> ~[?:1.8.0_151]
> at 
> io.netty.channel.ReflectiveChannelFactory.newChannel(ReflectiveChannelFactory.java:38)
>  ~[netty-all-4.1.17.Final.jar:4.1.17.Final]
> ... 32 more
> {noformat}
> It seems we have conflicts versions of class 
> {{io.netty.channel.DefaultChannelId}} from async-http-client.jar and 
> netty-all.jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18915) Better client logging when a HoS session can't be opened

[Aihua Xu (JIRA)]

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

Aihua Xu commented on HIVE-18915:
-

patch-2: seems we are providing the message in HiveException inconsistently. In 
many cases hive already add the cause to the message, so it's duplicate to 
print the cause again. In patch-2, just add the cause to the error message 
itself to be exposed to the client.

 

> Better client logging when a HoS session can't be opened
> 
>
> Key: HIVE-18915
> URL: https://issues.apache.org/jira/browse/HIVE-18915
> Project: Hive
>  Issue Type: Sub-task
>  Components: Spark
>Reporter: Sahil Takiar
>Assignee: Aihua Xu
>Priority: Major
> Attachments: HIVE-18915.1.patch, HIVE-18915.2.patch
>
>
> Users just get a {{FAILED: Execution Error, return code 30041 from 
> org.apache.hadoop.hive.ql.exec.spark.SparkTask. Failed to create Spark client 
> for Spark session [id]}} when a HoS session can't be opened, would be better 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18915) Better client logging when a HoS session can't be opened

[Aihua Xu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aihua Xu updated HIVE-18915:

Attachment: HIVE-18915.2.patch

> Better client logging when a HoS session can't be opened
> 
>
> Key: HIVE-18915
> URL: https://issues.apache.org/jira/browse/HIVE-18915
> Project: Hive
>  Issue Type: Sub-task
>  Components: Spark
>Reporter: Sahil Takiar
>Assignee: Aihua Xu
>Priority: Major
> Attachments: HIVE-18915.1.patch, HIVE-18915.2.patch
>
>
> Users just get a {{FAILED: Execution Error, return code 30041 from 
> org.apache.hadoop.hive.ql.exec.spark.SparkTask. Failed to create Spark client 
> for Spark session [id]}} when a HoS session can't be opened, would be better 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18970) add and improve WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18970:

Description: 
AM metrics need to be tagged with something like dag ID.
HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
even sets up metrics right now...

  was:
AM metrics need to be tagged them with something like dag ID.
HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
even sets up metrics right now...


> add and improve WM metrics for use in Grafana and such
> --
>
> Key: HIVE-18970
> URL: https://issues.apache.org/jira/browse/HIVE-18970
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>
> AM metrics need to be tagged with something like dag ID.
> HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
> even sets up metrics right now...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18970) add and improve WM metrics for use in Grafana and such

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin reassigned HIVE-18970:
---


> add and improve WM metrics for use in Grafana and such
> --
>
> Key: HIVE-18970
> URL: https://issues.apache.org/jira/browse/HIVE-18970
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>
> AM metrics need to be tagged them with something like dag ID.
> HS2 should have metrics added per pool, tagged accordingly. Not clear if HS2 
> even sets up metrics right now...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18962) add WM task state to Tez AM heartbeat

[Jason Dere (JIRA)]

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

Jason Dere commented on HIVE-18962:
---

+1

> add WM task state to Tez AM heartbeat
> -
>
> Key: HIVE-18962
> URL: https://issues.apache.org/jira/browse/HIVE-18962
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18962.01.patch, HIVE-18962.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18962) add WM task state to Tez AM heartbeat

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18962:

Attachment: HIVE-18962.01.patch

> add WM task state to Tez AM heartbeat
> -
>
> Key: HIVE-18962
> URL: https://issues.apache.org/jira/browse/HIVE-18962
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18962.01.patch, HIVE-18962.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18962) add WM task state to Tez AM heartbeat

[Sergey Shelukhin (JIRA)]

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

Sergey Shelukhin commented on HIVE-18962:
-

Addressed the RB feedback

> add WM task state to Tez AM heartbeat
> -
>
> Key: HIVE-18962
> URL: https://issues.apache.org/jira/browse/HIVE-18962
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18962.01.patch, HIVE-18962.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18969) Hive throws NPE when writing struct and list types data to a HBase backed table

[Kryvenko Igor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kryvenko Igor updated HIVE-18969:
-
Status: Patch Available  (was: Open)

> Hive throws NPE when writing struct and list types data to a HBase backed 
> table
> ---
>
> Key: HIVE-18969
> URL: https://issues.apache.org/jira/browse/HIVE-18969
> Project: Hive
>  Issue Type: Bug
>Reporter: Kryvenko Igor
>Assignee: Kryvenko Igor
>Priority: Major
> Attachments: HIVE-18969.01.patch
>
>
> "INSERT INTO" query fails with NPE when we inserting STRUCT datatype with 
> null values into a table stored in Hbase. The same issue for MAP datatype is 
> already resolved in https://issues.apache.org/jira/browse/HIVE-13065
> *Steps to reproduce*
> *1. Create tables:*
> {code}
> CREATE TABLE IF NOT EXISTS t1 (id INT);
> INSERT INTO TABLE t1 VALUES (1),(2),(3),(4),(5);
> CREATE TABLE IF NOT EXISTS `htable`(
>   `id` INT, 
>   `map_column` STRUCT)
> ROW FORMAT SERDE 'org.apache.hadoop.hive.hbase.HBaseSerDe' 
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' 
> WITH SERDEPROPERTIES ( 
>   'hbase.columns.mapping'=':key,id:id', 
>   'serialization.format'='1')
> TBLPROPERTIES ( 'hbase.table.name'='/tmp/h');
> {code}
> *2. Insert into table stored the struct with NULL value in it:*
> {code}
> INSERT INTO `htable` SELECT 2,NAMED_STRUCT("s_int",CAST(NULL AS 
> INT),"s_string","s1","s_date",CAST('2018-03-12' AS DATE)) FROM t1 LIMIT 1;
> {code}
> The mapreduce job for insert query fails. Error messages are as below:
> {code}
> Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
> org.apache.hadoop.hive.serde2.SerDeException: java.lan$
> at 
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.process(FileSinkOperator.java:787)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:879)
> at 
> org.apache.hadoop.hive.ql.exec.LimitOperator.process(LimitOperator.java:63)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:879)
> at 
> org.apache.hadoop.hive.ql.exec.SelectOperator.process(SelectOperator.java:95)
> at 
> org.apache.hadoop.hive.ql.exec.tez.ReduceRecordSource$GroupIterator.next(ReduceRecordSource.java:348)
> ... 17 more
> Caused by: org.apache.hadoop.hive.serde2.SerDeException: 
> java.lang.NullPointerException
> at 
> org.apache.hadoop.hive.hbase.HBaseSerDe.serialize(HBaseSerDe.java:301)
> at 
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.process(FileSinkOperator.java:714)
> ... 22 more
> Caused by: java.lang.NullPointerException
> at 
> org.apache.hadoop.hive.serde2.objectinspector.primitive.WritableIntObjectInspector.get(WritableIntObject$
> at 
> org.apache.hadoop.hive.serde2.lazy.LazyUtils.writePrimitiveUTF8(LazyUtils.java:239)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:236)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:295)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:222)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serializeField(HBaseRowSerializer.java:194)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:118)
> at 
> org.apache.hadoop.hive.hbase.HBaseSerDe.serialize(HBaseSerDe.java:297)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18969) Hive throws NPE when writing struct and list types data to a HBase backed table

[Kryvenko Igor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kryvenko Igor updated HIVE-18969:
-
Attachment: HIVE-18969.01.patch

> Hive throws NPE when writing struct and list types data to a HBase backed 
> table
> ---
>
> Key: HIVE-18969
> URL: https://issues.apache.org/jira/browse/HIVE-18969
> Project: Hive
>  Issue Type: Bug
>Reporter: Kryvenko Igor
>Assignee: Kryvenko Igor
>Priority: Major
> Attachments: HIVE-18969.01.patch
>
>
> "INSERT INTO" query fails with NPE when we inserting STRUCT datatype with 
> null values into a table stored in Hbase. The same issue for MAP datatype is 
> already resolved in https://issues.apache.org/jira/browse/HIVE-13065
> *Steps to reproduce*
> *1. Create tables:*
> {code}
> CREATE TABLE IF NOT EXISTS t1 (id INT);
> INSERT INTO TABLE t1 VALUES (1),(2),(3),(4),(5);
> CREATE TABLE IF NOT EXISTS `htable`(
>   `id` INT, 
>   `map_column` STRUCT)
> ROW FORMAT SERDE 'org.apache.hadoop.hive.hbase.HBaseSerDe' 
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' 
> WITH SERDEPROPERTIES ( 
>   'hbase.columns.mapping'=':key,id:id', 
>   'serialization.format'='1')
> TBLPROPERTIES ( 'hbase.table.name'='/tmp/h');
> {code}
> *2. Insert into table stored the struct with NULL value in it:*
> {code}
> INSERT INTO `htable` SELECT 2,NAMED_STRUCT("s_int",CAST(NULL AS 
> INT),"s_string","s1","s_date",CAST('2018-03-12' AS DATE)) FROM t1 LIMIT 1;
> {code}
> The mapreduce job for insert query fails. Error messages are as below:
> {code}
> Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
> org.apache.hadoop.hive.serde2.SerDeException: java.lan$
> at 
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.process(FileSinkOperator.java:787)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:879)
> at 
> org.apache.hadoop.hive.ql.exec.LimitOperator.process(LimitOperator.java:63)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:879)
> at 
> org.apache.hadoop.hive.ql.exec.SelectOperator.process(SelectOperator.java:95)
> at 
> org.apache.hadoop.hive.ql.exec.tez.ReduceRecordSource$GroupIterator.next(ReduceRecordSource.java:348)
> ... 17 more
> Caused by: org.apache.hadoop.hive.serde2.SerDeException: 
> java.lang.NullPointerException
> at 
> org.apache.hadoop.hive.hbase.HBaseSerDe.serialize(HBaseSerDe.java:301)
> at 
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.process(FileSinkOperator.java:714)
> ... 22 more
> Caused by: java.lang.NullPointerException
> at 
> org.apache.hadoop.hive.serde2.objectinspector.primitive.WritableIntObjectInspector.get(WritableIntObject$
> at 
> org.apache.hadoop.hive.serde2.lazy.LazyUtils.writePrimitiveUTF8(LazyUtils.java:239)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:236)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:295)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:222)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serializeField(HBaseRowSerializer.java:194)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:118)
> at 
> org.apache.hadoop.hive.hbase.HBaseSerDe.serialize(HBaseSerDe.java:297)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18969) Hive throws NPE when writing struct and list types data to a HBase backed table

[Kryvenko Igor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kryvenko Igor reassigned HIVE-18969:



> Hive throws NPE when writing struct and list types data to a HBase backed 
> table
> ---
>
> Key: HIVE-18969
> URL: https://issues.apache.org/jira/browse/HIVE-18969
> Project: Hive
>  Issue Type: Bug
>Reporter: Kryvenko Igor
>Assignee: Kryvenko Igor
>Priority: Major
>
> "INSERT INTO" query fails with NPE when we inserting STRUCT datatype with 
> null values into a table stored in Hbase. The same issue for MAP datatype is 
> already resolved in https://issues.apache.org/jira/browse/HIVE-13065
> *Steps to reproduce*
> *1. Create tables:*
> {code}
> CREATE TABLE IF NOT EXISTS t1 (id INT);
> INSERT INTO TABLE t1 VALUES (1),(2),(3),(4),(5);
> CREATE TABLE IF NOT EXISTS `htable`(
>   `id` INT, 
>   `map_column` STRUCT)
> ROW FORMAT SERDE 'org.apache.hadoop.hive.hbase.HBaseSerDe' 
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' 
> WITH SERDEPROPERTIES ( 
>   'hbase.columns.mapping'=':key,id:id', 
>   'serialization.format'='1')
> TBLPROPERTIES ( 'hbase.table.name'='/tmp/h');
> {code}
> *2. Insert into table stored the struct with NULL value in it:*
> {code}
> INSERT INTO `htable` SELECT 2,NAMED_STRUCT("s_int",CAST(NULL AS 
> INT),"s_string","s1","s_date",CAST('2018-03-12' AS DATE)) FROM t1 LIMIT 1;
> {code}
> The mapreduce job for insert query fails. Error messages are as below:
> {code}
> Caused by: org.apache.hadoop.hive.ql.metadata.HiveException: 
> org.apache.hadoop.hive.serde2.SerDeException: java.lan$
> at 
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.process(FileSinkOperator.java:787)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:879)
> at 
> org.apache.hadoop.hive.ql.exec.LimitOperator.process(LimitOperator.java:63)
> at org.apache.hadoop.hive.ql.exec.Operator.forward(Operator.java:879)
> at 
> org.apache.hadoop.hive.ql.exec.SelectOperator.process(SelectOperator.java:95)
> at 
> org.apache.hadoop.hive.ql.exec.tez.ReduceRecordSource$GroupIterator.next(ReduceRecordSource.java:348)
> ... 17 more
> Caused by: org.apache.hadoop.hive.serde2.SerDeException: 
> java.lang.NullPointerException
> at 
> org.apache.hadoop.hive.hbase.HBaseSerDe.serialize(HBaseSerDe.java:301)
> at 
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.process(FileSinkOperator.java:714)
> ... 22 more
> Caused by: java.lang.NullPointerException
> at 
> org.apache.hadoop.hive.serde2.objectinspector.primitive.WritableIntObjectInspector.get(WritableIntObject$
> at 
> org.apache.hadoop.hive.serde2.lazy.LazyUtils.writePrimitiveUTF8(LazyUtils.java:239)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:236)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:295)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:222)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serializeField(HBaseRowSerializer.java:194)
> at 
> org.apache.hadoop.hive.hbase.HBaseRowSerializer.serialize(HBaseRowSerializer.java:118)
> at 
> org.apache.hadoop.hive.hbase.HBaseSerDe.serialize(HBaseSerDe.java:297)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-16992) LLAP: monitoring and better default lambda for LRFU policy

[Gopal V (JIRA)]

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

Gopal V commented on HIVE-16992:


LGTM - +1

The Parquet cache changes would be interesting to look through the new metrics, 
since I haven't tested that heavily yet.

> LLAP: monitoring and better default lambda for LRFU policy
> --
>
> Key: HIVE-16992
> URL: https://issues.apache.org/jira/browse/HIVE-16992
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-16992.patch
>
>
> LRFU is currently skewed heavily towards LRU; there are 10k-s or 100k-s of 
> buffers tracked during a typical workload, but the heap size is around 700. 
> We should see if making it closer to LFU (by tweaking the lambda) will 
> improve hit rate with small queries infrequently interleaved with large 
> scans; and whether it will have negative effects due to perf overhead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18925) Hive doesn't work when JVM is America/Bahia_Banderas time zone

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18925:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  7m 
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
12s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  0m 
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
14s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
12s{color} | {color:red} common: The patch generated 3 new + 11 unchanged - 2 
fixed = 14 total (was 13) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
12s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
12s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black}  9m 23s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9648/dev-support/hive-personality.sh
 |
| git revision | master / 84f7be2 |
| Default Java | 1.8.0_111 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9648/yetus/diff-checkstyle-common.txt
 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9648/yetus/patch-asflicense-problems.txt
 |
| modules | C: common U: common |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9648/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This message was automatically generated.



> Hive doesn't work when JVM is America/Bahia_Banderas time zone
> --
>
> Key: HIVE-18925
> URL: https://issues.apache.org/jira/browse/HIVE-18925
> Project: Hive
>  Issue Type: Bug
> Environment: JVM in America/Bahia_Banderas zone
>Reporter: Piotr Findeisen
>Assignee: Piotr Findeisen
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-18925.patch
>
>
> Hive Server2 doesn't  work if started with 
> {{-Duser.timezone=America/Bahia_Banderas}}
>  
> Steps to reproduce
>  # use [https://github.com/big-data-europe/docker-hive]
>  # Add {{HADOOP_CLIENT_OPTS: '-Duser.timezone=America/Bahia_Banderas'}} to 
> {{hive-server}} docker container environment configuration
>  # {{docker-compose up}}
>  # 
> {code:java}
> host# docker-compose exec hive-server bash
> container# /opt/hive/bin/beeline -u jdbc:hive2://localhost:1 
> --verbose=true
> ...
> jdbc:hive2://localhost:1> select 1;{code}
> The above fails and prints
> {noformat}
> Error: java.lang.IllegalStateException: Can't overwrite cause with 
> org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 1970-01-01T00:00:00.000 
> (America/Bahia_Banderas) (state=08S01,code=0)
> java.sql.SQLException: java.lang.IllegalStateException: Can't overwrite cause 
> with org.joda.time.IllegalInstantException: Illegal instant due to time zone 
> offset transition (daylight savings time 'gap'): 

[jira] [Updated] (HIVE-18951) Fix the llapdump usage error in llapdump.sh

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18951:

   Resolution: Fixed
Fix Version/s: 3.0.0
   Status: Resolved  (was: Patch Available)

Committed to master. Thanks for the patch!

> Fix the llapdump usage error in llapdump.sh
> ---
>
> Key: HIVE-18951
> URL: https://issues.apache.org/jira/browse/HIVE-18951
> Project: Hive
>  Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Saijin Huang
>Assignee: Saijin Huang
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HIVE-18951.1.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18965) HIVE-17990 didn't update derby SQL scripts

[Vineet Garg (JIRA)]

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

Vineet Garg commented on HIVE-18965:


+1

> HIVE-17990 didn't update derby SQL scripts
> --
>
> Key: HIVE-18965
> URL: https://issues.apache.org/jira/browse/HIVE-18965
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18965.patch
>
>
> Owing to HIVE-18775, there are currently two copies of the derby installation 
> and upgrade script.  HIVE-17990 only updated the one in standalone-metastore. 
>  The one in metastore needs to be updated as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18968) LLAP: report guaranteed tasks count in AM registry to check for consistency

[Sergey Shelukhin (JIRA)]

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

Sergey Shelukhin commented on HIVE-18968:
-

[~prasanth_j] can you take a look? a relatively simple patch.

Lots of whitespace issues, I'll fix those on commit or next iter

> LLAP: report guaranteed tasks count in AM registry to check for consistency
> ---
>
> Key: HIVE-18968
> URL: https://issues.apache.org/jira/browse/HIVE-18968
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18968.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18908) Add support for FULL OUTER JOIN to MapJoin

[Matt McCline (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-18908:

Attachment: FULL OUTER MapJoin Code Changes.docx

> Add support for FULL OUTER JOIN to MapJoin
> --
>
> Key: HIVE-18908
> URL: https://issues.apache.org/jira/browse/HIVE-18908
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Matt McCline
>Assignee: Matt McCline
>Priority: Critical
> Attachments: FULL OUTER MapJoin Code Changes.docx, 
> HIVE-18908.01.patch, HIVE-18908.02.patch, HIVE-18908.03.patch, 
> HIVE-18908.04.patch, HIVE-18908.05.patch, HIVE-18908.06.patch, 
> HIVE-18908.07.patch, JOIN to MAPJOIN Transformation.pdf, SHARED-MEMORY FULL 
> OUTER MapJoin.pdf
>
>
> Currently, we do not support FULL OUTER JOIN in MapJoin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (HIVE-18940) Hive notifications serialize all write DDL operations

[Vihang Karajgaonkar (JIRA)]

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

Vihang Karajgaonkar edited comment on HIVE-18940 at 3/15/18 8:17 PM:
-

I think may be I didn't make my suggestion very clear. I did not suggest using 
auto-increment for commit id. auto-increment is just use to uniquely identify 
an event. This useful because now we are adding tons of information in one 
event. So instead of creating one giant event we can create several small 
events. The relationship between a commit id and event id is one to many. There 
could be many event ids associated with one commit id. The commit id itself is 
a monotonically increasing global number generated just before a transaction 
does an actual commit. Here is the pseudo code of my suggestion above:

Modify NOTIFICATION_LOG to add a new field CommitID

Modify NOTIFICATION_LOG table such that EVENT_ID is an auto-increment

Remove the use of NOTIFICATION_SEQUENCE (or perhaps we can reuse it to generate 
commit id)

Now here is how the methods generating events might look like
{code:java}
public someMethodWhichGeneratesEvents() {
List allEventsInThisTransaction;
openTransaction(allEventsInThisTransaction);
//do some work which adds events to allEventsInThisTransaction
//openTransaction again; pass the allEventsInThisTransaction
openTransaction(allEventsInThisTransaction);
//dummy commit
commit(allEventsInThisTransaction);
//actual commit
commit(allEventsInThisTransaction);
}
{code}
 The commits would look like this
  
{code:java}
public boolean commit(List eventsInThisTransaction) {
counter--;
//if this is an actual commit
if (counter == 0) {
//generate one monotonically increasing number from database
//same logic as used for generating event id currently from 
NOTIFICATION_SEQUENCE table
//lock is held for a constant time irrespective of how many events this 
transaction generates
commitId = getCommitID();
//add events
for (Event event : eventsInThisTransaction) {
  event.setCommitId(commitID);
  addNotificationEvent(event);
}
return pm.commit();
}
{code}
 

So if the commit fails, no events are generated. If the commit succeeds all the 
events are generated with unique event ids and the same commit id. If there are 
holes in commit id, it means that the transaction has failed and is guaranteed 
never to be filled.


was (Author: vihangk1):
I think may be I didn't make my suggestion very clear. I did not suggest using 
auto-increment for commit id. auto-increment is just use to uniquely identify 
an event. This useful because now we are adding tons of information in one 
event. The relationship between a commit id and event id is one to many. There 
could be many event ids associated with one commit id. The commit id itself is 
a monotonically increasing global number generated just before a transaction 
does an actual commit. Here is the pseudo code of my suggestion above:

Modify NOTIFICATION_LOG to add a new field CommitID

Modify NOTIFICATION_LOG table such that EVENT_ID is an auto-increment

Remove the use of NOTIFICATION_SEQUENCE (or perhaps we can reuse it to generate 
commit id)

Now here is how the methods generating events might look like
{code:java}
public someMethodWhichGeneratesEvents() {
List allEventsInThisTransaction;
openTransaction(allEventsInThisTransaction);
//do some work which adds events to allEventsInThisTransaction
//openTransaction again; pass the allEventsInThisTransaction
openTransaction(allEventsInThisTransaction);
//dummy commit
commit(allEventsInThisTransaction);
//actual commit
commit(allEventsInThisTransaction);
}
{code}
 The commits would look like this
  
{code:java}
public boolean commit(List eventsInThisTransaction) {
counter--;
//if this is an actual commit
if (counter == 0) {
//generate one monotonically increasing number from database
//same logic as used for generating event id currently from 
NOTIFICATION_SEQUENCE table
//lock is held for a constant time irrespective of how many events this 
transaction generates
commitId = getCommitID();
//add events
for (Event event : eventsInThisTransaction) {
  event.setCommitId(commitID);
  addNotificationEvent(event);
}
return pm.commit();
}
{code}
 

So if the commit fails, no events are generated. If the commit succeeds all the 
events are generated with unique event ids and the same commit id. If there are 
holes in commit id, it means that the transaction has failed and is guaranteed 
never to be filled.

> Hive notifications serialize all write DDL operations
> -
>
> Key: HIVE-18940
> URL: https://issues.apache.org/jira/browse/HIVE-18940
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alexander Kolbasov
>Priority: Major
>
> The 

[jira] [Commented] (HIVE-18910) Migrate to Murmur hash for shuffle and bucketing

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18910:




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

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

{color:red}ERROR:{color} -1 due to 202 failed/errored test(s), 13415 tests 
executed
*Failed tests:*
{noformat}
TestNegativeCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=95)

[jira] [Updated] (HIVE-18968) LLAP: report guaranteed tasks count in AM registry to check for consistency

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18968:

Status: Patch Available  (was: Open)

> LLAP: report guaranteed tasks count in AM registry to check for consistency
> ---
>
> Key: HIVE-18968
> URL: https://issues.apache.org/jira/browse/HIVE-18968
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18968.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18968) LLAP: report guaranteed tasks count in AM registry to check for consistency

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18968:

Attachment: HIVE-18968.patch

> LLAP: report guaranteed tasks count in AM registry to check for consistency
> ---
>
> Key: HIVE-18968
> URL: https://issues.apache.org/jira/browse/HIVE-18968
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18968.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18908) Add support for FULL OUTER JOIN to MapJoin

[Matt McCline (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-18908:

Attachment: (was: HIVE-18908.08.patch)

> Add support for FULL OUTER JOIN to MapJoin
> --
>
> Key: HIVE-18908
> URL: https://issues.apache.org/jira/browse/HIVE-18908
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Matt McCline
>Assignee: Matt McCline
>Priority: Critical
> Attachments: HIVE-18908.01.patch, HIVE-18908.02.patch, 
> HIVE-18908.03.patch, HIVE-18908.04.patch, HIVE-18908.05.patch, 
> HIVE-18908.06.patch, HIVE-18908.07.patch, JOIN to MAPJOIN Transformation.pdf, 
> SHARED-MEMORY FULL OUTER MapJoin.pdf
>
>
> Currently, we do not support FULL OUTER JOIN in MapJoin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18967) Standalone metastore SQL upgrade scripts do not properly set schema version

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-18967:
--
Attachment: HIVE-18967.patch

> Standalone metastore SQL upgrade scripts do not properly set schema version
> ---
>
> Key: HIVE-18967
> URL: https://issues.apache.org/jira/browse/HIVE-18967
> Project: Hive
>  Issue Type: Bug
>  Components: Standalone Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18967.patch
>
>
> The new combined upgrade scripts for Hive 2.3 to 3.0 transition do not 
> properly set the schema version after they have completed the upgrade.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18968) LLAP: report guaranteed tasks count in AM registry to check for consistency

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin reassigned HIVE-18968:
---


> LLAP: report guaranteed tasks count in AM registry to check for consistency
> ---
>
> Key: HIVE-18968
> URL: https://issues.apache.org/jira/browse/HIVE-18968
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18967) Standalone metastore SQL upgrade scripts do not properly set schema version

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-18967:
--
Status: Patch Available  (was: Open)

It turns out that the update of the schema version was being done, just in the 
middle of each upgrade script instead of at the end where it belonged.  This 
patch moves them to the end and adds a comment so that developers don't make 
the same mistake again.

This also fixes failures introduced in the Mysql and SqlServer upgrade scripts 
as part of HIVE-18675.

> Standalone metastore SQL upgrade scripts do not properly set schema version
> ---
>
> Key: HIVE-18967
> URL: https://issues.apache.org/jira/browse/HIVE-18967
> Project: Hive
>  Issue Type: Bug
>  Components: Standalone Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
>
> The new combined upgrade scripts for Hive 2.3 to 3.0 transition do not 
> properly set the schema version after they have completed the upgrade.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18965) HIVE-17990 didn't update derby SQL scripts

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-18965:
--
Attachment: HIVE-18965.patch

> HIVE-17990 didn't update derby SQL scripts
> --
>
> Key: HIVE-18965
> URL: https://issues.apache.org/jira/browse/HIVE-18965
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18965.patch
>
>
> Owing to HIVE-18775, there are currently two copies of the derby installation 
> and upgrade script.  HIVE-17990 only updated the one in standalone-metastore. 
>  The one in metastore needs to be updated as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18965) HIVE-17990 didn't update derby SQL scripts

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-18965:
--
Status: Patch Available  (was: Open)

> HIVE-17990 didn't update derby SQL scripts
> --
>
> Key: HIVE-18965
> URL: https://issues.apache.org/jira/browse/HIVE-18965
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18965.patch
>
>
> Owing to HIVE-18775, there are currently two copies of the derby installation 
> and upgrade script.  HIVE-17990 only updated the one in standalone-metastore. 
>  The one in metastore needs to be updated as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18910) Migrate to Murmur hash for shuffle and bucketing

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18910:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
1s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
39s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
 5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m  
9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  2m 
 9s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
49s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
7s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
17s{color} | {color:red} streaming in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
46s{color} | {color:red} ql in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m  
5s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  3m  
5s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} storage-api: The patch generated 3 new + 88 unchanged 
- 3 fixed = 91 total (was 91) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
19s{color} | {color:red} serde: The patch generated 142 new + 214 unchanged - 3 
fixed = 356 total (was 217) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
12s{color} | {color:red} hcatalog/streaming: The patch generated 1 new + 33 
unchanged - 0 fixed = 34 total (was 33) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
55s{color} | {color:red} ql: The patch generated 26 new + 1242 unchanged - 3 
fixed = 1268 total (was 1245) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
46s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
13s{color} | {color:red} The patch generated 50 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 28m 49s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests |  asflicense  javac  javadoc  findbugs  checkstyle  compile  |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian 
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9647/dev-support/hive-personality.sh
 |
| git revision | master / 52c6e89 |
| Default Java | 1.8.0_111 |
| mvninstall | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus/patch-mvninstall-hcatalog_streaming.txt
 |
| mvninstall | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus/patch-mvninstall-ql.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus/diff-checkstyle-storage-api.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus/diff-checkstyle-serde.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus/diff-checkstyle-hcatalog_streaming.txt
 |
| checkstyle | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus/diff-checkstyle-ql.txt
 |
| asflicense | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus/patch-asflicense-problems.txt
 |
| modules | C: storage-api serde hbase-handler hcatalog/streaming 
itests/hive-blobstore ql standalone-metastore U: . |
| Console output | 
http://104.198.109.242/logs//PreCommit-HIVE-Build-9647/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |


This 

[jira] [Commented] (HIVE-18281) HiveServer2 HA for LLAP and Workload Manager

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18281:




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

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

{color:red}ERROR:{color} -1 due to 48 failed/errored test(s), 12966 tests 
executed
*Failed tests:*
{noformat}
TestNegativeCliDriver - did not produce a TEST-*.xml file (likely timed out) 
(batchId=94)

[jira] [Commented] (HIVE-18718) Integer like types throws error when there is a mismatch

[Janaki Lahorani (JIRA)]

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

Janaki Lahorani commented on HIVE-18718:


[~vihangk1]: As discussed I ran the following locally
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[cbo_rp_gby_empty]
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[default_constraint]
org.apache.hive.jdbc.TestTriggersMoveWorkloadManager.testTriggerMoveAndKill
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[union22]
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[update_notnull_constraint]
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[split_sample_out_of_range]

They all ran clean.

Rest of the newly reported issues were all GC related.

> Integer like types throws error when there is a mismatch
> 
>
> Key: HIVE-18718
> URL: https://issues.apache.org/jira/browse/HIVE-18718
> Project: Hive
>  Issue Type: Improvement
>Reporter: Janaki Lahorani
>Assignee: Janaki Lahorani
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18718.1.patch, HIVE-18718.2.patch, 
> HIVE-18718.3.patch, HIVE-18718.4.patch, HIVE-18718.4.patch
>
>
> If a value is saved with long type and read as int type it results in
> FAILED: Execution Error, return code 2 from 
> org.apache.hadoop.hive.ql.exec.mr.MapRedTask



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18908) Add support for FULL OUTER JOIN to MapJoin

[Matt McCline (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-18908:

Status: Patch Available  (was: In Progress)

> Add support for FULL OUTER JOIN to MapJoin
> --
>
> Key: HIVE-18908
> URL: https://issues.apache.org/jira/browse/HIVE-18908
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Matt McCline
>Assignee: Matt McCline
>Priority: Critical
> Attachments: HIVE-18908.01.patch, HIVE-18908.02.patch, 
> HIVE-18908.03.patch, HIVE-18908.04.patch, HIVE-18908.05.patch, 
> HIVE-18908.06.patch, HIVE-18908.07.patch, HIVE-18908.08.patch, JOIN to 
> MAPJOIN Transformation.pdf, SHARED-MEMORY FULL OUTER MapJoin.pdf
>
>
> Currently, we do not support FULL OUTER JOIN in MapJoin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18910) Migrate to Murmur hash for shuffle and bucketing

[Deepak Jaiswal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepak Jaiswal updated HIVE-18910:
--
Attachment: HIVE-18910.9.patch

> Migrate to Murmur hash for shuffle and bucketing
> 
>
> Key: HIVE-18910
> URL: https://issues.apache.org/jira/browse/HIVE-18910
> Project: Hive
>  Issue Type: Task
>Reporter: Deepak Jaiswal
>Assignee: Deepak Jaiswal
>Priority: Major
> Attachments: HIVE-18910.1.patch, HIVE-18910.2.patch, 
> HIVE-18910.3.patch, HIVE-18910.4.patch, HIVE-18910.5.patch, 
> HIVE-18910.6.patch, HIVE-18910.7.patch, HIVE-18910.8.patch, HIVE-18910.9.patch
>
>
> Hive uses JAVA hash which is not as good as murmur for better distribution 
> and efficiency in bucketing a table.
> Migrate to murmur hash but still keep backward compatibility for existing 
> users so that they dont have to reload the existing tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18940) Hive notifications serialize all write DDL operations

[Vihang Karajgaonkar (JIRA)]

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

Vihang Karajgaonkar commented on HIVE-18940:


I think may be I didn't make my suggestion very clear. I did not suggest using 
auto-increment for commit id. auto-increment is just use to uniquely identify 
an event. This useful because now we are adding tons of information in one 
event. The relationship between a commit id and event id is one to many. There 
could be many event ids associated with one commit id. The commit id itself is 
a monotonically increasing global number generated just before a transaction 
does an actual commit. Here is the pseudo code of my suggestion above:

Modify NOTIFICATION_LOG to add a new field CommitID

Modify NOTIFICATION_LOG table such that EVENT_ID is an auto-increment

Remove the use of NOTIFICATION_SEQUENCE (or perhaps we can reuse it to generate 
commit id)

Now here is how the methods generating events might look like
{code:java}
public someMethodWhichGeneratesEvents() {
List allEventsInThisTransaction;
openTransaction(allEventsInThisTransaction);
//do some work which adds events to allEventsInThisTransaction
//openTransaction again; pass the allEventsInThisTransaction
openTransaction(allEventsInThisTransaction);
//dummy commit
commit(allEventsInThisTransaction);
//actual commit
commit(allEventsInThisTransaction);
}
{code}
 The commits would look like this
  
{code:java}
public boolean commit(List eventsInThisTransaction) {
counter--;
//if this is an actual commit
if (counter == 0) {
//generate one monotonically increasing number from database
//same logic as used for generating event id currently from 
NOTIFICATION_SEQUENCE table
//lock is held for a constant time irrespective of how many events this 
transaction generates
commitId = getCommitID();
//add events
for (Event event : eventsInThisTransaction) {
  event.setCommitId(commitID);
  addNotificationEvent(event);
}
return pm.commit();
}
{code}
 

So if the commit fails, no events are generated. If the commit succeeds all the 
events are generated with unique event ids and the same commit id. If there are 
holes in commit id, it means that the transaction has failed and is guaranteed 
never to be filled.

> Hive notifications serialize all write DDL operations
> -
>
> Key: HIVE-18940
> URL: https://issues.apache.org/jira/browse/HIVE-18940
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alexander Kolbasov
>Priority: Major
>
> The implementation of DbNotificationListener uses a single row to store 
> current notification ID and uses {{SELECT FOR UPDATE}} to lock the row. This 
> serializes all write DDL operations which isn't good.
> We should consider using database auto-increment for notification ID instead. 
> Especially on mMySQL/innoDb it is supported natively with relatively 
> light-weight locking. 
> This creates potential issue for consumers though because such IDs may have 
> holes. There are two types of holes - transient hole for a transaction which 
> have not committed yet and will be committed shortly and permanent holes for 
> transactions that fail. Consumers need to deal with it. It may be useful to 
> add DB-generated timestamp as well to assist in recovery from holes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18908) Add support for FULL OUTER JOIN to MapJoin

[Matt McCline (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-18908:

Attachment: HIVE-18908.08.patch

> Add support for FULL OUTER JOIN to MapJoin
> --
>
> Key: HIVE-18908
> URL: https://issues.apache.org/jira/browse/HIVE-18908
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Matt McCline
>Assignee: Matt McCline
>Priority: Critical
> Attachments: HIVE-18908.01.patch, HIVE-18908.02.patch, 
> HIVE-18908.03.patch, HIVE-18908.04.patch, HIVE-18908.05.patch, 
> HIVE-18908.06.patch, HIVE-18908.07.patch, HIVE-18908.08.patch, JOIN to 
> MAPJOIN Transformation.pdf, SHARED-MEMORY FULL OUTER MapJoin.pdf
>
>
> Currently, we do not support FULL OUTER JOIN in MapJoin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18908) Add support for FULL OUTER JOIN to MapJoin

[Matt McCline (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt McCline updated HIVE-18908:

Status: In Progress  (was: Patch Available)

> Add support for FULL OUTER JOIN to MapJoin
> --
>
> Key: HIVE-18908
> URL: https://issues.apache.org/jira/browse/HIVE-18908
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Matt McCline
>Assignee: Matt McCline
>Priority: Critical
> Attachments: HIVE-18908.01.patch, HIVE-18908.02.patch, 
> HIVE-18908.03.patch, HIVE-18908.04.patch, HIVE-18908.05.patch, 
> HIVE-18908.06.patch, HIVE-18908.07.patch, JOIN to MAPJOIN Transformation.pdf, 
> SHARED-MEMORY FULL OUTER MapJoin.pdf
>
>
> Currently, we do not support FULL OUTER JOIN in MapJoin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18281) HiveServer2 HA for LLAP and Workload Manager

[Prasanth Jayachandran (JIRA)]

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

Prasanth Jayachandran commented on HIVE-18281:
--

Fixes test failures mostly test scoped dependency issues.

> HiveServer2 HA for LLAP and Workload Manager
> 
>
> Key: HIVE-18281
> URL: https://issues.apache.org/jira/browse/HIVE-18281
> Project: Hive
>  Issue Type: New Feature
>Affects Versions: 3.0.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
>Priority: Major
> Attachments: HIVE-18281.1.patch, HIVE-18281.2.patch, 
> HIVE-18281.4.patch, HIVE-18281.5.patch, HIVE-18281.6.patch, 
> HIVE-18281.7.patch, HIVE-18281.WIP.patch, HSI-HA.pdf
>
>
> When running HS2 with LLAP and Workload Manager, HS2 becomes single point of 
> failure as some of the states for workload management and scheduling are 
> maintained in-memory. 
> The proposal is to support Active/Passive mode of high availability in which, 
> all HS2 and tez AMs registers with ZooKeeper and a leader have to be chosen 
> which will maintain stateful information. Clients using service discovery 
> will always connect to the leader for submitting queries. There will also be 
> some responsibilities for the leader, failover handling, tez session 
> reconnect etc. Will upload some more detailed information in a separate doc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18281) HiveServer2 HA for LLAP and Workload Manager

[Prasanth Jayachandran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanth Jayachandran updated HIVE-18281:
-
Attachment: HIVE-18281.7.patch

> HiveServer2 HA for LLAP and Workload Manager
> 
>
> Key: HIVE-18281
> URL: https://issues.apache.org/jira/browse/HIVE-18281
> Project: Hive
>  Issue Type: New Feature
>Affects Versions: 3.0.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
>Priority: Major
> Attachments: HIVE-18281.1.patch, HIVE-18281.2.patch, 
> HIVE-18281.4.patch, HIVE-18281.5.patch, HIVE-18281.6.patch, 
> HIVE-18281.7.patch, HIVE-18281.WIP.patch, HSI-HA.pdf
>
>
> When running HS2 with LLAP and Workload Manager, HS2 becomes single point of 
> failure as some of the states for workload management and scheduling are 
> maintained in-memory. 
> The proposal is to support Active/Passive mode of high availability in which, 
> all HS2 and tez AMs registers with ZooKeeper and a leader have to be chosen 
> which will maintain stateful information. Clients using service discovery 
> will always connect to the leader for submitting queries. There will also be 
> some responsibilities for the leader, failover handling, tez session 
> reconnect etc. Will upload some more detailed information in a separate doc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18693) Snapshot Isolation does not work for Micromanaged table when a insert transaction is aborted

[Eugene Koifman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eugene Koifman updated HIVE-18693:
--
   Resolution: Fixed
Fix Version/s: 3.0.0
 Release Note: n/a
   Status: Resolved  (was: Patch Available)

committed to master
thanks Steve for the contribution

> Snapshot Isolation does not work for Micromanaged table when a insert 
> transaction is aborted
> 
>
> Key: HIVE-18693
> URL: https://issues.apache.org/jira/browse/HIVE-18693
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Reporter: Steve Yeom
>Assignee: Steve Yeom
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18693.01.patch, HIVE-18693.02.patch, 
> HIVE-18693.03.patch, HIVE-18693.04.patch, HIVE-18693.05.patch, 
> HIVE-18693.06.patch
>
>
> TestTxnCommands2#writeBetweenWorkerAndCleaner with minor 
> changes (changing delete command to insert command) fails on MM table.
> Specifically the last SELECT commands returns wrong results. 
> But this test works fine with full ACID table. 
> ==
> MM table inserts were not making entries into TXN_COMPONENTS, thus the 
> {{txnHandler.cleanEmptyAbortedTxns();}} logic in {{Initiator}} can wipe out 
> TXNS entry for an aborted transaction before the relevant files on disk are 
> removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18281) HiveServer2 HA for LLAP and Workload Manager

[Sergey Shelukhin (JIRA)]

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

Sergey Shelukhin commented on HIVE-18281:
-

+1 pending tests

> HiveServer2 HA for LLAP and Workload Manager
> 
>
> Key: HIVE-18281
> URL: https://issues.apache.org/jira/browse/HIVE-18281
> Project: Hive
>  Issue Type: New Feature
>Affects Versions: 3.0.0
>Reporter: Prasanth Jayachandran
>Assignee: Prasanth Jayachandran
>Priority: Major
> Attachments: HIVE-18281.1.patch, HIVE-18281.2.patch, 
> HIVE-18281.4.patch, HIVE-18281.5.patch, HIVE-18281.6.patch, 
> HIVE-18281.WIP.patch, HSI-HA.pdf
>
>
> When running HS2 with LLAP and Workload Manager, HS2 becomes single point of 
> failure as some of the states for workload management and scheduling are 
> maintained in-memory. 
> The proposal is to support Active/Passive mode of high availability in which, 
> all HS2 and tez AMs registers with ZooKeeper and a leader have to be chosen 
> which will maintain stateful information. Clients using service discovery 
> will always connect to the leader for submitting queries. There will also be 
> some responsibilities for the leader, failover handling, tez session 
> reconnect etc. Will upload some more detailed information in a separate doc. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-18281) HiveServer2 HA for LLAP and Workload Manager

[Hive QA (JIRA)]

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

Hive QA commented on HIVE-18281:


| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue}  0m  
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
1s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
38s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  3m 
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  2m 
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  2m 
33s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m  
7s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
31s{color} | {color:red} hive-unit in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red}  0m 
24s{color} | {color:red} util in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red}  0m 
35s{color} | {color:red} hive-unit in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red}  0m 35s{color} 
| {color:red} hive-unit in the patch failed. {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
14s{color} | {color:red} itests/hive-unit: The patch generated 4 new + 0 
unchanged - 0 fixed = 4 total (was 0) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m  
9s{color} | {color:red} llap-client: The patch generated 33 new + 74 unchanged 
- 9 fixed = 107 total (was 83) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
10s{color} | {color:red} llap-ext-client: The patch generated 1 new + 39 
unchanged - 0 fixed = 40 total (was 39) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m  
9s{color} | {color:red} llap-tez: The patch generated 6 new + 66 unchanged - 0 
fixed = 72 total (was 66) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
36s{color} | {color:red} ql: The patch generated 5 new + 49 unchanged - 1 fixed 
= 54 total (was 50) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red}  0m 
11s{color} | {color:red} service: The patch generated 40 new + 20 unchanged - 2 
fixed = 60 total (was 22) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
12s{color} | {color:green} common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
20s{color} | {color:green} hive-unit in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
16s{color} | {color:green} util in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m  
9s{color} | {color:green} llap-client generated 0 new + 6 unchanged - 6 fixed = 
6 total (was 12) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
11s{color} | {color:green} llap-ext-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
12s{color} | {color:green} llap-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m  
9s{color} | {color:green} llap-tez in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
56s{color} | {color:green} ql in the patch passed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
16s{color} | {color:green} service in the patch passed. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red}  0m 
14s{color} | {color:red} The patch generated 49 ASF License 

[jira] [Commented] (HIVE-18962) add WM task state to Tez AM heartbeat

[Sergey Shelukhin (JIRA)]

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

Sergey Shelukhin commented on HIVE-18962:
-

Lots of tests have OOMed, as usual

> add WM task state to Tez AM heartbeat
> -
>
> Key: HIVE-18962
> URL: https://issues.apache.org/jira/browse/HIVE-18962
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
>Priority: Major
> Attachments: HIVE-18962.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18967) Standalone metastore SQL upgrade scripts do not properly set schema version

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates reassigned HIVE-18967:
-


> Standalone metastore SQL upgrade scripts do not properly set schema version
> ---
>
> Key: HIVE-18967
> URL: https://issues.apache.org/jira/browse/HIVE-18967
> Project: Hive
>  Issue Type: Bug
>  Components: Standalone Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
>
> The new combined upgrade scripts for Hive 2.3 to 3.0 transition do not 
> properly set the schema version after they have completed the upgrade.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18966) LLAP should not shut down when some random thread goes down

[Sergey Shelukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-18966:

Description: 
LlapDaemonUncaughtExceptionHandler shuts down LLAP on any thread failure.
Not sure it's the best idea... 3rd party libraries like permitted UDFs or 
Storage Handlers (e.g. Druid recently) can have errors that should not bring 
the entire daemon down.
Perhaps we can go by thread name pattern?
Overall logging the error, unless it's an OOM or other Error, might be better.

We can also add error handling to important threads like schedulers, if it's 
missing, that will convert an exception into some critical one that will tell 
the handler to shut everything down.

  was:
LlapDaemonUncaughtExceptionHandler shuts down LLAP on any thread failure.
Not sure it's the best idea... 3rd party libraries like permitted UDFs or 
Storage Handlers (e.g. Druid recently) can have errors that should not bring 
the entire daemon down.
Perhaps we can go by thread name pattern?
Overall logging the error, unless it's an OOM or other Error, might be better.

We can also add error handling to important threads like schedulers, if it's 
missing.


> LLAP should not shut down when some random thread goes down
> ---
>
> Key: HIVE-18966
> URL: https://issues.apache.org/jira/browse/HIVE-18966
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Priority: Major
>
> LlapDaemonUncaughtExceptionHandler shuts down LLAP on any thread failure.
> Not sure it's the best idea... 3rd party libraries like permitted UDFs or 
> Storage Handlers (e.g. Druid recently) can have errors that should not bring 
> the entire daemon down.
> Perhaps we can go by thread name pattern?
> Overall logging the error, unless it's an OOM or other Error, might be better.
> We can also add error handling to important threads like schedulers, if it's 
> missing, that will convert an exception into some critical one that will tell 
> the handler to shut everything down.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18693) Snapshot Isolation does not work for Micromanaged table when a insert transaction is aborted

[Eugene Koifman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eugene Koifman updated HIVE-18693:
--
Description: 
TestTxnCommands2#writeBetweenWorkerAndCleaner with minor 
changes (changing delete command to insert command) fails on MM table.

Specifically the last SELECT commands returns wrong results. 

But this test works fine with full ACID table. 
==
MM table inserts were not making entries into TXN_COMPONENTS, thus the 
{{txnHandler.cleanEmptyAbortedTxns();}} logic in {{Initiator}} can wipe out 
TXNS entry for an aborted transaction before the relevant files on disk are 
removed.

  was:
TestTxnCommands2#writeBetweenWorkerAndCleaner with minor 
changes (changing delete command to insert command) fails on MM table.

Specifically the last SELECT commands returns wrong results. 

But this test works fine with full ACID table. 


> Snapshot Isolation does not work for Micromanaged table when a insert 
> transaction is aborted
> 
>
> Key: HIVE-18693
> URL: https://issues.apache.org/jira/browse/HIVE-18693
> Project: Hive
>  Issue Type: Bug
>  Components: Transactions
>Reporter: Steve Yeom
>Assignee: Steve Yeom
>Priority: Major
> Attachments: HIVE-18693.01.patch, HIVE-18693.02.patch, 
> HIVE-18693.03.patch, HIVE-18693.04.patch, HIVE-18693.05.patch, 
> HIVE-18693.06.patch
>
>
> TestTxnCommands2#writeBetweenWorkerAndCleaner with minor 
> changes (changing delete command to insert command) fails on MM table.
> Specifically the last SELECT commands returns wrong results. 
> But this test works fine with full ACID table. 
> ==
> MM table inserts were not making entries into TXN_COMPONENTS, thus the 
> {{txnHandler.cleanEmptyAbortedTxns();}} logic in {{Initiator}} can wipe out 
> TXNS entry for an aborted transaction before the relevant files on disk are 
> removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HIVE-17990) Add Thrift and DB storage for Schema Registry objects

[Alan Gates (JIRA)]

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

Alan Gates commented on HIVE-17990:
---

Filed HIVE-18965 to track the fix for this.

> Add Thrift and DB storage for Schema Registry objects
> -
>
> Key: HIVE-17990
> URL: https://issues.apache.org/jira/browse/HIVE-17990
> Project: Hive
>  Issue Type: Sub-task
>  Components: Standalone Metastore
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: Adding-Schema-Registry-to-Metastore.pdf, 
> HIVE-17990.2.patch, HIVE-17990.3.patch, HIVE-17990.patch
>
>
> This JIRA tracks changes to Thrift, RawStore, and DB scripts to support 
> objects in the Schema Registry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18965) HIVE-17990 didn't update derby SQL scripts

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-18965:
--
Description: Owing to HIVE-18775, there are currently two copies of the 
derby installation and upgrade script.  HIVE-17990 only updated the one in 
standalone-metastore.  The one in metastore needs to be updated as well.  (was: 
Owing to -HIVE-1+8775+-, there are currently two copies of the derby 
installation and upgrade script.  HIVE-17990 only updated the one in 
standalone-metastore.  The one in metastore needs to be updated as well.)

> HIVE-17990 didn't update derby SQL scripts
> --
>
> Key: HIVE-18965
> URL: https://issues.apache.org/jira/browse/HIVE-18965
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
>
> Owing to HIVE-18775, there are currently two copies of the derby installation 
> and upgrade script.  HIVE-17990 only updated the one in standalone-metastore. 
>  The one in metastore needs to be updated as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18965) HIVE-17990 didn't update derby SQL scripts

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates reassigned HIVE-18965:
-


> HIVE-17990 didn't update derby SQL scripts
> --
>
> Key: HIVE-18965
> URL: https://issues.apache.org/jira/browse/HIVE-18965
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
>
> Owing to HIVE-17983, there are currently two copies of the derby installation 
> and upgrade script.  HIVE-17990 only updated the one in standalone-metastore. 
>  The one in metastore needs to be updated as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (HIVE-18965) HIVE-17990 didn't update derby SQL scripts

[Alan Gates (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Gates updated HIVE-18965:
--
Description: Owing to -HIVE-1+8775+-, there are currently two copies of the 
derby installation and upgrade script.  HIVE-17990 only updated the one in 
standalone-metastore.  The one in metastore needs to be updated as well.  (was: 
Owing to HIVE-17983, there are currently two copies of the derby installation 
and upgrade script.  HIVE-17990 only updated the one in standalone-metastore.  
The one in metastore needs to be updated as well.)

> HIVE-17990 didn't update derby SQL scripts
> --
>
> Key: HIVE-18965
> URL: https://issues.apache.org/jira/browse/HIVE-18965
> Project: Hive
>  Issue Type: Bug
>  Components: Metastore
>Affects Versions: 3.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
>Priority: Major
> Fix For: 3.0.0
>
>
> Owing to -HIVE-1+8775+-, there are currently two copies of the derby 
> installation and upgrade script.  HIVE-17990 only updated the one in 
> standalone-metastore.  The one in metastore needs to be updated as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (HIVE-18964) HiveServer2 should not log errors when clients issue connection reset

[Vihang Karajgaonkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HIVE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vihang Karajgaonkar reassigned HIVE-18964:
--


> HiveServer2 should not log errors when clients issue connection reset
> -
>
> Key: HIVE-18964
> URL: https://issues.apache.org/jira/browse/HIVE-18964
> Project: Hive
>  Issue Type: Improvement
>  Components: HiveServer2
>Affects Versions: 2.3.2, 3.0.0
>Reporter: Vihang Karajgaonkar
>Assignee: Vihang Karajgaonkar
>Priority: Minor
>
> HiveServer2 logs an ugly exception trace when clients issue a connection 
> reset. There is nothing we can do when the connection is reset. This 
> exception trace should either be ignored or logged only in debug mode.
> Things become worse if you are using load balancer like HAProxy which has its 
> own health checks. HAProxy issues a connection reset to "quickly" close the 
> connection once it finds that HS2 is up and available. This spams the logs at 
> a very high frequency and makes them unusable for debugging purposes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)