You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Zinoviev (Jira)" <ji...@apache.org> on 2019/10/01 14:15:01 UTC

[jira] [Resolved] (IGNITE-10297) Investigate possibility of restricting API of Upstream transformer

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

Alexey Zinoviev resolved IGNITE-10297.
--------------------------------------
    Resolution: Won't Fix

> Investigate possibility of restricting API of Upstream transformer
> ------------------------------------------------------------------
>
>                 Key: IGNITE-10297
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10297
>             Project: Ignite
>          Issue Type: Improvement
>          Components: ml
>    Affects Versions: 2.8
>            Reporter: Artem Malykh
>            Assignee: Artem Malykh
>            Priority: Major
>             Fix For: 2.8
>
>
> Signature of 'transform' method of UpstreamTransformer is Stream<UpstreamEntry> -> Stream<UpstreamEntry>. For now it is used only for bagging and for that purpose, UpstreamEntry -> Stream<UpstreamEntry> would suffice (just use 'flatMap' on upstream), maybe we should change signature to this form. From other hand, we'll cut some possibilities like limiting of upstream. This question needs investigation. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)