[
https://issues.apache.org/jira/browse/HIVE-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaliy Fuks updated HIVE-4576:
-------------------------------
Description:
templeton.hive.properties accepts a comma-separated list of key=value property
pairs that will be passed to Hive.
However, this makes it impossible to use any "value" that itself has a comma in
it.
For example:
{code:xml}<property>
<name>templeton.hive.properties</name>
<value>hive.metastore.sasl.enabled=false,hive.metastore.uris=thrift://foo1.example.com:9083,foo2.example.com:9083</value>
</property>{code}
{noformat}templeton: starting [/usr/bin/hive, --service, cli, --hiveconf,
hive.metastore.sasl.enabled=false, --hiveconf,
hive.metastore.uris=thrift://foo1.example.com:9083, --hiveconf,
foo2.example.com:9083 etc..{noformat}
because the value is parsed using standard
org.apache.hadoop.conf.Configuration.getStrings() call which simply splits on
commas from here:
{code:java}for (String prop :
appConf.getStrings(AppConfig.HIVE_PROPS_NAME)){code}
This is problematic for any hive property that itself has multiple values, such
as hive.metastore.uris above or hive.aux.jars.path.
There should be some way to "escape" commas or a different delimiter should be
used.
was:
templeton.hive.properties accepts a comma-separated list of key=value property
pairs that will be passed to Hive.
However, this makes it impossible to use any "value" that itself has a comma in
it.
For example:
{code:xml}<property>
<name>templeton.hive.properties</name>
<value>hive.metastore.sasl.enabled=false,hive.metastore.uris=thrift://foo1.example.com:9083,foo2.example.com</value>
</property>{code}
{noformat}templeton: starting [/usr/bin/hive, --service, cli, --hiveconf,
hive.metastore.sasl.enabled=false, --hiveconf,
hive.metastore.uris=thrift://foo1.example.com:9083, --hiveconf,
foo2.example.com:9083 etc..{noformat}
because the value is parsed using standard
org.apache.hadoop.conf.Configuration.getStrings() call which simply splits on
commas from here:
{code:java}for (String prop :
appConf.getStrings(AppConfig.HIVE_PROPS_NAME)){code}
This is problematic for any hive property that itself has multiple values, such
as hive.metastore.uris above or hive.aux.jars.path.
There should be some way to "escape" commas or a different delimiter should be
used.
> templeton.hive.properties does not allow values with commas
> -----------------------------------------------------------
>
> Key: HIVE-4576
> URL: https://issues.apache.org/jira/browse/HIVE-4576
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
> Affects Versions: 0.5.0
> Reporter: Vitaliy Fuks
> Priority: Minor
>
> templeton.hive.properties accepts a comma-separated list of key=value
> property pairs that will be passed to Hive.
> However, this makes it impossible to use any "value" that itself has a comma
> in it.
> For example:
> {code:xml}<property>
> <name>templeton.hive.properties</name>
>
> <value>hive.metastore.sasl.enabled=false,hive.metastore.uris=thrift://foo1.example.com:9083,foo2.example.com:9083</value>
> </property>{code}
> {noformat}templeton: starting [/usr/bin/hive, --service, cli, --hiveconf,
> hive.metastore.sasl.enabled=false, --hiveconf,
> hive.metastore.uris=thrift://foo1.example.com:9083, --hiveconf,
> foo2.example.com:9083 etc..{noformat}
> because the value is parsed using standard
> org.apache.hadoop.conf.Configuration.getStrings() call which simply splits on
> commas from here:
> {code:java}for (String prop :
> appConf.getStrings(AppConfig.HIVE_PROPS_NAME)){code}
> This is problematic for any hive property that itself has multiple values,
> such as hive.metastore.uris above or hive.aux.jars.path.
> There should be some way to "escape" commas or a different delimiter should
> be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
