You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "Alan Ho (JIRA)" <ji...@apache.org> on 2015/09/08 18:34:45 UTC

[jira] [Updated] (USERGRID-1002) Document and test S3 import capability

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

Alan Ho updated USERGRID-1002:
------------------------------
    Description: 
The work to be done on this ticket is to document a method for doing this (maybe in the cookbook).

We have a bunch of enterprise use cases where we're not the system of record but we're the preferred system of query.  For example, product catalogs, user management systems, etc.  In these cases, we need a way to import records or uses as entities in a way where a new duplicate entity is not created.  This can be possibly done by creating entities via name-based UUIDs or via duplicate checks, but we need the standard mechanism for doing this and to document that.

> Document and test S3 import capability
> --------------------------------------
>
>                 Key: USERGRID-1002
>                 URL: https://issues.apache.org/jira/browse/USERGRID-1002
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: Alan Ho
>
> The work to be done on this ticket is to document a method for doing this (maybe in the cookbook).
> We have a bunch of enterprise use cases where we're not the system of record but we're the preferred system of query.  For example, product catalogs, user management systems, etc.  In these cases, we need a way to import records or uses as entities in a way where a new duplicate entity is not created.  This can be possibly done by creating entities via name-based UUIDs or via duplicate checks, but we need the standard mechanism for doing this and to document that.



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