[
https://issues.apache.org/jira/browse/BEAM-10385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153216#comment-17153216
]
Valentyn Tymofieiev commented on BEAM-10385:
--------------------------------------------
Thanks for cc'ing me. According to current release guidelines, an issue should
not block the release if the problem exists in the current released version or
is a bug in new functionality that does not exist in the current released
version. It should be a blocker if the bug is a regression between the
currently released version and the release in progress and has no easy
workaround [1].
>From reading this thread, this appears to be an enhancement/new functionality.
>Following[1], I'd like to ask you to not backport or cherry-pick this to
>2.23.0 branch until the release is finalized to avoid increasing the release
>overhead.
[1]
https://beam.apache.org/contribute/release-guide/#4-triage-release-blocking-issues-in-jira
> Integrate SQL expansion into Flink job server
> ---------------------------------------------
>
> Key: BEAM-10385
> URL: https://issues.apache.org/jira/browse/BEAM-10385
> Project: Beam
> Issue Type: New Feature
> Components: runner-flink
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: P2
> Fix For: 2.24.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The expansion server is started with the job server to allow for an expansion
> of external transforms during pipeline submission. At the moment, an extra
> expansion server has to be started to expand SqlTransform. It would be
> desirable to include the SQL expansion into the expansion server that is
> started with the job server.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
