[jira] [Commented] (IGNITE-3345) Implement support for optional key type in REST HTTP get command

["Sergey Dorozhkin (JIRA)" <ji...@apache.org>]

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

Sergey Dorozhkin commented on IGNITE-3345:
------------------------------------------

1. What built-in data types should I use? In the ticket I see Integer, Long and UUID. What about Double, Float? May be something else?
2. If key datatype incompatible with keyType, should I throws exception or ignore it and use String?
3. Should I use fully qualified class name for keyType or try to search class by simple name?

> 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
>    Affects Versions: 1.6
>            Reporter: Alexey Kuznetsov
>            Assignee: Sergey Dorozhkin
>
> 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
(v6.4.14#64029)