[
https://issues.apache.org/jira/browse/HIVE-28018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809621#comment-17809621
]
Ayush Saxena commented on HIVE-28018:
-------------------------------------
Some discussion around the same code,
[https://github.com/apache/hive/pull/1443#discussion_r479722459]
The value should be present, when opening session with HS2 also the config
value should have been sent back, It was added in ThriftCLIService,
OpenService. I doubt if hiveconf: prefix isn't creating issue...
> Don't require HiveConf for JDBC Metadata calls
> ----------------------------------------------
>
> Key: HIVE-28018
> URL: https://issues.apache.org/jira/browse/HIVE-28018
> Project: Hive
> Issue Type: Improvement
> Reporter: Kurt Deschler
> Assignee: Kurt Deschler
> Priority: Major
>
> The following JDBC call will throw and exception if hive.default.nulls.last
> is not set in HiveConf:
> conn.getMetaData().nullsAreSortedLow();
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
