[jira] [Updated] (HIVE-24855) Introduce virtual colum ROW__IS__DELETED

2021-03-07 Thread ASF GitHub Bot (Jira)


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

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

> Introduce virtual colum ROW__IS__DELETED
> 
>
> Key: HIVE-24855
> URL: https://issues.apache.org/jira/browse/HIVE-24855
> Project: Hive
>  Issue Type: New Feature
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24855) Introduce virtual colum ROW__IS__DELETED

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24855?focusedWorklogId=562162=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562162
 ]

ASF GitHub Bot logged work on HIVE-24855:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 07:44
Start Date: 08/Mar/21 07:44
Worklog Time Spent: 10m 
  Work Description: kasakrisz opened a new pull request #2046:
URL: https://github.com/apache/hive/pull/2046


   ### What changes were proposed in this pull request?
   
   
   
   ### Why are the changes needed?
   
   
   
   ### Does this PR introduce _any_ user-facing change?
   
   
   
   ### How was this patch tested?
   
   



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: 562162)
Remaining Estimate: 0h
Time Spent: 10m

> Introduce virtual colum ROW__IS__DELETED
> 
>
> Key: HIVE-24855
> URL: https://issues.apache.org/jira/browse/HIVE-24855
> Project: Hive
>  Issue Type: New Feature
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24856) Skip functions created without 'using' clause during incremental replication

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24856?focusedWorklogId=562161=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562161
 ]

ASF GitHub Bot logged work on HIVE-24856:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 07:36
Start Date: 08/Mar/21 07:36
Worklog Time Spent: 10m 
  Work Description: ArkoSharma opened a new pull request #2045:
URL: https://github.com/apache/hive/pull/2045


   



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: 562161)
Remaining Estimate: 0h
Time Spent: 10m

> Skip functions created without 'using' clause during incremental replication
> 
>
> Key: HIVE-24856
> URL: https://issues.apache.org/jira/browse/HIVE-24856
> Project: Hive
>  Issue Type: Bug
>Reporter: Arko Sharma
>Assignee: Arko Sharma
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (HIVE-24856) Skip functions created without 'using' clause during incremental replication

2021-03-07 Thread ASF GitHub Bot (Jira)


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

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

> Skip functions created without 'using' clause during incremental replication
> 
>
> Key: HIVE-24856
> URL: https://issues.apache.org/jira/browse/HIVE-24856
> Project: Hive
>  Issue Type: Bug
>Reporter: Arko Sharma
>Assignee: Arko Sharma
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (HIVE-24856) Skip functions created without 'using' clause during incremental replication

2021-03-07 Thread Arko Sharma (Jira)


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

Arko Sharma reassigned HIVE-24856:
--


> Skip functions created without 'using' clause during incremental replication
> 
>
> Key: HIVE-24856
> URL: https://issues.apache.org/jira/browse/HIVE-24856
> Project: Hive
>  Issue Type: Bug
>Reporter: Arko Sharma
>Assignee: Arko Sharma
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (HIVE-24855) Introduce virtual colum ROW__IS__DELETED

2021-03-07 Thread Krisztian Kasa (Jira)


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

Krisztian Kasa reassigned HIVE-24855:
-


> Introduce virtual colum ROW__IS__DELETED
> 
>
> Key: HIVE-24855
> URL: https://issues.apache.org/jira/browse/HIVE-24855
> Project: Hive
>  Issue Type: New Feature
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (HIVE-24854) Incremental Materialized view refresh in presence of update/delete operations

2021-03-07 Thread Krisztian Kasa (Jira)


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

Krisztian Kasa reassigned HIVE-24854:
-


