[jira] [Commented] (HIVE-20615) CachedStore: Background refresh thread bug fixes
[
https://issues.apache.org/jira/browse/HIVE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821688#comment-16821688
]
Hive QA commented on HIVE-20615:
| (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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
11s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
27s{color} | {color:blue} storage-api in master has 48 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
10s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
13s{color} | {color:red} storage-api: The patch generated 63 new + 44 unchanged
- 1 fixed = 107 total (was 45) {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} findbugs {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
13s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 11m 31s{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.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16997/dev-support/hive-personality.sh
|
| git revision | master / bb71ce5 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.1 |
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16997/yetus/diff-checkstyle-storage-api.txt
|
| modules | C: storage-api U: storage-api |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16997/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> CachedStore: Background refresh thread bug fixes
>
>
> Key: HIVE-20615
> URL: https://issues.apache.org/jira/browse/HIVE-20615
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
>Affects Versions: 3.1.0
>Reporter: Vaibhav Gumashta
>Assignee: Daniel Dai
>Priority: Major
> Attachments: HIVE-20615.1.patch, HIVE-20615.1.patch,
> HIVE-20615.1.patch, HIVE-20615.1.patch, HIVE-20615.1.patch,
> HIVE-20615.1.patch, HIVE-21625.2.patch
>
>
> Regression introduced in HIVE-18264. Fixes background thread starting and
> refreshing of the table cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21621) Update Kafka Clients to recent release 2.2.0
[
https://issues.apache.org/jira/browse/HIVE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821679#comment-16821679
]
Hive QA commented on HIVE-21621:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966431/HIVE-21621.5.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15957 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16996/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16996/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16996/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966431 - PreCommit-HIVE-Build
> Update Kafka Clients to recent release 2.2.0
>
>
> Key: HIVE-21621
> URL: https://issues.apache.org/jira/browse/HIVE-21621
> Project: Hive
> Issue Type: Task
> Components: kafka integration
>Reporter: slim bouguerra
>Assignee: slim bouguerra
>Priority: Trivial
> Labels: pull-request-available
> Attachments: HIVE-21621.2.patch, HIVE-21621.3.patch,
> HIVE-21621.3.patch, HIVE-21621.4.patch, HIVE-21621.5.patch, HIVE-21621.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> all in the title update Kafka Storage Handler to the most recent clients
> library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21621) Update Kafka Clients to recent release 2.2.0
[
https://issues.apache.org/jira/browse/HIVE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821664#comment-16821664
]
Hive QA commented on HIVE-21621:
| (/) *{color:green}+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:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
53s{color} | {color:blue} Maven dependency ordering for branch {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
3s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
32s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
20s{color} | {color:blue} itests/qtest-druid in master has 7 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
40s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
25s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
33s{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} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
1s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
41s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
15s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 18m 36s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc xml compile findbugs
checkstyle |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16996/dev-support/hive-personality.sh
|
| git revision | master / bb71ce5 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: kafka-handler itests/qtest itests/qtest-druid U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16996/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Update Kafka Clients to recent release 2.2.0
>
>
> Key: HIVE-21621
> URL: https://issues.apache.org/jira/browse/HIVE-21621
> Project: Hive
> Issue Type: Task
> Components: kafka integration
>Reporter: slim bouguerra
>Assignee: slim bouguerra
>Priority: Trivial
> Labels: pull-request-available
> Attachments: HIVE-21621.2.patch, HIVE-21621.3.patch,
> HIVE-21621.3.patch, HIVE-21621.4.patch, HIVE-21621.5.patch, HIVE-21621.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> all in the title update Kafka Storage Handler to the most recent clients
> library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[
https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821652#comment-16821652
]
Hive QA commented on HIVE-21633:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966426/HIVE-21633.03.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15957 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16995/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16995/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16995/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966426 - PreCommit-HIVE-Build
> Estimate range for value generated by aggregate function in statistics
> annotation
> -
>
> Key: HIVE-21633
> URL: https://issues.apache.org/jira/browse/HIVE-21633
> Project: Hive
> Issue Type: Improvement
> Components: Statistics
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21633.02.patch, HIVE-21633.03.patch
>
>
> In some cases, we can infer the estimate of the range for a value generated
> by an aggregate function during statistics annotation. For instance, we can
> estimate the min of the sum of a column with positive min value as that same
> min value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-20615) CachedStore: Background refresh thread bug fixes
[ https://issues.apache.org/jira/browse/HIVE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated HIVE-20615: -- Attachment: HIVE-21625.2.patch > CachedStore: Background refresh thread bug fixes > > > Key: HIVE-20615 > URL: https://issues.apache.org/jira/browse/HIVE-20615 > Project: Hive > Issue Type: Sub-task > Components: Metastore >Affects Versions: 3.1.0 >Reporter: Vaibhav Gumashta >Assignee: Daniel Dai >Priority: Major > Attachments: HIVE-20615.1.patch, HIVE-20615.1.patch, > HIVE-20615.1.patch, HIVE-20615.1.patch, HIVE-20615.1.patch, > HIVE-20615.1.patch, HIVE-21625.2.patch > > > Regression introduced in HIVE-18264. Fixes background thread starting and > refreshing of the table cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HIVE-20615) CachedStore: Background refresh thread bug fixes
[ https://issues.apache.org/jira/browse/HIVE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai reassigned HIVE-20615: - Assignee: Daniel Dai (was: Vaibhav Gumashta) > CachedStore: Background refresh thread bug fixes > > > Key: HIVE-20615 > URL: https://issues.apache.org/jira/browse/HIVE-20615 > Project: Hive > Issue Type: Sub-task > Components: Metastore >Affects Versions: 3.1.0 >Reporter: Vaibhav Gumashta >Assignee: Daniel Dai >Priority: Major > Attachments: HIVE-20615.1.patch, HIVE-20615.1.patch, > HIVE-20615.1.patch, HIVE-20615.1.patch, HIVE-20615.1.patch, > HIVE-20615.1.patch, HIVE-21625.2.patch > > > Regression introduced in HIVE-18264. Fixes background thread starting and > refreshing of the table cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[
https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821640#comment-16821640
]
Hive QA commented on HIVE-21633:
| (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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
14s{color} | {color:blue} ql in master has 2256 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
59s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
7s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
41s{color} | {color:red} ql: The patch generated 1 new + 27 unchanged - 0 fixed
= 28 total (was 27) {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} findbugs {color} | {color:green} 4m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
59s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 25m 14s{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.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16995/dev-support/hive-personality.sh
|
| git revision | master / bb71ce5 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16995/yetus/diff-checkstyle-ql.txt
|
| modules | C: ql U: ql |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16995/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Estimate range for value generated by aggregate function in statistics
> annotation
> -
>
> Key: HIVE-21633
> URL: https://issues.apache.org/jira/browse/HIVE-21633
> Project: Hive
> Issue Type: Improvement
> Components: Statistics
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21633.02.patch, HIVE-21633.03.patch
>
>
> In some cases, we can infer the estimate of the range for a value generated
> by an aggregate function during statistics annotation. For instance, we can
> estimate the min of the sum of a column with positive min value as that same
> min value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21634) Materialized view rewriting over aggregate operators containing with grouping sets
[
https://issues.apache.org/jira/browse/HIVE-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821634#comment-16821634
]
Hive QA commented on HIVE-21634:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966425/HIVE-21634.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15958 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16994/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16994/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16994/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966425 - PreCommit-HIVE-Build
> Materialized view rewriting over aggregate operators containing with grouping
> sets
> --
>
> Key: HIVE-21634
> URL: https://issues.apache.org/jira/browse/HIVE-21634
> Project: Hive
> Issue Type: Improvement
> Components: Materialized views
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21634.patch
>
>
> A possible approach to support rewriting queries with an aggregate with
> grouping sets is implementing a rule that splits the aggregate in the query
> into an aggregate without grouping sets (bottom) and an aggregate with
> grouping sets (top). Then the materialized view rewriting rule will trigger
> on the former.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21621) Update Kafka Clients to recent release 2.2.0
[ https://issues.apache.org/jira/browse/HIVE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-21621: -- Attachment: HIVE-21621.5.patch > Update Kafka Clients to recent release 2.2.0 > > > Key: HIVE-21621 > URL: https://issues.apache.org/jira/browse/HIVE-21621 > Project: Hive > Issue Type: Task > Components: kafka integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Trivial > Labels: pull-request-available > Attachments: HIVE-21621.2.patch, HIVE-21621.3.patch, > HIVE-21621.3.patch, HIVE-21621.4.patch, HIVE-21621.5.patch, HIVE-21621.patch > > Time Spent: 10m > Remaining Estimate: 0h > > all in the title update Kafka Storage Handler to the most recent clients > library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21634) Materialized view rewriting over aggregate operators containing with grouping sets
[
https://issues.apache.org/jira/browse/HIVE-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821621#comment-16821621
]
Hive QA commented on HIVE-21634:
| (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:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
52s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
42s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
4s{color} | {color:blue} ql in master has 2256 extant Findbugs warnings.
{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
28s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
8s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
42s{color} | {color:red} ql: The patch generated 2 new + 147 unchanged - 0
fixed = 149 total (was 147) {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} findbugs {color} | {color:green} 4m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
0s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 25m 40s{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.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16994/dev-support/hive-personality.sh
|
| git revision | master / bb71ce5 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16994/yetus/diff-checkstyle-ql.txt
|
| modules | C: ql itests U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16994/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Materialized view rewriting over aggregate operators containing with grouping
> sets
> --
>
> Key: HIVE-21634
> URL: https://issues.apache.org/jira/browse/HIVE-21634
> Project: Hive
> Issue Type: Improvement
> Components: Materialized views
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21634.patch
>
>
> A possible approach to support rewriting queries with an aggregate with
> grouping sets is implementing a rule that splits the aggregate in the query
> into an aggregate without grouping sets (bottom) and an aggregate with
> grouping sets (top). Then the materialized view rewriting rule will trigger
> on the former.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21621) Update Kafka Clients to recent release 2.2.0
[
https://issues.apache.org/jira/browse/HIVE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821612#comment-16821612
]
Hive QA commented on HIVE-21621:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966419/HIVE-21621.4.patch
{color:green}SUCCESS:{color} +1 due to 3 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 15921 tests
executed
*Failed tests:*
{noformat}
TestReplAcidTablesWithJsonMessage - did not produce a TEST-*.xml file (likely
timed out) (batchId=256)
TestReplicationScenariosAcidTables - did not produce a TEST-*.xml file (likely
timed out) (batchId=258)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[sysdb]
(batchId=170)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16993/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16993/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16993/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 3 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966419 - PreCommit-HIVE-Build
> Update Kafka Clients to recent release 2.2.0
>
>
> Key: HIVE-21621
> URL: https://issues.apache.org/jira/browse/HIVE-21621
> Project: Hive
> Issue Type: Task
> Components: kafka integration
>Reporter: slim bouguerra
>Assignee: slim bouguerra
>Priority: Trivial
> Labels: pull-request-available
> Attachments: HIVE-21621.2.patch, HIVE-21621.3.patch,
> HIVE-21621.3.patch, HIVE-21621.4.patch, HIVE-21621.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> all in the title update Kafka Storage Handler to the most recent clients
> library.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21621) Update Kafka Clients to recent release 2.2.0
[
https://issues.apache.org/jira/browse/HIVE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821594#comment-16821594
]
Hive QA commented on HIVE-21621:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:red}-1{color} | {color:red} @author {color} | {color:red} 0m
0s{color} | {color:red} The patch appears to contain 5 @author tags which the
community has agreed to not allow in code contributions. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
59s{color} | {color:blue} Maven dependency ordering for branch {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} 2m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
30s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
3s{color} | {color:blue} ql in master has 2256 extant Findbugs warnings.
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
29s{color} | {color:blue} jdbc in master has 16 extant Findbugs warnings.
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
20s{color} | {color:blue} itests/qtest-druid in master has 7 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
50s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
29s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
31s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
46s{color} | {color:red} ql: The patch generated 43 new + 433 unchanged - 2
fixed = 476 total (was 435) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 11 line(s) that end in whitespace. Use
git apply --whitespace=fix <>. Refer
https://git-scm.com/docs/git-apply {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
4s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 4m
20s{color} | {color:red} ql generated 9 new + 2256 unchanged - 0 fixed = 2265
total (was 2256) {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
52s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 38m 13s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| FindBugs | module:ql |
| | org.apache.hadoop.hive.ql.exec.DDLTask.writeToFile(String, String) may
fail to close stream At DDLTask.java:close stream At DDLTask.java:[line 2328]
|
| | Class org.apache.hadoop.hive.ql.exec.DDLTask defines non-transient
non-serializable instance field defaultAuthorizationTranslator In
DDLTask.java:instance field defaultAuthorizationTranslator In DDLTask.java |
| |
org.apache.hadoop.hive.ql.security.authorization.DefaultHiveAuthorizationTranslator
stored into non-transient field DDLTask.defaultAuthorizationTranslator At
DDLTask.java:DDLTask.defaultAuthorizationTranslator At DDLTask.java:[line 234]
|
| | Dead store to hiveConf in
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAlterTableSkewedLocation(ASTNode,
String, HashMap) At
DDLSemanticAnalyzer.java:org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAlterTableSkewedLocation(ASTNode,
String, HashMap) At DDLSemanticAnalyzer.java:[line 4258] |
| | Dead store to hiveConf in
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAltertableSkewedby(String[],
ASTNode) At
DDLSemanticAnalyzer.java:org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAltertableSkewedby(String[],
ASTNode) At DDLSemanticAnalyzer.java:[line 4114] |
| | Class org.apache.hadoop.hive.ql.plan.DDLWork defin
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: HIVE-21633.03.patch > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.02.patch, HIVE-21633.03.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21596) HiveMetastoreClient should be able to connect to older metastore servers
[
https://issues.apache.org/jira/browse/HIVE-21596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vihang Karajgaonkar updated HIVE-21596:
---
Description:
{{HiveMetastoreClient}} currently depends on the fact that both the client and
server versions are the same. Additionally, since the server APIs are backwards
compatible, it is possible for a older client (eg. 2.1.0 client version) to
connect to a newer server (eg. 3.1.0 server version) without any issues. This
is useful in setups where HMS is deployed in a remote mode and clients connect
to it remotely.
It would be a good improvement if a newer version {{HiveMetastoreClient }} can
connect to the a older server version. When a newer client is talking to a
older server following things can happen:
1. Client invokes a RPC to the older server which doesn't exist.
In such a case, thrift will throw {{Invalid method name}} exception which
should be automatically be handled by the clients since each API already throws
TException.
2. Client invokes a RPC using thrift objects which has new fields added.
When a new field is added to a thrift object, the server does not deserialize
the field in the first place since it does not know about that field id. So the
wire-compatibility exists already. However, the client side application should
understand the implications of such a behavior. In such cases, it would be
better for the client to throw exception by checking the server version which
was added in HIVE-21484
3. If the newer client has re-implemented a certain API, for example, using
newer thrift API the client will start seeing exception {{Invalid method name}}
since the older server does not have such a method.
This can be handled on the client side by making sure that the newer
implementation is conditional to the server version. Which means client should
check the server version and invoke the new implementation only if the server
version supports the newer API. (On a side note, it would be great if metastore
also gives information of which APIs are supported for a given version)
4. In such cases the API itself is binary compatible (method signature is same)
but it is semantically different than previous versions. For example, in Hive-3
the {{getAllDatabases()}} API appends the default catalog name to the request
which a older server will interpret as a pattern for the dbName and will return
nothing.
In such case, the client should make sure that the server is at the newer
version or else fall-back to the older semantically equivalent call. In this
example, it should fallback to the old {{get_all_databases}} API call.
One of the real world use-case of such a feature is in Impala which wants to
have capability to talk to both HMS 2.x and HMS 3.x. But other applications
like Spark (or third party applications which want to support multiple HMS
versions) may also find this useful.
Also, this patch will do a best effort to fix all such cases between Hive 2.3.0
and newer versions of HMS. It should be a on-going effort to be exhaustive. We
will also need to add support for this in our test infrastructure to spin up
older HMS server versions and test using newer clients APIs. I will create a
separate sub-task for that since it may need more plumbing in ptest.
was:
{{HiveMetastoreClient}} currently depends on the fact that both the client and
server versions are the same. Additionally, since the server APIs are backwards
compatible, it is possible for a older client (eg. 2.1.0 client version) to
connect to a newer server (eg. 3.1.0 server version) without any issues. This
is useful in setups where HMS is deployed in a remote mode and clients connect
to it remotely.
It would be a good improvement if a newer version {{HiveMetastoreClient }} can
connect to the a older server version. When a newer client is talking to a
older server following things can happen:
1. Client invokes a RPC to the older server which doesn't exist.
In such a case, thrift will throw {{Invalid method name}} exception which
should be automatically be handled by the clients since each API already throws
TException.
2. Client invokes a RPC using thrift objects which has new fields added.
When a new field is added to a thrift object, the server does not deserialize
the field in the first place since it does not know about that field id. So the
wire-compatibility exists already. However, the client side application should
understand the implications of such a behavior. In such cases, it would be
better for the client to throw exception by checking the server version which
was added in HIVE-21484
3. If the newer client has re-implemented a certain API, for example, using
newer thrift API the client will start seeing exception {{Invalid method name}}
since the older server does not have such a method.
This can be handled on the client side by making sure that the new
[jira] [Commented] (HIVE-21529) Hive support bootstrap of ACID/MM tables on an existing policy.
[
https://issues.apache.org/jira/browse/HIVE-21529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821583#comment-16821583
]
Jesus Camacho Rodriguez commented on HIVE-21529:
[~ashutosh.bapat], [~sankarh], {{TestReplicationScenariosAcidTables}} seems to
be timing out repeatedly recently, e.g.,
https://issues.apache.org/jira/browse/HIVE-21633?focusedCommentId=16821576&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16821576.
I am wondering whether it may be related to this patch?
> Hive support bootstrap of ACID/MM tables on an existing policy.
> ---
>
> Key: HIVE-21529
> URL: https://issues.apache.org/jira/browse/HIVE-21529
> Project: Hive
> Issue Type: Sub-task
> Components: repl, Transactions
>Affects Versions: 4.0.0
>Reporter: Sankar Hariappan
>Assignee: Ashutosh Bapat
>Priority: Major
> Labels: DR, pull-request-available, replication
> Fix For: 4.0.0
>
> Attachments: HIVE-21529.01.patch, HIVE-21529.02.patch,
> HIVE-21529.03.patch, HIVE-21529.04.patch, HIVE-21529.05.patch,
> HIVE-21529.06.patch, HIVE-21529.07.patch
>
> Time Spent: 6h 50m
> Remaining Estimate: 0h
>
> If ACID/MM tables to be enabled (hive.repl.dump.include.acid.tables) on an
> existing repl policy, then need to combine bootstrap dump of these tables
> along with the ongoing incremental dump.
> Shall add a one time config "hive.repl.bootstrap.acid.tables" to include
> bootstrap in the given dump.
> The support for hive.repl.bootstrap.cleanup.type for ACID tables to clean-up
> partially bootstrapped tables in case of retry is already in place, thanks to
> the work done during external tables. Need to test that it actually works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[
https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821579#comment-16821579
]
Hive QA commented on HIVE-21633:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966415/HIVE-21633.02.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16992/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16992/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16992/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12966415/HIVE-21633.02.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966415 - PreCommit-HIVE-Build
> Estimate range for value generated by aggregate function in statistics
> annotation
> -
>
> Key: HIVE-21633
> URL: https://issues.apache.org/jira/browse/HIVE-21633
> Project: Hive
> Issue Type: Improvement
> Components: Statistics
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21633.02.patch
>
>
> In some cases, we can infer the estimate of the range for a value generated
> by an aggregate function during statistics annotation. For instance, we can
> estimate the min of the sum of a column with positive min value as that same
> min value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[
https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821578#comment-16821578
]
Hive QA commented on HIVE-21633:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966415/HIVE-21633.02.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16991/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16991/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16991/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12966415/HIVE-21633.02.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966415 - PreCommit-HIVE-Build
> Estimate range for value generated by aggregate function in statistics
> annotation
> -
>
> Key: HIVE-21633
> URL: https://issues.apache.org/jira/browse/HIVE-21633
> Project: Hive
> Issue Type: Improvement
> Components: Statistics
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21633.02.patch
>
>
> In some cases, we can infer the estimate of the range for a value generated
> by an aggregate function during statistics annotation. For instance, we can
> estimate the min of the sum of a column with positive min value as that same
> min value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[
https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821576#comment-16821576
]
Hive QA commented on HIVE-21633:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966415/HIVE-21633.02.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 6 failed/errored test(s), 15939 tests
executed
*Failed tests:*
{noformat}
TestReplicationScenariosAcidTables - did not produce a TEST-*.xml file (likely
timed out) (batchId=258)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[groupby_grouping_window]
(batchId=35)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[subquery_scalar]
(batchId=171)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[subquery_select]
(batchId=171)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_groupby_grouping_window]
(batchId=183)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[acid_vectorization_original_tez]
(batchId=111)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16990/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16990/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16990/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 6 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966415 - PreCommit-HIVE-Build
> Estimate range for value generated by aggregate function in statistics
> annotation
> -
>
> Key: HIVE-21633
> URL: https://issues.apache.org/jira/browse/HIVE-21633
> Project: Hive
> Issue Type: Improvement
> Components: Statistics
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21633.02.patch
>
>
> In some cases, we can infer the estimate of the range for a value generated
> by an aggregate function during statistics annotation. For instance, we can
> estimate the min of the sum of a column with positive min value as that same
> min value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21634) Materialized view rewriting over aggregate operators containing with grouping sets
[ https://issues.apache.org/jira/browse/HIVE-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21634: --- Attachment: HIVE-21634.patch > Materialized view rewriting over aggregate operators containing with grouping > sets > -- > > Key: HIVE-21634 > URL: https://issues.apache.org/jira/browse/HIVE-21634 > Project: Hive > Issue Type: Improvement > Components: Materialized views >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21634.patch > > > A possible approach to support rewriting queries with an aggregate with > grouping sets is implementing a rule that splits the aggregate in the query > into an aggregate without grouping sets (bottom) and an aggregate with > grouping sets (top). Then the materialized view rewriting rule will trigger > on the former. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (HIVE-21634) Materialized view rewriting over aggregate operators containing with grouping sets
[ https://issues.apache.org/jira/browse/HIVE-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-21634 started by Jesus Camacho Rodriguez. -- > Materialized view rewriting over aggregate operators containing with grouping > sets > -- > > Key: HIVE-21634 > URL: https://issues.apache.org/jira/browse/HIVE-21634 > Project: Hive > Issue Type: Improvement > Components: Materialized views >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > > A possible approach to support rewriting queries with an aggregate with > grouping sets is implementing a rule that splits the aggregate in the query > into an aggregate without grouping sets (bottom) and an aggregate with > grouping sets (top). Then the materialized view rewriting rule will trigger > on the former. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21634) Materialized view rewriting over aggregate operators containing with grouping sets
[ https://issues.apache.org/jira/browse/HIVE-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21634: --- Status: Patch Available (was: In Progress) > Materialized view rewriting over aggregate operators containing with grouping > sets > -- > > Key: HIVE-21634 > URL: https://issues.apache.org/jira/browse/HIVE-21634 > Project: Hive > Issue Type: Improvement > Components: Materialized views >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > > A possible approach to support rewriting queries with an aggregate with > grouping sets is implementing a rule that splits the aggregate in the query > into an aggregate without grouping sets (bottom) and an aggregate with > grouping sets (top). Then the materialized view rewriting rule will trigger > on the former. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HIVE-21634) Materialized view rewriting over aggregate operators containing with grouping sets
[ https://issues.apache.org/jira/browse/HIVE-21634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez reassigned HIVE-21634: -- > Materialized view rewriting over aggregate operators containing with grouping > sets > -- > > Key: HIVE-21634 > URL: https://issues.apache.org/jira/browse/HIVE-21634 > Project: Hive > Issue Type: Improvement > Components: Materialized views >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > > A possible approach to support rewriting queries with an aggregate with > grouping sets is implementing a rule that splits the aggregate in the query > into an aggregate without grouping sets (bottom) and an aggregate with > grouping sets (top). Then the materialized view rewriting rule will trigger > on the former. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21621) Update Kafka Clients to recent release 2.2.0
[ https://issues.apache.org/jira/browse/HIVE-21621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-21621: -- Attachment: HIVE-21621.4.patch > Update Kafka Clients to recent release 2.2.0 > > > Key: HIVE-21621 > URL: https://issues.apache.org/jira/browse/HIVE-21621 > Project: Hive > Issue Type: Task > Components: kafka integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Trivial > Labels: pull-request-available > Attachments: HIVE-21621.2.patch, HIVE-21621.3.patch, > HIVE-21621.3.patch, HIVE-21621.4.patch, HIVE-21621.patch > > Time Spent: 10m > Remaining Estimate: 0h > > all in the title update Kafka Storage Handler to the most recent clients > library. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[
https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821563#comment-16821563
]
Hive QA commented on HIVE-21633:
| (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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 9m
6s{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
41s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
5s{color} | {color:blue} ql in master has 2256 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
5s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
9s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
40s{color} | {color:red} ql: The patch generated 1 new + 27 unchanged - 0 fixed
= 28 total (was 27) {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} findbugs {color} | {color:green} 4m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
59s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 25m 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.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16990/dev-support/hive-personality.sh
|
| git revision | master / bb71ce5 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16990/yetus/diff-checkstyle-ql.txt
|
| modules | C: ql U: ql |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16990/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Estimate range for value generated by aggregate function in statistics
> annotation
> -
>
> Key: HIVE-21633
> URL: https://issues.apache.org/jira/browse/HIVE-21633
> Project: Hive
> Issue Type: Improvement
> Components: Statistics
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21633.02.patch
>
>
> In some cases, we can infer the estimate of the range for a value generated
> by an aggregate function during statistics annotation. For instance, we can
> estimate the min of the sum of a column with positive min value as that same
> min value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21619) Print timestamp type without precision in SQL explain extended
[ https://issues.apache.org/jira/browse/HIVE-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821560#comment-16821560 ] Jesus Camacho Rodriguez commented on HIVE-21619: TestReplicationScenariosAcidTables seems to always timeout... Not sure how this patch could be related, but will take a look. > Print timestamp type without precision in SQL explain extended > -- > > Key: HIVE-21619 > URL: https://issues.apache.org/jira/browse/HIVE-21619 > Project: Hive > Issue Type: Bug > Components: CBO >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21619.01.patch, HIVE-21619.01.patch, > HIVE-21619.01.patch, HIVE-21619.01.patch, HIVE-21619.01.patch, > HIVE-21619.patch > > > Hive dialect should print timestamp type without precision in generated SQL, > since currently Hive does not support user-defined precision. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21619) Print timestamp type without precision in SQL explain extended
[
https://issues.apache.org/jira/browse/HIVE-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821551#comment-16821551
]
Hive QA commented on HIVE-21619:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966410/HIVE-21619.01.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 15939 tests
executed
*Failed tests:*
{noformat}
TestReplicationScenariosAcidTables - did not produce a TEST-*.xml file (likely
timed out) (batchId=258)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16989/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16989/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16989/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966410 - PreCommit-HIVE-Build
> Print timestamp type without precision in SQL explain extended
> --
>
> Key: HIVE-21619
> URL: https://issues.apache.org/jira/browse/HIVE-21619
> Project: Hive
> Issue Type: Bug
> Components: CBO
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21619.01.patch, HIVE-21619.01.patch,
> HIVE-21619.01.patch, HIVE-21619.01.patch, HIVE-21619.01.patch,
> HIVE-21619.patch
>
>
> Hive dialect should print timestamp type without precision in generated SQL,
> since currently Hive does not support user-defined precision.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21619) Print timestamp type without precision in SQL explain extended
[
https://issues.apache.org/jira/browse/HIVE-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821524#comment-16821524
]
Hive QA commented on HIVE-21619:
| (/) *{color:green}+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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
39s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
12s{color} | {color:blue} ql in master has 2256 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
0s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
43s{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} findbugs {color} | {color:green} 4m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 51s{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.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16989/dev-support/hive-personality.sh
|
| git revision | master / bb71ce5 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: ql U: ql |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16989/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Print timestamp type without precision in SQL explain extended
> --
>
> Key: HIVE-21619
> URL: https://issues.apache.org/jira/browse/HIVE-21619
> Project: Hive
> Issue Type: Bug
> Components: CBO
>Reporter: Jesus Camacho Rodriguez
>Assignee: Jesus Camacho Rodriguez
>Priority: Major
> Attachments: HIVE-21619.01.patch, HIVE-21619.01.patch,
> HIVE-21619.01.patch, HIVE-21619.01.patch, HIVE-21619.01.patch,
> HIVE-21619.patch
>
>
> Hive dialect should print timestamp type without precision in generated SQL,
> since currently Hive does not support user-defined precision.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: HIVE-21633.02.patch > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.02.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: (was: HIVE-21633.01.patch) > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.02.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: (was: HIVE-21633.01.patch) > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.01.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: HIVE-21633.01.patch > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.01.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: HIVE-21633.01.patch > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.01.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: (was: HIVE-21633.patch) > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.01.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21619) Print timestamp type without precision in SQL explain extended
[ https://issues.apache.org/jira/browse/HIVE-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21619: --- Attachment: HIVE-21619.01.patch > Print timestamp type without precision in SQL explain extended > -- > > Key: HIVE-21619 > URL: https://issues.apache.org/jira/browse/HIVE-21619 > Project: Hive > Issue Type: Bug > Components: CBO >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21619.01.patch, HIVE-21619.01.patch, > HIVE-21619.01.patch, HIVE-21619.01.patch, HIVE-21619.01.patch, > HIVE-21619.patch > > > Hive dialect should print timestamp type without precision in generated SQL, > since currently Hive does not support user-defined precision. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Status: Patch Available (was: In Progress) > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Issue Type: Improvement (was: Bug) > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-21633 started by Jesus Camacho Rodriguez. -- > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez reassigned HIVE-21633: -- > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Bug > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21633) Estimate range for value generated by aggregate function in statistics annotation
[ https://issues.apache.org/jira/browse/HIVE-21633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21633: --- Attachment: HIVE-21633.patch > Estimate range for value generated by aggregate function in statistics > annotation > - > > Key: HIVE-21633 > URL: https://issues.apache.org/jira/browse/HIVE-21633 > Project: Hive > Issue Type: Improvement > Components: Statistics >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Attachments: HIVE-21633.patch > > > In some cases, we can infer the estimate of the range for a value generated > by an aggregate function during statistics annotation. For instance, we can > estimate the min of the sum of a column with positive min value as that same > min value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HIVE-21631) Enhance metastore API to allow bulk-loading materialized views
[ https://issues.apache.org/jira/browse/HIVE-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821476#comment-16821476 ] Jesus Camacho Rodriguez edited comment on HIVE-21631 at 4/18/19 8:45 PM: - No need to have this as a sub-task under the umbrella for materialized views enhancements that was already closed, I've converted it to issue. was (Author: jcamachorodriguez): No need to have this as a sub-task under the umbrella for materialized views enhancements that was already closed, I've moved it to issue. > Enhance metastore API to allow bulk-loading materialized views > -- > > Key: HIVE-21631 > URL: https://issues.apache.org/jira/browse/HIVE-21631 > Project: Hive > Issue Type: Bug > Components: Materialized views, Metastore >Affects Versions: 3.2.0, 3.1.1 >Reporter: Craig Condit >Assignee: Jesus Camacho Rodriguez >Priority: Major > > Currently, every query in HS2 results in a metastore call per database to > retrieve all materialized views. This causes severe performance degradation > on multi-tenant clusters with thousands of databases (very similar to how the > old get_function() metastore call didn't scale). > We should add a metastore call which can retrieve all materialized view > definitions at once (for all DBs) so that we don't have to make thousands of > metastore calls per query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21631) Enhance metastore API to allow bulk-loading materialized views
[ https://issues.apache.org/jira/browse/HIVE-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821476#comment-16821476 ] Jesus Camacho Rodriguez commented on HIVE-21631: No need to have this as a sub-task under the umbrella for materialized views enhancements that was already closed, I've moved it to issue. > Enhance metastore API to allow bulk-loading materialized views > -- > > Key: HIVE-21631 > URL: https://issues.apache.org/jira/browse/HIVE-21631 > Project: Hive > Issue Type: Bug > Components: Materialized views, Metastore >Affects Versions: 3.2.0, 3.1.1 >Reporter: Craig Condit >Assignee: Jesus Camacho Rodriguez >Priority: Major > > Currently, every query in HS2 results in a metastore call per database to > retrieve all materialized views. This causes severe performance degradation > on multi-tenant clusters with thousands of databases (very similar to how the > old get_function() metastore call didn't scale). > We should add a metastore call which can retrieve all materialized view > definitions at once (for all DBs) so that we don't have to make thousands of > metastore calls per query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21631) Enhance metastore API to allow bulk-loading materialized views
[ https://issues.apache.org/jira/browse/HIVE-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-21631: --- Issue Type: Bug (was: Sub-task) Parent: (was: HIVE-14484) > Enhance metastore API to allow bulk-loading materialized views > -- > > Key: HIVE-21631 > URL: https://issues.apache.org/jira/browse/HIVE-21631 > Project: Hive > Issue Type: Bug > Components: Materialized views, Metastore >Affects Versions: 3.2.0, 3.1.1 >Reporter: Craig Condit >Assignee: Jesus Camacho Rodriguez >Priority: Major > > Currently, every query in HS2 results in a metastore call per database to > retrieve all materialized views. This causes severe performance degradation > on multi-tenant clusters with thousands of databases (very similar to how the > old get_function() metastore call didn't scale). > We should add a metastore call which can retrieve all materialized view > definitions at once (for all DBs) so that we don't have to make thousands of > metastore calls per query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HIVE-14484) Extensions for initial materialized views implementation
[ https://issues.apache.org/jira/browse/HIVE-14484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez resolved HIVE-14484. Resolution: Fixed > Extensions for initial materialized views implementation > > > Key: HIVE-14484 > URL: https://issues.apache.org/jira/browse/HIVE-14484 > Project: Hive > Issue Type: Improvement > Components: Materialized views >Affects Versions: 2.2.0 >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Fix For: 3.2.0 > > > Follow-up of HIVE-14249. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HIVE-21631) Enhance metastore API to allow bulk-loading materialized views
[ https://issues.apache.org/jira/browse/HIVE-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit reassigned HIVE-21631: --- Assignee: Jesus Camacho Rodriguez > Enhance metastore API to allow bulk-loading materialized views > -- > > Key: HIVE-21631 > URL: https://issues.apache.org/jira/browse/HIVE-21631 > Project: Hive > Issue Type: Sub-task > Components: Materialized views, Metastore >Affects Versions: 3.2.0, 3.1.1 >Reporter: Craig Condit >Assignee: Jesus Camacho Rodriguez >Priority: Major > > Currently, every query in HS2 results in a metastore call per database to > retrieve all materialized views. This causes severe performance degradation > on multi-tenant clusters with thousands of databases (very similar to how the > old get_function() metastore call didn't scale). > We should add a metastore call which can retrieve all materialized view > definitions at once (for all DBs) so that we don't have to make thousands of > metastore calls per query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21631) Enhance metastore API to allow bulk-loading materialized views
[ https://issues.apache.org/jira/browse/HIVE-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit updated HIVE-21631: Issue Type: Sub-task (was: Improvement) Parent: HIVE-14484 > Enhance metastore API to allow bulk-loading materialized views > -- > > Key: HIVE-21631 > URL: https://issues.apache.org/jira/browse/HIVE-21631 > Project: Hive > Issue Type: Sub-task > Components: Materialized views, Metastore >Affects Versions: 3.2.0, 3.1.1 >Reporter: Craig Condit >Priority: Major > > Currently, every query in HS2 results in a metastore call per database to > retrieve all materialized views. This causes severe performance degradation > on multi-tenant clusters with thousands of databases (very similar to how the > old get_function() metastore call didn't scale). > We should add a metastore call which can retrieve all materialized view > definitions at once (for all DBs) so that we don't have to make thousands of > metastore calls per query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (HIVE-14484) Extensions for initial materialized views implementation
[ https://issues.apache.org/jira/browse/HIVE-14484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Condit reopened HIVE-14484: - > Extensions for initial materialized views implementation > > > Key: HIVE-14484 > URL: https://issues.apache.org/jira/browse/HIVE-14484 > Project: Hive > Issue Type: Improvement > Components: Materialized views >Affects Versions: 2.2.0 >Reporter: Jesus Camacho Rodriguez >Assignee: Jesus Camacho Rodriguez >Priority: Major > Fix For: 3.2.0 > > > Follow-up of HIVE-14249. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21584) Java 11 preparation: system class loader is not URLClassLoader
[
https://issues.apache.org/jira/browse/HIVE-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821372#comment-16821372
]
Hive QA commented on HIVE-21584:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966380/HIVE-21584.06.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 15945 tests
executed
*Failed tests:*
{noformat}
TestReplAcidTablesWithJsonMessage - did not produce a TEST-*.xml file (likely
timed out) (batchId=256)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16987/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16987/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16987/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966380 - PreCommit-HIVE-Build
> Java 11 preparation: system class loader is not URLClassLoader
> --
>
> Key: HIVE-21584
> URL: https://issues.apache.org/jira/browse/HIVE-21584
> Project: Hive
> Issue Type: Task
> Components: Hive
>Affects Versions: 4.0.0
>Reporter: Zoltan Matyus
>Assignee: Zoltan Matyus
>Priority: Major
> Attachments: HIVE-21584.01.patch, HIVE-21584.02.patch,
> HIVE-21584.03.patch, HIVE-21584.04.patch, HIVE-21584.05.patch,
> HIVE-21584.06.patch
>
>
> Currently, Hive assumes that the system class loader is instance of
> {{URLClassLoader}}. In Java 11 this is not the case. There are a few
> (unresolved) JIRAs about specific occurrences of {{URLClassLoader}} (e.g.
> [HIVE-21237|https://issues.apache.org/jira/browse/HIVE-21237],
> [HIVE-17909|https://issues.apache.org/jira/browse/HIVE-17909]), but no
> _"remove all occurrences"_. Also I couldn't find umbrella "Java 11 upgrade"
> JIRA.
> This ticket is to remove all unconditional casts of any random class loader
> to {{URLClassLoader}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21584) Java 11 preparation: system class loader is not URLClassLoader
[
https://issues.apache.org/jira/browse/HIVE-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821348#comment-16821348
]
Hive QA commented on HIVE-21584:
| (/) *{color:green}+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:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
47s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
23s{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
42s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 2m
43s{color} | {color:blue} standalone-metastore/metastore-common in master has
29 extant Findbugs warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
33s{color} | {color:blue} common in master has 63 extant Findbugs warnings.
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
28s{color} | {color:blue} spark-client in master has 10 extant Findbugs
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
7s{color} | {color:blue} ql in master has 2256 extant Findbugs warnings.
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
45s{color} | {color:blue} llap-server in master has 81 extant Findbugs
warnings. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
31s{color} | {color:blue} beeline in master has 44 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
52s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
28s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
22s{color} | {color:green} the patch passed {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:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
11s{color} | {color:green} standalone-metastore/metastore-common: The patch
generated 0 new + 22 unchanged - 2 fixed = 22 total (was 24) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
13s{color} | {color:green} common: The patch generated 0 new + 1 unchanged - 1
fixed = 1 total (was 2) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
10s{color} | {color:green} The patch spark-client passed checkstyle {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
43s{color} | {color:green} ql: The patch generated 0 new + 194 unchanged - 3
fixed = 194 total (was 197) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
14s{color} | {color:green} llap-server: The patch generated 0 new + 8 unchanged
- 1 fixed = 8 total (was 9) {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
12s{color} | {color:green} The patch beeline passed checkstyle {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} findbugs {color} | {color:green} 2m
48s{color} | {color:green} metastore-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
42s{color} | {color:green} common generated 0 new + 62 unchanged - 1 fixed = 62
total (was 63) {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
33s{color} | {color:green} spark-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
21s{color} | {color:green} ql generated 0 new + 2252 unchanged - 4 fixed = 2252
total (was 2256) {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
54s{color} | {color:green} llap-server in the patch passed. {color} |
| {co
[jira] [Updated] (HIVE-21632) Hive should not push partition columns to the Parquet predicate, even if the data file contains the partition column
[ https://issues.apache.org/jira/browse/HIVE-21632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marta Kuczora updated HIVE-21632: - Description: If there is a partitioned Parquet table in Hive, and the data file in one of the partitions (not correctly) contains the partition column as well, filtering on the partition column will return no rows if the Parquet predicate pushdown is enabled. If the PPD is disabled, the rows will return correctly. The reason why it doesn't work is that, if the PPD is switched on, Hive will send the predicate 'partition_column= ...' to parquet and a requested schema which doesn't contain the partition column. When the data is read from parquet, this column will be skipped, because the requested schema doesn't contain it, but it still tries to apply the filter predicate, so it will return an empty result set. I think if the rows are returned correctly without PPD, they should be returned with PPD as well. Hive should omit the partition column from the Parquet predicate. > Hive should not push partition columns to the Parquet predicate, even if the > data file contains the partition column > > > Key: HIVE-21632 > URL: https://issues.apache.org/jira/browse/HIVE-21632 > Project: Hive > Issue Type: Bug >Affects Versions: 4.0.0 >Reporter: Marta Kuczora >Priority: Minor > > If there is a partitioned Parquet table in Hive, and the data file in one of > the partitions (not correctly) contains the partition column as well, > filtering on the partition column will return no rows if the Parquet > predicate pushdown is enabled. If the PPD is disabled, the rows will return > correctly. > The reason why it doesn't work is that, if the PPD is switched on, Hive will > send the predicate 'partition_column= ...' to parquet and a requested schema > which doesn't contain the partition column. When the data is read from > parquet, this column will be skipped, because the requested schema doesn't > contain it, but it still tries to apply the filter predicate, so it will > return an empty result set. > I think if the rows are returned correctly without PPD, they should be > returned with PPD as well. Hive should omit the partition column from the > Parquet predicate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21632) Hive should not push partition columns to the Parquet predicate, even if the data file contains the partition column
[ https://issues.apache.org/jira/browse/HIVE-21632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marta Kuczora updated HIVE-21632: - Summary: Hive should not push partition columns to the Parquet predicate, even if the data file contains the partition column (was: Hive should not push partition columns to the Parquet predicate, even if the data file contains a column with the same name as the partition column) > Hive should not push partition columns to the Parquet predicate, even if the > data file contains the partition column > > > Key: HIVE-21632 > URL: https://issues.apache.org/jira/browse/HIVE-21632 > Project: Hive > Issue Type: Bug >Affects Versions: 4.0.0 >Reporter: Marta Kuczora >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21612) Upgrade druid to 0.14.0-incubating
[ https://issues.apache.org/jira/browse/HIVE-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821309#comment-16821309 ] slim bouguerra commented on HIVE-21612: --- +1 pending on tests. > Upgrade druid to 0.14.0-incubating > -- > > Key: HIVE-21612 > URL: https://issues.apache.org/jira/browse/HIVE-21612 > Project: Hive > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21612.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Druid 0.14.0-incubating is released. > This task is to upgrade hive to use 0.14.0-incubating version of druid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (HIVE-21612) Upgrade druid to 0.14.0-incubating
[ https://issues.apache.org/jira/browse/HIVE-21612?focusedWorklogId=229818&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-229818 ] ASF GitHub Bot logged work on HIVE-21612: - Author: ASF GitHub Bot Created on: 18/Apr/19 17:09 Start Date: 18/Apr/19 17:09 Worklog Time Spent: 10m Work Description: b-slim commented on issue #596: HIVE-21612: Upgrade to druid 0.14.0-incubating URL: https://github.com/apache/hive/pull/596#issuecomment-484595457 LGTM This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 229818) Time Spent: 20m (was: 10m) > Upgrade druid to 0.14.0-incubating > -- > > Key: HIVE-21612 > URL: https://issues.apache.org/jira/browse/HIVE-21612 > Project: Hive > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21612.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Druid 0.14.0-incubating is released. > This task is to upgrade hive to use 0.14.0-incubating version of druid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21291) Restore historical way of handling timestamps in Avro while keeping the new semantics at the same time
[
https://issues.apache.org/jira/browse/HIVE-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821299#comment-16821299
]
Hive QA commented on HIVE-21291:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966377/HIVE-21291.5.patch
{color:green}SUCCESS:{color} +1 due to 4 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 15960 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[timestamptz_2]
(batchId=87)
org.apache.hadoop.hive.serde2.avro.TestAvroDeserializer.canDeserializeTimestamps
(batchId=341)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16986/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16986/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16986/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966377 - PreCommit-HIVE-Build
> Restore historical way of handling timestamps in Avro while keeping the new
> semantics at the same time
> --
>
> Key: HIVE-21291
> URL: https://issues.apache.org/jira/browse/HIVE-21291
> Project: Hive
> Issue Type: Sub-task
>Reporter: Zoltan Ivanfi
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21291.1.patch, HIVE-21291.2.patch,
> HIVE-21291.3.patch, HIVE-21291.4.patch, HIVE-21291.4.patch, HIVE-21291.5.patch
>
>
> This sub-task is for implementing the Avro-specific parts of the following
> plan:
> h1. Problem
> Historically, the semantics of the TIMESTAMP type in Hive depended on the
> file format. Timestamps in Avro, Parquet and RCFiles with a binary SerDe had
> _Instant_ semantics, while timestamps in ORC, textfiles and RCFiles with a
> text SerDe had _LocalDateTime_ semantics.
> The Hive community wanted to get rid of this inconsistency and have
> _LocalDateTime_ semantics in Avro, Parquet and RCFiles with a binary SerDe as
> well. *Hive 3.1 turned off normalization to UTC* to achieve this. While this
> leads to the desired new semantics, it also leads to incorrect results when
> new Hive versions read timestamps written by old Hive versions or when old
> Hive versions or any other component not aware of this change (including
> legacy Impala and Spark versions) read timestamps written by new Hive
> versions.
> h1. Solution
> To work around this issue, Hive *should restore the practice of normalizing
> to UTC* when writing timestamps to Avro, Parquet and RCFiles with a binary
> SerDe. In itself, this would restore the historical _Instant_ semantics,
> which is undesirable. In order to achieve the desired _LocalDateTime_
> semantics in spite of normalizing to UTC, newer Hive versions should record
> the session-local local time zone in the file metadata fields serving
> arbitrary key-value storage purposes.
> When reading back files with this time zone metadata, newer Hive versions (or
> any other new component aware of this extra metadata) can achieve
> _LocalDateTime_ semantics by *converting from UTC to the saved time zone
> (instead of to the local time zone)*. Legacy components that are unaware of
> the new metadata can read the files without any problem and the timestamps
> will show the historical Instant behaviour to them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21291) Restore historical way of handling timestamps in Avro while keeping the new semantics at the same time
[
https://issues.apache.org/jira/browse/HIVE-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821296#comment-16821296
]
Hive QA commented on HIVE-21291:
| (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:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
12s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
25s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
35s{color} | {color:blue} common in master has 63 extant Findbugs warnings.
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
43s{color} | {color:blue} serde in master has 197 extant Findbugs warnings.
{color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
15s{color} | {color:blue} ql in master has 2256 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 8m
23s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
27s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 9m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 8m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 8m
8s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
15s{color} | {color:red} serde: The patch generated 2 new + 131 unchanged - 0
fixed = 133 total (was 131) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 2m
6s{color} | {color:red} root: The patch generated 2 new + 588 unchanged - 0
fixed = 590 total (was 588) {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} findbugs {color} | {color:green} 5m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 8m
12s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 70m 40s{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.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16986/dev-support/hive-personality.sh
|
| git revision | master / bb71ce5 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16986/yetus/diff-checkstyle-serde.txt
|
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16986/yetus/diff-checkstyle-root.txt
|
| modules | C: common serde ql . U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16986/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Restore historical way of handling timestamps in Avro while keeping the new
> semantics at the same time
> --
>
> Key: HIVE-21291
> URL: https://issues.apache.org/jira/browse/HIVE-21291
> Project: Hive
> Issue Type: Sub-task
>Reporter: Zoltan Ivanfi
>Assignee: Karen Coppage
>Priority: Major
> Attachments: HIVE-21291.1.patch, HIVE-21291.2.patch,
> HIVE-21291.3.patch, HIVE-21291.4.patch, HIVE-21291.4.patch, HIVE-21291
[jira] [Commented] (HIVE-21630) Refactor database object reference access
[
https://issues.apache.org/jira/browse/HIVE-21630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821281#comment-16821281
]
David Lavati commented on HIVE-21630:
-
Thanks [~alangates], I discovered it and utilized it while I was working on the
original issue HIVE-21198.
I turned that into a subtask of this umbrella, as introducing all the possible
changes in 1 ticket would be too much: There are some non-trivial state changes
around a couple of places, where doing the right thing in 1 commit would be too
convoluted.
> Refactor database object reference access
> -
>
> Key: HIVE-21630
> URL: https://issues.apache.org/jira/browse/HIVE-21630
> Project: Hive
> Issue Type: Improvement
>Reporter: David Lavati
>Assignee: David Lavati
>Priority: Major
> Labels: refactor
>
> There are many places in which "
> {databasename}
> .
> {tablename}
> " is passed as a single string; there are some places where the they travel
> as 2 separate arguments or as a {{String[]}}.
> Idea would be to introduce a simple immutable class with 2 fields ; and pass
> these informations together. Making this better is required if we would want
> to enable dot in tablenames: HIVE-16907, HIVE-21151
> The refactor requires large rework especially in the ql module: this ticket
> serves as an umbrella for these steps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21584) Java 11 preparation: system class loader is not URLClassLoader
[
https://issues.apache.org/jira/browse/HIVE-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Matyus updated HIVE-21584:
-
Attachment: HIVE-21584.06.patch
> Java 11 preparation: system class loader is not URLClassLoader
> --
>
> Key: HIVE-21584
> URL: https://issues.apache.org/jira/browse/HIVE-21584
> Project: Hive
> Issue Type: Task
> Components: Hive
>Affects Versions: 4.0.0
>Reporter: Zoltan Matyus
>Assignee: Zoltan Matyus
>Priority: Major
> Attachments: HIVE-21584.01.patch, HIVE-21584.02.patch,
> HIVE-21584.03.patch, HIVE-21584.04.patch, HIVE-21584.05.patch,
> HIVE-21584.06.patch
>
>
> Currently, Hive assumes that the system class loader is instance of
> {{URLClassLoader}}. In Java 11 this is not the case. There are a few
> (unresolved) JIRAs about specific occurrences of {{URLClassLoader}} (e.g.
> [HIVE-21237|https://issues.apache.org/jira/browse/HIVE-21237],
> [HIVE-17909|https://issues.apache.org/jira/browse/HIVE-17909]), but no
> _"remove all occurrences"_. Also I couldn't find umbrella "Java 11 upgrade"
> JIRA.
> This ticket is to remove all unconditional casts of any random class loader
> to {{URLClassLoader}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21630) Refactor database object reference access
[
https://issues.apache.org/jira/browse/HIVE-21630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821215#comment-16821215
]
Alan Gates commented on HIVE-21630:
---
A class for table name already exists:
storage-api/src/org/apache/hadoop/hive/common/TableName.java
You should use that rather than create a new one.
> Refactor database object reference access
> -
>
> Key: HIVE-21630
> URL: https://issues.apache.org/jira/browse/HIVE-21630
> Project: Hive
> Issue Type: Improvement
>Reporter: David Lavati
>Assignee: David Lavati
>Priority: Major
> Labels: refactor
>
> There are many places in which "
> {databasename}
> .
> {tablename}
> " is passed as a single string; there are some places where the they travel
> as 2 separate arguments or as a {{String[]}}.
> Idea would be to introduce a simple immutable class with 2 fields ; and pass
> these informations together. Making this better is required if we would want
> to enable dot in tablenames: HIVE-16907, HIVE-21151
> The refactor requires large rework especially in the ql module: this ticket
> serves as an umbrella for these steps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21291) Restore historical way of handling timestamps in Avro while keeping the new semantics at the same time
[ https://issues.apache.org/jira/browse/HIVE-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-21291: - Status: Open (was: Patch Available) > Restore historical way of handling timestamps in Avro while keeping the new > semantics at the same time > -- > > Key: HIVE-21291 > URL: https://issues.apache.org/jira/browse/HIVE-21291 > Project: Hive > Issue Type: Sub-task >Reporter: Zoltan Ivanfi >Assignee: Karen Coppage >Priority: Major > Attachments: HIVE-21291.1.patch, HIVE-21291.2.patch, > HIVE-21291.3.patch, HIVE-21291.4.patch, HIVE-21291.4.patch, HIVE-21291.5.patch > > > This sub-task is for implementing the Avro-specific parts of the following > plan: > h1. Problem > Historically, the semantics of the TIMESTAMP type in Hive depended on the > file format. Timestamps in Avro, Parquet and RCFiles with a binary SerDe had > _Instant_ semantics, while timestamps in ORC, textfiles and RCFiles with a > text SerDe had _LocalDateTime_ semantics. > The Hive community wanted to get rid of this inconsistency and have > _LocalDateTime_ semantics in Avro, Parquet and RCFiles with a binary SerDe as > well. *Hive 3.1 turned off normalization to UTC* to achieve this. While this > leads to the desired new semantics, it also leads to incorrect results when > new Hive versions read timestamps written by old Hive versions or when old > Hive versions or any other component not aware of this change (including > legacy Impala and Spark versions) read timestamps written by new Hive > versions. > h1. Solution > To work around this issue, Hive *should restore the practice of normalizing > to UTC* when writing timestamps to Avro, Parquet and RCFiles with a binary > SerDe. In itself, this would restore the historical _Instant_ semantics, > which is undesirable. In order to achieve the desired _LocalDateTime_ > semantics in spite of normalizing to UTC, newer Hive versions should record > the session-local local time zone in the file metadata fields serving > arbitrary key-value storage purposes. > When reading back files with this time zone metadata, newer Hive versions (or > any other new component aware of this extra metadata) can achieve > _LocalDateTime_ semantics by *converting from UTC to the saved time zone > (instead of to the local time zone)*. Legacy components that are unaware of > the new metadata can read the files without any problem and the timestamps > will show the historical Instant behaviour to them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21291) Restore historical way of handling timestamps in Avro while keeping the new semantics at the same time
[ https://issues.apache.org/jira/browse/HIVE-21291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Coppage updated HIVE-21291: - Attachment: HIVE-21291.5.patch Status: Patch Available (was: Open) > Restore historical way of handling timestamps in Avro while keeping the new > semantics at the same time > -- > > Key: HIVE-21291 > URL: https://issues.apache.org/jira/browse/HIVE-21291 > Project: Hive > Issue Type: Sub-task >Reporter: Zoltan Ivanfi >Assignee: Karen Coppage >Priority: Major > Attachments: HIVE-21291.1.patch, HIVE-21291.2.patch, > HIVE-21291.3.patch, HIVE-21291.4.patch, HIVE-21291.4.patch, HIVE-21291.5.patch > > > This sub-task is for implementing the Avro-specific parts of the following > plan: > h1. Problem > Historically, the semantics of the TIMESTAMP type in Hive depended on the > file format. Timestamps in Avro, Parquet and RCFiles with a binary SerDe had > _Instant_ semantics, while timestamps in ORC, textfiles and RCFiles with a > text SerDe had _LocalDateTime_ semantics. > The Hive community wanted to get rid of this inconsistency and have > _LocalDateTime_ semantics in Avro, Parquet and RCFiles with a binary SerDe as > well. *Hive 3.1 turned off normalization to UTC* to achieve this. While this > leads to the desired new semantics, it also leads to incorrect results when > new Hive versions read timestamps written by old Hive versions or when old > Hive versions or any other component not aware of this change (including > legacy Impala and Spark versions) read timestamps written by new Hive > versions. > h1. Solution > To work around this issue, Hive *should restore the practice of normalizing > to UTC* when writing timestamps to Avro, Parquet and RCFiles with a binary > SerDe. In itself, this would restore the historical _Instant_ semantics, > which is undesirable. In order to achieve the desired _LocalDateTime_ > semantics in spite of normalizing to UTC, newer Hive versions should record > the session-local local time zone in the file metadata fields serving > arbitrary key-value storage purposes. > When reading back files with this time zone metadata, newer Hive versions (or > any other new component aware of this extra metadata) can achieve > _LocalDateTime_ semantics by *converting from UTC to the saved time zone > (instead of to the local time zone)*. Legacy components that are unaware of > the new metadata can read the files without any problem and the timestamps > will show the historical Instant behaviour to them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21593) Break up DDLTask - extract Privilege related operations
[ https://issues.apache.org/jira/browse/HIVE-21593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltan Haindrich updated HIVE-21593: Resolution: Fixed Status: Resolved (was: Patch Available) pushed to master. Thank you [~mgergely]! > Break up DDLTask - extract Privilege related operations > --- > > Key: HIVE-21593 > URL: https://issues.apache.org/jira/browse/HIVE-21593 > Project: Hive > Issue Type: Sub-task > Components: Hive >Affects Versions: 3.1.1 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Major > Labels: refactor-ddl > Fix For: 4.0.0 > > Attachments: HIVE-21593.01.patch, HIVE-21593.02.patch, > HIVE-21593.03.patch > > > DDLTask is a huge class, more than 5000 lines long. The related DDLWork is > also a huge class, which has a field for each DDL operation it supports. The > goal is to refactor these in order to have everything cut into more > handleable classes under the package org.apache.hadoop.hive.ql.exec.ddl: > * have a separate class for each operation > * have a package for each operation group (database ddl, table ddl, etc), so > the amount of classes under a package is more manageable > * make all the requests (DDLDesc subclasses) immutable > * DDLTask should be agnostic to the actual operations > * right now let's ignore the issue of having some operations handled by > DDLTask which are not actual DDL operations (lock, unlock, desc...) > In the interim time when there are two DDLTask and DDLWork classes in the > code base the new ones in the new package are called DDLTask2 and DDLWork2 > thus avoiding the usage of fully qualified class names where both the old and > the new classes are in use. > Step #5: extract all the privilege related operations from the old DDLTask, > and move them under the new package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (HIVE-21198) Introduce a database object reference class
[
https://issues.apache.org/jira/browse/HIVE-21198?focusedWorklogId=229686&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-229686
]
ASF GitHub Bot logged work on HIVE-21198:
-
Author: ASF GitHub Bot
Created on: 18/Apr/19 13:48
Start Date: 18/Apr/19 13:48
Worklog Time Spent: 10m
Work Description: dlavati-hw commented on issue #550: HIVE-21198
Introduce a database object reference class
URL: https://github.com/apache/hive/pull/550#issuecomment-484516822
The amount of possible refactors is a lot bigger then comfortable in 1
issue, so I'm reducing the scope for this and opened HIVE-21630 as an umbrella
ticket.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 229686)
Time Spent: 2h 10m (was: 2h)
> Introduce a database object reference class
> ---
>
> Key: HIVE-21198
> URL: https://issues.apache.org/jira/browse/HIVE-21198
> Project: Hive
> Issue Type: Sub-task
>Reporter: Zoltan Haindrich
>Assignee: David Lavati
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-21198.1.patch, HIVE-21198.2.patch,
> HIVE-21198.3.patch, HIVE-21198.4.patch, HIVE-21198.5.patch
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> There are many places in which "{databasename}.{tablename}" is passed as a
> single string; there are some places where the they travel as 2 separate
> arguments.
> Idea would be to introduce a simple immutable class with 2 fields ; and pass
> these informations together. Making this better is required if we would be
> wanting to enable dot in tablenames
> HIVE-16907, HIVE-21151
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (HIVE-21630) Refactor database object reference access
[
https://issues.apache.org/jira/browse/HIVE-21630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HIVE-21630 started by David Lavati.
---
> Refactor database object reference access
> -
>
> Key: HIVE-21630
> URL: https://issues.apache.org/jira/browse/HIVE-21630
> Project: Hive
> Issue Type: Improvement
>Reporter: David Lavati
>Assignee: David Lavati
>Priority: Major
> Labels: refactor
>
> There are many places in which "
> {databasename}
> .
> {tablename}
> " is passed as a single string; there are some places where the they travel
> as 2 separate arguments or as a {{String[]}}.
> Idea would be to introduce a simple immutable class with 2 fields ; and pass
> these informations together. Making this better is required if we would want
> to enable dot in tablenames: HIVE-16907, HIVE-21151
> The refactor requires large rework especially in the ql module: this ticket
> serves as an umbrella for these steps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21198) Introduce a database object reference class
[
https://issues.apache.org/jira/browse/HIVE-21198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Lavati updated HIVE-21198:
Issue Type: Sub-task (was: Improvement)
Parent: HIVE-21630
> Introduce a database object reference class
> ---
>
> Key: HIVE-21198
> URL: https://issues.apache.org/jira/browse/HIVE-21198
> Project: Hive
> Issue Type: Sub-task
>Reporter: Zoltan Haindrich
>Assignee: David Lavati
>Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-21198.1.patch, HIVE-21198.2.patch,
> HIVE-21198.3.patch, HIVE-21198.4.patch, HIVE-21198.5.patch
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> There are many places in which "{databasename}.{tablename}" is passed as a
> single string; there are some places where the they travel as 2 separate
> arguments.
> Idea would be to introduce a simple immutable class with 2 fields ; and pass
> these informations together. Making this better is required if we would be
> wanting to enable dot in tablenames
> HIVE-16907, HIVE-21151
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HIVE-21630) Refactor database object reference access
[
https://issues.apache.org/jira/browse/HIVE-21630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Lavati reassigned HIVE-21630:
---
> Refactor database object reference access
> -
>
> Key: HIVE-21630
> URL: https://issues.apache.org/jira/browse/HIVE-21630
> Project: Hive
> Issue Type: Improvement
>Reporter: David Lavati
>Assignee: David Lavati
>Priority: Major
> Labels: refactor
>
> There are many places in which "
> {databasename}
> .
> {tablename}
> " is passed as a single string; there are some places where the they travel
> as 2 separate arguments or as a {{String[]}}.
> Idea would be to introduce a simple immutable class with 2 fields ; and pass
> these informations together. Making this better is required if we would want
> to enable dot in tablenames: HIVE-16907, HIVE-21151
> The refactor requires large rework especially in the ql module: this ticket
> serves as an umbrella for these steps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21629) Monitor qtest progress realtime on console
[
https://issues.apache.org/jira/browse/HIVE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Bodor updated HIVE-21629:
Description:
While running a qtest, or running multiple qtests with the same driver,
user/dev can only see top level message for a long time:
{code}
[INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
{code}
It would be helpful to introduce a cli argument to enable some realtime
monitoring. The challenge basically is that the tests run in separate surefire
JVMs, which basically log into surefire report files, and everything which is
logged with System.out can be found in that file:
{code}
itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
{code}
so, I would expect the same or similar behavior that I would get if I tailed
this file in a separate terminal (tail -f ...)
was:
While running a qtest, or running multiple qtests with the same driver,
user/dev can only see top level message for a long time:
{code}
[INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
{code}
It would be helpful to introduce a cli argument to enable some realtime
monitoring. The challenge basically is that the tests run in separate surefire
JVMs, which basically log into surefire report files, and everything which is
logged with System.out can be found in that file:
{code}
itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
{code}
so, I would expect the same or similar behavior that I would get if I tailed
this file in a separate terminal
> Monitor qtest progress realtime on console
> --
>
> Key: HIVE-21629
> URL: https://issues.apache.org/jira/browse/HIVE-21629
> Project: Hive
> Issue Type: Bug
>Reporter: Laszlo Bodor
>Priority: Major
>
> While running a qtest, or running multiple qtests with the same driver,
> user/dev can only see top level message for a long time:
> {code}
> [INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
> {code}
> It would be helpful to introduce a cli argument to enable some realtime
> monitoring. The challenge basically is that the tests run in separate
> surefire JVMs, which basically log into surefire report files, and everything
> which is logged with System.out can be found in that file:
> {code}
> itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
> {code}
> so, I would expect the same or similar behavior that I would get if I tailed
> this file in a separate terminal (tail -f ...)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21629) Monitor qtest progress realtime on console
[
https://issues.apache.org/jira/browse/HIVE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Bodor updated HIVE-21629:
Description:
While running a qtest, or running multiple qtests with the same driver,
user/dev can only see top level message for a long time:
{code}
[INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
{code}
It would be helpful to introduce a cli argument to enable some realtime
monitoring. The challenge basically is that the tests run in separate surefire
JVMs, which basically log into surefire report files, and everything which is
logged with System.out can be found in that file:
{code}
itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
{code}
so, I would expect the same or similar behavior that I would get if I tailed
this file in a separate terminal
was:
While running a qtest, or running multiple qtests with the same driver,
user/dev can only see top level message for a long time:
{code}
[INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
{code}
It would be helpful to introduce a cli argument to enable some realtime
monitoring. The challenge basically is that the tests run in separate surefire
JVMs, which basically log into surefire report files, and everything which is
logged with System.out can be found in that file:
{code}
itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
{code}
so, I would expect the same or similar behavior as with tailing that file in a
separate terminal
> Monitor qtest progress realtime on console
> --
>
> Key: HIVE-21629
> URL: https://issues.apache.org/jira/browse/HIVE-21629
> Project: Hive
> Issue Type: Bug
>Reporter: Laszlo Bodor
>Priority: Major
>
> While running a qtest, or running multiple qtests with the same driver,
> user/dev can only see top level message for a long time:
> {code}
> [INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
> {code}
> It would be helpful to introduce a cli argument to enable some realtime
> monitoring. The challenge basically is that the tests run in separate
> surefire JVMs, which basically log into surefire report files, and everything
> which is logged with System.out can be found in that file:
> {code}
> itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
> {code}
> so, I would expect the same or similar behavior that I would get if I tailed
> this file in a separate terminal
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21629) Monitor qtest progress realtime on console
[
https://issues.apache.org/jira/browse/HIVE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Bodor updated HIVE-21629:
Description:
While running a qtest, or running multiple qtests with the same driver,
user/dev can only see top level message for a long time:
{code}
[INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
{code}
It would be helpful to introduce a cli argument to enable some realtime
monitoring. The challenge basically is that the tests run in separate surefire
JVMs, which basically log into surefire report files, and everything which is
logged with System.out can be found in that file:
{code}
itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
{code}
so, I would expect the same or similar behavior as with tailing that file in a
separate terminal
> Monitor qtest progress realtime on console
> --
>
> Key: HIVE-21629
> URL: https://issues.apache.org/jira/browse/HIVE-21629
> Project: Hive
> Issue Type: Bug
>Reporter: Laszlo Bodor
>Priority: Major
>
> While running a qtest, or running multiple qtests with the same driver,
> user/dev can only see top level message for a long time:
> {code}
> [INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
> {code}
> It would be helpful to introduce a cli argument to enable some realtime
> monitoring. The challenge basically is that the tests run in separate
> surefire JVMs, which basically log into surefire report files, and everything
> which is logged with System.out can be found in that file:
> {code}
> itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
> {code}
> so, I would expect the same or similar behavior as with tailing that file in
> a separate terminal
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21366) Inconsistent behavior of ROUND() with integer in string as argument
[
https://issues.apache.org/jira/browse/HIVE-21366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821054#comment-16821054
]
Hive QA commented on HIVE-21366:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12966348/HIVE-21366.2.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 9 failed/errored test(s), 15914 tests
executed
*Failed tests:*
{noformat}
TestConcurrentJobRequests - did not produce a TEST-*.xml file (likely timed
out) (batchId=206)
TestConcurrentJobRequestsThreads - did not produce a TEST-*.xml file (likely
timed out) (batchId=206)
TestConcurrentJobRequestsThreadsAndTimeout - did not produce a TEST-*.xml file
(likely timed out) (batchId=206)
TestDesc - did not produce a TEST-*.xml file (likely timed out) (batchId=206)
TestJobIDParser - did not produce a TEST-*.xml file (likely timed out)
(batchId=206)
TestServer - did not produce a TEST-*.xml file (likely timed out) (batchId=206)
TestTempletonUtils - did not produce a TEST-*.xml file (likely timed out)
(batchId=206)
TestTrivialExecService - did not produce a TEST-*.xml file (likely timed out)
(batchId=206)
TestWebHCatE2e - did not produce a TEST-*.xml file (likely timed out)
(batchId=206)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/16985/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/16985/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-16985/
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
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 9 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12966348 - PreCommit-HIVE-Build
> Inconsistent behavior of ROUND() with integer in string as argument
> ---
>
> Key: HIVE-21366
> URL: https://issues.apache.org/jira/browse/HIVE-21366
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Yavorski
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21366.1.patch, HIVE-21366.2.patch
>
>
> hive> SELECT ROUND('1',4) AS r_str, ROUND(1,4) AS r_num;
> OK
> r_str r_num
> *{color:#FF}1.0{color}* 1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-21612) Upgrade druid to 0.14.0-incubating
[ https://issues.apache.org/jira/browse/HIVE-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821018#comment-16821018 ] Nishant Bangarwa commented on HIVE-21612: - [~bslim] [~ashutoshc] Any comments here ? > Upgrade druid to 0.14.0-incubating > -- > > Key: HIVE-21612 > URL: https://issues.apache.org/jira/browse/HIVE-21612 > Project: Hive > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa >Priority: Major > Labels: pull-request-available > Attachments: HIVE-21612.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Druid 0.14.0-incubating is released. > This task is to upgrade hive to use 0.14.0-incubating version of druid. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-21366) Inconsistent behavior of ROUND() with integer in string as argument
[
https://issues.apache.org/jira/browse/HIVE-21366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821003#comment-16821003
]
Hive QA commented on HIVE-21366:
| (/) *{color:green}+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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 4m
1s{color} | {color:blue} ql in master has 2265 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
0s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s{color} | {color:green} ql: The patch generated 0 new + 0 unchanged - 25
fixed = 0 total (was 25) {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} findbugs {color} | {color:green} 4m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
0s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 24m 33s{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.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-16985/dev-support/hive-personality.sh
|
| git revision | master / 8f7f5d1 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| modules | C: ql U: ql |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-16985/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> Inconsistent behavior of ROUND() with integer in string as argument
> ---
>
> Key: HIVE-21366
> URL: https://issues.apache.org/jira/browse/HIVE-21366
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Yavorski
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21366.1.patch, HIVE-21366.2.patch
>
>
> hive> SELECT ROUND('1',4) AS r_str, ROUND(1,4) AS r_num;
> OK
> r_str r_num
> *{color:#FF}1.0{color}* 1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21366) Inconsistent behavior of ROUND() with integer in string as argument
[
https://issues.apache.org/jira/browse/HIVE-21366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Pusztahazi updated HIVE-21366:
Status: Open (was: Patch Available)
> Inconsistent behavior of ROUND() with integer in string as argument
> ---
>
> Key: HIVE-21366
> URL: https://issues.apache.org/jira/browse/HIVE-21366
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Yavorski
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21366.1.patch, HIVE-21366.2.patch
>
>
> hive> SELECT ROUND('1',4) AS r_str, ROUND(1,4) AS r_num;
> OK
> r_str r_num
> *{color:#FF}1.0{color}* 1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21366) Inconsistent behavior of ROUND() with integer in string as argument
[
https://issues.apache.org/jira/browse/HIVE-21366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Pusztahazi updated HIVE-21366:
Attachment: HIVE-21366.2.patch
> Inconsistent behavior of ROUND() with integer in string as argument
> ---
>
> Key: HIVE-21366
> URL: https://issues.apache.org/jira/browse/HIVE-21366
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Yavorski
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21366.1.patch, HIVE-21366.2.patch
>
>
> hive> SELECT ROUND('1',4) AS r_str, ROUND(1,4) AS r_num;
> OK
> r_str r_num
> *{color:#FF}1.0{color}* 1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21366) Inconsistent behavior of ROUND() with integer in string as argument
[
https://issues.apache.org/jira/browse/HIVE-21366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Pusztahazi updated HIVE-21366:
Status: Patch Available (was: Open)
> Inconsistent behavior of ROUND() with integer in string as argument
> ---
>
> Key: HIVE-21366
> URL: https://issues.apache.org/jira/browse/HIVE-21366
> Project: Hive
> Issue Type: Bug
>Reporter: Sergey Yavorski
>Assignee: Bruno Pusztahazi
>Priority: Major
> Attachments: HIVE-21366.1.patch, HIVE-21366.2.patch
>
>
> hive> SELECT ROUND('1',4) AS r_str, ROUND(1,4) AS r_num;
> OK
> r_str r_num
> *{color:#FF}1.0{color}* 1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
