jason810496 commented on PR #65958:
URL: https://github.com/apache/airflow/pull/65958#issuecomment-4384732259
> I wonder if this could be `apache-airflow-coordinator-java` as the PyPI
package name, and `airflow.coordinator.java.*` as the module names?
>
> I haven't been following exactly, but it's just imported as a class name
right?
There're several thoughts come to my mind with this direction.
Could you deliberate more on it when you have a moment? @ashb
**a) Regarding the public interface for Airflow-Core / TaskSDK to interact
with Coordinator:**
1. Using existing `ProvidersManager`
2. Introduce new `CoordinaterManager` (probably live in `_shared` lib as
both Airflow-Core and TaskSDK required it)
**b) Regarding the module structure:**
1. Is it just name of smaller subset of "provider" (or a new provider type
as @jscheffl said) but the coordinator implementations (subclasses) still live
in `providers/` (like what @uranusjr said)
```
airflow-core/
task-sdk/
providers/
├── airbyte
├── akeyless
├── ...
├── coordinators/
├── executable
├── java
```
2. The coordinator implementations (subclasses) will live in a new
`coordinators` folder
```
airflow-core/
coordinators/
task-sdk/
providers/
```
--
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]
