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://github.com/samaitra/ignite IGNITE-3337
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/816.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #816
----
commit ab37ea39cc862338b09bb82d99a34e64ada1f1a5
Author: samaitra <
[hidden email]>
Date: 2016-06-19T12:44:49Z
IGNITE-3337 REST HTTP: metadata command returns all caches even if a cache name is passed to request
commit d0fd29ffb06c3fe46232221ed3e07c4ab5cceb89
Author: samaitra <
[hidden email]>
Date: 2016-06-19T15:19:17Z
IGNITE-3337 REST HTTP: metadata command returns all caches even if a cache name is passed to request
commit 3543270900331dd10beee8140dff6bbd4a21f700
Author: samaitra <
[hidden email]>
Date: 2016-06-19T15:20:41Z
IGNITE-3337 REST HTTP: metadata command returns all caches even if a cache name is passed to request
----
---
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 enabled but not working, please
contact infrastructure at
[hidden email] or file a JIRA ticket
with INFRA.
---