Repository navigation
Closed
Labels
fixVersion/0.3.0The feature or bug should be implemented/fixed in the 0.3.0 version.The feature or bug should be implemented/fixed in the 0.3.0 version.priority/blockerIndicates the PR or issue that should block the release until it gets resolved.Indicates the PR or issue that should block the release until it gets resolved.tech debt[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.
Description
Search before asking
- I searched in the issues and found nothing similar.
Description
In flink-agents, cross-language interaction between Python and Java relies on the pemja framework. Before pemja 0.5.7, errors or JVM crashes could occur when flink-agents performed cross-language interaction from an asynchronous thread. This issue was fixed in pemja 0.5.7: alibaba/pemja#95.
Since flink-agents depends on pemja transitively through PyFlink, adopting pemja 0.5.7 in flink-agents requires the following steps:
- Bump the pemja version used by Flink.
- Release a Flink version that includes this bump.
- Update the Flink version that flink-agents depends on.
Status:
- Step 1 has been completed on Flink's 1.20, 2.x, and master branches:
- Step 2: Flink 2.0.2 and 2.2.1 already include this bump, but no patch release containing the bump has been published yet for 1.20 or 2.1.
- Step 3: The Flink patch version referenced under the dist directory has been updated accordingly.
The remaining tasks are:
- Release versions 1.20 and 2.1 that include the pemja upgrade.
- Update the minor Flink version dependency in dist.
Are you willing to submit a PR?
- I'm willing to submit a PR!
Metadata
Metadata
Assignees
Labels
fixVersion/0.3.0The feature or bug should be implemented/fixed in the 0.3.0 version.The feature or bug should be implemented/fixed in the 0.3.0 version.priority/blockerIndicates the PR or issue that should block the release until it gets resolved.Indicates the PR or issue that should block the release until it gets resolved.tech debt[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.
Activity