Re: [hibernate-dev] 5.3 cache issues [Requires Steve]
1) That was specifically requested
2) This is easily handled by the providers, if they wish. They would
simply map any undefined regions/caches to a pre-defined one (probably
after warning the user). Keep in mind that region != cache. A provider
might map multiple region names to a single cache. That was always the
case, but every provider mapped region <-> cache as 1-1 - the new API makes
this much more clear.
Personally I think that not allowing on-the-fly creation is a good idea,
though maybe it can be made configurable.
On Mon, Jul 2, 2018 at 11:18 AM Guillaume Smet <guillaume.smet(a)gmail.com>
wrote:
Hi Steve,
Glad to have you back! Hope yo got some rest.
On Mon, Jul 2, 2018 at 5:28 PM Steve Ebersole <steve(a)hibernate.org> wrote:
> Overall what I would suggest is a hybrid approach where we move to a
> "short name" solution much like we have for most other config values. So,
> e.g., the name of the default query result region would be
> `default-query-result-region`. We could then have the providers understand
> that "magic value" and have them look for configs under either names they
> wish (temporarily which Emmanuel suggested, if that's what we want) - we'd
> change our OOTB providers to look for all three names.
>
Sounds like something we could do, given we implement the compatibility
layer. We would need a new release of the Infinispan region factory to
provide the compatibility layer there.
Any comment on the first issue (the new requirement to declare all the
caches)?
--
Guillaume