[ASTERIXDB-2841] Storage incompatibilities with created entities

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.9.6
• Fix Version/s: 0.9.7
• Component/s: *DB - AsterixDB, STO - Storage
• Assignee: Michael Blow
• Reporter: Michael Blow
• Created: 04/Mar/21 21:30
• Updated: 06/Mar/21 16:57
• Resolved: 05/Mar/21 13:37

Description

Currently there are multiple ways in which created entities conflict with storage:

• Most filesystems have 255 byte or character limit per path segment, for multipart dataverses we can greatly exceed this limit, and currently multipart dataverses are represented using canonical form into a single path element
• Index names can be 255 bytes long, which result in corresponding files exceeding the path limit on most file systems
• Dataverse / dataset / index names can contain characters which are illegal on the filesystem, e.g. \ and / on Windows, NUL (\u0000) on Linux