[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711741#comment-15711741
]
Pavel Tupitsyn edited comment on IGNITE-4045 at 12/1/16 12:24 PM:
------------------------------------------------------------------
Another thing to be ported to .NET is BinaryIdentityResolver interface
(BinaryTypeConfiguration.BinaryIdentityResolver).
For now we should provide mapping to two default implementations:
BinaryArrayIdentityResolver, BinaryFieldIdentityResolver
was (Author: ptupitsyn):
Another thing to be ported to .NET is BinaryIdentityResolver interface
(BinaryTypeConfiguration.BinaryIdentityResolver).
> .NET: Support DML API
> ---------------------
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Reporter: Denis Magda
> Assignee: Pavel Tupitsyn
> Labels: roadmap
> Fix For: 2.0
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready
> (https://apacheignite.readme.io/docs/distributed-dml).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)