[
https://issues.apache.org/jira/browse/TINKERPOP3-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030038#comment-15030038
]
Jeremy Hanna commented on TINKERPOP3-981:
-----------------------------------------
I would say +1 to this. It's confusing to have to specify the properties file
to the data store again in the authentication configuration. 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. I'm not sure when that would
be a reasonable use case. Perhaps if they are storing several graphs in
different data stores using different configs and they want a shared central
credentials db? You would know better about those use cases though
[~spmallette].
> 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)
