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/03/02 17:51:18 UTC
[jira] [Updated] (USERGRID-1251) Handle index processing event case
where an edge exists but entity is missing.
[ https://issues.apache.org/jira/browse/USERGRID-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Russo updated USERGRID-1251:
------------------------------------
Sprint: Usergrid 37 (was: Usergrid 36)
> Handle index processing event case where an edge exists but entity is missing.
> ------------------------------------------------------------------------------
>
> Key: USERGRID-1251
> URL: https://issues.apache.org/jira/browse/USERGRID-1251
> Project: Usergrid
> Issue Type: Story
> Affects Versions: 2.1.1, 2.1.0
> Reporter: Michael Russo
> Assignee: Michael Russo
> Fix For: 2.1.2
>
>
> In the event an edge exists in graph and the entity has been deleted, ensure this is handled as OK when processing the index event in AmazonAsyncEventService. Currently it logs an exception because when it tries to fetch the entity data it doesn't exist and therefore 0 messages are returned for an event that should have returned 1 message.
> Ideally, this should trigger a graph node compaction (read repair) to remove that edge.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)