[
https://issues.apache.org/jira/browse/HIVE-22497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Gangam updated HIVE-22497:
---------------------------------
Target Version/s: 4.0.0
Affects Version/s: 4.0.0
Assignee: Naveen Gangam
Status: Patch Available (was: Open)
Removed the default value from HiveConf.
For HiveServer2:
The value of CAPABILITIES for HiveServer2 is set during its init. Also adding
this value to hiveserver2-site.xml will override what has been set from the
code.
For HiveMetastoreClient:
Can be explicitly set by calling the HMSClient.setProcessorCapabilities() and
setProcessorId() during client initialization.
For backward compatibility with older code (like partners etc) that are not
able to change the code, this value has to be set in the hive-site.xml, value
gets picked from there.
if not set in hive-site.xml, then there are no defaults. Limitations imposed by
the translation layer will apply.
> Remove default value for Capabilities from HiveConf
> ---------------------------------------------------
>
> Key: HIVE-22497
> URL: https://issues.apache.org/jira/browse/HIVE-22497
> Project: Hive
> Issue Type: Sub-task
> Affects Versions: 4.0.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Major
> Attachments: HIVE-22497.patch
>
>
> This class is used and bundled in other jars that 3rd party connectors like
> teradata etc. So it would be good to remove this default value from HiveConf
> but rely on it being set in hive-site.xml instead. The HiveServer2 should
> still set this as part of HS2 initialization or via hiveserver2-site.xml
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
