[
https://issues.apache.org/jira/browse/IMPALA-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Bobrovytsky resolved IMPALA-6622.
---------------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.12.0
{noformat}
commit dee0ec0e74d7a740bea9e9e16403b4d7483f4515
Author: Taras Bobrovytsky <[email protected]>
Date: Fri Jan 12 14:05:08 2018 -0800
IMPALA-6622: Backport parts of IMPALA-4924 to 2.x
We enabled Decimal V2 by default on master (but not on the 2.x branch)
in IMPALA-4924. There were some other code changes that are not
specific to enableing Decimal V2 that are causing merge conflicts. In
this patch, we backport those changes to reduce the chance of
conflicts.
Change-Id: I2504fb6ec7fa350296b058156b6fd7fb97bc4f9b
Reviewed-on: http://gerrit.cloudera.org:8080/9768
Reviewed-by: Taras Bobrovytsky <[email protected]>
Tested-by: Impala Public Jenkins{noformat}
> Backport parts of IMPALA-4924 to 2.x
> -------------------------------------
>
> Key: IMPALA-6622
> URL: https://issues.apache.org/jira/browse/IMPALA-6622
> Project: IMPALA
> Issue Type: Task
> Components: Frontend, Infrastructure
> Affects Versions: Impala 2.12.0
> Reporter: Lars Volker
> Assignee: Taras Bobrovytsky
> Priority: Major
> Fix For: Impala 2.12.0
>
>
> We should consider backporting parts of the change that enabled Decimal V2 by
> default to the 2.x branch: https://gerrit.cloudera.org/#/c/9062/
> Some of the tests and infrastructure code should be compatible, and
> backporting them will reduce the chance of future merge conflicts, e.g.
> IMPALA-6405. This should not enable Decimal V2 by default.
> This came out of a discussion with [~alex.behm] and [~tarmstrong].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
