On Wed, Oct 6, 2021 at 3:59 PM Pablo Estrada <pabl...@google.com> wrote:
> Thanks Heejong! > > Can you show an example of how a user would define the dependencies of > their transform? > This creates two copies of the dependencies, right? (one copy in the Maven > / Gradle file, and another copy in the Java definition of the > ExternalTransform, correct?) - is there a way to keep these up to date > somehow? Perhaps - at least - users could have the possibility of not > passing the version of the artifact - and the version could be fetched from > the classpath? > Best > I believe the target is to extend the cross-language API (ExternalTransformBuilder) so that required dependencies can be specified (as a list of local paths) when registering such transforms in the expansion service. Such jars do not necessarily have to be added to Beam. We will also provide utility functions to easily use jars available in a remote Maven repository. Thanks, Cham > -P. > > On Wed, Oct 6, 2021 at 3:40 PM Heejong Lee <heej...@google.com> wrote: > >> Hi, >> >> I would like to implement artifact registration for Java expansion >> service. Since the plan includes small API changes, I'm sharing the >> overview documentation and PR with the dev mailing list first before moving >> forward. Please feel free to leave any comments. >> >> Doc: >> https://docs.google.com/document/d/1Wi8IMHFT54T274ybkbek79s_RGKa2X2zY-LVOR_RMNM/edit?usp=sharing >> PR: https://github.com/apache/beam/pull/15606 >> >> Thanks, >> >
