[ https://issues.apache.org/jira/browse/IGNITE-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828043#comment-15828043 ]
Igor Sapego commented on IGNITE-4046: ------------------------------------- After some studying, it seems that most flexible and optimized way to introduce identity resolvers to C++ is to add {{IdentityResolver}} interface, and introduce {{BynaryType<T>::GetIdentityResolver}} method for user types. {{IdentityResolver}} should be something like this: {code} class IdenntityResolver { virtual int32_t GetHashCode(const BinaryObject& obj) = 0; } {code} As you can see, {{BinaryObject}} type used here. It is used for the efficiency reasons, which Pavel has pointed out. {{BinaryObject}} however is not implemented currently for C++ client, so if there are no objections I'm going to add it as a blocking issue for this one. > C++: Support DML API > -------------------- > > Key: IGNITE-4046 > URL: https://issues.apache.org/jira/browse/IGNITE-4046 > Project: Ignite > Issue Type: Task > Components: platforms > Affects Versions: 1.8 > Reporter: Denis Magda > Assignee: Igor Sapego > 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.C++ > by doing the following: > - Implement DML API; > - Enhance {{query_example.cpp}} by doing INSERTs instead of cache.puts and > adding UPDATE and DELETE operation examples. > - Add documentation to Ignite.C++ 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)