[
https://issues.apache.org/jira/browse/IGNITE-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590277#comment-16590277
]
Ilya Kasnacheev commented on IGNITE-9301:
-----------------------------------------
[~alexzaitzev] My take, if you add a feature .Net, you add a test on that
feature.
Now, I can't speak for [~ptupitsyn], he's a principal contributor to .Net
codebase. I am not and I am wary of vetting commits without tests. Are there
objective reasons why this test is not feasible to write (e.g. almost
impossible to construct a negative case).
> Support method compute withNoResultCache in .Net
> ------------------------------------------------
>
> Key: IGNITE-9301
> URL: https://issues.apache.org/jira/browse/IGNITE-9301
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 2.6
> Reporter: Dmitriy Pavlov
> Assignee: Aleksei Zaitsev
> Priority: Major
> Labels: .net
> Fix For: 2.7
>
>
> During https://issues.apache.org/jira/browse/IGNITE-6284 implementation new
> method was added -
> org.apache.ignite.IgniteCompute#withNoResultCache
> but this method was not supported in .NET API version.
> It is required to add correct support to .NET.
> Please remove method name from UnneededMethods in
> modules/platforms/dotnet/Apache.Ignite.Core.Tests/ApiParity/ComputeParityTest.cs
> once issue is done
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
