Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Mejora del conector: merge api

Answered
Luis Garay User

Request that the Oracle Connector Historical Sync API accept per-table parameters.

Reference: The per-table API connector

Improvement: What is per-table parameterized connector?

 

The proposal is that the parameters of this API
https://fivetran.com/docs/rest-api/api-reference/connection-schema/resync-tables

be merged with this one
https://fivetran.com/docs/rest-api/api-reference/connections/resync-connection#resyncconnectiondatahistoricalsync

so that the former can execute the specific table historically, and not the entire connector.

 

 

REFERENCE

TICKET 

Id #267573

https://support.fivetran.com/hc/en-us/requests/267573?page=1

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Jimmy Fivetranner

    Hi Luis,

    I can see this being useful! Can you tell me more about your use case—for example, what specific challenges or business needs are driving the request for per-table parameterization in the Oracle Connector Historical Sync API?

    Thanks,
    Jimmy