Having too many configs complicates things for the user, and also complicates the code, and you also end up having many untested combinations of config flags. I think we should identify a bunch of non compatible changes that we think are important, fix it in a branch and make a major version release (say 1.x).
This is also related to HIVE-5875, where there is a discussion on switching the defaults for some of the configs to more desirable values, but non backward compatible values. On Wed, Dec 11, 2013 at 4:33 PM, Sergey Shelukhin <ser...@hortonworks.com> wrote: > Hi. > > There's recently been some discussion about data type changes in Hive > (double to decimal), and result changes for special cases like division by > zero, etc., to bring it in compliance with MySQL (that's what JIRAs use an > example; I am assuming ANSI SQL is meant). > The latter are non-controversial (I guess), but for the former, performance > may suffer and/or backward compat may be broken if Hive is brought in > compliance. > If fuller ANSI compat is sought in the future, there may be some even > hairier issues such as double-quoted identifiers. > > In light of that, and also following MySQL, I wonder if we should add a > flag, or set of flags, to HIVE to be able to force ANSI compliance. > When this/ese flag/s is/are not set, for example, int/int division could > return double for backward compat/perf, vectorization can skip the special > case handling for division by zero/etc., etc. > Wdyt? > > -- > 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. -- 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.