> Incremental Materialized view refresh in presence of update/delete operations
> -
>
> Key: HIVE-24854
> URL: https://issues.apache.org/jira/browse/HIVE-24854
> Project: Hive
>  Issue Type: Improvement
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
>
> Current implementation of incremental Materialized can not be used if any of 
> the Materialized view source tables has update or delete operation since the 
> last rebuild. In such cases a full rebuild should be performed.
> Steps to enable incremental rebuild:
> 1. Introduce a new virtual column to mark a row deleted
> 2. Execute the query in the view definition 
> 2.a. Add filter to each table scan in order to pull only the rows from each 
> source table which has a higher writeId than the writeId of the last rebuild 
> - this is already implemented by current incremental rebuild
> 2.b Add row is deleted virtual column to each table scan. In join nodes if 
> any of the branches has a deleted row the result row is also deleted.
> We should distinguish two type of view definition queries: with and without 
> Aggregate.
> 3.a No aggregate path:
> Rewrite the plan of the full rebuild to a multi insert statement with two 
> insert branches. One branch to insert new rows into the materialized view 
> table and the second one for insert deleted rows to the materialized view 
> delete delta.
> 3.b Aggregate path: TBD



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24818) REPL LOAD (Bootstrap ) of views with partitions fails

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24818?focusedWorklogId=562147=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562147
 ]

ASF GitHub Bot logged work on HIVE-24818:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 06:34
Start Date: 08/Mar/21 06:34
Worklog Time Spent: 10m 
  Work Description: pkumarsinha commented on a change in pull request #2029:
URL: https://github.com/apache/hive/pull/2029#discussion_r589189783



##
File path: 
itests/hive-unit/src/test/java/org/apache/hadoop/hive/ql/parse/TestReplicationScenarios.java
##
@@ -2851,6 +2854,8 @@ public void testViewsReplication() throws IOException {
 verifyRun("SELECT * from " + replDbName + ".virtual_view", empty, 
driverMirror);
 //verifyRun("SELECT a from " + replDbName + ".mat_view", ptn_data_1, 
driverMirror);
 
+verifySetup("SELECT * from " + replDbName + 
".virtual_view_with_partition", empty, driver);

Review comment:
   Shouldn't the same issue be there in incremental case also? If so, I 
think we should add a test for incremental also and modify the bug synopsis by 
removing 'bootstrap' word in it.

##
File path: 
itests/hive-unit/src/test/java/org/apache/hadoop/hive/ql/parse/TestReplicationScenarios.java
##
@@ -2851,6 +2854,8 @@ public void testViewsReplication() throws IOException {
 verifyRun("SELECT * from " + replDbName + ".virtual_view", empty, 
driverMirror);
 //verifyRun("SELECT a from " + replDbName + ".mat_view", ptn_data_1, 
driverMirror);
 
+verifySetup("SELECT * from " + replDbName + 
".virtual_view_with_partition", empty, driver);

Review comment:
   Also, can we have one non-empty table also covered?

##
File path: ql/src/java/org/apache/hadoop/hive/ql/exec/repl/ReplLoadTask.java
##
@@ -438,7 +438,7 @@ private TaskTracker addLoadFunctionTasks(Context 
loadContext, BootstrapEventsIte
   // texts using new DB name. Currently it refers to the source database 
name.
 }
 
-CreateViewDesc desc = new CreateViewDesc(dbDotView, table.getAllCols(), 
null, table.getParameters(),
+CreateViewDesc desc = new CreateViewDesc(dbDotView, table.getCols(), null, 
table.getParameters(),

Review comment:
   The first variant of method - createViewTask: Line:427 seems to be 
unused. Should we remove it altogether?





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: 562147)
Time Spent: 40m  (was: 0.5h)

> REPL LOAD (Bootstrap ) of views with partitions fails 
> --
>
> Key: HIVE-24818
> URL: https://issues.apache.org/jira/browse/HIVE-24818
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Reporter: Anurag Shekhar
>Assignee: Anurag Shekhar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24853) HMS leaks queries in case of timeout

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24853?focusedWorklogId=562127=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562127
 ]

ASF GitHub Bot logged work on HIVE-24853:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 05:36
Start Date: 08/Mar/21 05:36
Worklog Time Spent: 10m 
  Work Description: ayushtkn commented on pull request #2044:
