Skip to content

Conversation

@pnilan
Copy link
Contributor

@pnilan pnilan commented May 1, 2025

What

How

  • is_client_side_incremental = true

Review guide

  1. manifest.yaml
  2. else

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌
@pnilan pnilan requested a review from a team as a code owner May 1, 2025 23:29
@vercel
Copy link

vercel bot commented May 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
airbyte-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 7, 2025 4:06pm
$ref: "#/definitions/base_retriever"
requester:
$ref: "#/definitions/base_requester"
path: /crm-pipelines/v1/pipelines/deals
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note that I've maintained use of the v1 endpoint for this migration, but we should probably update to v3 at some point. There will be some annoyances (i.e. many transformations) involved with that.

Copy link
Contributor

Choose a reason for hiding this comment

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

yep for simplicity and no strict deprecation date, we can leave as is to make the migration easier

Copy link
Contributor

@brianjlai brianjlai left a comment

Choose a reason for hiding this comment

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

overall looks good, just a few notes and comments. Given that this is quite similar to many of our other client-side incremental streams, I think we can just rely on our regression testing result analysis and skip the progressive rollout. Once we have that and the comments then 👍

$ref: "#/definitions/base_retriever"
requester:
$ref: "#/definitions/base_requester"
path: /crm-pipelines/v1/pipelines/deals
Copy link
Contributor

Choose a reason for hiding this comment

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

yep for simplicity and no strict deprecation date, we can leave as is to make the migration easier

max_concurrency: 40

schemas:
deal_pipelines:
Copy link
Contributor

Choose a reason for hiding this comment

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

we should also delete the schemas/deal_pipelines.json since its now inline

Copy link
Contributor

@brianjlai brianjlai left a comment

Choose a reason for hiding this comment

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

lgtm!

@github-actions
Copy link
Contributor

github-actions bot commented May 7, 2025

source-hubspot Connector Test Results

348 tests   348 ✅  4m 23s ⏱️
  2 suites    0 💤
  2 files      0 ❌

Results for commit 497a931.

♻️ This comment has been updated with latest results.

@pnilan pnilan merged commit c7fe31a into master May 7, 2025
46 of 47 checks passed
@pnilan pnilan deleted the pnilan/source-hubspot/migrate-deal-pipelines branch May 7, 2025 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment