Re: Ability to check and completely fill transactions on creation

Anton, We cannot have TransactionStartedEvent without having events for all other transaction states, like TransactionPreparedEvent, TransactionCommittedEvent, etc. Considering this, I sill do not like the design, as we would have to create many extra event classes. Instead, I would suggest that

[jira] [Created] (IGNITE-8641) SpringDataExample should use example-ignite.xml config

Andrey Gura created IGNITE-8641: --- Summary: SpringDataExample should use example-ignite.xml config Key: IGNITE-8641 URL: https://issues.apache.org/jira/browse/IGNITE-8641 Project: Ignite Issue

Re: Platform .NET add to RunAll Basic suite

Sorry for the late notice, but there are no tests in that PR, so the regression is possible again. Let's not rely on .NET tests for this. On Tue, May 29, 2018 at 5:14 PM, Dmitry Pavlov wrote: > Hi Igniters, Pavel, Ilya, > > Ilya's fix is merged to master. Ilya, thank you for contribution. > >

[jira] [Created] (IGNITE-8642) Failure processor should dump state of all threads

Andrey Gura created IGNITE-8642: --- Summary: Failure processor should dump state of all threads Key: IGNITE-8642 URL: https://issues.apache.org/jira/browse/IGNITE-8642 Project: Ignite Issue

List of Companies who use Internet of things

Hello there, I would like to know if you are interested in acquiring Internet of things (IoT) Users List. Information fields: Names, Title, Email, Phone, Company Name, Company URL, Company physical address, SIC Code, Industry, Company Size (Revenue and Employee). If interested, let me

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpitimeouts

Stan, OK, I got confused a little :) I do agree that TcpDiscoverySpi.networkTimeout should inherit from IgniteConfiguration.networkTImeout if not set explicitly. Do we have the same setting for TcpCommunicationSpi, BTW? If yes, behavior should be consistent. As for

Re: MTCGA & 6th mass run-all

