Re: [VOTE] Apache Ignite 2.5.0 RC1

+1 (binding) On Thu, May 24, 2018 at 10:59 AM, Andrey Gura wrote: > Igniters, > > We've uploaded a 2.5.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.5.0-rc1/ > > Git tag name is > 2.5.0-rc1 > > This release includes the following changes: > > Ignite:

[GitHub] ignite pull request #4067: graceful shutdown test

GitHub user BiryukovVA opened a pull request: https://github.com/apache/ignite/pull/4067 graceful shutdown test You can merge this pull request into a Git repository by running: $ git pull https://github.com/BiryukovVA/ignite graceful_shutdown_test Alternatively you can

Re: Node.js Thin Client @ npmjs

As Denis said, there is no need to download the entire Ignite repo to install the client. Once published the client is going to be installed by users with a command: npm install -g apache-ignite-client The sources are going to be distributed as a part of the ignite repository, yes. But in

[GitHub] ignite pull request #4066: IGNITE-8612 Debugging NPE in GridCacheTtlManager:...

GitHub user andrewmed opened a pull request: https://github.com/apache/ignite/pull/4066 IGNITE-8612 Debugging NPE in GridCacheTtlManager: add assert You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrewmed/ignite ignite-8612

Re: Node.js Thin Client @ npmjs

