[jira] [Updated] (FLINK-12047) State Processor API (previously named Savepoint Connector) to read / write / process savepoints

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-12047:
-----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned  (was: auto-deprioritized-major auto-unassigned stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> State Processor API (previously named Savepoint Connector) to read / write / process savepoints
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-12047
>                 URL: https://issues.apache.org/jira/browse/FLINK-12047
>             Project: Flink
>          Issue Type: New Feature
>          Components: API / State Processor
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned
>
> This JIRA tracks the ongoing efforts and discussions about a means to read / write / process state in savepoints.
> There are already two known existing works (that was mentioned already in the mailing lists) related to this:
> 1. Bravo [1]
> 2. https://github.com/sjwiesman/flink/tree/savepoint-connector
> Essentially, the two tools both provide a connector to read or write a Flink savepoint, and allows to utilize Flink's processing APIs for querying / processing the state in the savepoint.
> We should try to converge the efforts on this, and have a savepoint connector like this in Flink.
> With this connector, the high-level benefits users should be able to achieve with it are:
> 1. Create savepoints using existing data from other systems (i.e. bootstrapping a Flink job's state with data in an external database).
> 2. Derive new state using existing state
> 3. Query state in savepoints, for example for debugging purposes
> 4. Migrate schema of state in savepoints offline, compared to the current more limited approach of online migration on state access.
> 5. Change max parallelism of jobs, or any other kind of fixed configuration, such as operator uids.
> [1] https://github.com/king/bravo



--
This message was sent by Atlassian Jira
(v8.20.1#820001)