Skip to content
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.

ISSUE-1376: Introduce Offset Index #65

Open
sijie opened this issue Jan 15, 2020 · 0 comments
Open

ISSUE-1376: Introduce Offset Index #65

sijie opened this issue Jan 15, 2020 · 0 comments

Comments

@sijie
Copy link
Member

sijie commented Jan 15, 2020

Original Issue: apache#1376


FEATURE REQUEST

  1. Please describe the feature you are requesting.

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)
  1. 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

  1. 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant