Release notes

[brimoor]

Summary by CodeRabbit

• New Features

  • Introduced a Databricks connector for lakehouse integration.
  • Added a new Data Lens connector with dynamic field configuration.
  • Enabled guest user access to the Data Lens.
  • Support for previewing 3D data imports within the Data Lens.
  • Added AWS session token support for cloud credential configuration.

• Bug Fixes

  • Resolved potential StopIteration errors during long-running API operations.

• Documentation

  • Enhanced documentation for the Data Lens feature, including new sections and clarified instructions.

[coderabbitai]

Walkthrough

The pull request focuses on updating documentation for FiftyOne Teams, specifically release notes for versions 2.2.0 and 2.3.0, and enhancing the Data Lens documentation. The changes introduce new features like Databricks connector, dynamic field configuration, 3D data import previews, and guest user access to Data Lens. The documentation updates provide more detailed instructions on data source connections, sample exploration, and a new section on dynamic user inputs.

Changes

File	Change Summary
docs/source/release-notes.rst	Added release note sections for FiftyOne Teams 2.2.0 and 2.3.0, detailing new features and improvements
docs/source/teams/data_lens.rst	Added "Dynamic user inputs" section, updated documentation on data sources, sample exploration, and import processes

Sequence Diagram

sequenceDiagram
    participant User
    participant DataLens
    participant DataSource
    
    User->>DataLens: Connect data source
    DataLens->>DataSource: Validate connection
    DataSource-->>DataLens: Connection confirmed
    User->>DataLens: Configure dynamic inputs
    DataLens->>DataLens: Resolve input options
    User->>DataLens: Explore and import samples

Loading

Possibly related PRs

• [docs only] Add documentation for Data Lens #5108: Adds documentation for the Data Lens feature
• [docs] update data lens documentation to include additional examples #5303: Updates Data Lens documentation with additional examples

Suggested reviewers

• findtopher

Poem

🐰 Hop into Data Lens, a magical sight
Connectors dancing, insights burning bright
Dynamic inputs, a rabbit's delight
Teams 2.3.0, taking data to new height
Innovation leaps with technical might! 🚀

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e5cd1bd and 4e04f98.

📒 Files selected for processing (2)

• docs/source/release-notes.rst (3 hunks)
• docs/source/teams/data_lens.rst (2 hunks)

👮 Files not reviewed due to content moderation or server errors (2)

• docs/source/teams/data_lens.rst
• docs/source/release-notes.rst

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[findtopher]

lgtm