[
https://issues.apache.org/jira/browse/FLINK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627140#comment-14627140
]
ASF GitHub Bot commented on FLINK-1963:
---------------------------------------
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/905#discussion_r34626753
--- Diff: flink-java/src/main/java/org/apache/flink/api/java/DataSet.java
---
@@ -618,9 +620,9 @@ public long count() throws Exception {
}
/**
- * Returns a distinct set of a {@link Tuple} {@link DataSet} using all
fields of the tuple.
+ * Returns a distinct set of a {@link DataSet} using all fields of the
tuple.
* <p>
- * Note: This operator can only be applied to Tuple DataSets.
+ * If the input is a {@link Tuple} {@link DataSet}, uses all fields of
the tuple.
--- End diff --
Can you change this to "If the input is a composite type (Tuple or Pojo
type), distinct is performed on all fields and each field must be a key type."
> Improve distinct() transformation
> ---------------------------------
>
> Key: FLINK-1963
> URL: https://issues.apache.org/jira/browse/FLINK-1963
> Project: Flink
> Issue Type: Improvement
> Components: Java API, Scala API
> Affects Versions: 0.9
> Reporter: Fabian Hueske
> Assignee: pietro pinoli
> Priority: Minor
> Labels: starter
> Fix For: 0.9
>
>
> The `distinct()` transformation is a bit limited right now with respect to
> processing atomic key types:
> - `distinct(String ...)` works only for composite data types (POJO, tuple),
> but wildcard expression should also be supported for atomic key types
> - `distinct()` only works for composite types, but should also work for
> atomic key types
> - `distinct(KeySelector)` is the most generic one, but not very handy to use
> - `distinct(int ...)` works only for Tuple data types (which is fine)
> Fixing this should be rather easy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