Once the client is built it will be uploaded to the npmjs repository, right? So, a JS developer can download the client from there without touching the whole Ignite binary release. However, those who download the whole Ignite binary distribution will find node.js there (as well as .NET, C++, JDBC

[jira] [Created] (IGNITE-8612) NPE in GridCacheTtlManager#expire on commit() or close()

Andrew Medvedev created IGNITE-8612: --- Summary: NPE in GridCacheTtlManager#expire on commit() or close() Key: IGNITE-8612 URL: https://issues.apache.org/jira/browse/IGNITE-8612 Project: Ignite

[jira] [Created] (IGNITE-8611) Binary marshaller documentation should cover how data classes can or can't be changed

Stanislav Lukyanov created IGNITE-8611: -- Summary: Binary marshaller documentation should cover how data classes can or can't be changed Key: IGNITE-8611 URL: https://issues.apache.org/jira/browse/IGNITE-8611

Re: Node.js Thin Client @ npmjs

On Thu, May 24, 2018 at 12:36 PM, Pavel Petroshenko wrote: > Fair enough. Consistency with the other clients is a good argument. > > Pavel, I would discuss it a bit more. Does it really make sense for a node.js user to download the whole Ignite distribution just to get a

[GitHub] ignite pull request #4065: IGNITE-8459 Do first checkpoint after all partiti...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4065 IGNITE-8459 Do first checkpoint after all partitions have been initialized You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8610) Searching checkpoint / WAL history for rebalancing is not properly working in case of local/global WAL disabling

Pavel Kovalenko created IGNITE-8610: --- Summary: Searching checkpoint / WAL history for rebalancing is not properly working in case of local/global WAL disabling Key: IGNITE-8610 URL:

Re: NodeJS thin client: full API

Hi Denis, That's a good point, thanks. This should be a part of the "Usage" section. I'll follow up in JIRA. p. On Thu, May 24, 2018 at 10:49 AM, Denis Magda wrote: > Pavel, > > Recalled that we've not described how to authenticate and set up SSL from > the client side.

Re: Node.js Thin Client @ npmjs

Fair enough. Consistency with the other clients is a good argument. p. On Thu, May 24, 2018 at 11:44 AM, Dmitriy Setrakyan wrote: > On Thu, May 24, 2018 at 11:42 AM, Igor Sapego wrote: > > > Well, all other clients have the same version as Ignite. >

Re: [VOTE] Apache Ignite 2.5.0 RC1

+1 (binding) Checked .NET side of things: build from sources, run examples. On Thu, May 24, 2018 at 8:59 PM, Andrey Gura wrote: > Igniters, > > We've uploaded a 2.5.0 release candidate to > https://dist.apache.org/repos/dist/dev/ignite/2.5.0-rc1/ > > Git tag name is >

[jira] [Created] (IGNITE-8609) SQL: Get rid of syncronization in mvcc processor.

Pavel Kuznetsov created IGNITE-8609: --- Summary: SQL: Get rid of syncronization in mvcc processor. Key: IGNITE-8609 URL: https://issues.apache.org/jira/browse/IGNITE-8609 Project: Ignite

Re: Node.js Thin Client @ npmjs

On Thu, May 24, 2018 at 11:42 AM, Igor Sapego wrote: > Well, all other clients have the same version as Ignite. > Are there any reasons to make a Node.js client some > kind of a special case? > > I may have spoken too soon. Do we plan to include the node.js client into Ignite

Re: Node.js Thin Client @ npmjs

Well, all other clients have the same version as Ignite. Are there any reasons to make a Node.js client some kind of a special case? Best Regards, Igor On Thu, May 24, 2018 at 8:21 PM, Dmitriy Setrakyan wrote: > On Thu, May 24, 2018 at 10:03 AM, Pavel Petroshenko

Re: IGNITE-8583 - review needed

Reasonable proposal and I hope most Igniters will follow it. In the same time I've just clicked to the link https://issues.apache.org/jira/browse/IGNITE-8583 provided by Dmitriy to check ticket name, and then I've clicked to review link https://reviews.ignite.apache.org/ignite/review/IGNT-CR-623

[GitHub] ignite pull request #4064: TcpDiscoveryMulticastIpFinder changed to TcpDisco...

GitHub user antkr opened a pull request: https://github.com/apache/ignite/pull/4064 TcpDiscoveryMulticastIpFinder changed to TcpDiscoveryVmIpFinder in xm… PR for TC purposes. You can merge this pull request into a Git repository by running: $ git pull

[VOTE] Apache Ignite 2.5.0 RC1

Igniters, We've uploaded a 2.5.0 release candidate to https://dist.apache.org/repos/dist/dev/ignite/2.5.0-rc1/ Git tag name is 2.5.0-rc1 This release includes the following changes: Ignite: * Implemented Zookeeper discovery SPI. * Added Java thin client. * Added continuous queries with

Re: NodeJS thin client: full API

Pavel, Recalled that we've not described how to authenticate and set up SSL from the client side. Please consider this for the doc. Left some notes in the JIRA. -- Denis On Wed, May 23, 2018 at 12:25 PM, Denis Magda wrote: > Alexey, Pavel, > > I've done a preliminary review

Re: IGNITE-8583 - review needed

I continuously ask not to provide naked ticket numbers in the subject. Please also add titles or descriptions. I doubt anyone in the community can tell what this is about just by looking at the number. D. On Thu, May 24, 2018 at 4:09 AM, Dmitry Pavlov wrote: > Hi

Re: MTCGA & 6th mass run-all

Great outcomes! Can't wait seeing how many tests were fixed since the previous mass run. -- Denis On Thu, May 24, 2018 at 7:06 AM, Dmitry Pavlov wrote: > Hi, > > A lot of Igniters made their contributions to Make TC Green during 6 last > weeks. It is Aleksey Plekhanov,

Re: Node.js Thin Client @ npmjs

On Thu, May 24, 2018 at 10:03 AM, Pavel Petroshenko wrote: > Igor, > > Are you proposing to update the Thin Client versions on every Ignite > release regardless of the changes made to them? > > I tend to think that an independent versioning scheme for the Thin Clients >

[jira] [Created] (IGNITE-8608) .NET: Sign release NuGet packages

Pavel Tupitsyn created IGNITE-8608: -- Summary: .NET: Sign release NuGet packages Key: IGNITE-8608 URL: https://issues.apache.org/jira/browse/IGNITE-8608 Project: Ignite Issue Type:

Re: Node.js Thin Client @ npmjs

Igor, Are you proposing to update the Thin Client versions on every Ignite release regardless of the changes made to them? I tend to think that an independent versioning scheme for the Thin Clients might be more flexible/meaningful. p. On Thu, May 24, 2018 at 2:04 AM, Igor Sapego

[GitHub] ignite pull request #4063: IGNITE-8547 Use JVM serialization for enum values...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4063 IGNITE-8547 Use JVM serialization for enum values with OptimizedMarsh… …aller, avoid deadlock. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #4042: IGNITE-8547 Use JVM serialization for enum values...

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

[GitHub] ignite pull request #4051: IGNITE-8560 checkFirst and checkThrough parameter...

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

[GitHub] ignite pull request #4062: IGNITE-8567: Imputer and Binarizer

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/4062 IGNITE-8567: Imputer and Binarizer You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8567 Alternatively you can

Re: [jira] [Created] (IGNITE-8595) SQL: Ability to cancel DDL operations

Thanks for the reply, Vladimir. Is there a ticket to track the cancel feature described by you? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #4054: IGNITE-8583 fix checkpoint buffer size metric

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

[jira] [Created] (IGNITE-8607) [.NET] Support metrics changes in DataStorageMetricsMXBean

Dmitriy Govorukhin created IGNITE-8607: -- Summary: [.NET] Support metrics changes in DataStorageMetricsMXBean Key: IGNITE-8607 URL: https://issues.apache.org/jira/browse/IGNITE-8607 Project:

[jira] [Created] (IGNITE-8606) Node hangs on next exchange, when no access to marshaller's folder

Vladislav Pyatkov created IGNITE-8606: - Summary: Node hangs on next exchange, when no access to marshaller's folder Key: IGNITE-8606 URL: https://issues.apache.org/jira/browse/IGNITE-8606

[GitHub] ignite pull request #4061: IGNITE-8605 Specify jline minor version to fix nc...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4061 IGNITE-8605 Specify jline minor version to fix ncurses issue. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8605) sqlline can't work with terminal on newer ncurses

Ilya Kasnacheev created IGNITE-8605: --- Summary: sqlline can't work with terminal on newer ncurses Key: IGNITE-8605 URL: https://issues.apache.org/jira/browse/IGNITE-8605 Project: Ignite

[GitHub] ignite pull request #4060: IGN-10640 [IGNITE-8603] Add JMX-metric to cluster...

GitHub user dgladkikh opened a pull request: https://github.com/apache/ignite/pull/4060 IGN-10640 [IGNITE-8603] Add JMX-metric to cluster: baseline nodes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8604) .NET test failures probably after IGNITE-5789 merge

Dmitriy Pavlov created IGNITE-8604: -- Summary: .NET test failures probably after IGNITE-5789 merge Key: IGNITE-8604 URL: https://issues.apache.org/jira/browse/IGNITE-8604 Project: Ignite

[jira] [Created] (IGNITE-8603) Add JMX-metric to cluster: baseline nodes

Dmitriy Gladkikh created IGNITE-8603: Summary: Add JMX-metric to cluster: baseline nodes Key: IGNITE-8603 URL: https://issues.apache.org/jira/browse/IGNITE-8603 Project: Ignite Issue

MTCGA & 6th mass run-all

Hi, A lot of Igniters made their contributions to Make TC Green during 6 last weeks. It is Aleksey Plekhanov, Maxim Muzafarov, Alexey Goncharuk, Ilya Lantukh, Ivan Rakov, Alexey Kuznetsov, Taras Ledkov, Andrey Kuznetsov, Alexei Scherbakov, Ivan Fedotov, Alexander Menshikov, Andrew Medvedev,

Re: Ability to check and completely fill transactions on creation

Anton, why do you need to *alter* event sub-system to introduce a new event? Yakov's issue was that you propagated private interface to public API, which is bad of course. Come up with a clean design and it will be accepted. My problem with TransactionValidator is that it only solves a small

Re: Cache 6 Suite Execution timeouts

Hi, guys. Thanks for pointing this out. I'll look at this then I'll have available time. Possibly next week. Meanwhile I suggest not to use async rollbacks for transactions on near caches. чт, 24 мая 2018 г. в 14:09, Dmitry Pavlov : > Alexey? Could I hope you will pick

[jira] [Created] (IGNITE-8602) Add support filter label=null for control.sh tx utility

Dmitry Sherstobitov created IGNITE-8602: --- Summary: Add support filter label=null for control.sh tx utility Key: IGNITE-8602 URL: https://issues.apache.org/jira/browse/IGNITE-8602 Project: Ignite

Re: async operation is not fair async

Alexey Goncharuk, I remember we started working on async connection establishment. This should fix latency issue related to network which I believe gives the most contribution to overall latency. Mapping logic and other stuff can be ignored as it can very rarely be an issue at least on stable

[jira] [Created] (IGNITE-8601) Add to control.sh tx utility information about transaction start time

Dmitry Sherstobitov created IGNITE-8601: --- Summary: Add to control.sh tx utility information about transaction start time Key: IGNITE-8601 URL: https://issues.apache.org/jira/browse/IGNITE-8601

Re: Ticket review checklist

Petr, good point. It is more intuitive, we should mark test we can ignore by mute. So Vladimir, you or other Ignite veteran can mute test, if can say it is not important. чт, 24 мая 2018 г. в 15:07, Petr Ivanov : > Why cannot we mute (and file corresponding tickets) all

Re: Ticket review checklist

We cannot change this requirement to be softer because we need to come to sutuation of 0-failed test. If we allow commit with test failures, there will be a lot of mistakes new failures will be considered as existing. All contributors will check only new/not new failures. But actually all

Re: Ticket review checklist

Why cannot we mute (and file corresponding tickets) all test failures (including flaky) to some date and start initiative Green TC? > On 24 May 2018, at 15:04, Vladimir Ozerov wrote: > > Dmitry, > > We cannot add this requirements, because we do have failures on TC.

Re: Ticket review checklist

Dmitry, We cannot add this requirements, because we do have failures on TC. This requirement implies that all development would stop until TC is green. We never had old requirement work, neither we need to enforce it now. On Thu, May 24, 2018 at 2:59 PM, Dmitry Pavlov

Re: Baseline topology documentation clarified: usage scenarios and definition

Hi Ivan, sure, I will. чт, 24 мая 2018 г. в 14:22, Ivan Rakov : > Well, let's give it a try. > Dmitry P., will you help me with organization of gotomeeting webinar and > announcement? I think, I'll be ready to do it at the end of the next week. > > Best Regards, > Ivan

Re: Ticket review checklist

3.c 1. All test suites *MUST* be run on TeamCity [3] before merge to master, there *MUST NOT* be any test failures 'New' word should be removed because we cant separate `new` and `non new` failures. Let's imagine example, we have 50 green runs in master. And PR Run-All contains this test

[GitHub] ignite pull request #3046: IGNITE-6612: Wrap ack methods in their own class

Github user 1vanan closed the pull request at: https://github.com/apache/ignite/pull/3046 ---

Re: Ticket review checklist

Dmitry, Could you please formulate this requirement? On Wed, May 23, 2018 at 5:06 PM, Dmitry Pavlov wrote: > Hi Vladimir, > > I've replied in separate thread. > > I would like to keep requirement of Green TC instead of separation to > new/old test failures. > > Once you

Re: Baseline topology documentation clarified: usage scenarios and definition

Well, let's give it a try. Dmitry P., will you help me with organization of gotomeeting webinar and announcement? I think, I'll be ready to do it at the end of the next week. Best Regards, Ivan Rakov On 24.05.2018 14:15, Vyacheslav Daradur wrote: +1 for GoToMeeting webinar. On Thu, May 24,

Re: Baseline topology documentation clarified: usage scenarios and definition

+1 for GoToMeeting webinar. On Thu, May 24, 2018 at 2:09 PM, Dmitriy Govorukhin wrote: > +1 for a webinar, I would like to see it. > > On Wed, May 23, 2018 at 5:34 PM, Dmitry Pavlov > wrote: > >> Hi Ivan, >> >> Would you like to run

[jira] [Created] (IGNITE-8600) SQL: lazy row materialization

Vladimir Ozerov created IGNITE-8600: --- Summary: SQL: lazy row materialization Key: IGNITE-8600 URL: https://issues.apache.org/jira/browse/IGNITE-8600 Project: Ignite Issue Type: Task

Re: Cache 6 Suite Execution timeouts

Alexey? Could I hope you will pick up https://issues.apache.org/jira/browse/IGNITE-8509? чт, 24 мая 2018 г. в 14:00, Maxim Muzafarov : > Hello, > > Just bump this topic up. > > 6/10 execution timeouts for the last 10 build in master! > > Will anyone help? > > [1] > >

Re: IGNITE-8583 - review needed

Hi Dmitriy, According to upsource https://reviews.ignite.apache.org/ignite/review/IGNT-CR-623 review was already started by Alexey G. and Alexey K. Sincerely, Dmitriy Pavlov чт, 24 мая 2018 г. в 14:04, Dmitriy Govorukhin : > Igniters, > > I fixed

Re: Baseline topology documentation clarified: usage scenarios and definition

+1 for a webinar, I would like to see it. On Wed, May 23, 2018 at 5:34 PM, Dmitry Pavlov wrote: > Hi Ivan, > > Would you like to run presentation based on this slides for Igniters? > > We can set up webinar using gotomeeting if you like this idea. > > Sincerely, > Dmitriy

[jira] [Created] (IGNITE-8599) Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge from Direct IO suite

Dmitriy Pavlov created IGNITE-8599: -- Summary: Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge from Direct IO suite Key: IGNITE-8599 URL:

IGNITE-8583 - review needed

Igniters, I fixed DataStorageMetricsMXBean.getOffHeapSize, please review my changes. https://issues.apache.org/jira/browse/IGNITE-8583

Re: Cache 6 Suite Execution timeouts

Hello, Just bump this topic up. 6/10 execution timeouts for the last 10 build in master! Will anyone help? [1] https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache6=1=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E пн, 21 мая 2018 г. в 12:58, Dmitry Pavlov

Re: async operation is not fair async

So, in a current implementation, how I can perform the real async operation in one thread? Any workaround? What can I do if I have event loop thread model? On Wed, May 16, 2018 at 12:14 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Dmitriy, > > I will add technical details to the

Re: IEP-4, Phase 2. Using BL(A)T for in-memory caches.

BLAT sounds good to me because it slightly funny in case you speak russian. "Node joined topology by BLAT (po blaty)" sounds reasonable :) чт, 24 мая 2018 г. в 1:15, Dmitriy Setrakyan : > Ed, > > Anyone speaking Russian would agree that BLAT is not a good name :) Let's >

