[ 
https://issues.apache.org/jira/browse/IGNITE-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-3345:
----------------------------------------

    Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Please test improved REST for put/get operations.

Added support for "keyType" and "valueType" params.

Supported Java built in types + IgniteUuid:

boolean, byte, short, int, long, float, double,

java.sql.Date, java.sql.Time, java.sql.Timestamp,

java.util.UUID, org.apache.ignite.lang.IgniteUuid

 

To test: execute in browser:

{{http://host:port/ignite?cmd=put&cacheName=testCache&keyType=long&key=11111&valueType=long&val=22222}}

> 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)

Reply via email to