[
https://issues.apache.org/jira/browse/GIRAPH-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583965#comment-13583965
]
Hudson commented on GIRAPH-453:
---
Integrated in Giraph-trunk-Commit #748 (See
[https://build
> On Feb. 21, 2013, 6:45 p.m., Maja Kabiljo wrote:
> > This is a lot of great work, Nitay, thanks! I really like that user doesn't
> > have to extend the whole Input/Output format anymore, that was a lot of
> > code duplication every time.
> >
> > Is it possible to provide some examples/tests
Nitay Joffe created GIRAPH-534:
--
Summary: Add tests / examples for new giraph-hive I/O
Key: GIRAPH-534
URL: https://issues.apache.org/jira/browse/GIRAPH-534
Project: Giraph
Issue Type: Bug
Eli Reisman created GIRAPH-533:
--
Summary: When a pseudo Hadoop cluster (and standalone ZK instance)
are running on the local machine, a test fails
Key: GIRAPH-533
URL: https://issues.apache.org/jira/browse/GIRAPH-533
[
https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583853#comment-13583853
]
Eli Reisman commented on GIRAPH-13:
---
I think I can steal a more robust version of the abo
[
https://issues.apache.org/jira/browse/GIRAPH-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583852#comment-13583852
]
Eli Reisman commented on GIRAPH-532:
+1 ditto!
> Give an explanation
[
https://issues.apache.org/jira/browse/GIRAPH-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583830#comment-13583830
]
Nitay Joffe commented on GIRAPH-532:
+1 love it
> Give an explanation
[
https://issues.apache.org/jira/browse/GIRAPH-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583820#comment-13583820
]
Nitay Joffe commented on GIRAPH-524:
I think if there is a demand for it we should add
[
https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Reisman updated GIRAPH-13:
--
Attachment: GIRAPH-13-5.patch
Here's the latest placeholder. Things are going very well so far, almost d
Maja Kabiljo created GIRAPH-532:
---
Summary: Give an explanation when trying to use unregistered
aggregators
Key: GIRAPH-532
URL: https://issues.apache.org/jira/browse/GIRAPH-532
Project: Giraph
[
https://issues.apache.org/jira/browse/GIRAPH-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maja Kabiljo updated GIRAPH-532:
Attachment: GIRAPH-532.diff
> Give an explanation when trying to use unregistered aggregators
>
I am thinking in the Hadoop repos its still called "trunk" as far as the
git branches go, and we named our profiles around those branches (hadoop
version names), "snapshot" is more of a Maven thing. So I'm going say
please convince me further. But in theory, not a bad idea.
On Sun, Feb 17, 2013 a
Alessandro Presta created GIRAPH-531:
Summary: EdgeIterables#getEdges() should reuse Edge objects
Key: GIRAPH-531
URL: https://issues.apache.org/jira/browse/GIRAPH-531
Project: Giraph
Iss
[
https://issues.apache.org/jira/browse/GIRAPH-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583739#comment-13583739
]
Eli Reisman commented on GIRAPH-524:
That makes sense, and if this doesn't get changed
Alessandro Presta created GIRAPH-530:
Summary: GiraphInputFormat#getSplits() should be aware of
multithreaded input
Key: GIRAPH-530
URL: https://issues.apache.org/jira/browse/GIRAPH-530
Project: G
[
https://issues.apache.org/jira/browse/GIRAPH-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583542#comment-13583542
]
Alessandro Presta commented on GIRAPH-524:
--
All I'm saying is that the concept of
[
https://issues.apache.org/jira/browse/GIRAPH-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583491#comment-13583491
]
Eli Reisman commented on GIRAPH-524:
Good discussion, and good points. I guess that es
Sorry thats what I meant, the supernode got the messages, and boom. So even
using the new byte buffering, one per vertex, you are hitting the wall
here. This is FloatWritible messages, converted to 4 bytes each, in a byte
buffer, and the hard limit for messages per vertex is going to be (2^30)/4
an
[
https://issues.apache.org/jira/browse/GIRAPH-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583429#comment-13583429
]
Eli Reisman commented on GIRAPH-285:
Thanks Alessandro! (My last reply ended up on the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8611/#review16868
---
Ship it!
Forgot to say, I'm +1 on this :-)
- Maja Kabiljo
On Feb.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8611/#review16867
---
This is a lot of great work, Nitay, thanks! I really like that user d
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/8611/
---
(Updated Feb. 21, 2013, 6:17 p.m.)
Review request for giraph.
Changes
---
Yeah, that's exactly what I told you.
We have one ExtendedDataOutput per vertex. And the limit is about
(2^30)/4, since you will have double of the size allocated at some point.
What do you mean you don't want to use a combiner for evaluation reasons?
On 2/21/13 5:38 AM, "Claudio Martella" wrote:
Yep. Actually more than a supernode sending messages it looks more like a
supernode receiving a lot of messages, and hence filling the inbox queue
(in bytearrayformat).
I assumed a max (2^31)/4 (for float messages) limit because I assumed we
had such an object per vertex, but it looks like the Byte
[
https://issues.apache.org/jira/browse/GIRAPH-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583187#comment-13583187
]
Claudio Martella commented on GIRAPH-528:
-
This would be really awesome. I agree w
25 matches
Mail list logo