[jira] [Created] (IGNITE-8598) SQL: ability to control partition pruning with explicit affinity column definition

Vladimir Ozerov created IGNITE-8598: --- Summary: SQL: ability to control partition pruning with explicit affinity column definition Key: IGNITE-8598 URL: https://issues.apache.org/jira/browse/IGNITE-8598

Re: [jira] [Created] (IGNITE-8595) SQL: Ability to cancel DDL operations

Hi Ray, We are working on it, All operations will be cancelled in case of either explicit user request, or when user session is terminated. On Thu, May 24, 2018 at 12:51 PM, Ray wrote: > Hello Vladimir. > > From the https://apacheignite-sql.readme.io/docs/query-cancellation,

[jira] [Created] (IGNITE-8597) Direct data load

Vladimir Ozerov created IGNITE-8597: --- Summary: Direct data load Key: IGNITE-8597 URL: https://issues.apache.org/jira/browse/IGNITE-8597 Project: Ignite Issue Type: Task

Re: [jira] [Created] (IGNITE-8595) SQL: Ability to cancel DDL operations

Hello Vladimir. >From the https://apacheignite-sql.readme.io/docs/query-cancellation, it is only possible to cancel select query in java API. So select query submitted from thin client(sqlline)/jdbc/odbc is not cancellable, is my understanding correct? -- Sent from:

