A bit of googling also showed both versions of the option. So two questions: 1. Should I change all cases of single-dash hiveconf to double-dash in the wiki? 2. Should a single-dash option be created to accommodate all the wrong information on the Internet and in books (including *Hadoop: The Definitive Guide* and chapters 9 & 12 of *Programming Hive*)?
I was not around when this change was made but I think we should have kept the old - dash version. We should consider adding it back. On Fri, Mar 7, 2014 at 8:56 PM, Lefty Leverenz <[EMAIL PROTECTED]>wrote:
OK, so just one of the pages in wiki has changed, and hive behavior has not changed ? (I have been using -hiveconf, but i haven't verified that with the tip of the trunk as of now).
On Fri, Mar 7, 2014 at 6:19 PM, Xuefu Zhang <[EMAIL PROTECTED]> wrote:
CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
That's right, and a closer look at the wiki shows that all the examples are -hiveconf except the new change. The only place --hiveconf appears is in duplications of help messages for the hive command, the old Hive server, or Beeline.
In a fresh export of the wiki --hiveconf occurs in these docs:
This is just getting more and more interesting. I never thought of -hiveconf option, and always assumed it was a typo of --hiveconf. (That's why I edited the one, which triggered the discovery.) I just checked and found that both work, which is out of my surprise.
With this assumption, Beeline has implemented only --hiveconf to mimic CLI.
As to the documentation, I think we can stick to --hiveconf from now on, since they are supported by both CLI and Beeline. However, -hiveconf will continue to work for CLI until its death.
Thanks, Xuefu On Fri, Mar 7, 2014 at 10:36 PM, Lefty Leverenz <[EMAIL PROTECTED]>wrote:
Great thanks for following up. THere might be a number of etl processes in the wild saying -hiveconf which is why it is important to keep around for the cli at least. On Sat, Mar 8, 2014 at 1:56 AM, Xuefu Zhang <[EMAIL PROTECTED]> wrote: