Re: [I] Create `airflow.core.*` module structure for Server-client separation [airflow]
amoghrajesh commented on issue #51554: URL: https://github.com/apache/airflow/issues/51554#issuecomment-3844926656 As discussed on mailing list, this can happen only after client server separation is complete, ie: 3.3+ -- 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]
Re: [I] Create `airflow.core.*` module structure for Server-client separation [airflow]
amoghrajesh commented on issue #51554: URL: https://github.com/apache/airflow/issues/51554#issuecomment-3709040603 Self assigning this one, will pick it up soon. -- 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]
Re: [I] Create `airflow.core.*` module structure for Server-client separation [airflow]
rich7420 commented on issue #51554: URL: https://github.com/apache/airflow/issues/51554#issuecomment-3528361348 thanks! -- 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]
Re: [I] Create `airflow.core.*` module structure for Server-client separation [airflow]
potiuk commented on issue #51554: URL: https://github.com/apache/airflow/issues/51554#issuecomment-3528208805 Same here - this is more of a "meta-task" rather than task that can be easily accomplished. -- 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]
Re: [I] Create `airflow.core.*` module structure for Server-client separation [airflow]
rich7420 commented on issue #51554: URL: https://github.com/apache/airflow/issues/51554#issuecomment-3524927407 Could I try this? -- 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]
Re: [I] Create `airflow.core.*` module structure for Server-client separation [airflow]
AryanK1511 commented on issue #51554: URL: https://github.com/apache/airflow/issues/51554#issuecomment-2957272033 I would love to work on this one!! -- 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]
[I] Create `airflow.core.*` module structure for Server-client separation [airflow]
kaxil opened a new issue, #51554: URL: https://github.com/apache/airflow/issues/51554 Move the current server components under `airflow.core.*` module structure & namespace to establish clear boundaries for AIP-72 server-client separation to clearly mark server components. Example: - `airflow.models.*` → `airflow.core.models.*` - `airflow.jobs.*` → `airflow.core.jobs.*` - `airflow.executors.*` → `airflow.core.executors.*` - `airflow.api_fastapi.*` → `airflow.core.api.*` ## Success Criteria - All server components in `airflow.core.*` namespace - No internal code imports from old locations - All tests pass with new structure - Clear separation between server and shared components -- 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]
