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

docs: pair session output: AJ + Brian Lai #212

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

aaronsteers
Copy link
Contributor

@aaronsteers aaronsteers commented Jan 9, 2025

Adds a new section to the API ref top-level page:

image

Marks some classes as deprecated, e.g.:

image

Summary by CodeRabbit

Release Notes

  • Documentation

    • Added a new section outlining key classes for declarative sources.
    • Updated documentation for several classes to include deprecation notices.
  • Dependencies

    • Introduced the typing_extensions library.
    • Updated the pdoc development dependency to version 15.0.1.
  • Deprecations

    • Marked DeclarativeStream, DatetimeBasedCursor, GlobalSubstreamCursor, PerPartitionCursor, and PerPartitionWithGlobalCursor as deprecated.
    • Recommended using DefaultStream and ConcurrentCursor as replacements.

@github-actions github-actions bot added the docs label Jan 9, 2025
@aaronsteers aaronsteers requested a review from brianjlai January 9, 2025 19:27
Copy link
Contributor

coderabbitai bot commented Jan 9, 2025

📝 Walkthrough

Walkthrough

This pull request focuses on documentation updates for the Airbyte CDK, primarily introducing deprecation notices for several cursor and stream-related classes while adding documentation for key declarative source classes. The changes aim to guide developers towards newer, recommended implementations and provide clearer documentation about the available interfaces for building declarative sources.

Changes

File Change Summary
airbyte_cdk/__init__.py Added documentation section "Key Classes for Declarative Sources"
airbyte_cdk/sources/declarative/declarative_stream.py Deprecated DeclarativeStream class, recommending DefaultStream
airbyte_cdk/sources/declarative/incremental/... Deprecated multiple cursor classes:
- DatetimeBasedCursor
- GlobalSubstreamCursor
- PerPartitionCursor
- PerPartitionWithGlobalCursor
Recommending ConcurrentCursor as replacement
pyproject.toml Added typing_extensions dependency
Updated pdoc dev dependency version

Possibly related PRs

Suggested reviewers

  • brianjlai
  • maxi297
  • natikgadzhi

Hey there! Quick question - would you like me to elaborate on any of these changes? The deprecation notices seem pretty straightforward, but I'm happy to dive deeper if you'd like. Wdyt? 🤔


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7b39688 and 301fd1a.

