[
https://issues.apache.org/jira/browse/TINKERPOP3-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030063#comment-15030063
]
stephen mallette commented on TINKERPOP3-981:
---------------------------------------------
> The only time it would seem to matter is when the user wants to specify a
> different data store (from the default) for the credentials database.
that is the use case and that seemed reasonable to me for having different data
stores. i'm not sure i'd want to mix the auth database with my application
data - or i'd at least want the option to not do so. note that this will still
be possible even without the {{credentialsDbLocation}}, but we just won't have
that extra setting for folks to worry about.
> Deprecate support for credentialsDbLocation in Gremlin Server Config
> --------------------------------------------------------------------
>
> Key: TINKERPOP3-981
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-981
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.1.1-incubating
>
>
> The {{credentialsDbLocation}} was created to deal with the fact that
> TinkerGraph did not support persistence. Now that we have
> {{gremlin.tinkergraph.graphLocation}} in the standard TinkerGraph config we
> can deprecate that old config option and simply rely on the configuration
> supplied to TinkerGraph itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
