it would be great if we establish this. I know in Hive these temporary tables "CREATE TEMPRARY TABLE ..." are private to the session and are put in a hidden staging directory as below
/user/hive/warehouse/.hive-staging_hive_2016-07-10_22-58-47_319_5605745346163312826-10 and removed when the session ends or table is dropped Not sure how Spark handles this. HTH Dr Mich Talebzadeh LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>* http://talebzadehmich.wordpress.com *Disclaimer:* Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction. On 1 November 2016 at 10:50, Michael David Pedersen < michael.d.peder...@googlemail.com> wrote: > Thanks for the link, I hadn't come across this. > > According to https://forums.databricks.com/questions/400/what-is-the-diff >> erence-between-registertemptable-a.html >> >> and I quote >> >> "registerTempTable() >> >> registerTempTable() creates an in-memory table that is scoped to the >> cluster in which it was created. The data is stored using Hive's >> highly-optimized, in-memory columnar format." >> > But then the last post in the thread corrects this, saying: > "registerTempTable does not create a 'cached' in-memory table, but rather > an alias or a reference to the DataFrame. It's akin to a pointer in C/C++ > or a reference in Java". > > So - probably need to dig into the sources to get more clarity on this. > > Cheers, > Michael >
