[
https://issues.apache.org/jira/browse/CALCITE-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde reopened CALCITE-3102:
----------------------------------
Assignee: Julian Hyde (was: Danny Chan)
I screwed up, I asked [~danny0405] to make this change and I now think that it
goes too far. I should have realized that removing (for example) methods whose
arguments are of type SemiJoin is a serious breaking change. People will still
want to use those methods while they are converting their code away from
SemiJoin.
I am re-opening this case, and have assigned to myself.
I intend to fix by:
* restoring these methods (so that people can continue to use SemiJoin but will
see deprecation warnings);
* adding comments (or whatever) to silence the deprecation warnings;
* changing the 'to be removed before 2.0' comments to 'to be removed before
1.21'.
> Deprecation warnings following [CALCITE-2969]
> ---------------------------------------------
>
> Key: CALCITE-3102
> URL: https://issues.apache.org/jira/browse/CALCITE-3102
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Following CALCITE-2969 there are a couple of dozen deprecation warnings. Our
> policy is to tolerate no deprecation warnings. So we either need to stop
> using deprecated APIs or silence the warnings.
> This is a blocker for 1.20.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
