You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "sunjincheng (JIRA)" <ji...@apache.org> on 2019/02/27 05:20:00 UTC

[jira] [Closed] (FLINK-11728) Deprecate CalciteConfig temporarily

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

sunjincheng closed FLINK-11728.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0
                   1.8.0

Fixed in master: 7fafb2080f16a78436636395480c44aac95a112e
Fixed in release-1.8: 4d82c7f6114d55a2b87c1324f3a3f4e2303595f1

> Deprecate CalciteConfig temporarily
> -----------------------------------
>
>                 Key: FLINK-11728
>                 URL: https://issues.apache.org/jira/browse/FLINK-11728
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0, 1.9.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The \{{CalciteConfig}} and the \{{CalciteConfigBuilder}} are tightly coupled to Calcite. However, once we move \{{TableConfig}} to \{{flink-table-api-java}} this configuration will not be possible anymore as Calcite is located in the planner module. We should deprecate the corresponding methods and classes for now to warn users until an alternative is available.
> This shortcoming has not been covered in FLIP-32.



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