You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Ashutosh Mestry (JIRA)" <ji...@apache.org> on 2017/03/01 22:35:45 UTC

[jira] [Created] (ATLAS-1618) Export API: Provide Option to Restrict Scope of Export Operation

Ashutosh Mestry created ATLAS-1618:
--------------------------------------

             Summary: Export API: Provide Option to Restrict Scope of Export Operation
                 Key: ATLAS-1618
                 URL: https://issues.apache.org/jira/browse/ATLAS-1618
             Project: Atlas
          Issue Type: Improvement
          Components:  atlas-core
    Affects Versions: 0.8-incubating
            Reporter: Ashutosh Mestry
            Assignee: Ashutosh Mestry
             Fix For: 0.8-incubating


*Background*
Existing Export API navigates the graph structure and get all the connected entities as part of export. The API is geared toward exporting of entire database and not parts of the database.

*Scenario*
It is possible to specify Export of 1 table. The resulting ZIP however, contains the entire database and all other tables in the database to be exported. Alternately stated, it is not possible to export subset of the graph of which the entity is part of.

This behavior impacts Import, as more entities get imported than needed.

*Resolution*
While the existing approach is useful, the user should be allowed to specify the scope of the export operation. 

The existing _ExportRequest.options_ could potentially have an option that indicate the scope.
{quote}
options
  FETCH = FULL | CONNECTED
{quote}

_FETCH = FULL_ All entities directly and indirectly entities are fetched.
_FETCH = CONNECTED_ All entities directly connected are fetched.

Examples:
{code:title=options.FULL}
{
  "itemsToExport": [
      {
          "typeName": "DB_v1",
          "uniqueAttributes": {
              "name": "Sales"
          }
    }
  ],
  "options": { 
        "FETCH": "FULL"
    }
}
{code}

{code:title=options.CONNECTED}
{
  "itemsToExport": [
      {
          "typeName": "Table_v1",
          "uniqueAttributes": {
              "name": "customer_view"
          }
    }
  ],
  "options": { 
        "FETCH": "CONNECTED"
    }
}
{code}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)