[jira] [Updated] (CLEREZZA-939) Make Triple Collections as services optional

["Minto van der Sluis (JIRA)" <ji...@apache.org>]

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

Minto van der Sluis updated CLEREZZA-939:
-----------------------------------------

    Summary: Make Triple Collections as services optional  (was: Create separate service to register the triple Collections as services)

Changed the issue name to better reflect the work that has been done. If (in future) it is needed to create a separate service for this then a new issue can be created.

> Make Triple Collections as services optional
> --------------------------------------------
>
>                 Key: CLEREZZA-939
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-939
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Minto van der Sluis
>            Assignee: Minto van der Sluis
>
> TcManager has functionality to register every triple collection (graph) as a service. As a result bundle startup slows down with a very large number of triple collections (graphs).
> Separating this functionality in a separate service reduces TcManager complexity. This service should be configurable to be able to disable the triple collection name as a service functionality.



--
This message was sent by Atlassian JIRA
(v6.2#6252)