Ivan,
I also don't think this issue is a blocker for 2.8 as it affects only
experimental functionality and only in special cases.
Removing key length limitations in MetaStorage seems more strategic
approach to me but depending on how we decide to approach it (as a local
fix or as part of a
Ivan,
This issue doesn't seem to be a blocker for 2.8 release from my point of view.
I think we definitely will have such bugs in future and 2.8.1 is our
goal for them.
Please, let me know if we should wait for the fix and include it exactly in 2.8.
On Fri, 28 Feb 2020 at 15:40, Nikolay
Igniters,
I think we can replace cache name with the cache id.
This should solve issue with the length limitation.
What do you think?
> 28 февр. 2020 г., в 15:32, Ivan Bessonov написал(а):
>
> Hello Igniters,
>
> we have an issue in master branch and in the upcoming 2.8 release that
>
Hello Igniters,
we have an issue in master branch and in the upcoming 2.8 release that
related to new metrics functionality implemented in [1]. You can't use new
"configureHistogramMetric" and "configureHitRateMetric" configuration
methods on caches with long names. My estimation shows that cache
