Done: Implement support for optional key type in REST HTTP get command https://issues.apache.org/jira/browse/IGNITE-3345
On Tue, Jun 21, 2016 at 8:13 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > I also like the idea. Should we file a ticket? > > On Mon, Jun 20, 2016 at 3:31 AM, Sergey Kozlov <skoz...@gridgain.com> > wrote: > > > Hi Alexey. > > > > It's a good idea! Now I'm facing the issue when load the data via java > code > > (Long, Person) but REST Get/GetAll returns null for loaded keys. I > suppose > > that the reason is wrong mapping of the key passed to REST command. > > > > On Mon, Jun 20, 2016 at 1:20 PM, Alexey Kuznetsov < > akuznet...@gridgain.com > > > > > wrote: > > > > > Hi, All! > > > > > > It seems that in current implementation ( > > > https://apacheignite.readme.io/docs/rest-api#get) > > > GET command could work only with String keys. > > > > > > How about to 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 > > > > > > Thoughts? > > > > > > -- > > > Alexey Kuznetsov > > > > > > > > > > > -- > > Sergey Kozlov > > GridGain Systems > > www.gridgain.com > > > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
