You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Saikat Maitra (JIRA)" <ji...@apache.org> on 2016/09/04 17:50:20 UTC

[jira] [Commented] (IGNITE-1242) HTTP REST node command required id for client node

    [ https://issues.apache.org/jira/browse/IGNITE-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15463261#comment-15463261 ] 

Saikat Maitra commented on IGNITE-1242:
---------------------------------------

[~skozlov]

Hi Sergey

I have validated the service for below 3 usecases.

1. Absence of ip or id.

http://localhost:8080/ignite?cmd=node&attr=true&mtr=true

{code}
{
successStatus: 1,
error: "Failed to handle request (either id or ip should be specified).",
response: null,
sessionToken: ""
}
{code}

2. If id is passed.

http://localhost:8080/ignite?cmd=node&attr=true&mtr=true&id=3826552a-da0c-4493-a637-f267071d2c84

In this case I am getting proper response with complete node information.

3. If ip is passed.

http://localhost:8080/ignite?cmd=node&attr=true&mtr=true&ip=127.0.0.1

In this case I am getting proper response with complete node information.

Please let me know if I have missed any usecase in validation.

Regards
Saikat



> HTTP REST node command required id for client node
> --------------------------------------------------
>
>                 Key: IGNITE-1242
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1242
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: ignite-1.4
>            Reporter: Sergey Kozlov
>            Assignee: Saikat Maitra
>            Priority: Minor
>
> HTTP REST node command requires node id for a client node though that parameter is optional.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)