-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Source SalesForce: Add Stream Slice Step option to specification #35421
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
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
c487384
Source SalesForce: add stream_slice_step
artem1205 ef6c923
Source SalesForce: add stream_slice_step
artem1205 ad5368c
Source SalesForce: update image
artem1205 dd83e4f
Source SalesForce: add examples
artem1205 9628526
Merge branch 'master' into artem1205/source-salesforce-OC-4225
artem1205 91c17d9
Source SalesForce: update docs
artem1205 b49deb2
Source SalesForce: update project toml
artem1205 7ff0317
Merge remote-tracking branch 'origin/master' into artem1205/source-sa…
artem1205 63b2704
Source SalesForce: update expected records
artem1205 6b716ce
Source SalesForce: update airbyte cdk version
artem1205 6a42c70
Source SalesForce: set stop_sync_on_stream_failure as default behaviour
artem1205 fcc1510
Source SalesForce: add unit test
artem1205 1015acf
Source SalesForce: add unit test
artem1205 b19b527
Source SalesForce: disable incremental test
artem1205 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
10 changes: 5 additions & 5 deletions
10
airbyte-integrations/connectors/source-salesforce/poetry.lock
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,7 +3,7 @@ requires = [ "poetry-core>=1.0.0",] | |
build-backend = "poetry.core.masonry.api" | ||
|
||
[tool.poetry] | ||
version = "2.3.1" | ||
version = "2.3.2" | ||
name = "source-salesforce" | ||
description = "Source implementation for Salesforce." | ||
authors = [ "Airbyte <[email protected]>",] | ||
|
@@ -18,7 +18,7 @@ include = "source_salesforce" | |
[tool.poetry.dependencies] | ||
python = "^3.9,<3.12" | ||
pandas = "==2.2.0" | ||
airbyte-cdk = "==0.59.2" | ||
airbyte-cdk = "^0.63.2" | ||
|
||
[tool.poetry.scripts] | ||
source-salesforce = "source_salesforce.run:run" | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests will be failing as @brianjlai changed the way errors are being thrown in the CDK. I suggest that we leave it at 0.59.2 for the purpose of the oncall and that we fix that later on
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
version 0.59.2 fails on abnormal_state test, that's why I upgraded to latest one
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brianjlai to be clear on what the issue is here. The previous AbstractSource code behavior was:
The new behavior is:
This is a breaking change as SourceSalesforce is expecting this error specifically. Would it make sense that if there is only one error that we rethrow the same error? I'm not sure because this would fix the test but the new behavior would be inconsistent... Else, we will need to do some development but the new code somewhat swallow the original error and only expose the
error_message
which seems flaky to me