-
Notifications
You must be signed in to change notification settings - Fork 9
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
CORE-16318 - API changes to support state manager #1223
CORE-16318 - API changes to support state manager #1223
Conversation
f8e26a1
to
64fccbc
Compare
Jenkins build for PR 1223 build 19 Build Successful: |
654ca36
to
13ef0cc
Compare
...a/src/main/resources/net/corda/schema/configuration/stateManager/1.0/corda.stateManager.json
Outdated
Show resolved
Hide resolved
c92a92a
to
d9aec2a
Compare
…ied via boot config - state manager database migrations - state manager configuration schema - state manager config key
0b3ecd0
to
62c1e75
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
<constraints nullable="false"/> | ||
</column> | ||
<column name="state" type="${state.column.type}"> | ||
<constraints nullable="false"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May need to double check this, but when we complete a flow, we null the state, we'll have to now delete the key from state storage if we can't null the state (probably a better thing anyway)
State manager configurations settings have been moved to #1240. |
The following design describes the state manager.
This set of changes facilitates these runtime-os changes. Most of these changes relate to https://r3-cev.atlassian.net/browse/CORE-16318.
state
table with some column types depending on the database being postgres or hsqldb.