Skip to content
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

chore: Standardise on queryAll operation in Bulk API 2.0 implementation #77

Conversation

maamoonhussain
Copy link
Contributor

Description

Currently, the Bulk API 2.0 implementation uses query operation while both REST API and Bulk API 1.0 use queryAll. This inconsistency means that Bulk API 2.0 might miss deleted and archived records that are captured by the other API types.

Current Behavior

  • REST API uses queryAll
  • Bulk API 1.0 uses queryAll
  • Bulk API 2.0 uses query

Expected Behavior

All API types should use queryAll to ensure consistent behavior and data completeness across different API implementations.

Technical Details

The change required is in tap_salesforce/salesforce/bulk2.py, updating the operation from "query" to "queryAll" in the _create_job method.

References

Impact

This change will ensure that Bulk API 2.0 returns the same set of records as the other API types, including deleted and archived records.

Type

  • Chore
  • Documentation

@maamoonhussain maamoonhussain changed the title Standardise on queryAll operation in Bulk API 2.0 implementation chore: Standardise on queryAll operation in Bulk API 2.0 implementation Feb 11, 2025
@edgarrmondragon edgarrmondragon self-assigned this Feb 11, 2025
@edgarrmondragon edgarrmondragon self-requested a review February 11, 2025 22:48
Copy link
Member

@edgarrmondragon edgarrmondragon left a comment

Choose a reason for hiding this comment

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

I think this makes sense. Thanks @maamoonhussain!

@edgarrmondragon edgarrmondragon merged commit 945f77c into MeltanoLabs:main Feb 11, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants