Re: [jira] [Created] (IGNITE-6769) SQL: prototype for hand-made parser

Hi Ray, Yes, we are going to gradually move away from H2. This will be long process, so first we create execution engine for simple queries, then for more complex, etc.. Also it is very likely that our current distributed execution engine and co-location model will be reworked somehow. On Mon,

Ignite SQL join performance

Currently the only way to join data is nested loops approach stated in this two tickets. https://issues.apache.org/jira/browse/IGNITE-6201 https://issues.apache.org/jira/browse/IGNITE-6202 So we can anticipate the SQL join performance will degrade a lot after the data size reached certain amount.

Re: New Compatibility Testing Framework module in the project

Thanks, Dmitry, but why wiki and not readme.io[1]? It has a section "Test and benchmarking", which suits well for such information. I thought, that wiki is deprecated source of documentation. Correct me if I am wrong. [1] https://apacheignite.readme.io/docs 27.10.2017, 20:29, "Dmitry Pavlov"

Re: [jira] [Created] (IGNITE-6769) SQL: prototype for hand-made parser

Hi Vladimir, What's the purpose of this ticket? Does it mean in the future Ignite will have its own SQL parser instead of H2's parser Ignite is using now? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

IGNITE-6252 patch

Hello, During our testing we have found an issue and I have raised a JIRA ticket https://issues.apache.org/jira/browse/IGNITE-6252. I have also provided a patch that would fix the issue. Could someone take a look and see whether the patch is acceptable? Thanks. The content of this

[GitHub] ignite pull request #2944: Ignite 6641 1

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/2944 Ignite 6641 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6641-1 Alternatively you can review

Re: [VOTE] Apache Ignite 2.3.0 RC2

-1 The reason is the issues at building via Maven 3.5.0, see 3rd environment below. 1 Environment - Build success (clean repo). Started several examples. Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T19:41:47+03:00) Maven home: c:\apache-maven-3.3.9 Java version:

[jira] [Created] (IGNITE-6787) Simplifying and optimising GridNioServer

Igor Seliverstov created IGNITE-6787: Summary: Simplifying and optimising GridNioServer Key: IGNITE-6787 URL: https://issues.apache.org/jira/browse/IGNITE-6787 Project: Ignite Issue

[jira] [Created] (IGNITE-6788) Ignite WAL reader fails on Tx marker record for persistent store with new style folder naming

Dmitriy Pavlov created IGNITE-6788: -- Summary: Ignite WAL reader fails on Tx marker record for persistent store with new style folder naming Key: IGNITE-6788 URL: https://issues.apache.org/jira/browse/IGNITE-6788

[jira] [Created] (IGNITE-6789) Web Console: Rework sorting of caches list on Queries screen to ignore case

Alexey Kuznetsov created IGNITE-6789: Summary: Web Console: Rework sorting of caches list on Queries screen to ignore case Key: IGNITE-6789 URL: https://issues.apache.org/jira/browse/IGNITE-6789

[GitHub] ignite pull request #2914: IGNITE-6713: Ignite Cache 5 flaky test CacheRebal...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2914 ---

[jira] [Created] (IGNITE-6786) Refactoring of GridNioServer

Igor Seliverstov created IGNITE-6786: Summary: Refactoring of GridNioServer Key: IGNITE-6786 URL: https://issues.apache.org/jira/browse/IGNITE-6786 Project: Ignite Issue Type:

Re: [VOTE] Apache Ignite 2.3.0 RC2

Hi Vyacheslav, I tried building Ignite on Maven 3.5.2 with clean local repository on Win10 and it worked fine. Looks like you have a kind of environmental issue. On Mon, Oct 30, 2017 at 12:57 PM, Vyacheslav Daradur wrote: > -1 > > The reason is the issues at building via

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 (binding) Checked .NET: * Build from source * Build and run examples * Binary distribution * NuGet package Release notes for .NET are not correct: local collection joins were added in 2.1 I would include the following tickets instead: https://issues.apache.org/jira/browse/IGNITE-5615

[GitHub] ignite pull request #2945: IGNITE-6788: Ignite WAL reader fails on Tx marker

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2945 IGNITE-6788: Ignite WAL reader fails on Tx marker NPE during reading of Tx marker record for persistent store with new style folder naming You can merge this pull request into a Git repository

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 (binding) I've checked release using automated checker https://ci.ignite.apache.org/viewLog.html?buildId=919727=AssemblyAndRelease_PrepareVote4CheckRcLicensesChecksum=buildLog Project should be visible for any PMC member. It checks: - licenses - pgp signatures - md5 & sha512 hashes -

Re: CacheConfiguration reusage issues with EvictionPolicy enabled.

Up. Would someone please review a PR#2896 for IGNITE-6649 [1]? [1] https://issues.apache.org/jira/browse/IGNITE-6649 On Sat, Oct 21, 2017 at 1:51 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > I don't think it's a big problem. But it would be great if someone better >

[GitHub] ignite pull request #2946: IGNITE-6786

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

[jira] [Created] (IGNITE-6791) .NET: Thin client: batch SQL

Pavel Tupitsyn created IGNITE-6791: -- Summary: .NET: Thin client: batch SQL Key: IGNITE-6791 URL: https://issues.apache.org/jira/browse/IGNITE-6791 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6790) .NET: Thin client: Multiple SQL statements

Pavel Tupitsyn created IGNITE-6790: -- Summary: .NET: Thin client: Multiple SQL statements Key: IGNITE-6790 URL: https://issues.apache.org/jira/browse/IGNITE-6790 Project: Ignite Issue Type:

Re: IGNITE-6666 BinaryObjectImpl.writeFieldByOrder method does not support TIME

Hi Nikita, See my comments in the ticket. On Fri, Oct 20, 2017 at 11:54 AM, Nikita Amelchev wrote: > Hello, Igniters! > > I found that the BinaryObjectImpl.writeFieldByOrder method does not > support > the TIME type [1]. I wrote test and fixed it [2]. TC tests look good

Re: [jira] [Created] (IGNITE-6769) SQL: prototype for hand-made parser

Hi Vladimir, Thanks for the reply. Is there any roadmap for this new execution engine? For example, in version 2.4 the new engine will process select commands and the rest commands will still be handled by H2. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 1. Building C++ from binary release - OK. 2. Building C++ examples - OK. 3. Building ODBC from binary release - OK. 4. ODBC installers - OK. 5. Building C++ from source release - OK. 6. Building ODBC from source release - OK. Best Regards, Igor On Mon, Oct 30, 2017 at 6:58 AM, Alexey

Re: New Compatibility Testing Framework module in the project

Hi Aleksei, Wiki in apache Ignite is used for design documents, Ignite Enhancement Proposals (IEPs), introductory for ignite developers, etc, but not for documentation. Readme.io is official Ignite documentation for ignite users. Recent created page describe how Ignite developer can test

IgniteSet implementation: changes required

Hi, Igniters! Current implementation of IgniteSet is fragile with respect to cluster recovery from a checkpoint. We have an issue (IGNITE-5553) that addresses set's size() behavior, but the problem is slightly broader. The text below is my comment from Jira issue. I encourage you to discuss it.

Re: Ignite SQL join performance

Hi Ray, Basically, there are two ways: 1) Implement missing feature in H2, submit a patch, wait for new H2 version to release, and then move Ignite to this version 2) Wait for our own execution engine to appear and then implement these join algorithms there. On Mon, Oct 30, 2017 at 9:49 AM, Ray

Re: [jira] [Created] (IGNITE-6769) SQL: prototype for hand-made parser

Hi Ray, Not yet, I think we will heave a roadmap by the end of this year. I hope that by the time of 2.4 release we will have the following: 1) Improve data loading speed [1]. As a part of this activity there is a chance that we will change our implementation of our indexes, so that they no

[jira] [Created] (IGNITE-6792) SQL fields query for huge replicated cache gives not correct count if rebalancing is in progress

Dmitriy Pavlov created IGNITE-6792: -- Summary: SQL fields query for huge replicated cache gives not correct count if rebalancing is in progress Key: IGNITE-6792 URL:

Re: Ignite 2.3 - replicated cache lost data after restart cluster nodes with persistence enabled

Hi, I've created issue for this case: https://issues.apache.org/jira/browse/IGNITE-6792 Reproducer is attached to JIRA, also test was added into branch. According to my brief testing, cache.size() method also returns less count than initial load. Sincerely, Dmitriy Pavlov пт, 27 окт. 2017 г. в

[jira] [Created] (IGNITE-6793) NPE in InitNewCoordinatorFuture leading to Cache3 suite hang

Alexey Goncharuk created IGNITE-6793: Summary: NPE in InitNewCoordinatorFuture leading to Cache3 suite hang Key: IGNITE-6793 URL: https://issues.apache.org/jira/browse/IGNITE-6793 Project: Ignite

Re: [VOTE] Apache Ignite 2.3.0 RC2

