You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jackjlli and I have come up with the design document for supporting the consistent push on Pinot. The main idea is to reuse the "segment replacement protocol" added as part of the merge-rollup service to switch old segments with new segments.
The existing protocol has some limitations since it was originally designed in the context of merge/rollup. Here are some main changes:
Add "reverted" state for segment lineage entry & revert API
Add "select" API that returns the list of target segments to be replaced given the time range.
Improve the segment name generator for the unique segment name
@jackjlli and I have come up with the design document for supporting the consistent push on Pinot. The main idea is to reuse the "segment replacement protocol" added as part of the merge-rollup service to switch old segments with new segments.
The existing protocol has some limitations since it was originally designed in the context of merge/rollup. Here are some main changes:
https://docs.google.com/document/d/1PUy4wSUPFyEWEW3a88Mipdug3cPj4EpV__lx-BVUTYk/edit#
The text was updated successfully, but these errors were encountered: