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
{{ message }}
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.
Currently in a ledger, we indexed entries by entry id. It would be good to have an index by offsets. This allows supporting APIs like:
readEntries(long startEntryId, int maxBytes)
readEntries(long startOffset, long endOffset)
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
nice-to-have
Provide any additional detail on your proposed use case for this feature.
entry(/request) oriented api is not very good friendly to resource-usage when do prefetching or batching reads. offset oriented api is much better for estimating resource usage.
The text was updated successfully, but these errors were encountered:
Original Issue: apache#1376
FEATURE REQUEST
Currently in a ledger, we indexed entries by entry id. It would be good to have an index by offsets. This allows supporting APIs like:
nice-to-have
entry(/request) oriented api is not very good friendly to resource-usage when do prefetching or batching reads. offset oriented api is much better for estimating resource usage.
The text was updated successfully, but these errors were encountered: