You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "Michael Russo (JIRA)" <ji...@apache.org> on 2016/08/05 21:22:20 UTC

[jira] [Resolved] (USERGRID-1315) Improve Duplicate Unique Value Message

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

Michael Russo resolved USERGRID-1315.
-------------------------------------
    Resolution: Won't Fix

You can do GET by name and fetch the UUID based on the exceptions logged. 

> Improve Duplicate Unique Value Message
> --------------------------------------
>
>                 Key: USERGRID-1315
>                 URL: https://issues.apache.org/jira/browse/USERGRID-1315
>             Project: Usergrid
>          Issue Type: Story
>          Components: Stack
>            Reporter: Jeffrey 
>
> At the moment, the log message when there is a duplicate unique value (name) only says there is a collision and does not indicate the UUID of the entity which currently holds the unique value for that type+field.  An improvement would be to include the UUID of the existing entity in the log message.
> For an individual operation this may not seem like a worthwhile thing to have.  However, in the case of a mass import of data, it would be useful to have the UUIDs in a log for troubleshooting purposes.  Also, there have beenUsergrid bugs in the past which have resulted in duplicate entities with the same name, so the user may not be able to take action without the UUID of the existing entity in Usergrid.



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