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 <https://issues.apache.org/jira/browse/FLINK-2663>: I've already opened a PR and will merge if no objections. 2. FLINK-2561 <https://issues.apache.org/jira/browse/FLINK-2561>, FLINK-2785 <https://issues.apache.org/jira/browse/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 <https://issues.apache.org/jira/browse/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.
