-
Notifications
You must be signed in to change notification settings - Fork 5k
feat(source-hubspot): allow for a configured catalog to specify a user defined cursor field #69782
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
base: master
Are you sure you want to change the base?
feat(source-hubspot): allow for a configured catalog to specify a user defined cursor field #69782
Conversation
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. Helpful Resources
PR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
|
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit 98a699b. |
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
1 similar comment
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
/run-regression-tests
|
…fore running tests The regression test harness was failing with 'lstat /tmp/live_tests_artifacts: no such file or directory' when pytest failed early (before pytest_configure hook runs). Root cause: The /tmp/live_tests_artifacts directory is created by pytest's pytest_configure hook in conftest.py. However, if pytest fails to start (e.g., cloud-sql-proxy fails, poetry install fails), the hook never runs and the directory is never created. The airbyte-ci code then crashes when trying to check if the directory exists. Fix: Ensure the base /tmp/live_tests_artifacts directory exists in the container before running pytest. This allows the error handling code to run properly even if pytest fails early. This fix addresses the issue reported in PR #69782 where regression tests were failing with directory not found errors. Co-Authored-By: AJ Steers <[email protected]>
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. Helpful Resources
PR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
|
|
|
/approve-regression-tests Run here: Looking over results. The record counts match, expected diff in the catalogs now that source_defined_cursor will be false for the affected streams since they support customer selecting the cursor. Record mismatches might be from run skew. Approving the results
|
updated to the latest CDK which allows for usage of the
allow_catalog_defined_cursor_fieldfield which enables a stream to support customers defining the cursor field when configuring their schema.The configured catalog will persist the custom
cursor_fieldand during a sync we will read thecursor_fieldfrom the configured catalog and use it when persisting state and extracting cursor values. If not defined, we fall back to the one defined on theincremental_synccomponent.Tested this on Cloud and seen the proper values reflected in the emitted state message
CDK PR with the feature:
airbytehq/airbyte-python-cdk#851