Missing several DTRuntime calls in the DT service client

[BenCarter44]

The DT runtime has the .add_input() method, but the DT service client doesn't expose that method currently.

[BenCarter44]

Missing also .add_data_join()

[BenCarter44]

Updated missing list:

Missing add_barrier
Missing add_input
Missing add_data_join
Missing add_data_split_task

[andre-merzky]

add_input and add_data_join — the two verbs run_me_service.py calls — are on a PR. add_barrier and add_data_split_task stay open here:

• add_data_split_task is mechanical (Package pattern, like add_task), just has no consumer yet.
• add_barrier needs a wire decision first: Barrier.__init__ holds asyncio primitives (Condition, Semaphore), so a client-built instance must not cross the wire. Proposal: the verb carries a declarative spec (name, hard/soft, per-dtype flags), the service constructs the barrier, and the client computes the derived output dtypes locally (dtype if hard, WindowDataType(dtype, name) if soft — deterministic from the spec).

[BenCarter44]

Hello Andre, awesome!

Yes, the add_data_split_task() will be very similar to add_task(). I agree on the add_barrier being built on the service side.

I'll take a look at the PR.

[BenCarter44]

Also, I'm not fully sure if I understand what you mean by "no consumer yet" for the add_data_split_task()?

[BenCarter44]

It looks like add_input() isn't working yet...

The DT appears to hang.