Update Python Client to 3.3.1rc1

Author: vatsrahul1001

CHANGELOG.md

@@ -17,6 +17,16 @@
  under the License.
  -->
 
+# v3.3.1
+
+## Bug Fixes:
+
+- Allow filtering Dag runs by partition date in the API (#70304)
+- Simplify the API docs on pattern search (#70509)
+- Document the 409 response from the XCom create endpoint (#71128)
+- API: Return 503 when SQLite locks during backfill creation (#69659)
+- Reject invalid partition keys in the create asset events API (#69581)
+
 # v3.3.0
 
 ## New Features:

airflow_client/client/__init__.py

@@ -5,7 +5,7 @@
 """
     Airflow API
 
-    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.
+    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.  **Filtering with pattern parameters.** Many list endpoints accept ``*_pattern`` and ``*_prefix_pattern`` query parameters. Unless a parameter's own description says otherwise, ``*_pattern`` is a case-insensitive substring match (SQL ``ILIKE '%term%'``) where ``%`` matches any sequence and ``_`` matches any single character (e.g. ``%customer_%``) — convenient, but it cannot use B-tree indexes, so it is slow on large tables. ``*_prefix_pattern`` matches the start of the value, is case-sensitive and index-friendly (prefer it at scale); there ``%`` and ``_`` are literal and trailing non-alphanumeric characters are stripped so the range scan stays index-compatible under locale-aware collations (e.g. ``test_`` matches values starting with ``test``, and ``s3://`` matches ``s3``). In both, ``|`` means OR (e.g. ``dag1|dag2``) and ``~`` matches everything. Regular expressions are not supported by these parameters; regex-capable endpoints expose a separate parameter.
 
     The version of the OpenAPI document: 2
     Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -14,7 +14,7 @@
 """  # noqa: E501
 
 
-__version__ = "3.3.0"
+__version__ = "3.3.1"
 
 # Define package exports
 __all__ = [

airflow_client/client/api/asset_api.py

@@ -1,7 +1,7 @@
 """
     Airflow API
 
-    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.
+    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.  **Filtering with pattern parameters.** Many list endpoints accept ``*_pattern`` and ``*_prefix_pattern`` query parameters. Unless a parameter's own description says otherwise, ``*_pattern`` is a case-insensitive substring match (SQL ``ILIKE '%term%'``) where ``%`` matches any sequence and ``_`` matches any single character (e.g. ``%customer_%``) — convenient, but it cannot use B-tree indexes, so it is slow on large tables. ``*_prefix_pattern`` matches the start of the value, is case-sensitive and index-friendly (prefer it at scale); there ``%`` and ``_`` are literal and trailing non-alphanumeric characters are stripped so the range scan stays index-compatible under locale-aware collations (e.g. ``test_`` matches values starting with ``test``, and ``s3://`` matches ``s3``). In both, ``|`` means OR (e.g. ``dag1|dag2``) and ``~`` matches everything. Regular expressions are not supported by these parameters; regex-capable endpoints expose a separate parameter.
 
     The version of the OpenAPI document: 2
     Generated by OpenAPI Generator (https://openapi-generator.tech)

airflow_client/client/api/asset_state_store_api.py

@@ -1,7 +1,7 @@
 """
     Airflow API
 
-    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.
+    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.  **Filtering with pattern parameters.** Many list endpoints accept ``*_pattern`` and ``*_prefix_pattern`` query parameters. Unless a parameter's own description says otherwise, ``*_pattern`` is a case-insensitive substring match (SQL ``ILIKE '%term%'``) where ``%`` matches any sequence and ``_`` matches any single character (e.g. ``%customer_%``) — convenient, but it cannot use B-tree indexes, so it is slow on large tables. ``*_prefix_pattern`` matches the start of the value, is case-sensitive and index-friendly (prefer it at scale); there ``%`` and ``_`` are literal and trailing non-alphanumeric characters are stripped so the range scan stays index-compatible under locale-aware collations (e.g. ``test_`` matches values starting with ``test``, and ``s3://`` matches ``s3``). In both, ``|`` means OR (e.g. ``dag1|dag2``) and ``~`` matches everything. Regular expressions are not supported by these parameters; regex-capable endpoints expose a separate parameter.
 
     The version of the OpenAPI document: 2
     Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -375,6 +375,7 @@ def create_backfill(
             '404': "HTTPExceptionResponse",
             '409': "HTTPExceptionResponse",
             '422': "HTTPValidationError",
+            '503': "HTTPExceptionResponse",
         }
         response_data = self.api_client.call_api(
             *_param,
@@ -447,6 +448,7 @@ def create_backfill_with_http_info(
             '404': "HTTPExceptionResponse",
             '409': "HTTPExceptionResponse",
             '422': "HTTPValidationError",
+            '503': "HTTPExceptionResponse",
         }
         response_data = self.api_client.call_api(
             *_param,
@@ -519,6 +521,7 @@ def create_backfill_without_preload_content(
             '404': "HTTPExceptionResponse",
             '409': "HTTPExceptionResponse",
             '422': "HTTPValidationError",
+            '503': "HTTPExceptionResponse",
         }
         response_data = self.api_client.call_api(
             *_param,
@@ -664,6 +667,7 @@ def create_backfill_dry_run(
             '404': "HTTPExceptionResponse",
             '409': "HTTPExceptionResponse",
             '422': "HTTPValidationError",
+            '503': "HTTPExceptionResponse",
         }
         response_data = self.api_client.call_api(
             *_param,
@@ -735,6 +739,7 @@ def create_backfill_dry_run_with_http_info(
             '404': "HTTPExceptionResponse",
             '409': "HTTPExceptionResponse",
             '422': "HTTPValidationError",
+            '503': "HTTPExceptionResponse",
         }
         response_data = self.api_client.call_api(
             *_param,
@@ -806,6 +811,7 @@ def create_backfill_dry_run_without_preload_content(
             '404': "HTTPExceptionResponse",
             '409': "HTTPExceptionResponse",
             '422': "HTTPValidationError",
+            '503': "HTTPExceptionResponse",
         }
         response_data = self.api_client.call_api(
             *_param,

airflow_client/client/api/backfill_api.py

@@ -1,7 +1,7 @@
 """
     Airflow API
 
-    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.
+    Airflow API. All endpoints located under ``/api/v2`` can be used safely, are stable and backward compatible. Endpoints located under ``/ui`` are dedicated to the UI and are subject to breaking change depending on the need of the frontend. Users should not rely on those but use the public ones instead.  **Filtering with pattern parameters.** Many list endpoints accept ``*_pattern`` and ``*_prefix_pattern`` query parameters. Unless a parameter's own description says otherwise, ``*_pattern`` is a case-insensitive substring match (SQL ``ILIKE '%term%'``) where ``%`` matches any sequence and ``_`` matches any single character (e.g. ``%customer_%``) — convenient, but it cannot use B-tree indexes, so it is slow on large tables. ``*_prefix_pattern`` matches the start of the value, is case-sensitive and index-friendly (prefer it at scale); there ``%`` and ``_`` are literal and trailing non-alphanumeric characters are stripped so the range scan stays index-compatible under locale-aware collations (e.g. ``test_`` matches values starting with ``test``, and ``s3://`` matches ``s3``). In both, ``|`` means OR (e.g. ``dag1|dag2``) and ``~`` matches everything. Regular expressions are not supported by these parameters; regex-capable endpoints expose a separate parameter.
 
     The version of the OpenAPI document: 2
     Generated by OpenAPI Generator (https://openapi-generator.tech)