@kapa.ai

is_client_side_incremental: false

here means we are actually utilising the

cursor_field

value?

semi_incremental_sync:
    type: DatetimeBasedCursor
    cursor_field: "modify_time"
    cursor_datetime_formats:
      - "%Y-%m-%d %H:%M:%S"
      - "%Y-%m-%dT%H:%M:%SZ"
    datetime_format: "%Y-%m-%d %H:%M:%SZ"
    start_datetime:
      type: MinMaxDatetime
      datetime: "{{ config.get('start_date', '2016-09-01') }}"
      datetime_format: "%Y-%m-%d"
    is_client_side_incremental: false

Yes. According to the

DatetimeBasedCursor

reference, setting

is_client_side_incremental

to

true

is specifically for APIs that do not accept cursor values to filter records and always return all records, in which case Airbyte filters records locally and only emits new ones. [[Datetime cursor ref](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/reference#/definitions/DatetimeBasedCursor)] In your config it is

false

, which means Airbyte expects the API to support server-side filtering by the cursor, and the incremental behavior is driven by the

cursor_field

(

modify_time

) together with the datetime windowing (

start_datetime

,

step

, etc.). The cursor value from

modify_time

is what will be used to advance state and define what’s fetched next. [[Datetime cursor ref](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/incremental-syncs#datetimebasedcursor); [Datetime cursor props](https://docs.airbyte.com/platform/connector-development/config-based/understanding-the-yaml-file/reference#/definitions/DatetimeBasedCursor)]