You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jason810496 (via GitHub)" <gi...@apache.org> on 2026/05/06 06:21:33 UTC
[I] Support `Airflow-Java-SDK-Bundle-Version` JAR menifest metadata [airflow]
jason810496 opened a new issue, #66454:
URL: https://github.com/apache/airflow/issues/66454
as title, user should be able to add the `Airflow-Java-SDK-Bundle-Version` metadata in build-time via flag from gradle extension. Additionally, the `Airflow-Java-SDK-Version` should identify the SDK toolkit.
--
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: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Support Airflow-Bundle-Version JAR menifest metadata [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on issue #66454:
URL: https://github.com/apache/airflow/issues/66454#issuecomment-4514974805
We probably should have bundle version now since the JARs are currently deployed out-of-band from dag bundles. This should only be added when we have a good story on
* How do we handle dag versioning with task-only (no dependency) JARs?
* How does versioning work with Java-only dags (where a binary is deployed)?
Not sure is the SDK version metadata is needed (nothing really uses it now…? And if we want we can just inspect the JAR containing `org.apache.airflow.sdk`).
We should add `Airflow-Supervisor-Schema-Version`.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Support Airflow-Supervisor-Schema-Version JAR menifest metadata [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr commented on issue #66454:
URL: https://github.com/apache/airflow/issues/66454#issuecomment-4570601466
Added to #65956 and validated through integration test.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Support Airflow-Supervisor-Schema-Version JAR menifest metadata [airflow]
Posted by "uranusjr (via GitHub)" <gi...@apache.org>.
uranusjr closed issue #66454: Support Airflow-Supervisor-Schema-Version JAR menifest metadata
URL: https://github.com/apache/airflow/issues/66454
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Support Airflow-Bundle-Version JAR menifest metadata [airflow]
Posted by "jason810496 (via GitHub)" <gi...@apache.org>.
jason810496 commented on issue #66454:
URL: https://github.com/apache/airflow/issues/66454#issuecomment-4516643716
From my perspective, no matter what's the concrete idea looks like. The "version" should be decided by "server-side" (by Dag Processor, and by comparing the hash of `airflow-metadata` more specifically) instead of deciding on user side.
So I think we can get rid of `Airflow-Bundle-Version`.
Then the question will be how does Dag Versioning and Bundle Versioing works in Multi-Lang era.
> How do we handle dag versioning with task-only (no dependency) JARs?
If I understand correct, we mean "Multi-Lang Task" or "Python Stub Dag" here, right?
( We should align the term before the user-facing docs settle anyway )
We haven't support task versioning for stub operator. I don't have concrete idea for it now. It's likely a big design to discuss (e.g . introducing callback for dag-processing? When the Dag-processor realized this is a stub operator, it will launch coordinator to retrieve the multi-lang specific `airflow-metadata` and merge into the dag processing result. )
> How does versioning work with Java-only dags (where a binary is deployed)?
This one should be easier.
However, I feel we should change the coordinator configuration to respect the bundle to make it more feasible.
> We should add Airflow-Supervisor-Schema-Version.
That's true, I update the issue description to include it as well.
If we include `Airflow-Supervisor-Schema-Version` in the metadata, then the `Airflow-SDK-Verion` is not necessary.
--
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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org