Config API

The Config API provides basic catalog management operations. Similarly to API Lookup, responses of Config API are cacheable, and we recommend requesting catalog configuration only once per instance / Spark or Flink worker node and keep reusing cached catalog configuration objects if needed.

API Lookup and Config API services do not require any special performance considerations due to the low request rate nature and their typically small response sizes.

Note

  • The /config/v1/status/{status_token} is used to determine the request succeeded, failed or is still being processed (pending). While in pending state the request should not be retried.
  • For consecutive delete and create requests, the recommendation is to wait 60 seconds due to the eventual consistency nature of the system.

results matching ""

    No results matching ""