[
https://issues.apache.org/jira/browse/IGNITE-11787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821937#comment-16821937
]
Igor Sapego commented on IGNITE-11787:
--------------------------------------
[~NIzhikov], there is no such commitment, that we only increment protocol
version no more than once per release. I do not see why can not we use two
different versions here, as it looks like a sound and most clear solution. It
looks definitely more clear than adding some workaround non-working code in
.Net client. Also, it will make it look, like .Net supports Affinity Awareness,
which is not true yet. Lately, if .Net implementation will be included in
release, we can always make it one version again.
> Thin client: Protocol version conflict in master
> ------------------------------------------------
>
> Key: IGNITE-11787
> URL: https://issues.apache.org/jira/browse/IGNITE-11787
> Project: Ignite
> Issue Type: Bug
> Components: thin client
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Two independent tickets (IGNITE-11043 and IGNITE-9113) introduced two
> different thin protocol versions - one for Affinity Awareness and another is
> for the Lazy Memory Allocation. These two different protocol versions were
> given the same value - 1.3.0. It is proposed to change one of versions to
> 1.4.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
