You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@rya.apache.org by "Kevin Chilton (JIRA)" <ji...@apache.org> on 2017/12/27 17:16:00 UTC

[jira] [Updated] (RYA-414) Fix inconsistent method of using MongoClient within a Sail object

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

Kevin Chilton updated RYA-414:
------------------------------
    Description: We've decided to introduce a stateful configuration object that is used to hold onto objects that needs to be shared across components within a Sail object in favor of having a static holder. The static holder limited our ability to use more than a single Sail object within a single JVM because all of those Sail objects would all have to access the same Mongo DB repository.

> Fix inconsistent method of using MongoClient within a Sail object
> -----------------------------------------------------------------
>
>                 Key: RYA-414
>                 URL: https://issues.apache.org/jira/browse/RYA-414
>             Project: Rya
>          Issue Type: Bug
>            Reporter: Andrew Smith
>            Assignee: Kevin Chilton
>            Priority: Blocker
>
> We've decided to introduce a stateful configuration object that is used to hold onto objects that needs to be shared across components within a Sail object in favor of having a static holder. The static holder limited our ability to use more than a single Sail object within a single JVM because all of those Sail objects would all have to access the same Mongo DB repository.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)