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 2014/12/12 23:26:13 UTC
[jira] [Resolved] (FLINK-378) Add Java UDF Code analysis to Flink
[ https://issues.apache.org/jira/browse/FLINK-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabian Hueske resolved FLINK-378.
---------------------------------
Resolution: Duplicate
Duplicate of FLINK-1319
> Add Java UDF Code analysis to Flink
> -----------------------------------
>
> Key: FLINK-378
> URL: https://issues.apache.org/jira/browse/FLINK-378
> Project: Flink
> Issue Type: New Feature
> Reporter: GitHub Import
> Priority: Minor
> Labels: github-import
> Fix For: pre-apache
>
>
> * Migrate and stabilize the research prototype of @aljoscha into the Flink mainline.
> * the first approach should only analyze tuple at a time operators (map, join, ..)
> The tool is able to detect which fields are being changed (or not) by an UDF. This information is used by the compiler to perform optimizations (such as reusing order)
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/378
> Created by: [rmetzger|https://github.com/rmetzger]
> Labels: enhancement, optimizer,
> Milestone: Release 0.6 (unplanned)
> Assignee: [skunert|https://github.com/skunert]
> Created at: Tue Jan 07 19:55:57 CET 2014
> State: open
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)