[
https://issues.apache.org/jira/browse/GIRAPH-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161243#comment-13161243
]
Avery Ching commented on GIRAPH-100:
------------------------------------
Ah, I see. We should file another JIRA to create a GiraphException and the
various types I suppose. Or do you want me to do it in this JIRA?
I can put the SuperstepHashPartitionerFactory into another directory
src/main/java/org/apache/giraph/integration/SuperstepHashPartitionerFactory.java
I like the idea of mocking in general, but not sure how mocking can verify the
behavior in this case. Probably leave it as an integration test only. IMO, we
should file a separate JIRA for separating the tests into unittests (mocking,
individual class tests) and integration tests, but integration tests can still
be run locally and/or remote.
Let me know what you think and I'll make the requested changes.
> Data input sampling and testing improvements
> --------------------------------------------
>
> Key: GIRAPH-100
> URL: https://issues.apache.org/jira/browse/GIRAPH-100
> Project: Giraph
> Issue Type: New Feature
> Components: graph
> Reporter: Avery Ching
> Assignee: Avery Ching
> Attachments: GIRAPH-100.patch
>
>
> It would be really nice to help debug an application by limiting the input
> data (% of input splits, max vertices per input split). Also, it would be
> nice for the workers to provide a little more debugging info on how far along
> they are with processing the input data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
