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: default* Better to replace it by the correctly formed error message that will point to the actual problem of the request. API documents will be updated accordingly when PR will be merged. On Sun, Jul 19, 2020 at 12:56 AM Saikat Maitra <saikat.mai...@gmail.com> wrote: > 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/apache/ignite/pull/8041/files#diff-a3477d5e0cfdfcceed3371fc899a9d15L30 > > Regards, > Saikat > > On Wed, Jul 15, 2020 at 10:43 PM Evgeniy Rudenko <e.a.rude...@gmail.com> > wrote: > > > 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 have any concerns. Update can be found at > > https://github.com/apache/ignite/pull/8041 > > > > -- > > Best regards, > > Evgeniy > > > -- Best regards, Evgeniy
