Draft of metadata API with timestamp tracking capabilities. #1725
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm on holidays this week can have a look next Friday. |
splatch
force-pushed
the
resultset-metadata
branch
from
989cc2c to
72b4ff2
Compare
|
It does feel a bit different from the other parts of our API ... but I guess I would simply need to play around with it a bit. I gess we can always change things in the future, if we want to give all parts the same feel. |
splatch
force-pushed
the
resultset-metadata
branch
from
72b4ff2 to
425e4a0
Compare
splatch
force-pushed
the
resultset-metadata
branch
4 times, most recently
from
6997913 to
4d590d3
Compare
|
@chrisdutz FYI I've separated API and SPI parts, now it is a bit closer to overall paradigm we have. Still metadata is immutable and a bit constrained in manipulation to avoid 1) putting too much there 2) relying too much on it. |
splatch
force-pushed
the
resultset-metadata
branch
from
4d590d3 to
862efa5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduction of tag metadata which serves similar purpose to result set metadata for JDBC, but with constraints on key syntax. Softly related to #1471 and other drivers which are capable of providing timestamp information as a part of message exchanges.
In order to force registration of metadata keys, so they can be identified by callers, if needed, keys have non-string form.
Feature been discussed recently in this thread:
https://lists.apache.org/thread/chc1p0czm7q33n1r57zbw7h11c7wzp4l
but origins of feature come from older thread:
https://lists.apache.org/thread/r3g4y6p7kst7z5bdpmccd8538h3hl80f