Ok, then can we replace dots in cache names only in metric names, and maybe in ignite 3.0 restrict all unwanted symbols directly to cache names?
вт, 15 сент. 2020 г. в 16:41, Nikolay Izhikov <nizhi...@apache.org>: > Hello, Alex. > > We can’t restrict dot in the cache name because it will break backward > compatibility of Ignite. > > > 15 сент. 2020 г., в 16:38, Alex Kozhenkov <wirtz...@gmail.com> > написал(а): > > > > Yeah, that would be even better for all cases. > > > > вт, 15 сент. 2020 г. в 15:51, Ilya Kasnacheev <ilya.kasnach...@gmail.com > >: > > > >> Hello! > >> > >> This seems suspiciously similar to > >> https://issues.apache.org/jira/browse/IGNITE-7264 > >> > >> Maybe we need to restrict cache names after all. > >> > >> Regards, > >> -- > >> Ilya Kasnacheev > >> > >> > >> вт, 15 сент. 2020 г. в 13:49, Alex Kozhenkov <wirtz...@gmail.com>: > >> > >>> Hi, guys! > >>> > >>> Cache names may contain dots, but in metic names we create hierarchy > with > >>> dots. > >>> So with the cache name "Person.statistic" we will have a metric > >>> "io.statistics.sortedIndexes.SQL_PUBLIC_Person.statistic._key_PK" which > >> is > >>> not obvious what is a cache name and what is next hierarchical element. > >>> > >>> I suggest replacing dots with the special symbol during metrics names > >>> construction. > >>> > >> > >
