[
https://issues.apache.org/jira/browse/HIVE-23962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217885#comment-17217885
]
Naveen Gangam commented on HIVE-23962:
--------------------------------------
[~Rajkumar Singh] We understand that beeline-site.xml is for this purpose. This
fix is a further enhancement to that feature. This allows users to control the
beeline profile being used via an environment variable. With existing
workloads, to change the beeline URL, user will have to
1) either change the existing URL in beeline-site.xml or
2) add a new URL to beeline-site.xml and make this the default.
The latter option works fine if you want to change it across all users. But
users may want to selectively do so across some sessions but not all. Having an
environment variable aids with this without having to change anything on the
workload.
For example, you might want to run a workload to test performance acid tables
vs non-acid tables. We can now create a new profiles in beeline-site.xml, one
that enables acid tables by default and other that uses legacy-mode where
tables are non-acid by default and run the workload again each like so
BEELINE_URL_LEGACY=acid
beeline -f "workload.hql"
BEELINE_URL_LEGACY=non-acid
beeline -f "workload.hql"
[~Xiaomeng Zhang] [~ychena] Could you please review this? I made a minor change
to the prior fix in PR1344 where we would only use "beeline -c" when
service="cli". It doesnt work when we invoke beeline.sh script. Thanks
> Make bin/hive pick user defined jdbc url
> -----------------------------------------
>
> Key: HIVE-23962
> URL: https://issues.apache.org/jira/browse/HIVE-23962
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 4.0.0
> Reporter: Xiaomeng Zhang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently hive command will trigger bin/hive which run "beeline" by default.
> We want to pass a env variable so that user can define which url beeline use.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