[jira] [Created] (IGNITE-8596) SQL: remove unnecessary index lookups when query parallelism is enabled

Vladimir Ozerov created IGNITE-8596: --- Summary: SQL: remove unnecessary index lookups when query parallelism is enabled Key: IGNITE-8596 URL: https://issues.apache.org/jira/browse/IGNITE-8596

[jira] [Created] (IGNITE-8595) SQL: Ability to cancel DDL operations

Vladimir Ozerov created IGNITE-8595: --- Summary: SQL: Ability to cancel DDL operations Key: IGNITE-8595 URL: https://issues.apache.org/jira/browse/IGNITE-8595 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-8594) Make error messages in validate_indexes command report more informative

Ivan Rakov created IGNITE-8594: -- Summary: Make error messages in validate_indexes command report more informative Key: IGNITE-8594 URL: https://issues.apache.org/jira/browse/IGNITE-8594 Project: Ignite

[jira] [Created] (IGNITE-8593) The semaphore's isBroken function doesn't work properly.

Mo created IGNITE-8593: -- Summary: The semaphore's isBroken function doesn't work properly. Key: IGNITE-8593 URL: https://issues.apache.org/jira/browse/IGNITE-8593 Project: Ignite Issue Type: Bug

Re: Node.js Thin Client @ npmjs

