-
Notifications
You must be signed in to change notification settings - Fork 407
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
RRD manifests bootstrap #9053
RRD manifests bootstrap #9053
Conversation
Web viewer built successfully. If applicable, you should also test it:
Note: This comment is updated whenever you push a commit. |
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.
Let's clean that up and make a quick PR for it.
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.
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.
There shouldn't be any reason not to use arrow1 everywhere anymore? Should try to make a standalone PR to remove all of this.
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.
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.
For now that PR cannot be merged, but I need this to be true in order to fix my metadata issue?
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.
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.
This needs a dedicated PR, and ideally a test.
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.
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.
In an ideal world, all of this new unstable manifest stuff should never make it into the main repo's proto definitions.
50146b0
to
0903f7a
Compare
0903f7a
to
77548af
Compare
Latest documentation preview deployed successfully.
Note: This comment is updated whenever you push a commit. |
77548af
to
b06e556
Compare
b06e556
to
cef10d6
Compare
QueryManifestLatestAtRelevantChunks latest_at = 300; | ||
|
||
// If specified, will perform a range query with the given parameters. | ||
// | ||
// Incompatible with `latest_at`. | ||
QueryManifestRangeRelevantChunks range = 400; | ||
|
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.
if I understood, "incompatible" here means that these 2 are mutually exclusive and both shouldn't be defined? if so, have you chosen not to use oneof
intentionally cause it comes with some obvious downsides? if nothing else, less ergonomic to use and forward breaking changes (although not sure how relevant that would be here)?
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.
Yes to all three of these questions.
This reverts commit 773e9cc.
No description provided.