⛔ Files ignored due to path filters (1)
  • poetry.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • airbyte_cdk/sources/declarative/stream_slicers/declarative_partition_generator.py (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • airbyte_cdk/sources/declarative/stream_slicers/declarative_partition_generator.py
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Check: 'source-the-guardian-api' (skip=false)
  • GitHub Check: Check: 'source-shopify' (skip=false)
  • GitHub Check: Pytest (All, Python 3.11, Ubuntu)
  • GitHub Check: Pytest (All, Python 3.10, Ubuntu)

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

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

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
pyproject.toml (1)

Line range hint 1-200: Update poetry.lock file

The pipeline is failing because the lock file needs to be updated. Please run:

poetry lock --no-update
🧰 Tools
🪛 GitHub Actions: Pytest (Fast)

[error] pyproject.toml changed significantly since poetry.lock was last generated. Run poetry lock [--no-update] to fix the lock file.

🧹 Nitpick comments (5)
airbyte_cdk/sources/declarative/incremental/global_substream_cursor.py (1)

Line range hint 75-85: Would you like to add a configuration example to the docstring?

The docstring is comprehensive, but users might benefit from seeing a concrete example of how to configure the global_substream_cursor. What do you think about adding a YAML configuration example? wdyt?

     - When using the `incremental_dependency` option, the sync will progress through parent records, preventing the sync from getting infinitely stuck. However, it is crucial to understand the requirements for both the `global_substream_cursor` and `incremental_dependency` options to avoid data loss.
+
+    Example configuration:
+        ```yaml
+        incremental_sync:
+          type: "GlobalSubstreamCursor"
+          stream_cursor:
+            type: "DatetimeBasedCursor"
+            datetime_format: "%Y-%m-%dT%H:%M:%SZ"
+            cursor_field: "updated_at"
+          partition_router:
+            type: "SubstreamPartitionRouter"
+            parent_stream_configs:
+              - stream: "parent_stream"
+                parent_key: "id"
+                partition_field: "parent_id"
+        ```
     """
pyproject.toml (1)

91-91: Consider pinning the pdoc version

The pdoc version update looks good, but using ^15.0.1 allows for potentially breaking changes. Would you consider pinning to a specific version for better reproducibility? wdyt?

-pdoc = "^15.0.1"
+pdoc = "15.0.1"
🧰 Tools
🪛 GitHub Actions: Pytest (Fast)

[error] pyproject.toml changed significantly since poetry.lock was last generated. Run poetry lock [--no-update] to fix the lock file.

airbyte_cdk/sources/declarative/incremental/per_partition_with_global.py (1)

22-26: Consider enhancing the deprecation notice with migration guidance.

The deprecation notice is clear, but developers might benefit from more detailed migration steps. What do you think about adding a brief example of how to migrate from PerPartitionWithGlobalCursor to ConcurrentCursor? Something like:

# Before
cursor = PerPartitionWithGlobalCursor(...)

# After
cursor = ConcurrentCursor(...)
airbyte_cdk/__init__.py (1)

19-27: The new documentation section is helpful! Want to make it even better? 🚀

Great addition of the key classes section! To make it even more valuable for developers, what do you think about:

  1. Adding code examples for each class?
  2. Including links to detailed API documentation?
  3. Mentioning common use cases or scenarios for each class?
airbyte_cdk/sources/declarative/incremental/per_partition_cursor.py (1)

29-33: Consider adding migration guidance for consistency.

The deprecation notice is clear, but for consistency with other files and to help developers, what do you think about adding migration guidance similar to what we suggested for PerPartitionWithGlobalCursor? This would help maintain a consistent documentation style across the codebase.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6d5ce67 and 7b39688.

📒 Files selected for processing (8)
  • airbyte_cdk/__init__.py (1 hunks)
  • airbyte_cdk/sources/declarative/declarative_stream.py (2 hunks)
  • airbyte_cdk/sources/declarative/incremental/datetime_based_cursor.py (2 hunks)
  • airbyte_cdk/sources/declarative/incremental/global_substream_cursor.py (2 hunks)
  • airbyte_cdk/sources/declarative/incremental/per_partition_cursor.py (2 hunks)
  • airbyte_cdk/sources/declarative/incremental/per_partition_with_global.py (2 hunks)
  • airbyte_cdk/sources/declarative/stream_slicers/declarative_partition_generator.py (0 hunks)
  • pyproject.toml (2 hunks)
💤 Files with no reviewable changes (1)
  • airbyte_cdk/sources/declarative/stream_slicers/declarative_partition_generator.py
✅ Files skipped from review due to trivial changes (1)
  • airbyte_cdk/sources/declarative/incremental/datetime_based_cursor.py
🧰 Additional context used
🪛 GitHub Actions: Pytest (Fast)
pyproject.toml

[error] pyproject.toml changed significantly since poetry.lock was last generated. Run poetry lock [--no-update] to fix the lock file.

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Check: 'source-pokeapi' (skip=false)
  • GitHub Check: Check: 'source-the-guardian-api' (skip=false)
  • GitHub Check: Check: 'source-shopify' (skip=false)
  • GitHub Check: Check: 'source-hardcoded-records' (skip=false)
🔇 Additional comments (4)
airbyte_cdk/sources/declarative/incremental/global_substream_cursor.py (2)

9-10: LGTM! Clear deprecation notice.

The deprecation notice and docstring update effectively communicate the transition to ConcurrentCursor. The original documentation is preserved while clearly marking the deprecation status.

Also applies to: 70-70, 73-74


Line range hint 258-261: Consider handling timer edge cases

The lookback window calculation assumes the timer was started. While the start_slices_generation method is called in stream_slices, there might be edge cases where the timer wasn't started. Should we add a guard clause in finish() to handle this case more gracefully? wdyt?

pyproject.toml (1)

54-54: LGTM! Required dependency for deprecation notices.

The addition of typing_extensions is necessary for the @deprecated decorator usage.

🧰 Tools
🪛 GitHub Actions: Pytest (Fast)

[error] pyproject.toml changed significantly since poetry.lock was last generated. Run poetry lock [--no-update] to fix the lock file.

airbyte_cdk/sources/declarative/declarative_stream.py (1)

33-39: Great job on providing context about future plans! 👍

The deprecation notice effectively communicates both the immediate action (use DefaultStream) and the longer-term context (future refactoring plans). This helps developers understand the bigger picture.

@aaronsteers
Copy link
Contributor Author

aaronsteers commented Jan 9, 2025

@brianjlai - Do you mind taking a look through the code changes? If anything is wrong or not as precise as it can be, you can use "suggest changes" and I'll apply those directly.

@aaronsteers
Copy link
Contributor Author

aaronsteers commented Jan 14, 2025

/autofix

Auto-Fix Job Info

This job attempts to auto-fix any linting or formating issues. If any fixes are made,
those changes will be automatically committed and pushed back to the PR.

Note: This job can only be run by maintainers. On PRs from forks, this command requires
that the PR author has enabled the Allow edits from maintainers option.

PR auto-fix job started... Check job output.

🟦 Job completed successfully (no changes).

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

Successfully merging this pull request may close these issues.

1 participant