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

stephen mallette closed TINKERPOP3-556.
---------------------------------------
       Resolution: Implemented
    Fix Version/s: 3.0.0.GA

Implemented this one as [~dalaro] suggested with the standard groovysh {{:set}} 
command.  Looks like this basically: {{:set max-iteration 25}} 

Had to extend the standard {{SetCommand}} though as I wanted to see 
{{max-iteration}} appear in auto-complete for {{:set}} and didn't see a way to 
do that given the API.

> Limiting Result Iteration in Gremlin Console
> --------------------------------------------
>
>                 Key: TINKERPOP3-556
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-556
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: console
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>             Fix For: 3.0.0.GA
>
>
> In the Titan Gremlin Console (and formerly the Faunus Console) there was some 
> limit on the number of results iterated before an ellipse (...) was 
> displayed.  In this way faunus jobs didn't iterate tons of results when the 
> job completed and thus blow the job logs off the console.  It would seem that 
> the TP3 Gremlin Console should have some kind of feature built into it to do 
> something similar.  Perhaps, even having some kind of result iteration limit 
> would prevent users from doing bad stuff to themselves and having to 
> {{ctrl-c}} themselves out of the console.  
> [~dalaro] proposed using the {{:set}} command to help set this value in the 
> console in https://github.com/thinkaurelius/titan/issues/924 -  perhaps using 
> standard groovysh infrastructure would be a good idea.
> There is also the question of whether or not there are two settings one for 
> those OLAP and one for OLTP - perhaps there is just a difference in settings 
> between local and remote submitted.   commands.  
> Thoughts welcome on this one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to