Well, I can't provide stable reproducer, it seems like described issue relates to my system environment. I will try to investigate the issue in more detail and will file a ticket if it will be necessary. Anyway, the release is built success via Maven 3.3.9. I cancel my negative vote if it is

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 (binding) I've verified result of automatic checker. On Mon, Oct 30, 2017 at 7:40 PM, Vyacheslav Daradur wrote: > Well, I can't provide stable reproducer, it seems like described issue > relates to my system environment. > I will try to investigate the issue in more

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 (binding) On Mon, Oct 30, 2017 at 10:28 AM, Andrey Gura wrote: > +1 > > Checked: > - Java: Build from sources. > - Tests of vertx-ignite project are passed successfully. > > On Mon, Oct 30, 2017 at 7:54 PM, Denis Magda wrote: > > +1 (binding) > > > > — >

Re: Let's keep Apache Ignite docs up-to-date

Good point. Renamed: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document — Denis > On Oct 30, 2017, at 12:37 PM, Dmitriy Setrakyan wrote: > > Thanks Denis! Any change we can rename the

[GitHub] ignite pull request #2948: IGNITE-6761: Change block numeration in SparseBlo...

GitHub user YuriBabak opened a pull request: https://github.com/apache/ignite/pull/2948 IGNITE-6761: Change block numeration in SparseBlockMatrixStorage You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-6796) GridClusterStateProcessor$5 has no @GridInternal annotation

Pavel Konstantinov created IGNITE-6796: -- Summary: GridClusterStateProcessor$5 has no @GridInternal annotation Key: IGNITE-6796 URL: https://issues.apache.org/jira/browse/IGNITE-6796 Project:

[jira] [Created] (IGNITE-6797) Handle IO errors in LFS files

Alexander Belyak created IGNITE-6797: Summary: Handle IO errors in LFS files Key: IGNITE-6797 URL: https://issues.apache.org/jira/browse/IGNITE-6797 Project: Ignite Issue Type: Bug

Re: IgniteSet implementation: changes required

Hi Andrey, Thanks for a detailed email. I think your suggestions do make sense. Ignite cannot afford to have a distributed set that is not fail-safe. Can you please focus only on solutions that provide consistent behavior in case of topology changes and failures and document them in the ticket?

Re: affinity key syntax

Thanks, Vladimir, got it. However, even though we may have different indexes, the data should be on the same node, if it is properly collocated. I do agree that we should try to remove extra index lookups, if possible. Do we have a ticket for it? Is it a lot of work? D. On Wed, Oct 25, 2017 at

[jira] [Created] (IGNITE-6795) Web console: Make default file name for saving scan results more informative

Pavel Konstantinov created IGNITE-6795: -- Summary: Web console: Make default file name for saving scan results more informative Key: IGNITE-6795 URL: https://issues.apache.org/jira/browse/IGNITE-6795

Re: Ignite 2.0.0 GridUnsafe unmonitor

Denis, We should definitely print out a thorough warning if HashMap is passed into a bulk method (instead of SortedMap). However, we should make sure that we only print that warning once and not ever time the API is called. Can you please file a ticket for 2.4? D. On Thu, Oct 26, 2017 at 11:05

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 (binding) — Denis > On Oct 28, 2017, at 3:58 AM, Vladimir Ozerov wrote: > > Igniters, > > We have uploaded a 2.3.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.3.0-rc2/ > > Git tag name is > 2.3.0-rc2 > > This release includes the following

[GitHub] ignite pull request #2947: IGNITE-6787

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

[jira] [Created] (IGNITE-6794) Local Cache start failed on client if default memory configuration is used.

Andrew Mashenkov created IGNITE-6794: Summary: Local Cache start failed on client if default memory configuration is used. Key: IGNITE-6794 URL: https://issues.apache.org/jira/browse/IGNITE-6794

Let's keep Apache Ignite docs up-to-date

Igniters, Our project is broadly documented so it’s becoming harder and harder to keep the docs consistent and updated. During several last months we tried the new approach with some of community members and took it down on paper: https://cwiki.apache.org/confluence/display/IGNITE/Documentation

Re: Let's keep Apache Ignite docs up-to-date

Thanks Denis! Any change we can rename the page to "How to Document?". On Mon, Oct 30, 2017 at 12:27 PM, Denis Magda wrote: > Igniters, > > Our project is broadly documented so it’s becoming harder and harder to > keep the docs consistent and updated. During several last

Re: IGNITE-6252 patch (Cassandra Integration Bug Fix)

Hi, thanks for the contribution! Igor R., could you review the change? — Denis > On Oct 30, 2017, at 12:57 AM, Sunny Chan, CLSA wrote: > > Hello, > > During our testing we have found an issue and I have raised a JIRA ticket >

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 Checked: - Java: Build from sources. - Tests of vertx-ignite project are passed successfully. On Mon, Oct 30, 2017 at 7:54 PM, Denis Magda wrote: > +1 (binding) > > — > Denis > >> On Oct 28, 2017, at 3:58 AM, Vladimir Ozerov wrote: >> >> Igniters, >>