Jira Atlas-230 is created asking for detail documentation/samples of REST API.
At meanwhile, can someone help provide some insights on how to create an entity
through REST API? supposedly the POST method of http:…/api/atlas/entities will
do the job, however, I couldn’t make it work:
class definition:
{
"typeName”:”BusinessMetadata",
"attributeDefinitions":[
{
"name”:”Category",
"dataTypeName”:”string",
…
},
...
]
}
JSON passed to the REST API:
{
"typeName":"BusinessMetaData",
"values":{
"category":"MiddleOffice",
…..
}
}
this results with exceptions “Unable to persist entity instance
(EntityResource:112) java.lang.IllegalArgumentException: Unable to deserialize
son”
Thanks
Herman.
> On Oct 13, 2015, at 8:02 PM, Seetharam Venkatesh <venkat...@innerzeal.com>
> wrote:
>
> Agreed that Atlas is quite thin on documentation. Please open a jira and we
> will try to add more documentation.
>
> Let me clarify about the APIs.
>
> There are 2 parts to Atlas,
>
> 1. Data Models aka Types that are expressed using the flexible type system
> API
> The type and entity (typed instances) are Data Models expressed using the
> type system API - think of it like POJO. We provide a wrapper to serialize
> the data models as JSON to make it easy to send it over the wire.
>
> 2. APIs to add data models and associated instances
> These APIs are RESTful - more akin to CRUD operations.
>
> Does things make sense now?
>
> On Tue, Oct 13, 2015 at 2:12 PM Herman Yu <herman...@teeupdata.com> wrote:
>
>> The challenge (at least for me) is there is no detail documentation of
>> REST API, e.g. I still can’t create new entities through REST API so has to
>> code in Java as the client does. I followed the same son structure as
>> traced out from log, but still get exceptions complaining either unknown
>> token or error deserialize json.
>>
>> Thanks
>> Herman.
>>
>>
>>> On Oct 13, 2015, at 4:48 PM, Seetharam Venkatesh <
>> venkat...@innerzeal.com> wrote:
>>>
>>> The java client is a thin wrapper over the REST api and is provided for
>>> convenience. The intent was to provide a CLI based on this wrapper and is
>>> yet to be worked upon.
>>>
>>> I agree with you that folks can directly sue the REST APIs from their
>>> favorite languages.
>>>
>>> Thanks!
>>>
>>> On Tue, Oct 13, 2015 at 8:49 AM Nigel Jones <jon...@uk.ibm.com> wrote:
>>>
>>>>
>>>> The AtlasClient is tempting for Java users to make use of, but I was
>>>> wondering where it's expected to go.. I tend to see it as sample code
>>>> but not more. Programmers may use their favoured frameworks/patterns,
>>>> and all focus is on the rest API (or the bridge plugin mechanism).
>>>>
>>>> Is that fair?
>>>>
>>>> nigel jones
>>>>
>>>>
>>
>>
