Re: Removal of "default" cache from REST APIs

2020-07-30 Thread Ilya Kasnacheev
Hello! It is only available for example node startup shipped with our examples. However, it is not available when you just start a node from a downloaded distribution. I concur that we should no longer rely on "default" cache. Regards, -- Ilya Kasnacheev ср, 22 июл. 2020 г. в 03:09, Saikat M

Re: Removal of "default" cache from REST APIs

2020-07-21 Thread Saikat Maitra
Hi Evgeniy, Can you please confirm in your configuration you have this example config file. https://github.com/apache/ignite/blob/master/examples/config/example-cache.xml#L26-L32 This has instructions on default cache config. My understanding is when node startup then the default cache should a

Re: Removal of "default" cache from REST APIs

2020-07-19 Thread Evgeniy Rudenko
Hi Saikat, I understand this, but as I wrote this is pointless. It is not safe fallback, because there is no "default" cache. If you will try to use any API without a name you will receive the following error: *org.apache.ignite.IgniteCheckedException: Failed to find cache for given cache name: d

Re: Removal of "default" cache from REST APIs

2020-07-18 Thread Saikat Maitra
Hi Evgeniy, The default cacheName is safe fallback when cache name is not provided in the request. It is part of rest document. https://apacheignite.readme.io/docs/rest-api#put When request do not have cacheName since it is optional param then this DFLT_CACHE_NAME is used https://github.com/apac

Removal of "default" cache from REST APIs

2020-07-15 Thread Evgeniy Rudenko
Hi guys, Most of the cache APIs are trying to use "default" cache when cacheName is not provided. This is pointless, because we don't have such cache by default. I would like to change that and just return "Failed to find mandatory parameter in request" error if name is absent. Please tell if you