[
https://issues.apache.org/jira/browse/FLINK-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749452#comment-15749452
]
ASF GitHub Bot commented on FLINK-5104:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2985
@mushketyk the build is failing due to unused imports (IntelliJ can be
configured to automatically remove these).
There are so many ways to implement the validator. Projections would reduce
the data to be transmitted and sorted. I like to document when we are
performing a different kind of join (here, an anti-join) for the day when these
are available in Flink. I don't know how counting in the `FlatJoinFunction`
followed by two `DiscardingOutputFormat` compares with the current
implementation of a union and count (which is a dummy `OutputFormat`).
We'll need to rebase this PR once FLINK-5311 has been committed.
> Implement BipartiteGraph validator
> ----------------------------------
>
> Key: FLINK-5104
> URL: https://issues.apache.org/jira/browse/FLINK-5104
> Project: Flink
> Issue Type: Sub-task
> Components: Gelly
> Reporter: Ivan Mushketyk
> Assignee: Ivan Mushketyk
>
> BipartiteGraph should have a validator similar to GraphValidator for Graph
> class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
