Ahmed Abualsaud
Ahmed Abualsaud
> you could consider extracting the portion that generates the yaml Makes sense to have the gradle command only generate the config. Then each remote SDK can have its own...
@tvalentyn this is already the case, the steps are in different functions. e.g. we're only importing `apache_beam` when using the function to generate transform configs. But this function is unusable...
The newly added precommit that performs a transform config sync check (beam_PreCommit_Xlang_Generated_Transforms) is running green on my fork: https://github.com/ahmedabu98/beam/actions/runs/7933231703/ Will merge after current tests pass
@theshanbhag tagging for visibility
Thanks! Is there a timeline we can follow for this feature? Also, are there any workarounds someone can implement in the meantime?
Thanks @bvolpato and @theshanbhag, I'm looking through #523 and I'm not sure if the problem mentioned in this issue is solved yet. Support for getting TableSchema after invoking a UDF...
Hmmm, does UDF support possibly allow for a workaround? Is there a way this can be utilized to rearrange a MongoDB collection such that the Document with the most columns...
Is there a plan to support this on the utils side instead? It would makes sense to not burden the user with writing the logic of setting a reliable TableSchema.
@reuvenlax agreed. pranav and I decided to just expose a parameter to configure the datetime pattern