URL: https://github.com/apache/hive/pull/2044#issuecomment-792478370


   Thanx @rbalamohan for the review. I have fixed this in 
`MetastoreDirectSqlUtils ` as well, There were two occurances there, and one 
had this `Deadline` check, so have added the fix for that one



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: 562127)
Time Spent: 40m  (was: 0.5h)

> HMS leaks queries in case of timeout
> 
>
> Key: HIVE-24853
> URL: https://issues.apache.org/jira/browse/HIVE-24853
> Project: Hive
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> The queries aren't closed in case of timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24818) REPL LOAD (Bootstrap ) of views with partitions fails

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24818?focusedWorklogId=562113=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562113
 ]

ASF GitHub Bot logged work on HIVE-24818:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 03:51
Start Date: 08/Mar/21 03:51
Worklog Time Spent: 10m 
  Work Description: anuragshekhar2020 commented on a change in pull request 
#2029:
URL: https://github.com/apache/hive/pull/2029#discussion_r589154569



##
File path: ql/src/java/org/apache/hadoop/hive/ql/exec/repl/ReplLoadTask.java
##
@@ -435,7 +435,7 @@ private TaskTracker addLoadFunctionTasks(Context 
loadContext, BootstrapEventsIte
   // texts using new DB name. Currently it refers to the source database 
name.
 }
 
-CreateViewDesc desc = new CreateViewDesc(dbDotView, table.getAllCols(), 
null, table.getParameters(),
+CreateViewDesc desc = new CreateViewDesc(dbDotView, table.getCols(), null, 
table.getParameters(),

Review comment:
   I have listed the steps to reproduce the issue in jira.
   We do need getPartCols and its part of the constructor parameters for 
CreateViewDesc (its in next line so its not showing in the diff, expanded view 
will show). However list from getAllCols adds partition columns to both column 
list and partition column list and latter in the code flow the check fails due 
to duplicate entry.





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: 562113)
Time Spent: 0.5h  (was: 20m)

> REPL LOAD (Bootstrap ) of views with partitions fails 
> --
>
> Key: HIVE-24818
> URL: https://issues.apache.org/jira/browse/HIVE-24818
> Project: Hive
>  Issue Type: Bug
>  Components: repl
>Reporter: Anurag Shekhar
>Assignee: Anurag Shekhar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24524) LLAP ShuffleHandler: upgrade to netty4

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24524?focusedWorklogId=562083=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562083
 ]

ASF GitHub Bot logged work on HIVE-24524:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 00:55
Start Date: 08/Mar/21 00:55
Worklog Time Spent: 10m 
  Work Description: github-actions[bot] commented on pull request #1778:
URL: https://github.com/apache/hive/pull/1778#issuecomment-792393727


   This pull request has been automatically marked as stale because it has not 
had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the d...@hive.apache.org list if the patch is in 
need of reviews.



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: 562083)
Time Spent: 20m  (was: 10m)

> LLAP ShuffleHandler: upgrade to netty4
> --
>
> Key: HIVE-24524
> URL: https://issues.apache.org/jira/browse/HIVE-24524
> Project: Hive
>  Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Tez already has a WIP patch for upgrading its shuffle handler to netty4. 
> Netty4 is told to be a possible performance improvement compared to Netty3. 
> However, the refactor is not trivial, TEZ-4157 covers that more or less (the 
> code bases are very similar).
> Background:
> netty4 migration guideline: 
> https://netty.io/wiki/new-and-noteworthy-in-4.0.html
> articles of possible performance improvement:
> https://blog.twitter.com/engineering/en_us/a/2013/netty-4-at-twitter-reduced-gc-overhead.html
> https://developer.squareup.com/blog/upgrading-a-reverse-proxy-from-netty-3-to-4/
> some other notes: Netty3 is EOL since 2016:
> https://netty.io/news/2016/06/29/3-10-6-Final.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-21737) Upgrade Avro to version 1.10.1

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-21737?focusedWorklogId=562085=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562085
 ]

