Agree on both points. For now, what I had in mind was double vs decimal,
and other such backward compat vs SQL compat and potentially perf vs SQL
compact cases.
I think one flag would not be so bad...
On Mon, Dec 16, 2013 at 8:29 AM, Alan Gates wrote:
> A couple of thoughts on this:
>
> 1) If
A couple of thoughts on this:
1) If we did this I think we should have one flag, not many. As Thejas points
out, your test matrix goes insane when you have too many flags and hence things
don't get properly tested.
2) We could do this in an incremental way, where we create this new ANSI flag
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
releas
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-controversia
