flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fhueske <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-1328] Reworked semantic annotations
Date Wed, 14 Jan 2015 22:36:33 GMT
GitHub user fhueske opened a pull request:

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

    [FLINK-1328] Reworked semantic annotations

    This PR is based on #83
    
    Open Issues:
    - Naming of class annotations (`ConstantFields`, `ConstantFieldsExcept`, `ReadFields`,
...) and API methods (`withConstantSet()`, ...). Constant fields and constant set is a bit
inconsistent. Do we want to keep the term *constant* or should we go with preserved or forwarded
fields? Right now, the original naming is preserved. 
    - Documentation except for JavaDocs not done yet.

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

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

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

    https://github.com/apache/flink/pull/311.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 #311
    
----
commit 25af81509c997b1f6748447db97bfe59322dde73
Author: sebastian kunert <skunert49@gmail.com>
Date:   2014-08-31T17:22:56Z

    integrated forwarded Fields into the optimizer

commit e6fb7116e3c0cbf2b615f0f3f580aa37707df3d3
Author: Fabian Hueske <fhueske@apache.org>
Date:   2014-12-17T17:59:14Z

    [FLINK-1328] Reworked semantic annotations for functions.
    - Constant fields can be defined for (nested) tuples, Pojos, case classes
    - Added semantic function information to example programs

commit a6f50ac7238507c8bb8b8c1739170fa95ca8e7d6
Author: Fabian Hueske <fhueske@apache.org>
Date:   2015-01-14T15:48:07Z

    [FLINK-1328] Added previously failing semantic annotations to examples and fixed them
by enabling partitioning on AtomicTypes.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message