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

[WIP] Defer index creation in view stages until usage? #5326

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

brimoor
Copy link
Contributor

@brimoor brimoor commented Dec 28, 2024

Create indexes in view stages in their to_mongo() method rather than validate().

The motivation here is to defer potentially expensive actions like index creation until the view is actually used, rather than performing them immediately when the view is created.

As currently implemented, create_index() could be called in surprising circumstances, eg an operation that requires loading a saved view but not actually iterating over it.

Marking this PR as a draft so we can ponder this change a bit more, as there are other view stages (to_frames(), to_patches(), etc) that do perform expensive operations immediately when the view is created 🤔

Example usage

import random

import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart-geo")

# geo_near()

view = dataset.geo_near([-73.9855, 40.7580])
assert view._stages[0]._index_spec is not None

_ = len(view)
assert view._stages[0]._index_spec is None

# sort_by()

classes = ["cat", "dog", "rabbit"]
predictions = [
    fo.Classification(label=random.choice(classes))
    for _ in range(len(dataset))
]
dataset.set_values("predictions", predictions)

view = dataset.sort_by("predictions.label")
assert view._stages[0]._index_spec is not None

_ = len(view)
assert view._stages[0]._index_spec is None

# group_by()

view = dataset.group_by("predictions.label")
assert view._stages[0]._index_spec is not None

_ = len(view)
assert view._stages[0]._index_spec is None

@brimoor brimoor requested a review from a team December 28, 2024 23:12
Copy link
Contributor

coderabbitai bot commented Dec 28, 2024

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@brimoor brimoor changed the title Defer index creation in view stages until usage Defer index creation in view stages until usage? Dec 28, 2024
@brimoor brimoor changed the title Defer index creation in view stages until usage? [WIP] Defer index creation in view stages until usage? Dec 28, 2024
Base automatically changed from geo-create-index to develop January 2, 2025 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant