[
https://issues.apache.org/jira/browse/OAK-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh resolved OAK-4299.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.5.2
[r1740950|https://svn.apache.org/r1740950]@trunk changes default behavior to
use read-only mode. (Updated doc in
[r1740951|https://svn.apache.org/r1740951]@trunk)
{{\-\-read\-write}} is now exposed instead of {{\-\-read\-only}} to connect in
read-write mode.
As suggested, in read-only mode, we'd log
{noformat}
Repository connected in read-only mode. Use '--read-write' for write operations
{noformat}
> oak-run console should connect to repository in read-only mode by default
> -------------------------------------------------------------------------
>
> Key: OAK-4299
> URL: https://issues.apache.org/jira/browse/OAK-4299
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Labels: production, tools
> Fix For: 1.6, 1.5.2
>
>
> With OAK-4182 and OAK-4298, oak-run->console supports connecting to a
> repository in read only mode. But, as [~edivad] suggested
> [here|https://issues.apache.org/jira/browse/OAK-4182?focusedCommentId=15245661&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15245661],
> it might be more useful to connect to repositories in read-only mode by
> default and require an explicit read-write flag for write operations.
> This, of course, doesn't align with 'always read-write mode' that's
> operational currently.
> Btw, since, 1.5.2 hasn't been release yet, so, we can do this switch pretty
> cleanly currently. Post 1.5.2 (which would then have {{--read-only}}, we
> might have to retain that flag)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
