[ 
https://issues.apache.org/jira/browse/FLINK-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-7142:
----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Scala DataSet API ignores ResultTypeQueryable interface
> -------------------------------------------------------
>
>                 Key: FLINK-7142
>                 URL: https://issues.apache.org/jira/browse/FLINK-7142
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataSet, API / Scala
>    Affects Versions: 1.3.1, 1.4.0
>            Reporter: Fabian Hueske
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> The {{ResultTypeQueryable}} is used to specify the return type of 
> user-defined functions. The Scala DataSet API ignores this interface. The 
> only way to override the inferred type information is to use implicit values. 
> However, the {{ResultTypeQueryable}} interface has the nice property that the 
> return type is defined in the actual function, whereas implicit types are 
> defined in the program, i.e., outside of the function.
> IMO, the Scala DataSet API should also support the {{ResultTypeQueryable}} 
> interface.
> What do you think [~aljoscha], [~till.rohrmann]?
> Was it a conscious decision to only support implicit type definitions?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to