Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-37045][Runtime] Expose state creation APIs for state v2 to datastream(v1) #25925

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Zakelly
Copy link
Contributor

@Zakelly Zakelly commented Jan 8, 2025

What is the purpose of the change

Currently, the state v2 is limited for internal use. This PR exposes those state APIs for DSv1 as the FLIP-488 discussed.

Brief change log

Please check the each commit.

  • Move state descriptors to flink-core (move classes by IDE) -- Leave corresponding placeholder of state descriptor to make existing PRs work well. -- will remove after several days.
  • Merge two versions of KeyedStateStore -- Thus many functions need not to change the signature while enabling state v2.
  • Merge two versions of OperatorStateStore

Verifying this change

This change is already covered by existing tests.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): no
  • The public API, i.e., is any changed class annotated with @Public(Evolving): no
  • The serializers: no
  • The runtime per-record code paths (performance sensitive): no
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
  • The S3 file system connector: no

Documentation

  • Does this pull request introduce a new feature? yes
  • If yes, how is the feature documented? no -- will add an intro doc of state v2 in later PR.

@flinkbot
Copy link
Collaborator

flinkbot commented Jan 8, 2025

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants