I think it's not enough to define key type for get/getAll only. Same
defintion needs other commands that modify the data on cache.
I updated the filed ticket.
On Tue, Jun 21, 2016 at 5:06 AM, Alexey Kuznetsov
wrote:
> Done:
> Implement support for optional key type in REST HTTP get command
> ht
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
wrote:
> I also like the idea. Should we file a ticket?
>
> On Mon, Jun 20, 2016 at 3:31 AM, Sergey Kozlov
> wrote:
>
> > H
I also like the idea. Should we file a ticket?
On Mon, Jun 20, 2016 at 3:31 AM, Sergey Kozlov 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 wron
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
wrote:
> Hi, Al
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
