You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2016/11/03 00:26:59 UTC

[jira] [Updated] (ATLAS-1266) TypeRegistry post commit mechanism

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

Apoorv Naik updated ATLAS-1266:
-------------------------------
    Summary: TypeRegistry post commit mechanism  (was: Guice injection for TypeRegistry )

> TypeRegistry post commit mechanism
> ----------------------------------
>
>                 Key: ATLAS-1266
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1266
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.8-incubating
>            Reporter: Apoorv Naik
>            Assignee: Apoorv Naik
>             Fix For: 0.8-incubating
>
>         Attachments: ATLAS-1266.patch
>
>
> Currently for every injection of TypeRegistry there's a new instance created which interferes with the indexer. Also the logs report a success even when there's a failure during indexing.
> Listeners should be notified after the transient commit to the registry and not before that, else the new transient types are not picked up during indexing.
> Side effect/bug: If the graph commit fails for some reason the AtlasTypeRegistry has no way of knowing that and will host some stale data, until a refresh is forced.



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