[jira] [Commented] (HIVE-27897) Backport of HIVE-22373, HIVE-25553, HIVE-23561, HIVE-24321, HIVE-22856, HIVE-22973, HIVE-21729
[ https://issues.apache.org/jira/browse/HIVE-27897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816870#comment-17816870 ] tanishqchugh commented on HIVE-27897: - what are the source & target branches? > Backport of HIVE-22373, HIVE-25553, HIVE-23561, HIVE-24321, HIVE-22856, > HIVE-22973, HIVE-21729 > -- > > Key: HIVE-27897 > URL: https://issues.apache.org/jira/browse/HIVE-27897 > Project: Hive > Issue Type: Sub-task >Affects Versions: 3.2.0 >Reporter: Aman Raj >Assignee: Aman Raj >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-25694) HIVE-17132 deprecated UDAF resolver without documenting path forward.
[ https://issues.apache.org/jira/browse/HIVE-25694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816863#comment-17816863 ] HiuFung Kwok commented on HIVE-25694: - [~stakiar] I found this equally confusing, as I attempted to bump Hive on SPARK-44114. Any documentation on GenericUDAFResolver2 deprecation would be appreciated. > HIVE-17132 deprecated UDAF resolver without documenting path forward. > - > > Key: HIVE-25694 > URL: https://issues.apache.org/jira/browse/HIVE-25694 > Project: Hive > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Matt Andruff >Priority: Major > > HIVE-17132弃用了GenericUDAFResolver2或扩展AbstractGenericUDAFResolver，但没有帮助解释应该使用什么来代替它。（它可能意外地弃用了它们，目前尚不清楚UDAF是否应该与UDF混为一谈。 > HIVE-6331是相关的，因为这发生在上次弃用的实现之前。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (HIVE-28075) Vectorized DayOFWeek returns inconsistent results for non-UTC timezones.
[
https://issues.apache.org/jira/browse/HIVE-28075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HIVE-28075 started by Riju Trivedi.
---
> Vectorized DayOFWeek returns inconsistent results for non-UTC timezones.
>
>
> Key: HIVE-28075
> URL: https://issues.apache.org/jira/browse/HIVE-28075
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Affects Versions: 4.0.0-beta-1
>Reporter: Riju Trivedi
>Assignee: Riju Trivedi
>Priority: Major
>
> Simple problem reproduce -
> {code:java}
> --! qt:timezone:Asia/Shanghai
> CREATE EXTERNAL TABLE dayOfWeek_test(
> `fund_code` string,
> `test_date` string
> );
> INSERT INTO dayOfWeek_test(fund_code,test_date)
> values('SEC016210079','2023-04-13');
> SELECT fund_code,
> test_date,
> dayofweek(test_date) AS SR,
> CASE
> WHEN dayofweek(test_date) = 1 THEN 7
> ELSE dayofweek(test_date) - 1
> END AS week_day
> FROM dayOfWeek_test;
> Result :
> SEC0162100792023-04-13 4 3
> Expected Result:
> SEC016210079 2023-04-13 5 4
> {code}
> The issue is only with Vectorized path and non-UTC timezones. The
> non-vectorized path uses _DateTimeFormatter_ and the vectorized path __ uses
> _SimpleDateFormat_ and calendar initialized with UTC timezone. Hence, the
> local time zone date is converted to UTC which changes the date and
> dayOfWeek() result.
> [https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/VectorUDFDayOfWeekString.java#L59]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HIVE-28075) Vectorized DayOFWeek returns inconsistent results for non-UTC timezones.
Riju Trivedi created HIVE-28075:
---
Summary: Vectorized DayOFWeek returns inconsistent results for
non-UTC timezones.
Key: HIVE-28075
URL: https://issues.apache.org/jira/browse/HIVE-28075
Project: Hive
Issue Type: Bug
Components: Hive
Affects Versions: 4.0.0-beta-1
Reporter: Riju Trivedi
Assignee: Riju Trivedi
Simple problem reproduce -
{code:java}
--! qt:timezone:Asia/Shanghai
CREATE EXTERNAL TABLE dayOfWeek_test(
`fund_code` string,
`test_date` string
);
INSERT INTO dayOfWeek_test(fund_code,test_date)
values('SEC016210079','2023-04-13');
SELECT fund_code,
test_date,
dayofweek(test_date) AS SR,
CASE
WHEN dayofweek(test_date) = 1 THEN 7
ELSE dayofweek(test_date) - 1
END AS week_day
FROM dayOfWeek_test;
Result :
SEC0162100792023-04-13 4 3
Expected Result:
SEC016210079 2023-04-13 5 4
{code}
The issue is only with Vectorized path and non-UTC timezones. The
non-vectorized path uses _DateTimeFormatter_ and the vectorized path __ uses
_SimpleDateFormat_ and calendar initialized with UTC timezone. Hence, the local
time zone date is converted to UTC which changes the date and dayOfWeek()
result.
[https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/exec/vector/expressions/VectorUDFDayOfWeekString.java#L59]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-28074) Normalize db/table name in the alter table operation in HMS
[
https://issues.apache.org/jira/browse/HIVE-28074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816814#comment-17816814
]
Sai Hemanth Gantasala commented on HIVE-28074:
--
cc [~dengzh] [~ngangam]
> Normalize db/table name in the alter table operation in HMS
> ---
>
> Key: HIVE-28074
> URL: https://issues.apache.org/jira/browse/HIVE-28074
> Project: Hive
> Issue Type: Improvement
> Components: Standalone Metastore
>Reporter: Sai Hemanth Gantasala
>Priority: Major
>
> Normalize db/table names in alter table event in the HMS.
> In create_table_core(), we do the following
> {code:java}
> tbl.setDbName(normalizeIdentifier(tbl.getDbName()));
> tbl.setTableName(normalizeIdentifier(tbl.getTableName())); {code}
> But in the alter_table, we are just taking case insensititive names and
> firing the alter_table event
> {code:java}
> firePreEvent(new PreAlterTableEvent(oldt, newTable, this)); {code}
> As a result, event consumers of HMS like Impala would face issues with the
> case insensitive names while consuming events.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (HIVE-28074) Normalize db/table name in the alter table operation in HMS
Sai Hemanth Gantasala created HIVE-28074:
Summary: Normalize db/table name in the alter table operation in
HMS
Key: HIVE-28074
URL: https://issues.apache.org/jira/browse/HIVE-28074
Project: Hive
Issue Type: Improvement
Components: Standalone Metastore
Reporter: Sai Hemanth Gantasala
Normalize db/table names in alter table event in the HMS.
In create_table_core(), we do the following
{code:java}
tbl.setDbName(normalizeIdentifier(tbl.getDbName()));
tbl.setTableName(normalizeIdentifier(tbl.getTableName())); {code}
But in the alter_table, we are just taking case insensititive names and firing
the alter_table event
{code:java}
firePreEvent(new PreAlterTableEvent(oldt, newTable, this)); {code}
As a result, event consumers of HMS like Impala would face issues with the case
insensitive names while consuming events.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-27022) Split removeDuplicateCompletedTxnComponents away from AcidHouseKeeper and onto a separate timer
[ https://issues.apache.org/jira/browse/HIVE-27022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816662#comment-17816662 ] Denys Kuzmenko commented on HIVE-27022: --- Merged to master Thanks for the patch [~tarak271]! > Split removeDuplicateCompletedTxnComponents away from AcidHouseKeeper and > onto a separate timer > --- > > Key: HIVE-27022 > URL: https://issues.apache.org/jira/browse/HIVE-27022 > Project: Hive > Issue Type: Improvement >Reporter: Jason Phelps >Assignee: Taraka Rama Rao Lethavadla >Priority: Major > Labels: pull-request-available > > The operations and queries involved with > removeDuplicateCompletedTxnComponents are much costlier than the rest of the > AcidHouseKeeper jobs. The default timer for > metastore.acid.housekeeper.interval is 60s [0], which is much too frequent > for removeDuplicateCompletedTxnComponents, but fine for the other operations. > There is no way of lowering the internal for just > removeDuplicateCompletedTxnComponents without impacting the other > AcidHouseKeeper jobs, so I am requesting that it be split into its own > process/timer > [0] > https://github.com/apache/hive/blob/master/standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java#L286 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-27022) Split removeDuplicateCompletedTxnComponents away from AcidHouseKeeper and onto a separate timer
[ https://issues.apache.org/jira/browse/HIVE-27022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Kuzmenko resolved HIVE-27022. --- Fix Version/s: 4.0.0 Resolution: Fixed > Split removeDuplicateCompletedTxnComponents away from AcidHouseKeeper and > onto a separate timer > --- > > Key: HIVE-27022 > URL: https://issues.apache.org/jira/browse/HIVE-27022 > Project: Hive > Issue Type: Improvement >Reporter: Jason Phelps >Assignee: Taraka Rama Rao Lethavadla >Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > > The operations and queries involved with > removeDuplicateCompletedTxnComponents are much costlier than the rest of the > AcidHouseKeeper jobs. The default timer for > metastore.acid.housekeeper.interval is 60s [0], which is much too frequent > for removeDuplicateCompletedTxnComponents, but fine for the other operations. > There is no way of lowering the internal for just > removeDuplicateCompletedTxnComponents without impacting the other > AcidHouseKeeper jobs, so I am requesting that it be split into its own > process/timer > [0] > https://github.com/apache/hive/blob/master/standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java#L286 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HIVE-28059) Expose Iceberg REST Catalog
[ https://issues.apache.org/jira/browse/HIVE-28059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816540#comment-17816540 ] Denys Kuzmenko edited comment on HIVE-28059 at 2/12/24 9:52 AM: would be nice if you could attach the design doc. also some useful reading: https://datastrato.ai/docs/0.3.1/iceberg-rest-service/ https://lists.apache.org/thread/05c18jbdtn61o8po021vfmrsnf5h8h3h Works as a catalog proxy, supporting HiveCatalog and JDBCCatalog https://datastrato.ai/blog/gravitino-iceberg-rest-catalog-service/ !Screenshot 2024-02-12 at 9.46.38.png! was (Author: dkuzmenko): would be nice if you could attach the design doc. also some useful reading: https://datastrato.ai/docs/0.3.1/iceberg-rest-service/ Works as a catalog proxy, supporting HiveCatalog and JDBCCatalog https://datastrato.ai/blog/gravitino-iceberg-rest-catalog-service/ !Screenshot 2024-02-12 at 9.46.38.png! > Expose Iceberg REST Catalog > --- > > Key: HIVE-28059 > URL: https://issues.apache.org/jira/browse/HIVE-28059 > Project: Hive > Issue Type: New Feature > Components: Hive >Affects Versions: 4.0.0-beta-1 >Reporter: Henri Biestro >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2024-02-12 at 9.46.38.png > > > Iceberg provides a REST catalog implementation that allows 3rd party query > engines to integrate with iceberg tables. > The API specification is at > https://github.com/apache/iceberg/blob/master/open-api/rest-catalog-open-api.yaml > Exposing a REST implementation for Hive Metastore for the tables hosted in > HMS will allow non-thrift-speaking 3rd party engines to integrate with HMS. > To allow a different deployment scenario (without HMS), the service should > also be easily running standalone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HIVE-26445) Use tez.local.mode.without.network for qtests
[
https://issues.apache.org/jira/browse/HIVE-26445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor resolved HIVE-26445.
-
Resolution: Fixed
> Use tez.local.mode.without.network for qtests
> -
>
> Key: HIVE-26445
> URL: https://issues.apache.org/jira/browse/HIVE-26445
> Project: Hive
> Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> looks like in case of iceberg, the local dagclient behaves weird:
> {code}
> 2022-08-02T06:54:36,669 ERROR [2f953972-7675-4594-8d6b-d1c295c056a5
> Time-limited test] tez.TezTask: Failed to execute tez graph.
> java.lang.NullPointerException: null
> at
> org.apache.hadoop.hive.ql.exec.tez.TezTask.collectCommitInformation(TezTask.java:367)
> ~[hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:279)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:212)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:105)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.launchTask(Executor.java:354)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.launchTasks(Executor.java:327)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.runTasks(Executor.java:244)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.execute(Executor.java:105)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:355)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:205)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:154)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:149)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> {code}
> it's thrown from
> https://github.com/apache/hive/blob/e0f2d287c562423dc2632910aae4f1cd8bcd4b4d/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/TezTask.java#L367
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HIVE-26445) Use tez.local.mode.without.network for qtests
[
https://issues.apache.org/jira/browse/HIVE-26445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816541#comment-17816541
]
László Bodor commented on HIVE-26445:
-
merged to master, thanks [~ayushtkn] for the review!
> Use tez.local.mode.without.network for qtests
> -
>
> Key: HIVE-26445
> URL: https://issues.apache.org/jira/browse/HIVE-26445
> Project: Hive
> Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> looks like in case of iceberg, the local dagclient behaves weird:
> {code}
> 2022-08-02T06:54:36,669 ERROR [2f953972-7675-4594-8d6b-d1c295c056a5
> Time-limited test] tez.TezTask: Failed to execute tez graph.
> java.lang.NullPointerException: null
> at
> org.apache.hadoop.hive.ql.exec.tez.TezTask.collectCommitInformation(TezTask.java:367)
> ~[hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:279)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:212)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:105)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.launchTask(Executor.java:354)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.launchTasks(Executor.java:327)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.runTasks(Executor.java:244)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.execute(Executor.java:105)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:355)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:205)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:154)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:149)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> {code}
> it's thrown from
> https://github.com/apache/hive/blob/e0f2d287c562423dc2632910aae4f1cd8bcd4b4d/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/TezTask.java#L367
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-26445) Use tez.local.mode.without.network for qtests
[
https://issues.apache.org/jira/browse/HIVE-26445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated HIVE-26445:
Fix Version/s: 4.0.0
> Use tez.local.mode.without.network for qtests
> -
>
> Key: HIVE-26445
> URL: https://issues.apache.org/jira/browse/HIVE-26445
> Project: Hive
> Issue Type: Improvement
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> looks like in case of iceberg, the local dagclient behaves weird:
> {code}
> 2022-08-02T06:54:36,669 ERROR [2f953972-7675-4594-8d6b-d1c295c056a5
> Time-limited test] tez.TezTask: Failed to execute tez graph.
> java.lang.NullPointerException: null
> at
> org.apache.hadoop.hive.ql.exec.tez.TezTask.collectCommitInformation(TezTask.java:367)
> ~[hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.exec.tez.TezTask.execute(TezTask.java:279)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:212)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at
> org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:105)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.launchTask(Executor.java:354)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.launchTasks(Executor.java:327)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.runTasks(Executor.java:244)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Executor.execute(Executor.java:105)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:355)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:205)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:154)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> at org.apache.hadoop.hive.ql.Driver.run(Driver.java:149)
> [hive-exec-4.0.0-alpha-2-SNAPSHOT.jar:4.0.0-alpha-2-SNAPSHOT]
> {code}
> it's thrown from
> https://github.com/apache/hive/blob/e0f2d287c562423dc2632910aae4f1cd8bcd4b4d/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/TezTask.java#L367
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HIVE-28059) Expose Iceberg REST Catalog
[ https://issues.apache.org/jira/browse/HIVE-28059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Kuzmenko updated HIVE-28059: -- Attachment: Screenshot 2024-02-12 at 9.46.38.png > Expose Iceberg REST Catalog > --- > > Key: HIVE-28059 > URL: https://issues.apache.org/jira/browse/HIVE-28059 > Project: Hive > Issue Type: New Feature > Components: Hive >Affects Versions: 4.0.0-beta-1 >Reporter: Henri Biestro >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2024-02-12 at 9.46.38.png > > > Iceberg provides a REST catalog implementation that allows 3rd party query > engines to integrate with iceberg tables. > The API specification is at > https://github.com/apache/iceberg/blob/master/open-api/rest-catalog-open-api.yaml > Exposing a REST implementation for Hive Metastore for the tables hosted in > HMS will allow non-thrift-speaking 3rd party engines to integrate with HMS. > To allow a different deployment scenario (without HMS), the service should > also be easily running standalone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (HIVE-28059) Expose Iceberg REST Catalog
[ https://issues.apache.org/jira/browse/HIVE-28059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816540#comment-17816540 ] Denys Kuzmenko commented on HIVE-28059: --- would be nice if you could attach the design doc. also some useful reading: https://datastrato.ai/docs/0.3.1/iceberg-rest-service/ Works as a catalog proxy, supporting HiveCatalog and JDBCCatalog https://datastrato.ai/blog/gravitino-iceberg-rest-catalog-service/ !Screenshot 2024-02-12 at 9.46.38.png! > Expose Iceberg REST Catalog > --- > > Key: HIVE-28059 > URL: https://issues.apache.org/jira/browse/HIVE-28059 > Project: Hive > Issue Type: New Feature > Components: Hive >Affects Versions: 4.0.0-beta-1 >Reporter: Henri Biestro >Priority: Major > Labels: pull-request-available > Attachments: Screenshot 2024-02-12 at 9.46.38.png > > > Iceberg provides a REST catalog implementation that allows 3rd party query > engines to integrate with iceberg tables. > The API specification is at > https://github.com/apache/iceberg/blob/master/open-api/rest-catalog-open-api.yaml > Exposing a REST implementation for Hive Metastore for the tables hosted in > HMS will allow non-thrift-speaking 3rd party engines to integrate with HMS. > To allow a different deployment scenario (without HMS), the service should > also be easily running standalone. -- This message was sent by Atlassian Jira (v8.20.10#820010)
