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
This has come up in ML workflows; see JuliaAI/MLJ.jl#915. Would TableOperations.jl be the appropriate place for this?
What I have in mind is a simple concatenation - not a fancy join. So, if a column name of table1 appears in table2, then the table2 column just gets added with its name modified.
The tricky part is deciding on what the return type should be. I don't have fixed ideas about this, but perhaps if the tables do have the same type, and that is a sink type, then that is also the return type.
Although it is not a part of the public API, I see that TableTransforms.jl has an implementation. (To get the final table, the type of the first table is materialized.):
This has come up in ML workflows; see JuliaAI/MLJ.jl#915. Would TableOperations.jl be the appropriate place for this?
What I have in mind is a simple concatenation - not a fancy join. So, if a column name of
table1
appears intable2
, then thetable2
column just gets added with its name modified.The tricky part is deciding on what the return type should be. I don't have fixed ideas about this, but perhaps if the tables do have the same type, and that is a sink type, then that is also the return type.
Although it is not a part of the public API, I see that TableTransforms.jl has an implementation. (To get the final table, the type of the first table is materialized.):
cc @ExpandingMan @juliohm
The text was updated successfully, but these errors were encountered: