[
https://issues.apache.org/jira/browse/IGNITE-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081830#comment-16081830
]
Andrey Novikov commented on IGNITE-5649:
----------------------------------------
Hi [~roman_s],
As I remember in Ignite 1.x we can create cache with name = null (default) In
this case we can't detect return metadata for all caches or for cache with
default name.
Metadata cache with {{cacheName}} should be returned first in list
In Ignite 2.x cache with name = null (default) was removed and we can return
metadata for specified {{cacheName}}
I reviewed changes in https://github.com/shroman/ignite/tree/IGNITE-5649 and I
think it is not good idea to change {{GridCacheQueryManager#sqlMetadata}} will
be better send job on node where cache with {{cacheName}} exists
{{GridCacheCommandHandler.MetadataTask#map}} and return its metadata or error
in {{GridCacheCommandHandler.MetadataTask#reduce}}
> REST API, metadata command always returns list of cache
> -------------------------------------------------------
>
> Key: IGNITE-5649
> URL: https://issues.apache.org/jira/browse/IGNITE-5649
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Aleksandr
> Assignee: Roman Shtykh
>
> How to reproduce:
> 1) start Ignite server with example config with Person and Organization.
> 2) run:
> curl http://localhost:8080/ignite?cmd=metadata&cacheName=Person
> curl http://localhost:8080/ignite?cmd=metadata&cacheName=Organization
> curl http://localhost:8080/ignite?cmd=metadata&cacheName=blablabla
> Ignite always returns list of cache instead of information about selected
> cache or error
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
