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
Currently we enforce a limit of 256 chars for the total length of URIs, which was originally intended to improve cross-filesystem compatibility.
However, this is a fairly restrictive limit and ultimately I don't think it should be TileDB's responsibility to enforce this: the limit should depend on and be enforced by the underlying filesystem/object store. Instead, we should allow long URIs internally, and properly propagate any underlying filesystem errors. E.g. on ext4 when creating a filename that is too long:
ubuntu@ip-172-31-35-56:~$ touch xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ubuntu@ip-172-31-35-56:~$ touch yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
touch: cannot touch 'yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy': File name too long
we should just propagate the File name too long message on our error path.
The text was updated successfully, but these errors were encountered:
Currently we enforce a limit of 256 chars for the total length of URIs, which was originally intended to improve cross-filesystem compatibility.
However, this is a fairly restrictive limit and ultimately I don't think it should be TileDB's responsibility to enforce this: the limit should depend on and be enforced by the underlying filesystem/object store. Instead, we should allow long URIs internally, and properly propagate any underlying filesystem errors. E.g. on
ext4
when creating a filename that is too long:we should just propagate the
File name too long
message on our error path.The text was updated successfully, but these errors were encountered: