[
https://issues.apache.org/jira/browse/IGNITE-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666111#comment-16666111
]
ASF GitHub Bot commented on IGNITE-10031:
-----------------------------------------
GitHub user akuznetsov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/5095
IGNITE-10031 REST: Added "excludeCaches" parameter for "top" command.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10031
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5095.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5095
----
commit e13c5f6d8b8d11d2a84dc00c1fe8aeff8e450313
Author: Alexey Kuznetsov <akuznetsov@...>
Date: 2018-10-27T14:47:26Z
IGNITE-10031 REST: Added "excludeCaches" parameter for "top" command.
----
> REST: Introduce "caches" param for "top" command.
> -------------------------------------------------
>
> Key: IGNITE-10031
> URL: https://issues.apache.org/jira/browse/IGNITE-10031
> Project: Ignite
> Issue Type: Improvement
> Components: rest
> Reporter: Alexey Kuznetsov
> Assignee: Alexey Kuznetsov
> Priority: Major
> Fix For: 2.8
>
>
> We have top command on REST API:
> https://apacheignite.readme.io/docs/rest-api#topology
> And result of this command also contains short caches info (name, mode & SQL
> Schema).
> But in situation when node contains thousand caches and hundred nodes and
> caches have long names - that will result in a HUGE JSON.
> For example, I get 88Mb JSON for cluster of 128 nodes and 6000 caches.
> And my application do not need that info about caches, I just need a list of
> node IDs.
> Lets add one more flag "excludeCaches" as we already have "attr" & "mtr".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
