Name collisions are possible in snapshot (.chunks, .component)

[vladsud]

Blob with this name

const chunksBlobName = ".chunks";

is written in the root of container runtime tree, thus in the same namespace as data stores.
If data store with such name is created, it will cause corruption of the tile.

We need to isolate namespace of special blobs and data stores.
I believe (need to check) same goes with .component blob and DDs.
Within DDSs I believe things are correct (as .attributes is not colliding with DDS blobs as they are under "content" sub-tree), but need to check

[vladsud]

Aldo for search results, we are adding .app//#search/ blobs
Need to reduce collisions with DDSs as well

[vladsud]

@arinwt, any chance you can help me here?
I believe we should revisit this layer.
First question - can blobs & trees have same name? That what would happen if someone called their DDS ".component".
But I believe answer might not be even interesting, as we want to separate them anyway. For example, we are adding support for search / alternative blobs at data store runtime layer, and we will add "search" tree under data store. This will collide with "search" DDS if such exists.
I believe our system should be flexible to allow such scenarios and clearly separate DDS sub-trees vs. root-level system trees/blobs in data store.
Backward compat is clearly an issue here, we should think about how to achieve it without breaking existing files (I have a feeling that having a feeling that easiest way to do so is to pivot based on snapshot version stored in .component blob and have two different paths in code).

[arinwt]

Closing this issue with PR #4485, because that PR allows for clients to read in the new format.
Opened another issue #4706 to track the work for writing in the new format. This must go in a release 2 versions later than the first to ensure compatibility requirements.