[jira] [Resolved] (IMPALA-4924) Remove DECIMAL V1 code at next compatibility breaking version

["Taras Bobrovytsky (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Taras Bobrovytsky resolved IMPALA-4924.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.0

{noformat}
commit a493a016450dc217d4d034d49f4a150429828454
Author: Taras Bobrovytsky <tb...@cloudera.com>
Date: Fri Feb 2 17:23:06 2018 -0800

IMPALA-4924 addendum: Change result type to decimal in a TPCH query

Change the expected result type of Kudu TPCH Q17 to Decimal because
DECIMAL_V2 is now enabled by default. This was not done earlier because
we were not running TPCH on Kudu regularly.

Cherry-picks: not for 2.x

Change-Id: I46fc038d40969547622707ce77a037494f0ed0a9
Reviewed-on: http://gerrit.cloudera.org:8080/9208
Reviewed-by: Taras Bobrovytsky <tb...@cloudera.com>
Tested-by: Impala Public Jenkins{noformat}

> Remove DECIMAL V1 code at next compatibility breaking version
> -------------------------------------------------------------
>
>                 Key: IMPALA-4924
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4924
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 2.9.0
>            Reporter: Dan Hecht
>            Assignee: Taras Bobrovytsky
>            Priority: Major
>              Labels: compatibility, include-in-v3, incompatibility
>             Fix For: Impala 3.0
>
>
> The next time Impala can make compatibility breaking changes, we should make DECIMAL_V2 the default DECIMAL behavior and remove the V1 code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)