You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very interesting if h2o could have a syntax to chain transformation stages based on the use of pipes, equivalent to the one that already exists in R with dplyr, recently exported to Julia with tidier.jl. Within Python there are already alternatives such as datar and tidypolars. Not to mention that for BigData, sparklyr also uses this approach.
All these approaches resemble each other, allowing the use of different languages in a simpler way. The advantages of readability, maintainability of code based on this syntax is what is leading to the emergence of these cross-language equivalences.
I believe that this syntax would give an extra advantage to h2o to be able to encapsulate transformations or pipelines that further facilitate its implementation in production as well as making easier its learning and adoption.
Hi,
It would be very interesting if
h2o
could have a syntax to chain transformation stages based on the use ofpipes
, equivalent to the one that already exists in R withdplyr
, recently exported to Julia withtidier.jl
. Within Python there are already alternatives such asdatar
andtidypolars
. Not to mention that for BigData,sparklyr
also uses this approach.All these approaches resemble each other, allowing the use of different languages in a simpler way. The advantages of readability, maintainability of code based on this syntax is what is leading to the emergence of these cross-language equivalences.
I believe that this syntax would give an extra advantage to
h2o
to be able to encapsulate transformations or pipelines that further facilitate its implementation in production as well as making easier its learning and adoption.Thank you very much,
Carlos.
The text was updated successfully, but these errors were encountered: