Description
Current FileGAVNameMapper "mimics" loosely local reposiory layout, uses long paths, hence (relatively) big strings etc.
More compact layout would be just to hash strings like "a:G:A:V" and "m:G[:A[:V]]" for artifacts and metadata instead, and create 2 level deep hashed storage.
Problem with "loose" layout is that they do end up as files in OS, while these would be much shorter.
Attachments
Issue Links
- links to