Hi Sir Quick clarification on Shallow Clone : If I run any query on top of cloned table , since it does not have any physical data then how come it will gives you the result. My internal understanding is -> It is pointing out to latest version of source table, so that the results will be coming from there. (please correct me if I'm wrong).
'emp_dc' 👥 is the deep clone of 'emp' 👤, copying both metadata and data. The folder of 'emp_dc' 👥 on Azure has both data files and log files, which were copied from the folder of 'emp' 👤. But when being first created, 'emp_dc' 👥 started from version_0, which corresponded to version_4 of 'emp' 👤. ❓ So I have a question: Is that possible for 'emp_dc' 👥 to go back to any previous version (e.g. version_3) of 'emp' 👤? (And if not, what is the point of copying both data files and log files from the original table?) 🙏 Hope you will clarify well this issue for me and the other people with the same concern.
Deep Clone doesn't copy the history from the source table (no log files/ history data files). It copies only the table metadata (table ddl, nullability, partitions, stream metadata etc.) and data as of the version on which it was created. You can create deep clone from any earlier version of source as well with the below command: CREATE TABLE target_table DEEP CLONE source_table VERSION AS OF version; The 4 files that you see in example being created as part of Deep clone are of the latest data (data is with 4 partitions thus 4 files). And you cannot go back in history on the cloned table.
Thumbs up from Brazil!
best playlist on databricks ever !
Please make sure to share with your network over LinkedIn ❤️
Very informative 😊
If you like my content, Please make sure to share with your network over LinkedIn 👍
excellent content
If you like my content, Please make sure to share with your network over LinkedIn 👍
Hi Sir
Quick clarification on Shallow Clone :
If I run any query on top of cloned table , since it does not have any physical data then how come it will gives you the result.
My internal understanding is -> It is pointing out to latest version of source table, so that the results will be coming from there.
(please correct me if I'm wrong).
'emp_dc' 👥 is the deep clone of 'emp' 👤, copying both metadata and data. The folder of 'emp_dc' 👥 on Azure has both data files and log files, which were copied from the folder of 'emp' 👤.
But when being first created, 'emp_dc' 👥 started from version_0, which corresponded to version_4 of 'emp' 👤.
❓ So I have a question: Is that possible for 'emp_dc' 👥 to go back to any previous version (e.g. version_3) of 'emp' 👤?
(And if not, what is the point of copying both data files and log files from the original table?)
🙏 Hope you will clarify well this issue for me and the other people with the same concern.
Deep Clone doesn't copy the history from the source table (no log files/ history data files). It copies only the table metadata (table ddl, nullability, partitions, stream metadata etc.) and data as of the version on which it was created.
You can create deep clone from any earlier version of source as well with the below command:
CREATE TABLE target_table DEEP CLONE source_table VERSION AS OF version;
The 4 files that you see in example being created as part of Deep clone are of the latest data (data is with 4 partitions thus 4 files).
And you cannot go back in history on the cloned table.
I'm totally clear now. Thanks, Subham!
@@jeremine9259 Thanks 👍 If you like my content, Please make share with your network over LinkedIn ❤
thanks sir
Thank you ❤️ Please make sure to share with your network over LinkedIn 👍
Hi Subham, Good Evening!! Could you please upload this playlist Notebook scripts If you have in Github and share us the repo? Thanks Much Again!!
Sure, will add them in Github and share the link.
If you like my content, Please make sure to share with your network over LinkedIn 👍
@@easewithdata Sure!! i have already recommended to my peers :)