[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827681#comment-15827681
]
Pavel Tupitsyn commented on IGNITE-4045:
Sure, IGNITE-4556 created.
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Reporter: Denis Magda
> Labels: roadmap
> Fix For: 1.9
>
>
> 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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826838#comment-15826838
]
Denis Magda commented on IGNITE-4045:
-
[~ptupitsyn], please create a documentation section for DML on .NET side. In
general, it makes sense to introduce SQL Grid paragraph in .NET as we did for
Java and document only those pieces that are related to .NET. For the rest you
can refer to Java doc from .NET doc.
In addition, it will be great if you add a DML example similar to the one we
have in Java. What do you think?
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Reporter: Denis Magda
> Labels: roadmap
> Fix For: 1.9
>
>
> 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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824104#comment-15824104
]
Pavel Tupitsyn commented on IGNITE-4045:
{{BinaryFieldEqualityComparer}} moved, comment added.
Merged to master.
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Labels: roadmap
> Fix For: 1.9
>
>
> 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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824103#comment-15824103
]
ASF GitHub Bot commented on IGNITE-4045:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1309
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Labels: roadmap
> Fix For: 1.9
>
>
> 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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782352#comment-15782352
]
Pavel Tupitsyn commented on IGNITE-4045:
Fixed FullFooter tests.
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Reporter: Denis Magda
>Assignee: Vladimir Ozerov
> 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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778622#comment-15778622
]
Pavel Tupitsyn commented on IGNITE-4045:
3) There is already a ticket: IGNITE-4397. In current ticket FieldComparer is
hidden from public API, please ignore it.
5) IGNITE-4495
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> 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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731742#comment-15731742
]
Pavel Tupitsyn commented on IGNITE-4045:
BinaryFieldEqualityComparer is hidden from public API. Let's port all hash code
implementations from Java as a separate task: IGNITE-4397
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: New Feature
> 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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728746#comment-15728746
]
Pavel Tupitsyn commented on IGNITE-4045:
FieldIdentityResolver issue uncovered:
Hash codes for many basic types (strings, for example) are computed differently
in .NET and Java.
What should we do?
* Implement hash code algorithms the same way as in Java for all basic types
* Remove FieldIdentityResolver support in .NET
> .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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722918#comment-15722918
]
Pavel Tupitsyn commented on IGNITE-4045:
Identity resolvers implemented. In some cases the resolver is ignored,
investigating.
> .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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15715369#comment-15715369
]
Pavel Tupitsyn commented on IGNITE-4045:
BinaryIdentityResolver is not part of binary metadata (that is distributed
across cluster), therefore each node has to have explicitly configured resolver.
This also means that we have to propagate .NET BinaryConfiguration to Java on
start so that configured resolver is mapped properly.
> .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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[ https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712549#comment-15712549 ] ASF GitHub Bot commented on IGNITE-4045: GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1309 IGNITE-4045 .NET: Support DML API You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-4045 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1309.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1309 commit 23a8b92720ff192143451f1498d40cba57e23a3d Author: Pavel Tupitsyn Date: 2016-11-30T14:33:53Z QueryField.IsKeyField commit 4c2d2c835924fa3b0be4328b602376ce5a3cfd2a Author: Pavel Tupitsyn Date: 2016-11-30T14:42:14Z Update isKey from attributes commit 4633b0faa87c73998e38d840c5927782abe77c72 Author: Pavel Tupitsyn Date: 2016-11-30T15:41:09Z wip commit 4e5a97bdb68c7d7afcca78008a9fa58ce782a877 Author: Pavel Tupitsyn Date: 2016-11-30T15:44:19Z Propagate keyFields to Java commit a25ccaf6a1e3729dd62449dfe2be8ca13778e9fd Author: Pavel Tupitsyn Date: 2016-11-30T15:45:47Z wip commit 3ebcd29d204a60ce7696f7c76ebf93f73353b078 Author: Pavel Tupitsyn Date: 2016-11-30T15:47:04Z Propagate keyFields from Java commit 82c1ff0c45bf9cc30b54fe42c1ca017ffe21ad7a Author: Pavel Tupitsyn Date: 2016-11-30T15:55:49Z fix read commit 03e77d927ef1d906bb87d64251709283f1d35458 Author: Pavel Tupitsyn Date: 2016-11-30T15:59:34Z wip commit 0982aafda6e9e68feb0b15438eca6d6b55f4dfa1 Author: Pavel Tupitsyn Date: 2016-11-30T16:02:02Z XSD schema commit de5ef0d531fb4b5b1aa7761925e3f206c9d50816 Author: Pavel Tupitsyn Date: 2016-11-30T16:07:51Z Fix non-deterministic XML serialization order commit f2410ee6789985f8721df08db4b00bb0aed89b36 Author: Pavel Tupitsyn Date: 2016-12-01T08:51:56Z wip commit a19a9766631054e588fd4c5d966f6ea58426f04d Author: Pavel Tupitsyn Date: 2016-12-01T08:52:34Z wip commit 939a6dd62ed869ae3850b587e872cfd621bc9243 Author: Pavel Tupitsyn Date: 2016-12-01T08:53:01Z wip commit ba75336fd7dbdb6c82f90c8d2342fac9f9e0503e Author: Pavel Tupitsyn Date: 2016-12-01T08:53:48Z wip commit 67857f2c8586cdc386025df87587a4238105a7ac Author: Pavel Tupitsyn Date: 2016-12-01T08:55:22Z Move tests to a separate class commit 3c0e599619ac16638035fa899b6d23cfe10da26e Author: Pavel Tupitsyn Date: 2016-12-01T09:29:49Z wip commit 86a7ef8cf94d8066e0dc4a5d307ca40397ecf64c Author: Pavel Tupitsyn Date: 2016-12-01T09:39:06Z wip commit 9e07ad47b677f31a7e5f187cbf08ff23cdf9f72b Author: Pavel Tupitsyn Date: 2016-12-01T09:40:39Z wip commit 409c8190a4bf36a5b8a443cbce4bbe7776f3a96e Author: Pavel Tupitsyn Date: 2016-12-01T09:44:40Z wip commit 3b7f6bb3adaed05751024a5ddf1c5274b09c11a5 Author: Pavel Tupitsyn Date: 2016-12-01T09:50:22Z wip commit 031bed2f0aa6e0353bcfb035224382f3f37f2d2d Author: Pavel Tupitsyn Date: 2016-12-01T09:52:07Z wip commit 9877456c993e0d5fd1429b2fd65c0dce40f22294 Author: Pavel Tupitsyn Date: 2016-12-01T09:58:04Z wip commit 66bd614c1b936408411bffa455c0768c9e156766 Author: Pavel Tupitsyn Date: 2016-12-01T09:59:20Z wip commit c9fc24d3399257e733c53294ed97cce18dcfd1f3 Author: Pavel Tupitsyn Date: 2016-12-01T10:02:12Z cleanup commit c87dd8fdb394e32aa16ea7be786dad98e2cba6cb Author: Pavel Tupitsyn Date: 2016-12-01T10:09:14Z Fix config commit c3e48413dbd6b6400df368d988ea4ab1f0574bab Author: Pavel Tupitsyn Date: 2016-12-01T10:15:42Z Insert works, but deserialization fails commit 03e39149ac5516b914ba483e2fdf60a2de74fbb2 Author: Pavel Tupitsyn Date: 2016-12-01T10:18:10Z Deserialization actually works! commit 986414a11e265f0311531a22cd58d2dd4d614177 Author: Pavel Tupitsyn Date: 2016-12-01T10:23:44Z Tests work! commit b64e4db4bfed8130c5a704b3115519479fd0bda5 Author: Pavel Tupitsyn Date: 2016-12-01T11:18:43Z TestInvalidCompositeKey done commit c81732ae4c82f78f4c197e22ca2e783564f6b2b7 Author: Pavel Tupitsyn Date: 2016-12-01T11:34:56Z wip TestBinaryMode > .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 s
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15711741#comment-15711741
]
Pavel Tupitsyn commented on IGNITE-4045:
Another thing to be ported to .NET is BinaryIdentityResolver interface.
> .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)
[jira] [Commented] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708670#comment-15708670
]
Pavel Tupitsyn commented on IGNITE-4045:
The only API change is QueryEntity.keyFields. Everything else goes through
SqlFieldsQuery.
> .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)
