Re: IGNITE-3337

2016-06-29 Thread Saikat Maitra
gt; >> > > > get "default" cache (with name=null) > > >> > > > And now it will be impossible to take metadata for such cache. > > >> > > > > > >> > > > But I think for this command there is a little sense to extract &

Re: IGNITE-3337

2016-06-29 Thread Andrey Novikov
single cache, > >> > > > because any way on server side they will be extracted for all > >> caches. > >> > > > See: > >> > > > > >> > > > >> > > >> > org.apache.ignite.internal.processors.c

[GitHub] ignite pull request #816: IGNITE-3337 REST HTTP: metadata command returns al...

2016-06-29 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/816 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: IGNITE-3337

2016-06-28 Thread Saikat Maitra
; > for single cache, >> > > > because any way on server side they will be extracted for all >> caches. >> > > > See: >> > > > >> > > >> > >> org.apache.ignite.internal.processors.cache.quer

Re: IGNITE-3337

2016-06-23 Thread Saikat Maitra
t; > > > org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager#sqlMetadata > > > > line 999. > > > > > > > > Also for performance reason it is much faster to get all metadata at > > > once. > > &

Re: IGNITE-3337

2016-06-23 Thread Andrey Novikov
; > > Also for performance reason it is much faster to get all metadata at > > once. > > > > > > So, I suggest - to deprecate "cacheName" parameter and fix > documentation. > > > > > > Thoughts? > >

Re: IGNITE-3337

2016-06-20 Thread Saikat Maitra
> once. > > > > So, I suggest - to deprecate "cacheName" parameter and fix documentation. > > > > Thoughts? > > > > > > On Sun, Jun 19, 2016 at 10:42 PM, Saikat Maitra > > > wrote: > > > > > Hello,

Re: IGNITE-3337

2016-06-20 Thread Sergey Kozlov
or the following Jira ticket[2]. > > > > Please review and let me know any feedback > > > > Regards > > Saikat > > > > [1] https://github.com/apache/ignite/pull/816 > > [2] https://issues.apache.org/jira/browse/IGNITE-3337 > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > -- Sergey Kozlov GridGain Systems www.gridgain.com

Re: IGNITE-3337

2016-06-20 Thread Alexey Kuznetsov
Please review and let me know any feedback > > Regards > Saikat > > [1] https://github.com/apache/ignite/pull/816 > [2] https://issues.apache.org/jira/browse/IGNITE-3337 > -- Alexey Kuznetsov GridGain Systems www.gridgain.com

IGNITE-3337

2016-06-19 Thread Saikat Maitra
Hello, I have raised the PR[1] for the following Jira ticket[2]. Please review and let me know any feedback Regards Saikat [1] https://github.com/apache/ignite/pull/816 [2] https://issues.apache.org/jira/browse/IGNITE-3337

[GitHub] ignite pull request #816: IGNITE-3337 REST HTTP: metadata command returns al...

2016-06-19 Thread samaitra
GitHub user samaitra opened a pull request: https://github.com/apache/ignite/pull/816 IGNITE-3337 REST HTTP: metadata command returns all caches even if a cache name is passed to request You can merge this pull request into a Git repository by running: $ git pull https

[jira] [Created] (IGNITE-3337) REST HTTP: metadata command returns all caches even if cache name is passed to request

2016-06-17 Thread Sergey Kozlov (JIRA)
Sergey Kozlov created IGNITE-3337: - Summary: REST HTTP: metadata command returns all caches even if cache name is passed to request Key: IGNITE-3337 URL: https://issues.apache.org/jira/browse/IGNITE-3337