You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Dmitriev (JIRA)" <ji...@apache.org> on 2018/11/16 14:19:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16689467#comment-16689467 ]
Anton Dmitriev commented on IGNITE-10297:
-----------------------------------------
Could we also consider in this task an ability to avoid using of additional _TransformerChain_ and just use _andThen_ approach?
> 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
> Reporter: Artem Malykh
> Assignee: Artem Malykh
> Priority: Major
>
> 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
(v7.6.3#76005)