You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2016/07/01 12:19:10 UTC

[jira] [Created] (ATLAS-982) Search response is slightly inconsistent with other request / response types in Atlas

Hemanth Yamijala created ATLAS-982:
--------------------------------------

             Summary: Search response is slightly inconsistent with other request / response types in Atlas
                 Key: ATLAS-982
                 URL: https://issues.apache.org/jira/browse/ATLAS-982
             Project: Atlas
          Issue Type: Improvement
            Reporter: Hemanth Yamijala


In search responses that return entity encodings, there are slight differences to the entity definition structure that is used in all other APIs:

* id is encoded as $id$
* typeName is encoded as $typeName$
* In the dataType attribute that returns a TypesDef structure encoding, the attribute encoding for multiplicity is different. It doesn't cast the value to a string like "optional" or "required", instead it expands it as min 0, max 0 etc.

These can be made consistent with respect to EntityDefinition and TypesDef  structures used in other APIs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)