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

2018-11-28 Thread Artem Malykh (JIRA)


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

Artem Malykh commented on IGNITE-10297:
---

[~dmitrievanthony] This is already done in IGNITE-10272

> 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 -> Stream. For now it is used only for 
> bagging and for that purpose, UpstreamEntry -> Stream 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)


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

2018-11-16 Thread Anton Dmitriev (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 -> Stream. For now it is used only for 
> bagging and for that purpose, UpstreamEntry -> Stream 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)