[
https://issues.apache.org/jira/browse/OAK-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592348#comment-14592348
]
Michael Marth commented on OAK-2920:
------------------------------------
But for the configs that are known not to work: that would not be risky, right?
The point of this issue is to reduce user's guessing why their instance is
borked...
In any case we could still add a --force option to ignore this check.
> RDBDocumentStore: fail init when database config seems to be inadequate
> -----------------------------------------------------------------------
>
> Key: OAK-2920
> URL: https://issues.apache.org/jira/browse/OAK-2920
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: rdbmk
> Reporter: Julian Reschke
> Priority: Minor
> Labels: resilience
> Fix For: 1.3.1
>
>
> It has been suggested that the implementation should fail to start (rather
> than warn) when it detects a DB configuration that is likely to cause
> problems (such as wrt character encoding or collation sequences)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
