Regarding deprecation, I think the general meaning is "this will be removed
in the future releases", it nowhere means it is broken or has issues. I
don't think if we are deprecating it, we can just ignore the failures if
they are indeed bugs or issues with the prod code. We shouldn't release
Yi Zhang created HIVE-27115:
---
Summary: HiveInputFormat column project push down wrong fields (MR)
Key: HIVE-27115
URL: https://issues.apache.org/jira/browse/HIVE-27115
Project: Hive
Issue Type:
Naresh P R created HIVE-27114:
-
Summary: Provide a configurable filter for removing useless
properties from PartitionDesc objects from getPartitions HMS Calls
Key: HIVE-27114
URL:
Riju Trivedi created HIVE-27113:
---
Summary: Documentation for hive.thrift.client.max.message.size
config needs to be corrected
Key: HIVE-27113
URL: https://issues.apache.org/jira/browse/HIVE-27113
Taraka Rama Rao Lethavadla created HIVE-27112:
-
Summary: implement array_except UDF in Hive
Key: HIVE-27112
URL: https://issues.apache.org/jira/browse/HIVE-27112
Project: Hive
xiongyinke created HIVE-27111:
-
Summary: Import zstd-jni to support Parquet ZSTD compression
Key: HIVE-27111
URL: https://issues.apache.org/jira/browse/HIVE-27111
Project: Hive
Issue Type: Wish
