Pavel,
Agree. Looks like we should leave our compatibility policy as is and do not
limit it to several adjacent versions.
On Thu, Jun 7, 2018 at 12:35 PM Pavel Tupitsyn wrote:
> Vladimir,
>
> Not sure I see the point of 2 release policy.
> It is not very good both for users and developers.
>
>
Vladimir,
Not sure I see the point of 2 release policy.
It is not very good both for users and developers.
* Developers still have the burden on maintaining multiple protocol versions
* Users are quite limited with version choices
We should either go with a full-blown versioning so any client
Igniters,
Let's discuss how to implement tests in separate thread. At this point it
is more important to agree on compatibility policies.
On Wed, Jun 6, 2018 at 6:02 PM, Vyacheslav Daradur
wrote:
> Hello, Igniters!
>
> I am not familiar with the Ignite's thin client.
>
> I'd suggest defining
Hello, Igniters!
I am not familiar with the Ignite's thin client.
I'd suggest defining tests scenarios first, to understand what we need
for testing.
For example, our Compatibility Framework may be used for the following scenario:
1. Start node of a previously released version in separate JVM
Hi Vyacheslav,
WDYT about applicability of PDS compatibiltiy framework for thin clients?
Sincerely,
Dmitriy Pavlov
ср, 6 июн. 2018 г. в 13:45, Vladimir Ozerov :
> Hi Nikolay,
>
> Huge +1 for automated compatibility tests. Luckily, we already did that for
> persistence, so probably we can
Hi Nikolay,
Huge +1 for automated compatibility tests. Luckily, we already did that for
persistence, so probably we can re-use some infrastructure from there.
On Wed, Jun 6, 2018 at 1:20 PM, Nikolay Izhikov wrote:
> +1 From me.
>
> As I wrote in previous mail-threads,
> I think we need to
+1 From me.
As I wrote in previous mail-threads,
I think we need to create test framework to be able to test compatibility for
all clients we have.
AFAIK, currently, there is no possibility to automatically check compatibility.
В Ср, 06/06/2018 в 11:39 +0300, Vladimir Ozerov пишет:
> Igniters,
Igniters,
I'd like to discuss once again our compatibility policy for thin clients
(.JDBC, ODBC, .NET, Java, etc.). We have no clear rules for now, so let's
try to come to agreement.
Normally database vendors work as follows:
1) There is a set of currently supported database versions
2) There is
