You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/08/03 16:22:06 UTC

[jira] [Commented] (TINKERPOP3-623) More output for OLAP jobs

    [ https://issues.apache.org/jira/browse/TINKERPOP3-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651904#comment-14651904 ] 

Marko A. Rodriguez commented on TINKERPOP3-623:
-----------------------------------------------

I concur. There is (was?) a ticket about extending the {{Future<ComputerResult>}} interface to suppose such runtime grabbing of metrics. We would have to do that first. 

> More output for OLAP jobs
> -------------------------
>
>                 Key: TINKERPOP3-623
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-623
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: console, hadoop
>    Affects Versions: 3.0.0-incubating
>            Reporter: Daniel Kuppitz
>            Priority: Minor
>
> Long running OLAP / Giraph jobs leave the user in the dark. You have to check several logs to see where you currently are. The REPL just shows
> {noformat}
> ...
> INFO  org.apache.hadoop.mapred.JobClient  -  map 99% reduce 0%
> {noformat}
> ... for hours. Spark is better, it seems to have its own progress bar that's shown in the REPL. For Giraph it would be great to have more than just the standard Hadoop job output, so that users get the feeling that something is done under the hood (use {{Future<ComputerResult>}} to query for updates?)



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