[
https://issues.apache.org/jira/browse/OAK-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257538#comment-15257538
]
Chetan Mehrotra edited comment on OAK-4299 at 4/26/16 4:14 AM:
---------------------------------------------------------------
Yeah this would change in expected behaviour. May be log a message at start if
running in read only and mentioning about what flag to pass to switch to read
write mode
was (Author: chetanm):
Yeah this would change in expected behaviour. May be log a message at start if
running in read only and mentioning about what flag to pass to switch to read
write mede
> 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
>
>
> 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)
