Hevo Hook

HevoHook is the primary interface between Airflow and Hevo’s APIs. The following parameters are available when creating a hook for the Hevo Pipeline. You can also use these parameters in Hevo Operators, Sensors, and Triggers.

Parameters

The HevoHook accepts the following parameters:

Types of Hooks

Hevo provides the following hooks for interacting with the Pipeline, job management, and Pipeline object APIs. Each hook provides methods to run these APIs. The methods that the hook provides can be categorized into:

• Async: These methods can be used in async contexts, such as triggers. The method names in this category are suffixed with _async.

• Sync: These methods can be used in sync contexts, such as operators, sensors, and poke. The method names in this category are suffixed with _sync. Sync methods internally invoke the corresponding async method.

HevoPipelineHook

HevoObjectHook

Retry Behavior

Refer to the following table for information on the errors and the retry policy:

Example

The following example creates two instances of HevoPipelineHook with a custom retry configuration:

• The first instance hook is configured to trigger retry attempts every 3 seconds up to 5 attempts for 429, 500, 502, 503, and 504 errors.

• The second instance hook_no_retry triggers retry attempts only for network errors, such as connection failures and timeouts. HTTP status code-based errors are not retried.

from airflow.hevo.hooks.hevo_pipeline_hook import HevoPipelineHook
# Custom retry configuration
hook = HevoPipelineHook(
    pipeline_id=123,
    connection_id="hevo_production",
    retry_limit=5,
    retry_delay=3,
    timeout=60,
    retryable_status_codes=[429, 500, 502, 503, 504],  # Include rate limiting
    extra_headers={"X-Custom-Header": "value"}
)
# Disable status code retries (network errors only)
hook_no_retry = HevoPipelineHook(
    pipeline_id=456,
    retry_limit=3,
    retryable_status_codes=[]  # Only retry network errors
)

Revision History