[jira] [Updated] (HIVE-20788) Extended SJ reduction may backtrack columns incorrectly when creating filters

[ https://issues.apache.org/jira/browse/HIVE-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-20788: --- Attachment: HIVE-20788.01.patch > Extended SJ reduction may backtrack

[jira] [Work started] (HIVE-20788) Extended SJ reduction may backtrack columns incorrectly when creating filters

[ https://issues.apache.org/jira/browse/HIVE-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-20788 started by Jesus Camacho Rodriguez. -- > Extended SJ reduction may backtrack columns incorrectly

[jira] [Updated] (HIVE-20788) Extended SJ reduction may backtrack columns incorrectly when creating filters

[ https://issues.apache.org/jira/browse/HIVE-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-20788: --- Status: Patch Available (was: In Progress) > Extended SJ reduction may

[jira] [Updated] (HIVE-20788) Extended SJ reduction may backtrack columns incorrectly when creating filters

[ https://issues.apache.org/jira/browse/HIVE-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez updated HIVE-20788: --- Attachment: HIVE-20788.patch > Extended SJ reduction may backtrack columns

[jira] [Assigned] (HIVE-20788) Extended SJ reduction may backtrack columns incorrectly when creating filters

[ https://issues.apache.org/jira/browse/HIVE-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesus Camacho Rodriguez reassigned HIVE-20788: -- > Extended SJ reduction may backtrack columns incorrectly when creating

[jira] [Comment Edited] (HIVE-20786) Maven Build Failed with group id is too big

[ https://issues.apache.org/jira/browse/HIVE-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659982#comment-16659982 ] PENG Zhengshuai edited comment on HIVE-20786 at 10/23/18 2:57 AM: -- Hi

[jira] [Updated] (HIVE-20786) Maven Build Failed with group id is too big

[ https://issues.apache.org/jira/browse/HIVE-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PENG Zhengshuai updated HIVE-20786: --- Attachment: hive_build_error.log > Maven Build Failed with group id is too big >

[jira] [Commented] (HIVE-20786) Maven Build Failed with group id is too big

[ https://issues.apache.org/jira/browse/HIVE-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659982#comment-16659982 ] PENG Zhengshuai commented on HIVE-20786: Hi [~vihangk1] , Tested with maven 3.3.3, with Hive git

[jira] [Commented] (HIVE-20613) CachedStore: Add more UT coverage (outside of .q files)

[ https://issues.apache.org/jira/browse/HIVE-20613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659836#comment-16659836 ] Daniel Dai commented on HIVE-20613: --- [~vgumashta], can you create a review board? > CachedStore: Add

[jira] [Updated] (HIVE-20787) MapJoinBytesTableContainer dummyRow case doesn't handle reuse

[ https://issues.apache.org/jira/browse/HIVE-20787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-20787: Attachment: HIVE-20787.patch > MapJoinBytesTableContainer dummyRow case doesn't handle

[jira] [Updated] (HIVE-20787) MapJoinBytesTableContainer dummyRow case doesn't handle reuse

[ https://issues.apache.org/jira/browse/HIVE-20787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-20787: Status: Patch Available (was: Open) [~teddy.choi] [~prasanth_j] can you take a look? >

[jira] [Assigned] (HIVE-20787) MapJoinBytesTableContainer dummyRow case doesn't handle reuse

[ https://issues.apache.org/jira/browse/HIVE-20787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin reassigned HIVE-20787: --- > MapJoinBytesTableContainer dummyRow case doesn't handle reuse >

[jira] [Updated] (HIVE-20538) Allow to store a key value together with a transaction.

[ https://issues.apache.org/jira/browse/HIVE-20538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-20538: - Component/s: Streaming > Allow to store a key value together with a transaction.

[jira] [Updated] (HIVE-20538) Allow to store a key value together with a transaction.

[ https://issues.apache.org/jira/browse/HIVE-20538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-20538: - Affects Version/s: 4.0.0 > Allow to store a key value together with a

[jira] [Updated] (HIVE-20701) Allow HiveStreaming to receive a key value to commit atomically together with the transaction

[ https://issues.apache.org/jira/browse/HIVE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-20701: - Affects Version/s: 4.0.0 > Allow HiveStreaming to receive a key value to commit

[jira] [Updated] (HIVE-20701) Allow HiveStreaming to receive a key value to commit atomically together with the transaction

[ https://issues.apache.org/jira/browse/HIVE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-20701: - Labels: Streaming (was: ) > Allow HiveStreaming to receive a key value to

[jira] [Updated] (HIVE-20701) Allow HiveStreaming to receive a key value to commit atomically together with the transaction

[ https://issues.apache.org/jira/browse/HIVE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-20701: - Resolution: Fixed Fix Version/s: 4.0.0 Status: Resolved (was:

[jira] [Updated] (HIVE-20701) Allow HiveStreaming to receive a key value to commit atomically together with the transaction

[ https://issues.apache.org/jira/browse/HIVE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-20701: - Component/s: Streaming > Allow HiveStreaming to receive a key value to commit

[jira] [Updated] (HIVE-20701) Allow HiveStreaming to receive a key value to commit atomically together with the transaction

[ https://issues.apache.org/jira/browse/HIVE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-20701: - Labels: Streaming Transaction (was: Streaming) > Allow HiveStreaming to receive

[jira] [Commented] (HIVE-20701) Allow HiveStreaming to receive a key value to commit atomically together with the transaction

[ https://issues.apache.org/jira/browse/HIVE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659685#comment-16659685 ] Prasanth Jayachandran commented on HIVE-20701: -- +1 > Allow HiveStreaming to receive a key

[jira] [Updated] (HIVE-20765) fetch partitions for txn stats validation in get_aggr_stats with one call

[ https://issues.apache.org/jira/browse/HIVE-20765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-20765: Resolution: Fixed Fix Version/s: 4.0.0 Status: Resolved (was: Patch

[jira] [Commented] (HIVE-18045) can VectorizedOrcAcidRowBatchReader be used all the time

[ https://issues.apache.org/jira/browse/HIVE-18045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659680#comment-16659680 ] Eugene Koifman commented on HIVE-18045: --- make sure VirtualColumn like INPUT__FILE__NAME continue to

[jira] [Updated] (HIVE-20772) record per-task CPU counters in LLAP

[ https://issues.apache.org/jira/browse/HIVE-20772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-20772: Attachment: HIVE-20772.02.patch > record per-task CPU counters in LLAP >

[jira] [Updated] (HIVE-20782) Cleaning some unused code

[ https://issues.apache.org/jira/browse/HIVE-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-20782: -- Attachment: HIVE-20782.2.patch > Cleaning some unused code > - > >

[jira] [Commented] (HIVE-12812) Enable mapred.input.dir.recursive by default to support union with aggregate function

[ https://issues.apache.org/jira/browse/HIVE-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659597#comment-16659597 ] Yongzhi Chen commented on HIVE-12812: - [~wanghaihua], are you saying the fix breaks tez ? > Enable

[jira] [Commented] (HIVE-20786) Maven Build Failed with group id is too big

[ https://issues.apache.org/jira/browse/HIVE-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659277#comment-16659277 ] Vihang Karajgaonkar commented on HIVE-20786: Hmm .. this doesn't happen on my environment (or

[jira] [Commented] (HIVE-20740) Remove global lock in ObjectStore.setConf method

[ https://issues.apache.org/jira/browse/HIVE-20740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659247#comment-16659247 ] Vihang Karajgaonkar commented on HIVE-20740: Okay, so looks like there is more to this than

[jira] [Work started] (HIVE-20779) Fix missing results when IN operator has a struct with a null field

[ https://issues.apache.org/jira/browse/HIVE-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HIVE-20779 started by Igor Kryvenko. > Fix missing results when IN operator has a struct with a null field >

[jira] [Commented] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659172#comment-16659172 ] Vineet Garg commented on HIVE-20778: [~jcamachorodriguez] I have rebased and uploaded a new patch. >

[jira] [Assigned] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg reassigned HIVE-20778: -- Assignee: Vineet Garg (was: Jesus Camacho Rodriguez) > Join reordering may not be triggered

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Attachment: (was: HIVE-20778.2.patch) > Join reordering may not be triggered if all joins in

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Status: Patch Available (was: Open) > Join reordering may not be triggered if all joins in plan are

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Attachment: HIVE-20778.2.patch > Join reordering may not be triggered if all joins in plan are

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Status: Open (was: Patch Available) > Join reordering may not be triggered if all joins in plan are

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Attachment: HIVE-20778.2.patch > Join reordering may not be triggered if all joins in plan are

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Attachment: (was: HIVE-20778.2.patch) > Join reordering may not be triggered if all joins in

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Status: Open (was: Patch Available) > Join reordering may not be triggered if all joins in plan are

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Status: Patch Available (was: Open) > Join reordering may not be triggered if all joins in plan are

[jira] [Updated] (HIVE-20778) Join reordering may not be triggered if all joins in plan are created by decorrelation logic

[ https://issues.apache.org/jira/browse/HIVE-20778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vineet Garg updated HIVE-20778: --- Attachment: HIVE-20778.2.patch > Join reordering may not be triggered if all joins in plan are

[jira] [Commented] (HIVE-20608) Incorrect handling of sql command args in hive service leading to misleading error messages

[ https://issues.apache.org/jira/browse/HIVE-20608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659161#comment-16659161 ] Daniel Dai commented on HIVE-20608: --- Yes, I did a trace, empty spaces of both "statement" and "command"

[jira] [Commented] (HIVE-20608) Incorrect handling of sql command args in hive service leading to misleading error messages

[ https://issues.apache.org/jira/browse/HIVE-20608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16659029#comment-16659029 ] Soumabrata Chakraborty commented on HIVE-20608: --- Hi [~daijy],  thats

[jira] [Assigned] (HIVE-20779) Fix missing results when IN operator has a struct with a null field

[ https://issues.apache.org/jira/browse/HIVE-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Kryvenko reassigned HIVE-20779: Assignee: Igor Kryvenko > Fix missing results when IN operator has a struct with a null

[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

[ https://issues.apache.org/jira/browse/HIVE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658940#comment-16658940 ] Hive QA commented on HIVE-20542: Here are the results of testing the latest attachment:

[jira] [Commented] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

[ https://issues.apache.org/jira/browse/HIVE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658921#comment-16658921 ] Hive QA commented on HIVE-20542: | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (HIVE-12812) Enable mapred.input.dir.recursive by default to support union with aggregate function

[ https://issues.apache.org/jira/browse/HIVE-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658913#comment-16658913 ] Wang Haihua commented on HIVE-12812: For those who use tez and mapreduce mixed in Hive, you should

[jira] [Commented] (HIVE-20751) Upgrade arrow version to 0.10.0

[ https://issues.apache.org/jira/browse/HIVE-20751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658871#comment-16658871 ] Teddy Choi commented on HIVE-20751: --- +1 LGTM. :) > Upgrade arrow version to 0.10.0 >

[jira] [Updated] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

[ https://issues.apache.org/jira/browse/HIVE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Bapat updated HIVE-20542: -- Attachment: HIVE-20542.04 Status: Patch Available (was: In Progress) Addressed

[jira] [Updated] (HIVE-20542) Incremental REPL DUMP progress information log message is incorrect.

[ https://issues.apache.org/jira/browse/HIVE-20542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Bapat updated HIVE-20542: -- Status: In Progress (was: Patch Available) > Incremental REPL DUMP progress information log

[jira] [Commented] (HIVE-20751) Upgrade arrow version to 0.10.0

[ https://issues.apache.org/jira/browse/HIVE-20751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658746#comment-16658746 ] Shubham Chaurasia commented on HIVE-20751: -- [~teddy.choi] Please review > Upgrade arrow version

[jira] [Updated] (HIVE-20679) DDL operations on hive might create large messages for DBNotification

[ https://issues.apache.org/jira/browse/HIVE-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anishek updated HIVE-20679: --- Resolution: Fixed Fix Version/s: 4.0.0 Status: Resolved (was: Patch Available) Committed

[jira] [Updated] (HIVE-20786) Maven Build Failed with group id is too big

[ https://issues.apache.org/jira/browse/HIVE-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PENG Zhengshuai updated HIVE-20786: --- Labels: maven (was: ) > Maven Build Failed with group id is too big >

[jira] [Commented] (HIVE-20679) DDL operations on hive might create large messages for DBNotification

[ https://issues.apache.org/jira/browse/HIVE-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658630#comment-16658630 ] Hive QA commented on HIVE-20679: Here are the results of testing the latest attachment: