da-daken commented on issue #1016: URL: https://github.com/apache/flink-agents/issues/1016#issuecomment-5651968955
> In an earlier community meeting we reached a consensus: Java and Python differ in language characteristics — since Java methods are not first-class citizens, some natural Python usages require complex interface implementations in Java. We should respect Python's ergonomics, not force Python into a strict correspondence with Java, and instead keep the two sides semantically consistent. @pltbkd Thanks for the additional information. Adding args on the Java side would also be a fairly breaking change, so I propose removing args to keep the two languages consistent. From this perspective, keeping this inconsistency also seems to be expected. > outcomes = await ctx.durable_gather( > ctx.durable_execute_async(foo, x, durable_id="foo-x"), > ctx.durable_execute_async(bar, y, durable_id="bar-y"), > ) @wenjin272 Great proposal ! Unifying the structure of the Python-side API perfectly resolves the three issues raised by @pltbkd. I also agree that the unique ID should be used first, and that when no durable_id is provided, an automatically derived identifier should be used. This also applies only to the Python-side API; the Java-side API still uses the unique ID. I’m not sure whether my understanding is correct. -- 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]
