Changes to rename()

[nvoxland-al]

🚀 🚀 Pull Request

Impact

• Optimization
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Previously, deeplake.rename() and dataset.rename() tried to rename both managed and unmanaged datasets.

• For managed datasets, it would change the URL to the dataset without impacting the underlying storage.
• For unmanaged datasets, it would move the storage location from one location to another. For storage systems that do not support "move" operations, it would copy and delete the data

This PR removes the "rename" support for non-managed datasets, to avoid confusion on whether it does anything to the underlying storage or not. It's now purely a way to rename the URLs of a managed (hub://) dataset.

It also adds the ability to just give the new name as the argument to rename rather than the whole new URL. So the new preferred syntax is: deeplake.rename("hub://my_org/old_path", "new_path" or dataset.rename("new_path"). In either case the new URL will be hub://my_org/new_path

Things to be aware of

That change does mean that you can't use deeplake.rename() to do a storage-level "move" anymore, but that was never the purpose of this method.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
15.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud