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
With hive, you can create a table and point to the storage using location= or external_location=. If location= is used, the storage is deleted when the table is dropped (in hive or Presto). If you use external_location= with hive, and then drop the table, the objects for the table are left on the object store.
We will need to mimic this behavior. Currently, the S3 connector only supports tables created using 'external_location='. We need to also support 'location=' and delete the storage when those tables are dropped.
We should add this capability soon, since the intern summer project is creating tables on S3, and needs to be able to delete the storage when the tables are dropped.
The text was updated successfully, but these errors were encountered:
With hive, you can create a table and point to the storage using location= or external_location=. If location= is used, the storage is deleted when the table is dropped (in hive or Presto). If you use external_location= with hive, and then drop the table, the objects for the table are left on the object store.
We will need to mimic this behavior. Currently, the S3 connector only supports tables created using 'external_location='. We need to also support 'location=' and delete the storage when those tables are dropped.
We should add this capability soon, since the intern summer project is creating tables on S3, and needs to be able to delete the storage when the tables are dropped.
The text was updated successfully, but these errors were encountered: