[
https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068117#comment-14068117
]
Lefty Leverenz commented on HIVE-6037:
--------------------------------------
bq. I think having a hive-default.xml in trunk that is in sync with
HiveConf.java is useful. We can resort to the profile approach as a workaround
if we keep hitting into issues of spurious updates to it.
Agreed, the template file in trunk should match HiveConf.java if possible. But
people aren't consistent about updating the template file along with
HiveConf.java, and now that all parameter descriptions are in HiveConf.java it
seems redundant to update the template file with patches. (I'm sure everyone's
tired of me nagging about it and cluttering up the mailing list.)
So could the template file be generated frequently, either on a periodic basis
or every time HiveConf.java gets patched?
> Synchronize HiveConf with hive-default.xml.template and support show conf
> -------------------------------------------------------------------------
>
> Key: HIVE-6037
> URL: https://issues.apache.org/jira/browse/HIVE-6037
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Labels: TODOC14
> Fix For: 0.14.0
>
> Attachments: CHIVE-6037.3.patch.txt, HIVE-6037-0.13.0,
> HIVE-6037.1.patch.txt, HIVE-6037.10.patch.txt, HIVE-6037.11.patch.txt,
> HIVE-6037.12.patch.txt, HIVE-6037.14.patch.txt, HIVE-6037.15.patch.txt,
> HIVE-6037.16.patch.txt, HIVE-6037.17.patch, HIVE-6037.18.patch.txt,
> HIVE-6037.19.patch.txt, HIVE-6037.19.patch.txt, HIVE-6037.2.patch.txt,
> HIVE-6037.20.patch.txt, HIVE-6037.4.patch.txt, HIVE-6037.5.patch.txt,
> HIVE-6037.6.patch.txt, HIVE-6037.7.patch.txt, HIVE-6037.8.patch.txt,
> HIVE-6037.9.patch.txt, HIVE-6037.patch
>
>
> see HIVE-5879
--
This message was sent by Atlassian JIRA
(v6.2#6252)
