dabla opened a new pull request, #75272:
URL: https://github.com/apache/airflow/pull/75272

   Follow-up to #74675, addressing @amoghrajesh's post-merge review
   (https://github.com/apache/airflow/pull/74675#pullrequestreview-5596928776) 
before the provider
   release that ships it.
   
   **MSGraphAsyncOperator (durable)**
   - A page is stored as `{"result": ...}`. A page whose `result_processor` 
returned `None` no longer
     fails the task (the task state store refuses `None`). A page that is gone 
from the store, for
     instance expired under `[state_store] default_retention_days`, now fails 
the try with
     `MSGraphPageNotInTaskStateStoreError` and clears the store, so the next 
try starts again from the
     first page instead of returning a result with a hole in it.
   - The pages and the cursor are removed from the store once the result is 
returned. A request that is
     not a GET keeps only its result, written before the pages are removed.
   - `durable=True` below Airflow 3.3 warns at parse time and is turned off, as 
it is for the operators
     on `ResumableJobMixin`.
   - The store keys and the cursor type are private, and a dead assignment is 
gone.
   
   **PowerBIDatasetRefreshOperator**
   - Fire-and-forget pushes the refresh id once. A retry that finds the refresh 
still in progress counts
     it as done, since the task only had to start it.
   - The changelog and the operator docs say what changed for users who set 
nothing: the refresh starts
     from the worker, so workers need network access to `api.powerbi.com`, and 
a durable refresh is not
     cancelled when polling fails. `durable=False` restores both.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code (Opus 5.5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to