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
{{ message }}
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.
When the Configurator is set to debug, maybe it would be advantaveous to not create hive-table entries.
So when the Configurator is in debug, AND a table is marked as format:delta in yaml, then return a name of the format
delta.`path`
Then a user has the following possiblity:
If the paths are set up like /{MNT}/{ID}/myDB/myTable, Then is no hive tables are set up, the user can quickly erase the temporary tables like dbutils.fs.rm('/tmp/<ID here>',True). SQL CREATE TABLE statements still work with such delta names. The user just has to make sure to move database creation to another sql that is then maybe not executed in the tests.
Since this feature changes existing behavior, maybe it should be opt-in with a flag Configurator().enable_path_based_debug_delta_names()
The text was updated successfully, but these errors were encountered:
When the Configurator is set to debug, maybe it would be advantaveous to not create hive-table entries.
So when the Configurator is in debug, AND a table is marked as format:delta in yaml, then return a name of the format
Then a user has the following possiblity:
If the paths are set up like
/{MNT}/{ID}/myDB/myTable
, Then is no hive tables are set up, the user can quickly erase the temporary tables likedbutils.fs.rm('/tmp/<ID here>',True)
. SQLCREATE TABLE
statements still work with such delta names. The user just has to make sure to move database creation to another sql that is then maybe not executed in the tests.Since this feature changes existing behavior, maybe it should be opt-in with a flag
Configurator().enable_path_based_debug_delta_names()
The text was updated successfully, but these errors were encountered: