[
https://issues.apache.org/jira/browse/IGNITE-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083320#comment-16083320
]
Roman Shtykh edited comment on IGNITE-5649 at 7/12/17 4:05 AM:
---------------------------------------------------------------
[~anovikov] Thanks for your suggestion!
Even if a job is sent to the nodes where {{cacheName}} exists,
{{GridCacheQueryManager#sqlMetadata}} picks the metadata of all caches in
{{GridCacheQueryManager.MetadataJob#call}}. Is my understanding correct?
I updated the solution without modifying {{GridCacheQueryManager#sqlMetadata}}
-- it filters meta data and leaves only one for the cache with the specified
name to return (tests are not updated yet). What do you think?
https://github.com/shroman/ignite/commits/IGNITE-5649
was (Author: roman_s):
[~anovikov] Thanks for your suggestion!
Even if a job is sent to the nodes where {{cacheName}} exists,
{{GridCacheQueryManager#sqlMetadata}} picks the metadata of all caches in
{{GridCacheQueryManager.MetadataJob#call}}. Is my understanding correct?
> 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)
