Return-Path: X-Original-To: apmail-flink-dev-archive@www.apache.org Delivered-To: apmail-flink-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08EFB17399 for ; Wed, 30 Sep 2015 08:06:25 +0000 (UTC) Received: (qmail 33808 invoked by uid 500); 30 Sep 2015 08:06:10 -0000 Delivered-To: apmail-flink-dev-archive@flink.apache.org Received: (qmail 33736 invoked by uid 500); 30 Sep 2015 08:06:10 -0000 Mailing-List: contact dev-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 dev@flink.apache.org Received: (qmail 33725 invoked by uid 99); 30 Sep 2015 08:06:10 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Sep 2015 08:06:10 +0000 Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 2DC431A022D for ; Wed, 30 Sep 2015 08:06:09 +0000 (UTC) Received: by igbni9 with SMTP id ni9so25098326igb.0 for ; Wed, 30 Sep 2015 01:06:09 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.26.66 with SMTP id j2mr2959823igg.42.1443600369038; Wed, 30 Sep 2015 01:06:09 -0700 (PDT) Received: by 10.79.73.1 with HTTP; Wed, 30 Sep 2015 01:06:08 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Sep 2015 10:06:08 +0200 Message-ID: Subject: Re: Graduating Gelly in 0.10 From: Kostas Tzoumas To: "dev@flink.apache.org" Content-Type: multipart/alternative; boundary=047d7bd75bb231c4ad0520f2670a --047d7bd75bb231c4ad0520f2670a Content-Type: text/plain; charset=UTF-8 Does the workaround work, or can FLINK-2443 still appear? If we have a workaround, we can schedule a fix to FLINK-2443 for 0.10.1 On Tue, Sep 29, 2015 at 9:59 PM, Vasiliki Kalavri wrote: > Hello squirrels, > > since it was already mentioned in the other thread, I'm starting this > discussion to see what the community thinks about graduating Gelly in the > upcoming 0.10 release. > > In my opinion, in order to do that we have to look into the following > issues: > > 1. FLINK-2663 : I've > already opened a PR and will merge if no objections. > > 2. FLINK-2561 , > FLINK-2785 > : These are about > syncing > the Scala and Java APIs. There is one method missing, documentation, and > examples. I'm working on these and should have a PR tomorrow or Thursday. > > 3. FLINK-2443 : This is > a > bug in the CompactingHashTable that might affect Gelly iterations. The > problem with this one is that it's hard to reproduce and debug. I ran > GSAConnectedComponents with the same dataset mentioned in the JIRA on EC2 > and couldn't reproduce the bug. However, I did ran into (probably) the same > bug with some other delta iteration code of mine (not Gelly), but I had no > luck debugging it. You can see the discussion here > < > https://mail-archives.apache.org/mod_mbox/flink-dev/201509.mbox/%3CCAJZ2dcW5JK3khtndSu4ixPfe5WgHOj-%3DiCJaUN3pdhK1DY_6ZQ%40mail.gmail.com%3E > >. > The good news is that Gelly iteration methods have a > "setSolutionSetUnmanaged" option, which avoids this. > > From my side, I don't see any blocking issues or major functionality > missing (after 1-2 are addressed). > > My only concern is FLINK-2443. What do you think we should do about it? > > Thank you! > > Cheers, > Vasia. > --047d7bd75bb231c4ad0520f2670a--