[ 
https://issues.apache.org/jira/browse/FLINK-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312977#comment-14312977
 ] 

ASF GitHub Bot commented on FLINK-1444:
---------------------------------------

GitHub user fhueske opened a pull request:

    https://github.com/apache/flink/pull/379

    [FLINK-1444][api-extending] Add support for split data properties on data 
sources

    This pull request adds support for declaring global and local properties 
for input splits.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/fhueske/flink sourceProperties

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/379.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #379
    
----
commit c1f77c1293320094b8d07b357a40960f4a657cf0
Author: Fabian Hueske <[email protected]>
Date:   2015-02-06T13:28:00Z

    [FLINK-1444][api-extending] Add support for attaching data properties to 
data sources

----


> Add data properties for data sources
> ------------------------------------
>
>                 Key: FLINK-1444
>                 URL: https://issues.apache.org/jira/browse/FLINK-1444
>             Project: Flink
>          Issue Type: New Feature
>          Components: Java API, JobManager, Optimizer
>    Affects Versions: 0.9
>            Reporter: Fabian Hueske
>            Assignee: Fabian Hueske
>            Priority: Minor
>
> This issue proposes to add support for attaching data properties to data 
> sources. These data properties are defined with respect to input splits.
> Possible properties are:
> - partitioning across splits: all elements of the same key (combination) are 
> contained in one split
> - sorting / grouping with splits: elements are sorted or grouped on certain 
> keys within a split
> - key uniqueness: a certain key (combination) is unique for all elements of 
> the data source. This property is not defined wrt. input splits.
> The optimizer can leverage this information to generate more efficient 
> execution plans.
> The InputFormat will be responsible to generate input splits such that the 
> promised data properties are actually in place. Otherwise, the program will 
> produce invalid results. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to