incubator-giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (Commented) (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-100) Data input sampling and testing improvements
Date Thu, 01 Dec 2011 22:18:40 GMT


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 

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:
>             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:!default.jspa
For more information on JIRA, see:


View raw message