Completely agree on B. On A I feel the necessity to centralize everything
in one place but also without losing the capabilities of Jira. I think we
will have to explore tools in eitherways.
Thanks,
Sudha
On Thu, Jul 15, 2021 at 10:42 PM vino yang wrote:
> +1 for option B.
>
> Best,
> Vino
>
>
+1 for option B.
Best,
Vino
Sivabalan 于2021年7月16日周五 上午10:35写道：
> +1 on B. Not sure on A though. I understand the intent to have all in
> one place. but not very sure if we can get all functionality (version,
> type, component, status, parent- child relation), etc ported over to
> github. I
I don't have much knowledge wrt catalog, but is there an option of
exploring spark catalog based table to create a hudi table? I do know with
spark3.2, you can add Distribution(a.k.a partitioning) and Sort order to
your table. But still not sure on custom transformation for indexing, etc.
Also,
+1 agree we don't have recipes for each feature as such. would benefit
users who are interested in a particular feature.
On Tue, Jul 6, 2021 at 2:17 AM Vinoth Chandar wrote:
> Hi Raymond,
>
> Are you suggesting a fix to the dev workflow or general site/quickstart
> docs?
>
> Agree, that the
+1 on B. Not sure on A though. I understand the intent to have all in
one place. but not very sure if we can get all functionality (version,
type, component, status, parent- child relation), etc ported over to
github. I assume labels are the only option we have to achieve these.
Probably, we
Hi, experts.
Currently, Hudi sql statements for DML are executed by Hive Driver with
concatenation SQL statements in most cases. The way SQL is concatenated is hard
to maintain and the code is easy to break. Other than that, multiple versions
of Hive cannot be supported at the moment and