ASF GitHub Bot logged work on HIVE-21737:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 00:55
Start Date: 08/Mar/21 00:55
Worklog Time Spent: 10m 
  Work Description: github-actions[bot] commented on pull request #1806:
URL: https://github.com/apache/hive/pull/1806#issuecomment-792393720


   This pull request has been automatically marked as stale because it has not 
had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the d...@hive.apache.org list if the patch is in 
need of reviews.



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: 562085)
Time Spent: 8h 50m  (was: 8h 40m)

> Upgrade Avro to version 1.10.1
> --
>
> Key: HIVE-21737
> URL: https://issues.apache.org/jira/browse/HIVE-21737
> Project: Hive
>  Issue Type: Improvement
>  Components: Hive
>Reporter: Ismaël Mejía
>Assignee: Fokko Driesprong
>Priority: Major
>  Labels: pull-request-available
> Attachments: 
> 0001-HIVE-21737-Make-Avro-use-in-Hive-compatible-with-Avr.patch
>
>  Time Spent: 8h 50m
>  Remaining Estimate: 0h
>
> Avro >= 1.9.x bring a lot of fixes including a leaner version of Avro without 
> Jackson in the public API and Guava as a dependency. Worth the update.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24594) results_cache_invalidation2.q is flaky

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24594?focusedWorklogId=562084=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562084
 ]

ASF GitHub Bot logged work on HIVE-24594:
-

Author: ASF GitHub Bot
Created on: 08/Mar/21 00:55
Start Date: 08/Mar/21 00:55
Worklog Time Spent: 10m 
  Work Description: github-actions[bot] commented on pull request #1837:
URL: https://github.com/apache/hive/pull/1837#issuecomment-792393713


   This pull request has been automatically marked as stale because it has not 
had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the d...@hive.apache.org list if the patch is in 
need of reviews.



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: 562084)
Time Spent: 20m  (was: 10m)

> results_cache_invalidation2.q is flaky
> --
>
> Key: HIVE-24594
> URL: https://issues.apache.org/jira/browse/HIVE-24594
> Project: Hive
>  Issue Type: Test
>Reporter: Vihang Karajgaonkar
>Assignee: Vihang Karajgaonkar
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> results_cache_invalidation2.q failed for me couple of times on a unrelated 
> PR. Here is the error log.
> {noformat}
> ---
> Test set: org.apache.hadoop.hive.cli.split19.TestMiniLlapLocalCliDriver
> ---
> Tests run: 90, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 450.54 s <<< 
> FAILURE! - in org.apache.hadoop.hive.cli.split19.TestMiniLlapLocalCliDriver
> org.apache.hadoop.hive.cli.split19.TestMiniLlapLocalCliDriver.testCliDriver[results_cache_invalidation2]
>   Time elapsed: 15.087 s  <<< FAILURE!
> java.lang.AssertionError:
> Client Execution succeeded but contained differences (error code = 1) after 
> executing results_cache_invalidation2.q ^M
> 266a267
> >  A masked pattern was here 
> 271a273
> >  A masked pattern was here 
> 273c275,276
> <   Stage-0 is a root stage
> ---
> >   Stage-1 is a root stage
> >   Stage-0 depends on stages: Stage-1
> 275a279,365
> >   Stage: Stage-1
> > Tez
> >  A masked pattern was here 
> >   Edges:
> > Reducer 2 <- Map 1 (SIMPLE_EDGE), Map 4 (SIMPLE_EDGE)
> > Reducer 3 <- Reducer 2 (CUSTOM_SIMPLE_EDGE)
> >  A masked pattern was here 
> >   Vertices:
> > Map 1
> > Map Operator Tree:
> > TableScan
> >   alias: tab1
> >   filterExpr: key is not null (type: boolean)
> >   Statistics: Num rows: 1500 Data size: 130500 Basic stats: 
> > COMPLETE Column stats: COMPLETE
> >   Filter Operator
> > predicate: key is not null (type: boolean)
> > Statistics: Num rows: 1500 Data size: 130500 Basic 
> > stats: COMPLETE Column stats: COMPLETE
> > Select Operator
> >   expressions: key (type: string)
> >   outputColumnNames: _col0
> >   Statistics: Num rows: 1500 Data size: 130500 Basic 
> > stats: COMPLETE Column stats: COMPLETE
> >   Reduce Output Operator
> > key expressions: _col0 (type: string)
> > null sort order: z
> > sort order: +
> > Map-reduce partition columns: _col0 (type: string)
> > Statistics: Num rows: 1500 Data size: 130500 Basic 
> > stats: COMPLETE Column stats: COMPLETE
> > Execution mode: vectorized, llap
> > LLAP IO: all inputs
> > Map 4
> > Map Operator Tree:
> > TableScan
> >   alias: tab2
> >   filterExpr: key is not null (type: boolean)
> >   Statistics: Num rows: 500 Data size: 43500 Basic stats: 
> > COMPLETE Column stats: COMPLETE
> >   Fil^M
> {noformat}
> The test works for me locally. In fact the same PR had a successful run of 
> this test in a previous commit. I think we should disable this and re-enable 
> it after fixing the flakiness.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24853) HMS leaks queries in case of timeout

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24853?focusedWorklogId=562080=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562080
 ]

