[ 
https://issues.apache.org/jira/browse/ATLAS-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884230#comment-16884230
 ] 

ASF subversion and git services commented on ATLAS-3315:
--------------------------------------------------------

Commit 35142e55ac52fdd46a86f770d71328c72031be55 in atlas's branch 
refs/heads/branch-2.0 from Ashutosh Mestry
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=35142e5 ]

ATLAS-3315: Database initialization exception handling.

(cherry picked from commit 8188a96e2aa3114502098eced91edfe3b1fb3674)


> AtlasGraphProvider: Allow for Creation of JanusGraph DB Connection 
> Initialized with Batch Loading Enabled
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-3315
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3315
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 1.2.0, 2.0.0
>            Reporter: Ashutosh Mestry
>            Assignee: Ashutosh Mestry
>            Priority: Major
>             Fix For: 1.2.0, 2.0.0, trunk
>
>         Attachments: 
> ATLAS-3315-Database-initialization-exception-handlin.patch
>
>
> *Description*
> Case where _JanusGraphFactory.open_ throws an exception, the initialization 
> goes into an infinite loop.
> _Expected Behavior_: The exception should be logged and initialization should 
> exit.
> _Actual Behavior_: Initialization goes into an infinite loop.
> _Root cause:_
>  # If _JanusGraphFactory.open_ encounters errors, we log it and proceed with 
> construction of _AtlasJanusGraphDatabase_.
>  # The ctor of _AtlasJanusGraphDatabase_ calls _getInstance_ which goes back 
> to step 1.
>  *Solution*
> Handle exception and log, initialize _AtlasJanusGraphDatabase_ only on 
> successful completion of _JanusGraphFactory.open._



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to