[FLINK-1328] Rework Constant Field Annotations

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.0-incubating
• Component/s: API / DataSet, API / Scala
• Assignee: Fabian Hueske
• Reporter: Fabian Hueske
• Created: 15/Dec/14 16:26
• Updated: 28/Feb/19 14:30
• Resolved: 28/Jan/15 01:32

Description

Constant field annotations are used by the optimizer to determine whether physical data properties such as sorting or partitioning are retained by user defined functions.

The current implementation is limited and can be extended in several ways:

• Fields that are copied to other positions
• Field definitions for non-tuple data types (Pojos)

There is a pull request (#83) that goes into this direction and which can be extended.

Sub-Tasks

• Semantic Annotations - Inconsistencies: Resolved
• Bug in Constant Fields Annotation (Semantic Properties): Closed
• Enable constant field definitions for Pojo DataTypes: Resolved