[
https://issues.apache.org/jira/browse/TINKERPOP-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086929#comment-17086929
]
Stephen Mallette commented on TINKERPOP-2359:
---------------------------------------------
> i havent been able to spot how to send via it the graph.close
just send a script:
https://tinkerpop.apache.org/docs/current/reference/#_submitting_scripts_4
we don't like recommending that option but in this case it's all you can do.
> I did look at g.io() but it doesnt answer my needs.
Could you explain why? If you're relying on sending {{graph.close()}} as a
workaround I'm not sure I understand why you couldn't send {{g.io()}}. In some
ways {{g.io()}} is a bit better since you then avoid script usage.
> onShutDown not being called when docker container stopped
> ---------------------------------------------------------
>
> Key: TINKERPOP-2359
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2359
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.6
> Reporter: ohad israeli
> Priority: Minor
>
> When one uses groovy hooks with tinkerpop server hosted within the official
> docker the onStartUp hook will be called at server startup but the onShutDown
> will not be called.
> I am using tinkergraph server for local testing and i would like to persist
> the data upon the server exit. i've added a graph.close to the onShutDown
> hook but i havent been able to get it called.
> It will be called of course if you use the server start / server stop shell
> script but not if you kill / stop the docker container.
> If there is some other way to persist the date i.e. call the graph.close from
> code and note via the console it would also be great as using it from node
> javascript i havent been able to find a way to call the graph.close directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