ASF GitHub Bot logged work on HIVE-24853:
-

Author: ASF GitHub Bot
Created on: 07/Mar/21 23:51
Start Date: 07/Mar/21 23:51
Worklog Time Spent: 10m 
  Work Description: rbalamohan edited a comment on pull request #2044:
URL: https://github.com/apache/hive/pull/2044#issuecomment-792377866


   @ayushtkn : Should this be fixed in the set of methods in 
"MetastoreDirectSqlUtils" (e.g MetastoreDirectSqlUtils::loopJoinOrderedResult) 
as well?



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: 562080)
Time Spent: 0.5h  (was: 20m)

> HMS leaks queries in case of timeout
> 
>
> Key: HIVE-24853
> URL: https://issues.apache.org/jira/browse/HIVE-24853
> Project: Hive
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The queries aren't closed in case of timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24853) HMS leaks queries in case of timeout

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24853?focusedWorklogId=562079=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562079
 ]

ASF GitHub Bot logged work on HIVE-24853:
-

Author: ASF GitHub Bot
Created on: 07/Mar/21 23:51
Start Date: 07/Mar/21 23:51
Worklog Time Spent: 10m 
  Work Description: rbalamohan commented on pull request #2044:
URL: https://github.com/apache/hive/pull/2044#issuecomment-792377866


   Should this be fixed in the set of methods in "MetastoreDirectSqlUtils" (e.g 
MetastoreDirectSqlUtils::loopJoinOrderedResult) as well?



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: 562079)
Time Spent: 20m  (was: 10m)

> HMS leaks queries in case of timeout
> 
>
> Key: HIVE-24853
> URL: https://issues.apache.org/jira/browse/HIVE-24853
> Project: Hive
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The queries aren't closed in case of timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (HIVE-24853) HMS leaks queries in case of timeout

2021-03-07 Thread ASF GitHub Bot (Jira)


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

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

> HMS leaks queries in case of timeout
> 
>
> Key: HIVE-24853
> URL: https://issues.apache.org/jira/browse/HIVE-24853
> Project: Hive
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The queries aren't closed in case of timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24853) HMS leaks queries in case of timeout

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24853?focusedWorklogId=562050=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562050
 ]

ASF GitHub Bot logged work on HIVE-24853:
-

Author: ASF GitHub Bot
Created on: 07/Mar/21 20:18
Start Date: 07/Mar/21 20:18
Worklog Time Spent: 10m 
  Work Description: ayushtkn opened a new pull request #2044:
URL: https://github.com/apache/hive/pull/2044


   



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: 562050)
Remaining Estimate: 0h
Time Spent: 10m

