How about using both escaping and a text file with the name? One can think of the escaped name as of a kind of ID, which happens to be human-readable when the name is in ASCII, and as unreadable as an UUID when the name is in UTF. This way we have all the readability in the common case (when name is all English letters and digits), and some limited readability (via looking into text files) when other alphabets are used.
Thanks, Stan From: Pavel Tupitsyn Sent: 16 января 2018 г. 14:01 To: dev@ignite.apache.org Subject: Re: Handling slashes in cache names > folder named by ID and txt file inside should do the trick Agree On Tue, Jan 16, 2018 at 1:02 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > On Mon, Jan 15, 2018 at 7:31 AM, Pavel Tupitsyn <ptupit...@apache.org> > wrote: > > > > You will never ever relate smth like "fdee0456adcc" to "мои_данные". > > > > As a user, why do I need to understand file names in Ignite work > directory? > > > > Because it is better to have an understandable and human readable directory > structure than not. Let's do it right. >
