[jira] [Created] (HIVE-22125) Move to Kafka 2.3 Clients
slim bouguerra created HIVE-22125: - Summary: Move to Kafka 2.3 Clients Key: HIVE-22125 URL: https://issues.apache.org/jira/browse/HIVE-22125 Project: Hive Issue Type: Improvement Reporter: slim bouguerra Assignee: slim bouguerra -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HIVE-22124) Fix wrong results/ArrayOutOfBound exception in left outer map joins on specific boundary conditions with limit
Ramesh Kumar Thangarajan created HIVE-22124: --- Summary: Fix wrong results/ArrayOutOfBound exception in left outer map joins on specific boundary conditions with limit Key: HIVE-22124 URL: https://issues.apache.org/jira/browse/HIVE-22124 Project: Hive Issue Type: Bug Components: Hive, llap, Vectorization Affects Versions: 4.0.0 Reporter: Ramesh Kumar Thangarajan Assignee: Ramesh Kumar Thangarajan This is the extension of the bug HIVE-22120. All the boundary conditions mentioned in HIVE-22120 also apply here plus the query needs to have a limit. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HIVE-22123) Use GetDatabaseResponse to allow for future extension
Naveen Gangam created HIVE-22123: Summary: Use GetDatabaseResponse to allow for future extension Key: HIVE-22123 URL: https://issues.apache.org/jira/browse/HIVE-22123 Project: Hive Issue Type: Sub-task Components: Hive Affects Versions: 4.0.0 Reporter: Naveen Gangam Assignee: Naveen Gangam As part of the review, it was suggested to use the GetDatabaseResponse object to allow for any potential future expansions for these requests. https://reviews.apache.org/r/71267/#comment304501 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HIVE-22122) TxnHandler.getValidWriteIdsForTable optimization for compacted tables
Peter Vary created HIVE-22122: - Summary: TxnHandler.getValidWriteIdsForTable optimization for compacted tables Key: HIVE-22122 URL: https://issues.apache.org/jira/browse/HIVE-22122 Project: Hive Issue Type: Bug Components: Transactions Reporter: Peter Vary When we do not find open writes for the given validTxnList then we either: # do not have any writes on the table - we can return writeIdHwm = 0, and no invalid/aborted writes; # we have only compacted writes on the table - we can return writeIdHwm = nextWriteId -1, and no invalid/aborted; # we have compacted writes and some invalid writes on the table - we can return the lowest invalid write as a writeIdHwm and set it as invalid. What the current code does instead is sending writeIdHwm = nextWriteId -1, and sending every write as invalid. This results the same response in case 1-2, but probably a longer list in case 3. So we have place for some optimizations -- This message was sent by Atlassian JIRA (v7.6.14#76016)
