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

Ondrej Rysavy edited comment on IGNITE-11337 at 2/21/19 12:00 PM:
------------------------------------------------------------------

StreamReceiverHolder serialization should use PeerLoadingObjectHolder to 
provide information about Receiver implementation type - see 
StreamReceiverHolder.cs, method WriteBinary.


was (Author: rysavy):
StreamReceiverHolder serialization should use PeerLoadingObjectHolder to 
provide information about Receiver implementation type. 

> Ignite .NET - Remote Assembly Loading problem when using Data Streamers
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-11337
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11337
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.7
>         Environment: Apache Ignite 2.7.0 installed from NuGet, running on 
> Windows 10.
> Ignite server executed as:
> {{...\.nuget\packages\apache.ignite\2.7.0\lib\net40>Apache.Ignite.exe}}
> The test console program (.NET 4.6 target) attached.
>            Reporter: Ondrej Rysavy
>            Priority: Major
>              Labels: .NET, .net-core
>         Attachments: Program.cs, StreamReceiverHolder.cs
>
>
> When using data streaming, the server raises "IgniteException: No matching 
> type found for object [typeId=721826618, 
> typeName=StreamingDemo.StringPairVisitor]".
> StreamingDemo.StringPairVisitor implements IStreamReceiver interface (see the 
> attached file).
> Neither suggested solution works (remote assembly loading, -assembly 
> argument, etc.)
> The possible workaround is to execute some compute action prior to streaming. 
> Then everything works as expected. 
> In general, it seems that Streaming itself does not load the necessary 
> assembly to locate the matching type implementing custom logic for stream 
> processing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to