You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Jason Plurad (JIRA)" <ji...@apache.org> on 2016/05/16 14:41:12 UTC
[jira] [Updated] (TINKERPOP-1303) add help for :remote config for
Gephi Plugin
[ https://issues.apache.org/jira/browse/TINKERPOP-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Plurad updated TINKERPOP-1303:
------------------------------------
Fix Version/s: (was: 3.2.1)
> add help for :remote config for Gephi Plugin
> --------------------------------------------
>
> Key: TINKERPOP-1303
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1303
> Project: TinkerPop
> Issue Type: Improvement
> Components: console
> Affects Versions: 3.2.1
> Reporter: Jason Plurad
> Priority: Minor
>
> This idea came from reviewing the [patch|https://github.com/apache/incubator-tinkerpop/pull/308] for TINKERPOP-1297. Currently {{:remote config}} with no arguments returns an unfriendly message "Invalid config arguments - check syntax". It might be more user-friendly if {{:remote config}} either returned the existing configuration settings or if it listed some help.
> {{:remote config help}} could let the user know what parameters are available and how they can be configured. Or perhaps something similar to how {{:remote connect}} works when you leave out parameters would help lead the user down the path of getting the syntax right.
> Although I approached this from a Gephi perspective, it seems that the config options help must be based on the remote type, whether it is {{tinkerpop.gephi}} vs {{tinkerpop.server}} vs {{tinkerpop.hadoop}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)