Hi Igniters, New results (433 - tests, 22-suites). We can mention there is regression since last mass run (3 weeks ago it was (361, 12)). We can notice 1) a lot of new timeouts ocurred 2) ~72 tests came from bug indicated by .NET tests (bug was discussed in separate thread and already fixed by

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

NuGet (.NET) packages pushed: https://www.nuget.org/packages?q=Apache.Ignite On Tue, May 29, 2018 at 8:59 PM, Andrey Gura wrote: > Dmitry, > > First we should check docker images. Also we are waiting for > publishing of artifacts to Maven Central. > > On Tue, May 29, 2018 at 8:24 PM, Dmitriy

[GitHub] ignite pull request #4091: IGNITE-8642: Added thread dumping to FailureProce...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4091 IGNITE-8642: Added thread dumping to FailureProcessor. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Dmitry, First we should check docker images. Also we are waiting for publishing of artifacts to Maven Central. On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan wrote: > > > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura wrote: >> >> RPM and DEB packages are published to bintray [1] [2] >> >>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Andrey, Please help to generate 2.5 release HTML file and add it to Ignite website SVN. Sergey K and Ilya S. should be able to assist with this. Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We can't announce the release and close it without having the docs done. -- Denis

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

I just tried the Debian install. This is what I got after executing "sudo apt get" command: > > *E: The repository 'https://apache.org/dist/ignite/deb > apache-ignite Release' does not have a > Release file.N: Updating from such a repository can't be done

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Peter, I updated the RPM and DEB description on the downloads page[1] (following the instructions on the documentation [2]). Please check that the repositories and installation instructions are up-to-date. [1] https://ignite.apache.org/download.cgi#rpm-package [2]

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Pavel, Thanks a lot! вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn : > NuGet (.NET) packages pushed: > https://www.nuget.org/packages?q=Apache.Ignite > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura wrote: > >> Dmitry, >> >> First we should check docker images. Also we are waiting for >>

[jira] [Created] (IGNITE-8634) Web Console: Remove shadow from "Beta" ribbon and header delimeter.

Alexey Kuznetsov created IGNITE-8634: Summary: Web Console: Remove shadow from "Beta" ribbon and header delimeter. Key: IGNITE-8634 URL: https://issues.apache.org/jira/browse/IGNITE-8634 Project:

[jira] [Created] (IGNITE-8635) Add a method to inspect BinaryObject size

Alexey Goncharuk created IGNITE-8635: Summary: Add a method to inspect BinaryObject size Key: IGNITE-8635 URL: https://issues.apache.org/jira/browse/IGNITE-8635 Project: Ignite Issue

Re: Platform .NET add to RunAll Basic suite

Dmitry, the fix looks good to me, I would appreciate if you merge it. Thanks, Pavel On Tue, May 29, 2018 at 12:02 AM, Dmitry Pavlov wrote: > Hi Pavel, > > Thank you for pointing to this. We've noticed that, and Ilya K. has already > prepared the fix, >

[jira] [Created] (IGNITE-8643) Web console: Invalid chart width

Vasiliy Sisko created IGNITE-8643: - Summary: Web console: Invalid chart width Key: IGNITE-8643 URL: https://issues.apache.org/jira/browse/IGNITE-8643 Project: Ignite Issue Type: Bug

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

I’ve updated instructions correspondingly: it seems that redirect from https to https requires more complicated rules, which I will try to introduce in next release (2.6). Currently we should use http, i. e. ignite.list should be look like this: deb http://apache.org/dist/ignite/deb/

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

Instructions for RPM Package Installation (snippet with repository configuration) at ignite.apache.org are obsolete and should be replaced by apacheignite.readme.io snippet. > On 30 May 2018, at 02:57, Prachi Garg wrote: > > Peter, > > I updated the RPM and DEB description on the downloads

[jira] [Created] (IGNITE-8644) CacheMetrics.getCacheMisses() returns incorrect values

Roman Guseinov created IGNITE-8644: -- Summary: CacheMetrics.getCacheMisses() returns incorrect values Key: IGNITE-8644 URL: https://issues.apache.org/jira/browse/IGNITE-8644 Project: Ignite

[GitHub] ignite pull request #4085: Ignite 8476 no macs

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/4085 Ignite 8476 no macs You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8476-nomacs Alternatively you can review and

[GitHub] ignite pull request #4083: IGNITE-8476 AssertionError exception occurs when ...

GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/4083 IGNITE-8476 AssertionError exception occurs when trying to remove nod… You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #4087: IGNITE-8636 debug logging for client join scenari...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4087 IGNITE-8636 debug logging for client join scenario You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-8639) Query with a lot of nesting causes NPE in org.h2.util.StringUtils.indent

Ilya Kasnacheev created IGNITE-8639: --- Summary: Query with a lot of nesting causes NPE in org.h2.util.StringUtils.indent Key: IGNITE-8639 URL: https://issues.apache.org/jira/browse/IGNITE-8639

[GitHub] ignite pull request #4072: IGNITE-8604 Avoid starting cache templates on cli...

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

Re: Ability to check and completely fill transactions on creation

Dmitriy, I fixed design according to your and Yakov's comments, thanks again for clear explanation. >> 1. You use internal API in public event, i.e. you cannot have user >> accessing to IgniteInternalTx instance through TxEvent. Event definition changed to public class TransactionStartedEvent

[jira] [Created] (IGNITE-8638) CPP Thin: Implement Cache API for C++ thin client

Igor Sapego created IGNITE-8638: --- Summary: CPP Thin: Implement Cache API for C++ thin client Key: IGNITE-8638 URL: https://issues.apache.org/jira/browse/IGNITE-8638 Project: Ignite Issue Type:

[GitHub] ignite pull request #4086: IGNITE-8530 fixed onNodeLeft for InitNewCoordinat...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/4086 IGNITE-8530 fixed onNodeLeft for InitNewCoordinatorFuture You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8530

[jira] [Created] (IGNITE-8637) Web Console: Fix the UI bugs

Vica Abramova created IGNITE-8637: - Summary: Web Console: Fix the UI bugs Key: IGNITE-8637 URL: https://issues.apache.org/jira/browse/IGNITE-8637 Project: Ignite Issue Type: Bug

Re: IGNITE-640: multimap initial implementation

Hi Amir, As far as I know, several Igniters provided some feedback in ticket. Are you agree? Sincerely, Dmitriy Pavlov чт, 10 мая 2018 г. в 20:01, Dmitry Pavlov : > Hi Amir, > > This is a very necessary contribution, the patch defenetely will not be > ignored. > > Igniters, > > Who can make a

[GitHub] ignite pull request #4077: IGNITE-8624: Add reproducer to IGNITE-8624 issue.

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

Re: IGNITE-6827 - Review needed.

Hi Nick, I can't find any timeouts specified for transaction creation in IGNITE-6967 code (for services cache), so I'm not sure current fix wil help. But anyway soon it can be double-checked with 2.5 release. I hope IGNITE-6967 will be fixed soon in the IEP-17. Vyacheslav Daradur picked up this

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

RPM and DEB packages are published to bintray [1] [2] [1] https://bintray.com/apache/ignite-rpm [2] https://bintray.com/apache/ignite-deb On Mon, May 28, 2018 at 5:38 PM, Andrey Gura wrote: > Igniters, > > Apache Ignite 2.5.0 release (RC1) has been accepted. > > 4 "+1" binding votes received: >

IGNITE-8238

Hi, Andrew. You suggested continuing the discussion on dev-list about IGNITE-8238 [1] I have reworked my PR [2]. Have I moved in the right direction? I see 57 usages of `checkpointReadLock` in the core module (without tests). And it still unclear for me should I catch all exceptions from

[GitHub] ignite pull request #4089: Ignite 6587 true

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4089 Ignite 6587 true For TC tests now You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6587-true

[GitHub] ignite pull request #4043: IGNITE-8406

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

Re: Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.

Hi Ray, Status of this ticket is In Progress, so it is not displayed in filters. Could you please set status to Patch Available if PR is ready for review? Sincerely, Dmitriy Pavlov пн, 28 мая 2018 г. в 8:40, Ray : > Valentin Kulichenko and Nikolay Izhikov can you please take a look at PR >

[GitHub] ignite pull request #4087: IGNITE-8636 debug logging for client join scenari...

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

[GitHub] ignite pull request #4088: ignite-7163 Validate connection from a pre-previo...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/4088 ignite-7163 Validate connection from a pre-previous node You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1917: IGNITE-5011: Add validation on args and show prop...

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

Re: Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.

Hi Ray, Could you also please resolve conflicts in PR? Conflicting files modules/spark-2.10/pom.xml вт, 29 мая 2018 г. в 18:19, Dmitry Pavlov : > Hi Ray, > > Status of this ticket is In Progress, so it is not displayed in filters. > > Could you please set status to Patch Available if PR is

[GitHub] ignite pull request #4090: IGNITE-8610 Checkpoint history search fix + refac...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4090 IGNITE-8610 Checkpoint history search fix + refactoring You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8610

Re: NodeJS thin client: full API

Hi Pavel, Thanks for prompt improvements. I'll check them this week. -- Denis On Sun, May 27, 2018 at 5:04 PM, Pavel Petroshenko wrote: > Hi Denis, > > Thanks for your feedback on the documentation! I addressed all your > comments from https://issues.apache.org/jira/browse/IGNITE-8589. > >

Re: IGNITE-8238 - Operation can fails with unexpected RuntimeException when node is stopping

As suggested before, please do not put blank ticket numbers into subjects because no one understands ticket numbers. Please add titles or some other context to the subject. This will improve the level of engagement from the community. I have changed the subject of this thread, let's continue the

Re: I am sorry for causing confusion. IGNITE-6531

Hello, Thanks for outlining your problem and sending a patch for it. In general, if such minor improvements help to solve business cases, then I would add them to the project. Guess, we might need to rename the interface method. Dmitriy P., as one of the reviewers, could you please chime in and