1. Sounds OK for me. 2. Since Node.js client is going to be included in Ignite releases, I guess it make sense to align its version with the version of Ignite, i.e. 2.6, etc... Best Regards, Igor On Thu, May 24, 2018 at 9:02 AM, Pavel Petroshenko wrote: >

[jira] [Created] (IGNITE-8592) Network partitions lead to two independent clusters

Mo created IGNITE-8592: -- Summary: Network partitions lead to two independent clusters Key: IGNITE-8592 URL: https://issues.apache.org/jira/browse/IGNITE-8592 Project: Ignite Issue Type: Bug Affects

[GitHub] ignite pull request #4059: IGNITE-8587 GridToStringBuilder use ConcurrentHas...

GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/4059 IGNITE-8587 GridToStringBuilder use ConcurrentHashMap to avoid global… … locks on classCache You can merge this pull request into a Git repository by running: $ git pull

Re: Ability to check and completely fill transactions on creation

Dmitriy, Yakov is against the solution based on event sub-system >> I think that we should think about some other solution instead of altering >> event sub-system. Also, I checked is there any chances to fix all the issues found by Yakov and see that solution becomes overcomplicated in that

[GitHub] ignite pull request #4058: IGNITE-8591

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

[jira] [Created] (IGNITE-8591) SQL: Sort links on index pages in physical page order before row access

Vladimir Ozerov created IGNITE-8591: --- Summary: SQL: Sort links on index pages in physical page order before row access Key: IGNITE-8591 URL: https://issues.apache.org/jira/browse/IGNITE-8591

Node.js Thin Client @ npmjs

Igniters, I'm finalizing the docs (with regards to installation instructions) for the Node.js Thin Client at readme.io. And I've got a couple of questions. 1. Does the name "apache-ignite-client" for the Node.js Thin Client npm module sound good to everyone? This name will be used to install the