You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Kelvin R. Lawrence (JIRA)" <ji...@apache.org> on 2018/11/22 18:00:00 UTC

[jira] [Updated] (TINKERPOP-2098) gremlin-server.sh start does not seem to work as advertised

     [ https://issues.apache.org/jira/browse/TINKERPOP-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kelvin R. Lawrence updated TINKERPOP-2098:
------------------------------------------
    Description: 
This may be as simple as a documentation issue but the help text for Gremlin server implies that I should be able to do:
{code:java}
gremlin-server.sh start conf/myyaml.yaml{code}
However when I do that it does not seem to actually be reading my YAML file or if it is it is not reading it fully as I am specifying the WsAndHttp channelizer in the YAML and when the server starts the HTTP endpoint is not available.

 

If I start the server in the terminal with

 
{code:java}
 gremlin-server.sh  conf/myyaml.yaml{code}
 

all is fine but I want to start it in the background.

 

I spoke to [~pluradj] and he had me try using the environment variable to specify the YAML file name and that worked with the *start* keyword.

 

Is *gremlin-server.sh start conf/myyaml.yam*l supposed to work?

 

If not it would be good to change the help text for gremlin-server.sh which currently reads as follows:

 

 
{code:java}
Usage: bin/gremlin-server.sh {start|stop|restart|status|console|install <group> <artifact> <version>|<conf file>}{code}
 

  was:
This may be as simple as a documentation issue but the help text for Gremlin server implies that I should be able to do:


{code:java}
gremlin-server.sh start conf/myyaml.yam{code}

However when I do that it does not seem to actually be reading my YAML file or if it is it is not reading it fully as I am specifying the WsAndHttp channelizer in the YAML and when the server starts the HTTP endpoint is not available.

 

If I start the server in the terminal with

 
{code:java}
 gremlin-server.sh  conf/myyaml.yaml{code}
 

all is fine but I want to start it in the background.

 

I spoke to [~pluradj] and he had me try using the environment variable to specify the YAML file name and that worked with the *start* keyword.

 

Is *gremlin-server.sh start conf/myyaml.yam*l supposed to work?

 

If not it would be good to change the help text for gremlin-server.sh which currently reads as follows:

 

 
{code:java}
Usage: bin/gremlin-server.sh {start|stop|restart|status|console|install <group> <artifact> <version>|<conf file>}{code}
 


> gremlin-server.sh start does not seem to work as advertised
> -----------------------------------------------------------
>
>                 Key: TINKERPOP-2098
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2098
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.3.4
>            Reporter: Kelvin R. Lawrence
>            Priority: Minor
>
> This may be as simple as a documentation issue but the help text for Gremlin server implies that I should be able to do:
> {code:java}
> gremlin-server.sh start conf/myyaml.yaml{code}
> However when I do that it does not seem to actually be reading my YAML file or if it is it is not reading it fully as I am specifying the WsAndHttp channelizer in the YAML and when the server starts the HTTP endpoint is not available.
>  
> If I start the server in the terminal with
>  
> {code:java}
>  gremlin-server.sh  conf/myyaml.yaml{code}
>  
> all is fine but I want to start it in the background.
>  
> I spoke to [~pluradj] and he had me try using the environment variable to specify the YAML file name and that worked with the *start* keyword.
>  
> Is *gremlin-server.sh start conf/myyaml.yam*l supposed to work?
>  
> If not it would be good to change the help text for gremlin-server.sh which currently reads as follows:
>  
>  
> {code:java}
> Usage: bin/gremlin-server.sh {start|stop|restart|status|console|install <group> <artifact> <version>|<conf file>}{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)