[
https://issues.apache.org/jira/browse/BEAM-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189064#comment-17189064
]
Niels Basjes commented on BEAM-9379:
------------------------------------
I thought to look into finding out why apparently simple "Update dependency"
ticket is so hard.
One thing I found is that the exact version of Calcite is propagated into all
Java files that use it:
import
org.apache.beam.vendor.calcite.v1_20_0.org.apache.calcite.schema.Function;
That makes any update of a version immediately a huge (many touched files)
change.
Why is that?
How about we drop the `v1_20_0.` part from the package name so that future
updates become so much simpler?
> Upgrade to Calcite 1.25.0
> -------------------------
>
> Key: BEAM-9379
> URL: https://issues.apache.org/jira/browse/BEAM-9379
> Project: Beam
> Issue Type: Task
> Components: dsl-sql
> Reporter: Rui Wang
> Assignee: Robin Qiu
> Priority: P2
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Upgrade to Calcite 1.22.0 after it gets released (expected by end of Feb
> 2020).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
