[
https://issues.apache.org/jira/browse/IGNITE-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166107#comment-16166107
]
ASF GitHub Bot commented on IGNITE-6258:
----------------------------------------
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/2662
IGNITE-6258 .NET: Thin client: Define metadata exchange protocol
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6258
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2662.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 #2662
----
commit 53da5c892a7310ed57ea7c43d78b074f90eed03a
Author: Pavel Tupitsyn <[email protected]>
Date: 2017-09-14T11:29:44Z
IGNITE-6258 .NET: Thin client: Define metadata exchange protocol
----
> .NET: Thin client: Define metadata exchange protocol
> ----------------------------------------------------
>
> Key: IGNITE-6258
> URL: https://issues.apache.org/jira/browse/IGNITE-6258
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.3
>
>
> IGNITE-6236 introduced some metadata operations in client protocol.
> Let's formalize these operations:
> * Which operations should be present? PutMeta, PutMetas, GetMeta, GetSchema,
> etc.
> * Do we need to retrieve schemas separately from entire metadata?
> * Dynamic type registration
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