> HMS leaks queries in case of timeout
> 
>
> Key: HIVE-24853
> URL: https://issues.apache.org/jira/browse/HIVE-24853
> Project: Hive
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The queries aren't closed in case of timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (HIVE-24853) HMS leaks queries in case of timeout

2021-03-07 Thread Ayush Saxena (Jira)


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

Ayush Saxena reassigned HIVE-24853:
---


> HMS leaks queries in case of timeout
> 
>
> Key: HIVE-24853
> URL: https://issues.apache.org/jira/browse/HIVE-24853
> Project: Hive
>  Issue Type: Bug
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
>
> The queries aren't closed in case of timeout.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (HIVE-24852) Add support for Snapshots during external table replication

2021-03-07 Thread ASF GitHub Bot (Jira)


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

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

> Add support for Snapshots during external table replication
> ---
>
> Key: HIVE-24852
> URL: https://issues.apache.org/jira/browse/HIVE-24852
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add support for use of snapshot diff for external table replication.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-24852) Add support for Snapshots during external table replication

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-24852?focusedWorklogId=562027=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-562027
 ]

ASF GitHub Bot logged work on HIVE-24852:
-

Author: ASF GitHub Bot
Created on: 07/Mar/21 19:15
Start Date: 07/Mar/21 19:15
Worklog Time Spent: 10m 
  Work Description: ayushtkn opened a new pull request #2043:
URL: https://github.com/apache/hive/pull/2043


   



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: 562027)
Remaining Estimate: 0h
Time Spent: 10m

> Add support for Snapshots during external table replication
> ---
>
> Key: HIVE-24852
> URL: https://issues.apache.org/jira/browse/HIVE-24852
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Critical
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add support for use of snapshot diff for external table replication.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (HIVE-24852) Add support for Snapshots during external table replication

2021-03-07 Thread Ayush Saxena (Jira)


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

Ayush Saxena reassigned HIVE-24852:
---


> Add support for Snapshots during external table replication
> ---
>
> Key: HIVE-24852
> URL: https://issues.apache.org/jira/browse/HIVE-24852
> Project: Hive
>  Issue Type: Improvement
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Critical
>
> Add support for use of snapshot diff for external table replication.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work logged] (HIVE-22601) Some columns will be lost when a UDTF has multiple aliases in some cases

2021-03-07 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HIVE-22601?focusedWorklogId=561985=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-561985
 ]

ASF GitHub Bot logged work on HIVE-22601:
-

Author: ASF GitHub Bot
Created on: 07/Mar/21 15:51
Start Date: 07/Mar/21 15:51
Worklog Time Spent: 10m 
  Work Description: okumin opened a new pull request #2042:
URL: https://github.com/apache/hive/pull/2042


   https://issues.apache.org/jira/browse/HIVE-22601
   
   ### What changes were proposed in this pull request?
   A bug fix. Hive can't handle multiple aliases now.
   
   ### Why are the changes needed?
   This bug causes incorrect results. It's inconvenient especially when we use 
Hivemall. It has UDTFs that return multiple columns.
   
   ### Does this PR introduce _any_ user-facing change?
   Yes, but the current behavior is apparently buggy.
   
   ### How was this patch tested?
   Add 2 test cases.



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: 561985)
Time Spent: 40m  (was: 0.5h)

> Some columns will be lost when a UDTF has multiple aliases in some cases
> 
>
> Key: HIVE-22601
> URL: https://issues.apache.org/jira/browse/HIVE-22601
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Affects Versions: 2.1.1, 2.2.0, 2.3.6, 3.1.2
>Reporter: okumin
>Assignee: okumin
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-22601.1.patch, HIVE-22601.2.patch, 
> HIVE-22601.3.patch, HIVE-22601.patch
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Only one column will be retained when putting UDTFs with multiple aliases and 
> a top-level UNION together.
> For example, the result of the following SQL should have three columns, c1, 
> c2 and c3.
> {code:java}
> SELECT stack(1, 'a', 'b', 'c') AS (c1, c2, c3)
> UNION ALL
> SELECT stack(1, 'd', 'e', 'f') AS (c1, c2, c3);
> {code}
> However, It's only the c3 column which I can get.
> {code:java}
> +-+
> | _u1.c3  |
> +-+
> | c   |
> | f   |
> +-+
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (HIVE-22601) Some columns will be lost when a UDTF has multiple aliases in some cases

