You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/01/26 13:31:39 UTC
[jira] [Closed] (FLINK-1666) Clean-up Field Expression Code
[ https://issues.apache.org/jira/browse/FLINK-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabian Hueske closed FLINK-1666.
--------------------------------
Resolution: Done
Fix Version/s: 1.0.0
Done with af029e7e0c6377ec12edafedb4d6ea53c4fa9fe9
> Clean-up Field Expression Code
> ------------------------------
>
> Key: FLINK-1666
> URL: https://issues.apache.org/jira/browse/FLINK-1666
> Project: Flink
> Issue Type: Improvement
> Components: DataSet API
> Affects Versions: 0.9
> Reporter: Fabian Hueske
> Assignee: Fabian Hueske
> Fix For: 1.0.0
>
>
> Field expressions are supported at various places in the user facing APIs.
> However, not every feature allows exactly the same syntax. Also, code for analyzing field expressions is scattered around several places.
> Right now, most of the field expression handling is done in the {{PojoTypeInfo}}, {{CaseClassTypeInfo}}, and {{ExpressionKeys}} classes. Corner cases are inconsistently handled at several other places.
> We should clean this up and add one utility class that defines the syntax of field expressions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)