You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2020/09/18 08:23:00 UTC

[jira] [Updated] (IGNITE-12977) Document the ability to add non-primitive objects via REST.

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

Pavel Pereslegin updated IGNITE-12977:
--------------------------------------
    Attachment: restapi-short-before.png
                restapi-short-after.png

> Document the ability to add non-primitive objects via REST.
> -----------------------------------------------------------
>
>                 Key: IGNITE-12977
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12977
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation, rest
>            Reporter: Pavel Pereslegin
>            Assignee: Pavel Pereslegin
>            Priority: Major
>             Fix For: 2.9
>
>         Attachments: restapi-short-after.png, restapi-short-before.png
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> [https://apacheignite.readme.io/docs/rest-api]
> [Data types]
> The REST API also supports custom types.
>  For such objects, the JSON format is used.
> If the type name is a Java class that is available on the server, the fields will be stored according to the definition of the Java class.
>  If the type name is a query entity type, the fields will be stored according to the type of field defined in the query entity.
>  If the type name is a different type, the fields will be stored according to regular JSON types.
> [Sql query execute]
>  [Sql fields query execute]
>  [Scan query execute]
> Request parameters 
>  keepBinary | boolean | yes | do not deserialize [binary objects|https://apacheignite.readme.io/docs/binary-marshaller], _false_ by default



--
This message was sent by Atlassian Jira
(v8.3.4#803005)