-
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-13119 Add resumePoint
Avro field to support stable query paging
#1229
CORE-13119 Add resumePoint
Avro field to support stable query paging
#1229
Conversation
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.
PR title failed to match regex -> ^((CORDA|EG|ENT|INFRA|CORE|DOC|ES)-\d+)(.*)
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.
PR title failed to match regex -> ^((CORDA|EG|ENT|INFRA|CORE|DOC|ES)-\d+)(.*)
sequence_num
primary key on utxo_visible_transaction_states
sequence_num
primary key on utxo_visible_transaction_states
...a/src/main/resources/net/corda/db/schema/vnode-vault/migration/ledger-utxo-creation-v5.1.xml
Outdated
Show resolved
Hide resolved
d0cfa15
to
6399a7b
Compare
sequence_num
primary key on utxo_visible_transaction_states
resumePoint
Avro field to support stable query paging
Jenkins build for PR 1229 build 4 Build Successful: |
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
{ | ||
"name": "resumePoint", | ||
"doc": "Used by queries that support stable paging to return opaque data that indicates where the next page should resume from", | ||
"type": ["null", "bytes"], |
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.
Why is this a byte array rather than a structured type?
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.
We don't want to be opinionated on the contents of the field, it could vary from query to query - the data is opaque from the perspective of the interface.
This is a pre-requisite change to enable a
resumePoint
field to be passed back and forth between ledger custom queries initiated in a flow processor and the query execution logic in a ledger persistence processor.See corda/corda-runtime-os#4548 for full details of the changes.