[jira] [Created] (IGNITE-5735) NPE during populated data (CacheQueryDdlExample)

Ilya Suntsov created IGNITE-5735: Summary: NPE during populated data (CacheQueryDdlExample) Key: IGNITE-5735 URL: https://issues.apache.org/jira/browse/IGNITE-5735 Project: Ignite Issue Type:

Testing of backward compatibility in Ignite

Hi Igniters. There is a need to test backward compatibility with previous release within a task[1]. As far as I understand: it needs to provide methods in the Ignite-test-framework to start instance of specific version of Ignite. I popose to add such api in the project, for example: "Ignite star

[jira] [Created] (IGNITE-5736) Add test of backward-compatibility

Vyacheslav Daradur created IGNITE-5736: -- Summary: Add test of backward-compatibility Key: IGNITE-5736 URL: https://issues.apache.org/jira/browse/IGNITE-5736 Project: Ignite Issue Type: S

Re: Testing of backward compatibility in Ignite

Hi Vyacheslav, Currently Ignite nodes with different versions can not join the same cluster, look at OsDiscoveryNodeValidationProcessor (this check is called from discovery ServerImpl IgniteSpiContext.validateNode). Thanks On Wed, Jul 12, 2017 at 11:09 AM, Vyacheslav Daradur wrote: > Hi Ignite

[GitHub] ignite pull request #2284: Ignite 5103 Drop client from cluster on missed he...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/2284 Ignite 5103 Drop client from cluster on missed heartbeats You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5

[GitHub] ignite pull request #2285: IGNITE-5123

GitHub user YevIgn opened a pull request: https://github.com/apache/ignite/pull/2285 IGNITE-5123 You can merge this pull request into a Git repository by running: $ git pull https://github.com/YevIgn/ignite ignite-5123 Alternatively you can review and apply these changes as t

Re: Testing of backward compatibility in Ignite

Semen, As far as I know, it is possible to allow nodes with different versions to join topology. Some products based on Ignite provides this feature. We'd like to check that changes at Ignite will not break compatibility feature of these products. Could you provide some tips how to connect diffe

Re: Testing of backward compatibility in Ignite

It is possible to implement a test plugin which will override DiscoveryNodeValidationProcessor. Also IMO it is better to start different Ignite versions in different processes to avoid potential problems with custom classloaders (there is already some helper classes for multi-jvm tests). Thanks

[jira] [Created] (IGNITE-5737) Web Console: make cluster a root configuration entity

Ilya Borisov created IGNITE-5737: Summary: Web Console: make cluster a root configuration entity Key: IGNITE-5737 URL: https://issues.apache.org/jira/browse/IGNITE-5737 Project: Ignite Issue

[jira] [Created] (IGNITE-5738) Add support of batch requests for jdbc2

Evgenii Zhuravlev created IGNITE-5738: - Summary: Add support of batch requests for jdbc2 Key: IGNITE-5738 URL: https://issues.apache.org/jira/browse/IGNITE-5738 Project: Ignite Issue Type

[jira] [Created] (IGNITE-5739) JVM crash on node deactivation

Alexey Kuznetsov created IGNITE-5739: Summary: JVM crash on node deactivation Key: IGNITE-5739 URL: https://issues.apache.org/jira/browse/IGNITE-5739 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-5740) Transactional load benchmark

Oleg Ostanin created IGNITE-5740: Summary: Transactional load benchmark Key: IGNITE-5740 URL: https://issues.apache.org/jira/browse/IGNITE-5740 Project: Ignite Issue Type: Improvement

Re: IGNITE-5123

Provided a patch - https://github.com/apache/ignite/pull/2285, the change is straight-forward - simply placed PluginProvider#onIgniteStart right after components #onKernalStart callbacks are called. In basic test suite (as I can see it includes platform and plugin tests) - http://ci.ignite.apac

Re: Patch for IGNITE-5597 is ready.

Hi, Thanks for interest to Apache Ignite development. I'd like to propose you to make direct "review request". This should help to speedup review process, you can find tips here: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute# HowtoContribute-SubmittingforReview On Tue, Jul

Re: IGNITE-5123

