ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Konstantinov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3345) Implement support for optional key type in REST HTTP get command
Date Mon, 19 Feb 2018 08:05:00 GMT

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

Pavel Konstantinov commented on IGNITE-3345:
--------------------------------------------

Successful in general but in some case error is empty in response although the node console
had an error

> Implement support for optional key type in REST HTTP get command
> ----------------------------------------------------------------
>
>                 Key: IGNITE-3345
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3345
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, rest
>    Affects Versions: 1.6
>            Reporter: Alexey Kuznetsov
>            Assignee: Pavel Konstantinov
>            Priority: Major
>             Fix For: 2.5
>
>
> It seems that in current implementation (https://apacheignite.readme.io/docs/rest-api#get)
> GET command could work only with String keys.
> We can add optional parameter "keyType" and implement support for common built-in types
such as Integer, Long, UUID,... and user classes that a valid JavaBeans.
> Sample: http://host:port/ignite?cmd=get&key=1&cacheName=myCache&keyType=Long



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message