Other: Historical resync API for google sheets. Make schema and tables not required fields in order to trigger a sync of all tables
Answered
We are adding a feature to let our users trigger historical sync of their connectors. We are looking at the resync API but don't see some of the features(listed below) from Fivetran UI being supported by the API.
- Ability to trigger historical resyncs of connectors like google sheets via the API. Google sheets doesn't have tables but API requires tables.
- Ability to trigger a historical resync of all the tables in a connector without specifying each schema and tables in the schema in the API. Schema and tables are required field in API but not in Fivetran UI
-
Official comment
Hi Abha Chaudhary, thanks for writing in and clarifying your use cases. I agree these are missing options in our API and would be super reasonable additions. We don't currently have this planned, but these feel like gaps I'd like to fill in the mid to near term.
Thank you for bringing them to our attention!
-
Actually, one of our engineers just reminded me of the is_historic_sync field in our Modify a Connector endpoint. Would that solve for what you're looking to do?
-
Hi Jimmy,
Actually, one of our engineers just reminded me of the is_historic_sync field in our Modify a Connector endpoint. Would that solve for what you're looking to do?
Thanks for the response! Does setting `is_historical_sync` field to True at connector level means every subsequent sync is going to be a historical sync instead of an incremental update?
-
Hi Abha Chaudhary, It just runs the historic sync once. We're going to clarify this in the docs, because I think it is currently a bit confusing.
Please sign in to leave a comment.
Comments
4 comments