Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6CAAD17FCD for ; Tue, 17 Mar 2015 20:42:05 +0000 (UTC) Received: (qmail 89973 invoked by uid 500); 17 Mar 2015 20:41:56 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 89935 invoked by uid 500); 17 Mar 2015 20:41:55 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 89926 invoked by uid 99); 17 Mar 2015 20:41:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 20:41:55 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 17 Mar 2015 20:41:54 +0000 Received: (qmail 88829 invoked by uid 99); 17 Mar 2015 20:41:29 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 20:41:29 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 69638E180E; Tue, 17 Mar 2015 20:41:29 +0000 (UTC) From: vasia To: issues@flink.incubator.apache.org Reply-To: issues@flink.incubator.apache.org References: In-Reply-To: Subject: [GitHub] flink pull request: [FLINK-1514][Gelly] Add a Gather-Sum-Apply ite... Content-Type: text/plain Message-Id: <20150317204129.69638E180E@git1-us-west.apache.org> Date: Tue, 17 Mar 2015 20:41:29 +0000 (UTC) X-Virus-Checked: Checked by ClamAV on apache.org Github user vasia commented on the pull request: https://github.com/apache/flink/pull/408#issuecomment-82588861 Hi @balidani, thanks a lot for the changes! I'll try to run some tests on a cluster soon and test the new version. I have a question about the graph coloring example. As far as I understand, in this algorithm, colors are represented by numbers (vertex values) and the goal is to color the graph with the minimum number of colors, so that no 2 neighboring vertices have the same color. So, in each superstep, each vertex gathers the colors of its neighbors in a set and then assigns itself the minimum color that isn't in this set. However, it seems to me that in your implementation, you're only propagating the minimum neighbor value, similar to what you would do in connected components. Is there anything I'm missing here? Thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---