barak/cayley
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Use time.Duration according to the time docs

Browse source 
Having a time.Duration measuring seconds is likely to cause problems at
a later stage. This change retains configuration compatibility while
adding idiomatic duration use.
This commit is contained in:
kortschak 2014-08-02 23:15:41 +09:30
parent 2d884f92e9
commit 0fedecd392
4 changed files with 102 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/Configuration.md
View file

@ -74,10 +74,10 @@ All command line flags take precedence over the configuration file.
#### **`gremlin_timeout`**
* Type: Integer
* Type: Integer or String
* Default: 30
The value in seconds of the maximum length of time the Javascript runtime should run until cancelling the query and returning a 408 Timeout. A negative value means no limit.
The maximum length of time the Javascript runtime should run until cancelling the query and returning a 408 Timeout. When gremlin_timeout is an integer is is interpretted as seconds, when it is a string it is [parsed](http://golang.org/pkg/time/#ParseDuration) as a Go time.Duration. A negative duration means no limit.
## Per-Database Options