ilyasse05
ilyasse05
I think it's not secure to do it like that, the more secure will do it on resulat with select and after do a merge.
@MrPowers @brayanjuls Ah okay i indrestand the objectif, so i think it's better to rename the function to replicateTable() or cloneTable, the use case of this functionality is to clone...
@brayanjuls why not but i am not expert in scala langage. For columns, i think for performance, we have to keep the same columns from table source + technical column,...
@brayanjuls yes that exactly what we need to do, for the path we create the same table, with the same columns + technical columns like you suggested.