Chore: Refactor: Rename module _future_cdk to shared

[aaronsteers]

Summary by CodeRabbit

• Refactor

  • Updated import statements across multiple files to transition from the _future_cdk module to the shared module for improved organization and clarity.
  • Enhanced modularity by consolidating shared components under the shared namespace.

• Bug Fixes

  • No new functionality introduced; existing logic remains unchanged, ensuring stability across the application.

• Tests

  • Adjusted test imports to reflect the new structure, maintaining test integrity without altering functionality.

[coderabbitai]

Walkthrough

Walkthrough

The changes involve a restructuring of import statements across multiple files in the Airbyte codebase. Specifically, imports for various classes such as SqlProcessorBase, SqlConfig, CatalogProvider, and StateWriterBase have been transitioned from the airbyte._future_cdk module to the airbyte.shared module. This reorganization centralizes shared components and updates the dependencies throughout the codebase.

Changes

Files	Change Summary
airbyte/_processors/sql/bigquery.py, airbyte/_processors/sql/duckdb.py, airbyte/_processors/sql/postgres.py, airbyte/_processors/sql/snowflake.py	Changed imports for SqlProcessorBase and SqlConfig from airbyte._future_cdk to airbyte.shared.
airbyte/_writers/base.py, airbyte/_writers/file_writers.py	Updated imports for CatalogProvider and StateWriterBase from airbyte._future_cdk to airbyte.shared.
airbyte/caches/_catalog_backend.py, airbyte/caches/_state_backend.py, airbyte/caches/_state_backend_base.py, airbyte/caches/base.py, airbyte/caches/snowflake.py	Reorganized imports for various classes from airbyte._future_cdk to airbyte.shared.
airbyte/destinations/base.py, airbyte/results.py, airbyte/sources/base.py	Replaced imports from airbyte._future_cdk with imports from airbyte.shared for several components.
tests/integration_tests/destinations/test_source_to_destination.py, tests/integration_tests/test_source_test_fixture.py, tests/integration_tests/test_state_handling.py	Updated test imports for CatalogProvider, SqlProcessorBase, and StateWriterBase to the airbyte.shared module.

Sequence Diagram(s)

sequenceDiagram
    participant A as User
    participant B as Application
    participant C as Shared Module

    A->>B: Request data processing
    B->>C: Import required components
    C-->>B: Provide components
    B-->>A: Return processed data

Loading

Would you like to make any adjustments to the wording or details in the summary or changes?

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e8a8cd7 and 7c8399c.

Files selected for processing (2)

• airbyte/shared/catalog_providers.py (3 hunks)
• airbyte/shared/sql_processor.py (5 hunks)

Files skipped from review due to trivial changes (2)

• airbyte/shared/catalog_providers.py
• airbyte/shared/sql_processor.py

---

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:

‼️ 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 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 or @coderabbitai title 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.

Tip

Early access features: enabled

We are currently testing the following features in early access:

• Anthropic claude-3-5-sonnet for code reviews: Anthropic claims that the new Claude model has stronger code understanding and code generation capabilities than their previous models. Note: Our default code review model was also updated late last week. Please compare the quality of the reviews between the two models by toggling the early access feature.

Note:

• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
• Please join our Discord Community to provide feedback and report issues on the discussion post.

[coderabbitai]

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)

airbyte/shared/sql_processor.py (1)

52-52: Consider using absolute imports for consistency?

I noticed that we're using a relative import for StdOutStateWriter. Given that other imports in this file use absolute paths, would it make sense to use an absolute import here as well for consistency? For example:

from airbyte.shared.state_writers import StdOutStateWriter

What do you think? This could help maintain a consistent import style throughout the file.