2021-03-07 Thread okumin (Jira)


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

okumin reassigned HIVE-22601:
-

Assignee: okumin  (was: Owen O'Malley)

> Some columns will be lost when a UDTF has multiple aliases in some cases
> 
>
> Key: HIVE-22601
> URL: https://issues.apache.org/jira/browse/HIVE-22601
> Project: Hive
>  Issue Type: Bug
>  Components: Query Processor
>Affects Versions: 2.1.1, 2.2.0, 2.3.6, 3.1.2
>Reporter: okumin
>Assignee: okumin
>Priority: Major
>  Labels: pull-request-available
> Attachments: HIVE-22601.1.patch, HIVE-22601.2.patch, 
> HIVE-22601.3.patch, HIVE-22601.patch
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Only one column will be retained when putting UDTFs with multiple aliases and 
> a top-level UNION together.
> For example, the result of the following SQL should have three columns, c1, 
> c2 and c3.
> {code:java}
> SELECT stack(1, 'a', 'b', 'c') AS (c1, c2, c3)
> UNION ALL
> SELECT stack(1, 'd', 'e', 'f') AS (c1, c2, c3);
> {code}
> However, It's only the c3 column which I can get.
> {code:java}
> +-+
> | _u1.c3  |
> +-+
> | c   |
> | f   |
> +-+
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Work started] (HIVE-24529) Metastore truncates milliseconds while storing timestamp column stats

2021-03-07 Thread Ashish Sharma (Jira)


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

Work on HIVE-24529 started by Ashish Sharma.

> Metastore truncates milliseconds while storing timestamp column stats
> -
>
> Key: HIVE-24529
> URL: https://issues.apache.org/jira/browse/HIVE-24529
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 4.0.0
>Reporter: Nikhil Gupta
>Assignee: Ashish Sharma
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce the issue:
> create table tnikhil (t timestamp);
> insert into tnikhil values ('2019-01-01 23:12:45.123456');
> analyze table tnikhil compute statistics for columns;
> select * from tnikhil;
> {noformat}
> +-+
> |  tnikhil.t  |
> +-+
> | 2019-01-01 23:12:45.123456  |
> +-+{noformat}
> desc formatted tnikhil t; 
> {noformat}
> +++
> |col_name| data_type  
> |
> +++
> | col_name   | t  
> |
> | data_type  | timestamp  
> |
> | min| 1546384365 
> |
> | max| 1546384365 
> |
> +++
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (HIVE-24529) Metastore truncates milliseconds while storing timestamp column stats

2021-03-07 Thread Ashish Sharma (Jira)


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

Ashish Sharma reassigned HIVE-24529:


Assignee: Ashish Sharma  (was: Nikhil Gupta)

> Metastore truncates milliseconds while storing timestamp column stats
> -
>
> Key: HIVE-24529
> URL: https://issues.apache.org/jira/browse/HIVE-24529
> Project: Hive
>  Issue Type: Improvement
>Affects Versions: 4.0.0
>Reporter: Nikhil Gupta
>Assignee: Ashish Sharma
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Steps to reproduce the issue:
> create table tnikhil (t timestamp);
> insert into tnikhil values ('2019-01-01 23:12:45.123456');
> analyze table tnikhil compute statistics for columns;
> select * from tnikhil;
> {noformat}
> +-+
> |  tnikhil.t  |
> +-+
> | 2019-01-01 23:12:45.123456  |
> +-+{noformat}
> desc formatted tnikhil t; 
> {noformat}
> +++
> |col_name| data_type  
> |
> +++
> | col_name   | t  
> |
> | data_type  | timestamp  
> |
> | min| 1546384365 
> |
> | max| 1546384365 
> |
> +++
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)