-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Source Salesforce: Deprecate API Type parameter (#9302)
* use BULK for the first sync, REST for incremental sync * if stream contains compound data or/and base64 use always REST * fix get stream state from connector state * fix integration test * refactor catalog name * format code * refactor unit tests * refactor unit tests 2 * format code 2 * Set additionalProperties to true not to break test temporarily * fix unit test and remove unnecessary filtering fields * bump version * updated spec and def yaml Co-authored-by: auganbay <auganenu@gmail.com>
- Loading branch information
1 parent
f3798ed
commit 0a3713a
Showing
14 changed files
with
135 additions
and
308 deletions.
There are no files selected for viewing
This file contains 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 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 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 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 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 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
98 changes: 0 additions & 98 deletions
98
...-integrations/connectors/source-salesforce/integration_tests/configured_catalog_rest.json
This file was deleted.
Oops, something went wrong.
This file contains 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 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 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 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.
0a3713a
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.
@augan-rymkhan
As I was testing a pull request I was submitting, I ran across some unexpected behavior related to this commit.
This condition seems to evaluates to
TRUE
forstream_state
in any incremental stream (other than the very first run).As a result, BULK API supported streams will switch to using the REST/non-BULK API after the first run.
source.generate_streams
Is this behavior intentional?
By replacing this line with the following, the BulkIncremental stream is leveraged as expected for subsequent runs:
0a3713a
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.
@jkaelin Yes, that was intentional behaviour. For the initial sync (without state), always use BULK API, where it's possible (Some streams don't support BULK API, for them always use REST). For the subsequent incremental syncs (when state is provided), use REST API.
Did you face any issue related to this logic?
If yes, you can create an issue.
0a3713a
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.
@augan-rymkhan Thanks.
I guess I'm asking: is there any particular reason that you wouldn't want to use the BULK API for subsequent syncs on streams which supported this method?
I can see a few issues switching to REST but I do not understand if there's a compelling reason to do so.
Happy to create an Issue but wanted to better understand the rationale in case I was missing something.
General issues
Specific Issue
414 URI Too Long
which is unhandled in the codeThe resolution for my specific issue would depend on whether or not there was a compelling reason to force non-BULK API usage in the first place.
stream_state
condition would suffice.414
error. Therefore, the user should be notified when configuring the connection that incremental syncs are not allowed for this stream.