You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/05/16 13:59:14 UTC

[jira] [Closed] (OAK-4182) oak-run->console should have a read-only mode to connect to document stores (mongo, rdb, etc)

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

Davide Giannella closed OAK-4182.
---------------------------------

Bulk close for 1.5.2

> oak-run->console should have a read-only mode to connect to document stores (mongo, rdb, etc)
> ---------------------------------------------------------------------------------------------
>
>                 Key: OAK-4182
>                 URL: https://issues.apache.org/jira/browse/OAK-4182
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: run
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Minor
>              Labels: docs-impacting, production, tools
>             Fix For: 1.6, 1.5.2
>
>
> oak-run, when connecting to a persistence storage, works like a live/independent oak instance. For clustered setup (read doc stores such backed by mongo or rdb), this means that another connected instance would treat oak-run's connection as a new one. While, theoretically, there is no issue with it and the world would work fine BUT an investigative tool such as oak-run->console should minimize touching the system as much as possible (especially while collecting forensics).
> So, we should expose a parameter (say {{\-\-read-only}} to oak-run->console while stating oak-run to connect to a document store storage. Note, read-only mode can be a global boolean for lifetime of oak-run (i.e. we don't really need dynamic switching between read-only and read-write modes)



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