You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2017/05/05 12:51:04 UTC
[jira] [Commented] (IGNITE-4043) Visor CMD: cache scan - support
execution on selected node only
[ https://issues.apache.org/jira/browse/IGNITE-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998286#comment-15998286 ]
Alexey Kuznetsov commented on IGNITE-4043:
------------------------------------------
Hi, [~rishi007bansod],
First, please make sure that you are fixing this issue making a branch from latest master (in ignite 2.0 we changed scan command a bit).
Seconf, to my mind, all you need - is a check that if user specify -scan and -id8 options then set in param {{local}} of {{VisorScanQueryTaskArg}} in line 141 of {{VisorCacheScanCommand}} to {{true}}. And as you mentioned in your comment instead of {{executeRandom}} you should use {{executeOne}}. But it will be cool if instead of "java-like-way style" {{if scanArgId.isDefined then}} you will use "scala-way" like {{scanArgId match ...}}.
Thanks.
> Visor CMD: cache scan - support execution on selected node only
> ---------------------------------------------------------------
>
> Key: IGNITE-4043
> URL: https://issues.apache.org/jira/browse/IGNITE-4043
> Project: Ignite
> Issue Type: Task
> Components: wizards
> Affects Versions: 1.7
> Reporter: Alexey Kuznetsov
> Assignee: RISHIKESH BANSOD
> Fix For: 2.1
>
>
> See: http://stackoverflow.com/questions/39887651/get-cache-entrieskeys-values-list-on-particular-node-in-apache-ignite#
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)