Hi, Thanks for interest to Apache Ignite development. I'd like to propose you to make direct "review request". This should help to speedup review process, you can find tips here: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute# HowtoContribute-SubmittingforReview On Wed, Jul

[GitHub] ignite pull request #2286: IGNITE-5740 created new benchmark for load transa...

GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/2286 IGNITE-5740 created new benchmark for load transaction You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5740

Hello

Hello

Hello

Hello

Re: Hello

Hello Andrey, welcome to Apache Ignite developers mailing list. Do you need help with something? On Wed, Jul 12, 2017 at 5:45 PM, wrote: > Hello > >

RE: Hello

Hello Pavel. I’m has no experience how to contribute to apache backed projects. But I would like to implement https://issues.apache.org/jira/browse/IGNITE-5602 feature. Issue was created after my request in freshdesk. I’ve already post patch in issue comment. Отправлено из Почты для Windows 1

[jira] [Created] (IGNITE-5741) Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator

Dmitriy Govorukhin created IGNITE-5741: -- Summary: Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator Key: IGNITE-5741 URL: https://issues.apache.org/jira/browse/IGNITE-5741 Project

Re: Patch for IGNITE-5597 is ready.

Many thanks. Done. Andrei On Wednesday, July 12, 2017 3:03 PM, Anton Vinogradov wrote: Hi, Thanks for interest to Apache Ignite development. I'd like to propose you to make direct "review request". This should help to speedup review process, you can find tips here: https://cwiki.apach

[jira] [Created] (IGNITE-5743) .NET: PageMemory and PersistentStore documentation

Pavel Tupitsyn created IGNITE-5743: -- Summary: .NET: PageMemory and PersistentStore documentation Key: IGNITE-5743 URL: https://issues.apache.org/jira/browse/IGNITE-5743 Project: Ignite Issue

Re: Apache Ignite 2.1 scope

Cos, IMO, If we really want to get a valuable feedback from a wider audience then in addition to the new version the audience has to be given both a high-level and deep documentation, proper messaging, etc. It will take time to soak in the information and a week might not be enough in general.

[jira] [Created] (IGNITE-5742) .NET: PersistentStore example

Pavel Tupitsyn created IGNITE-5742: -- Summary: .NET: PersistentStore example Key: IGNITE-5742 URL: https://issues.apache.org/jira/browse/IGNITE-5742 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #2287: ignite-5489 Fixed possible connection leaks when ...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/2287 ignite-5489 Fixed possible connection leaks when loadPreviousValue set to true You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-i

[GitHub] ignite pull request #2288: ignite-5489 Fixed possible connection leaks when ...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/2288 ignite-5489 Fixed possible connection leaks when loadPreviousValue set to true You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-i

Changing public IgniteCompute API to improve changes in 5037 ticket

Igniters, jira: https://issues.apache.org/jira/browse/IGNITE-5037 How do you look to solve this ticket by adding two methods to the public IgniteCompute API? @IgniteAsyncSupported public void affinityRun(@NotNull Collection cacheNames, Collec

Re: Changing public IgniteCompute API to improve changes in 5037 ticket

Hi Max, This ticket doesn't assume any API changes, it's about broken functionality. I would start with checking what tests we have for @AffinityKeyMapped and creating missing one. From what I understand functionality is broken completely or almost completely, so I guess testing coverage is very w

[jira] [Created] (IGNITE-5744) Ignore non user caches when automatically choosing a queryable cache inside JDBC driver

Alexander Paschenko created IGNITE-5744: --- Summary: Ignore non user caches when automatically choosing a queryable cache inside JDBC driver Key: IGNITE-5744 URL: https://issues.apache.org/jira/browse/IGNITE-5

[GitHub] ignite pull request #2289: IGNITE-5744

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/2289 IGNITE-5744 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5744 Alternatively you can review and apply th

[GitHub] ignite pull request #2290: IGNITE-5382: SQL: Added per-schema connection loo...

GitHub user skalashnikov opened a pull request: https://github.com/apache/ignite/pull/2290 IGNITE-5382: SQL: Added per-schema connection lookup You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5382 A