Skip to content
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

Propagate more ReadOptions to ApproximateOffsetOf/Sizes #12764

Closed
wants to merge 1 commit into from

Conversation

pdillinger
Copy link
Contributor

Summary: Unknown why these would ignore options like deadline and read_tier. Setting total_order_seek=true is unnecessary because of the disable_prefix_seek (= true) parameter to NewIndexIterator. This is only used by the hash index, which uses total order seek if either the ReadOption or the parameter is true. The parameter is arguably redundant with the total_order_seek option, meaning it could be eliminated, but I think this case is exceptional (compared to e.g. no_io):

  • Prefix seek is particular to user iterators, though might be usable, carefully, for other read operations.
  • The historical default of total_order_seek=false in a sense is "wrong result by default" so cannot be interpreted as an intent to force prefix seek in an operation for which it might be usual or give bad results.

Also added a generic release note to cover this and related PRs.

Test Plan: existing tests

Summary: Unknown why these would ignore options like deadline and
read_tier. Setting total_order_seek=true is unnecessary because of the
disable_prefix_seek (= true) parameter to NewIndexIterator. This is only
used by the hash index, which uses total order seek if either the
ReadOption or the parameter is true. The parameter is arguably redundant
with the total_order_seek option, meaning it could be eliminated, but
I think this case is exceptional (compared to e.g. no_io):
* Prefix seek is particular to user iterators, though might be usable,
  carefully, for other read operations.
* The historical default of total_order_seek=false in a sense is "wrong
  result by default" so cannot be interpreted as an intent to force prefix
  seek in an operation for which it might be usual or give bad results.

Also added a generic release note to cover this and related PRs.

Test Plan: existing tests
@facebook-github-bot
Copy link
Contributor

@pdillinger has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@pdillinger merged this pull request in 3abcba8.

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

Successfully merging this pull request may close these issues.

3 participants