[jira] [Created] (IGNITE-8155) Warning in log on opening of cluster tab in advanced mode

Vasiliy Sisko created IGNITE-8155: - Summary: Warning in log on opening of cluster tab in advanced mode Key: IGNITE-8155 URL: https://issues.apache.org/jira/browse/IGNITE-8155 Project: Ignite

[GitHub] ignite pull request #3763: Ignite-1.7.20

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

[jira] [Created] (IGNITE-8154) Add an ability to provide ExceptionListener to JmsStreamer

Valentin Kulichenko created IGNITE-8154: --- Summary: Add an ability to provide ExceptionListener to JmsStreamer Key: IGNITE-8154 URL: https://issues.apache.org/jira/browse/IGNITE-8154 Project:

[jira] [Created] (IGNITE-8153) Nodes fail to connect each other when SSL is enabled

Mikhail Cherkasov created IGNITE-8153: - Summary: Nodes fail to connect each other when SSL is enabled Key: IGNITE-8153 URL: https://issues.apache.org/jira/browse/IGNITE-8153 Project: Ignite

Re: IEP-18: Transparent Data Encryption

Here is a correct link to IEP: https://cwiki.apache.org/confluence/display/IGNITE/IEP-18%3A+Transparent+Data+Encryption On Thu, Apr 5, 2018 at 12:01 PM, Nikolay Izhikov wrote: > Hello, Igniters. > > Based on previous discussion [1] we've created "IEP-18: Transparent Data >

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Ivan, How can we facilitate the user here? Can we generate a meaningful exception that explains how to tackle the issue? -- Denis On Thu, Apr 5, 2018 at 2:49 AM, Ivan Rakov wrote: > Hi, > > Cache configuration is persisted in >

Re: Service grid redesign

Val, Sounds like a great solution. I'm totally for it. -- Denis On Thu, Apr 5, 2018 at 12:32 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Denis, > > This is why I'm suggesting to use DeploymentSpi for this. The way I see > this is that instead of deploying classes on local

Re: Breaking change in JDBC connection string format

Vladimir, Igor, Shouldn't we do the same for ODBC? -- Denis On Thu, Apr 5, 2018 at 5:53 AM, Vladimir Ozerov wrote: > I think colon is not very good candidate as it clashes with other > properties (e.g. host-port delimiter). Semicolon looks good to me. I'll > created a

Re: Service grid redesign

Denis, This is why I'm suggesting to use DeploymentSpi for this. The way I see this is that instead of deploying classes on local classpath, user can deploy them in the storage that SPI points to. If class is updated in the storage, Ignite detects this and automatically restarts the service. This

Re: Service grid redesign

> > There is no need to deserialize services on the coordinator. It should only > be able to calculate the assignments. > *LazyServiceConfiguration *should be used to deliver the service > configurations, just like it is done right now. Can that configuration be tweaked over the time requiring

Re: Ability to check and completely fill transactions on creation

Guys, Sorry for a dumb question but how the user is expected to use this event? -- Denis On Thu, Apr 5, 2018 at 6:06 AM, Anton Vinogradov wrote: > Igniters, > > As far as I know we're working on additional 'label' field for transactions > [1]. > That's great and will be

IEP-18: Transparent Data Encryption

Hello, Igniters. Based on previous discussion [1] we've created "IEP-18: Transparent Data Encryption" [2] I've planned to start implementation of TDE in few weeks. I will create JIRA ticket for each piece of implementation. So, please, see IEP-18 and give us feedback. Dima Ryabov, huge thanks

Re: Apache Ignite 2.5 release

Thanks Andrey! Folks, if you'd like to add anything to 2.5 please make sure it gets merged into 2.5 branch. -- Denis On Thu, Apr 5, 2018 at 11:29 AM, Andrey Gura wrote: > Hi, > > I've created branch ignite-2.5 for Apache Ignite 2.5 release. > > As always please follow the

Re: Apache Ignite 2.5 release

Hi, I've created branch ignite-2.5 for Apache Ignite 2.5 release. As always please follow the rules below when merging new commits to master: 1) If ticket is targeted for 2.5 release, please merge to master, then cherry-pick to ignite-2.5 2) Otherwise just merge to master. On Wed, Apr 4,

[GitHub] ignite pull request #3762: Ignite-7772-review

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/3762 Ignite-7772-review You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-7772-review Alternatively you can review and

Re: Trimming exceptions in IgniteUtils::cast

Stanislav, Thanks for the patch. It is a bit complex change, I will try to review it over the next weekend. --AG 2018-03-12 21:34 GMT+03:00 Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Generally, I think we should not trim any exceptions, because this way we > can unexpectedly

[GitHub] ignite pull request #3761: sql schema validation on jdbc thin connects to no...

GitHub user pavel-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3761 sql schema validation on jdbc thin connects to node. Now if we are connecting to node using thin driver and schema is incorrect, connection will be rejected Specifying quoted empty

[jira] [Created] (IGNITE-8152) Forbid empty sql schema name

Pavel Kuznetsov created IGNITE-8152: --- Summary: Forbid empty sql schema name Key: IGNITE-8152 URL: https://issues.apache.org/jira/browse/IGNITE-8152 Project: Ignite Issue Type: Bug

Re: Ability to check and completely fill transactions on creation

How about to set label name with some useful info if user does not provide custom name? For example thread name + global counter? Thoughts? -- Alexey Kuznetsov

[GitHub] ignite pull request #3760: IGNITE-8059 Integrate decision tree with partitio...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/3760 IGNITE-8059 Integrate decision tree with partition based dataset You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8151) ODBC driver should scheck schema on connection start

Pavel Kuznetsov created IGNITE-8151: --- Summary: ODBC driver should scheck schema on connection start Key: IGNITE-8151 URL: https://issues.apache.org/jira/browse/IGNITE-8151 Project: Ignite

[GitHub] ignite pull request #3758: IGNITE-8150: Fix for release suite step 1

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

Re: Service grid redesign

Denis, There is no need to deserialize services on the coordinator. It should only be able to calculate the assignments. *LazyServiceConfiguration *should be used to deliver the service configurations, just like it is done right now. Val, Usage of DeploymentSpi is a good idea, I didn't think

[GitHub] ignite pull request #3759: ignite zk merged master

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3759 ignite zk merged master You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-zk-merged-master

Re: IGNITE-6879

Thank you, Roman! 2018-04-05 17:49 GMT+03:00 Роман Меерсон : > Hi Slava, > > Fixed > > чт, 5 апр. 2018 г. в 18:41, Вячеслав Коптилин : > > > Hi Roman, > > > > please take into account my comment IgniteQueryGenerator.java > > < > >

Re: IGNITE-6879

Hi Slava, Fixed чт, 5 апр. 2018 г. в 18:41, Вячеслав Коптилин : > Hi Roman, > > please take into account my comment IgniteQueryGenerator.java > < >

Re: Ability to check and completely fill transactions on creation

Hi Igniters, I also do not see any reasons against this solution. But I have concern about performance. How can you estimate impact to performance ? Sincerely, Dmitriy Pavlov чт, 5 апр. 2018 г. в 17:20, Nikolay Izhikov : > +1 from me. > > Let's have this events! > > I

[GitHub] ignite pull request #2651: Ignite-gg12701-

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

[GitHub] ignite pull request #2353: IGNITE-5813: Inconsistent cache store state when ...

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

[GitHub] ignite pull request #2262: IGNITE-5473: Create ignite troubleshooting logger...

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

Re: IGNITE-6879

Hi Roman, please take into account my comment IgniteQueryGenerator.java Best

[GitHub] ignite pull request #3758: IGNITE-8150: Fix for release suite step 1

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3758 IGNITE-8150: Fix for release suite step 1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8150 Alternatively

Re: Ability to check and completely fill transactions on creation

+1 from me. Let's have this events! I think `EVT_USR_TX_*START*` is more convinient name for it. As far as we have method `IgniteTransctions#txStart` В Чт, 05/04/2018 в 16:06 +0300, Anton Vinogradov пишет: > Igniters, > > As far as I know we're working on additional 'label' field for

Re: Exploiting GP GPUs in Ignite ML

Hi, Andrey This is a very good question and a bit tricky one. To start with, one can argue that you already can use GPU in Ignite ML. This is because we support BLAS via netlib (IGNITE-5278) and netlib, in turn, can be configured to use NVBLAS, as explained in this library documentation:

[jira] [Created] (IGNITE-8150) Fix suite [Prepare Vote #1] .Net & C++

Igor Sapego created IGNITE-8150: --- Summary: Fix suite [Prepare Vote #1] .Net & C++ Key: IGNITE-8150 URL: https://issues.apache.org/jira/browse/IGNITE-8150 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #3757: SqlQuery hangs indefinitely with additional not r...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/3757 SqlQuery hangs indefinitely with additional not registered in baseline node. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-8149) MVCC TX Size method should use tx snapshot

Igor Seliverstov created IGNITE-8149: Summary: MVCC TX Size method should use tx snapshot Key: IGNITE-8149 URL: https://issues.apache.org/jira/browse/IGNITE-8149 Project: Ignite Issue

Ability to check and completely fill transactions on creation

Igniters, As far as I know we're working on additional 'label' field for transactions [1]. That's great and will be helpful for customers with huge deploymens to see reason of each transaction. But, since 'label' is optional field, there is no way to guarantee it will be filled. I'd like to

Re: Breaking change in JDBC connection string format

I mentioned this in the ticket. Hopefully, yes. There is a corner case when both ampersands and semicolons are there - need to think better how to handle this. On Thu, Apr 5, 2018 at 3:56 PM, Dmitriy Setrakyan wrote: > Vladimir, my older email got kind of lost. Can you

Re: Breaking change in JDBC connection string format

Vladimir, my older email got kind of lost. Can you please clarify, will we be able to support both, older and newer formats, to avoid a breaking compatibility change between releases? D. On Thu, Apr 5, 2018 at 5:53 AM, Vladimir Ozerov wrote: > I think colon is not very

Re: Breaking change in JDBC connection string format

I think colon is not very good candidate as it clashes with other properties (e.g. host-port delimiter). Semicolon looks good to me. I'll created a ticket [1] to address this. [1] https://issues.apache.org/jira/browse/IGNITE-8148 On Wed, Apr 4, 2018 at 12:35 AM, Andrey Gura

[GitHub] ignite pull request #3752: IGNITE-8139

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

Re: Upgrade from 2.1.0 to 2.4.0 resulting in error within transaction block

I've just fixed possible root cause in master [1]. However, as exact use case details is not known, may be it was something else. Is it possible to provide more info on the use case: cache configuratioh, model classes? [1] https://issues.apache.org/jira/browse/IGNITE-8147 On Mon, Apr 2, 2018 at

[jira] [Created] (IGNITE-8147) SQL: NPE during key/value pair validation

Vladimir Ozerov created IGNITE-8147: --- Summary: SQL: NPE during key/value pair validation Key: IGNITE-8147 URL: https://issues.apache.org/jira/browse/IGNITE-8147 Project: Ignite Issue Type:

[GitHub] ignite pull request #3756: IGNITE-8101: Ability to terminate system workers ...

GitHub user x-kreator opened a pull request: https://github.com/apache/ignite/pull/3756 IGNITE-8101: Ability to terminate system workers by JMX for test purp… …oses. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3755: Ignite 7712v1

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3755 Ignite 7712v1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7712v1 Alternatively you can review and apply

[GitHub] ignite pull request #3747: IGNITE-5978

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

Re: IGNITE-6879

Ok, so waiting for accept and commit чт, 5 апр. 2018 г. в 15:29, Alexey Kukushkin : > Roman, > > Just pay commiter's (Dmitry Pavlov will most likely commit your code) > attention to include the new test suite to TeamCity configuration. >

[GitHub] ignite pull request #3750: Ignite PDS 1 (Direct IO): failed test IgnitePdsCh...

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

Re: IGNITE-6879

Roman, Just pay commiter's (Dmitry Pavlov will most likely commit your code) attention to include the new test suite to TeamCity configuration.

[GitHub] ignite pull request #3514: IGNITE-7481 suspended tx timeout rollback fix

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

[jira] [Created] (IGNITE-8146) IgniteUtils classLoaderUrls() JDK9 bug

Sujit Kumar Mahapatra created IGNITE-8146: - Summary: IgniteUtils classLoaderUrls() JDK9 bug Key: IGNITE-8146 URL: https://issues.apache.org/jira/browse/IGNITE-8146 Project: Ignite

[GitHub] ignite pull request #3542: IGNITE-6842: stopAllGrids for afterTestsStop

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

Re: IGNITE-6879

Alexey, 1) Fixed 2) How could i be sure? What do i need to do? чт, 5 апр. 2018 г. в 14:24, Alexey Kukushkin : > Roman, > > Just two small comments from me: > >1. I suggest renaming IgniteSpringDataTestSuite to >IgniteSpringData2TestSuite: we must be able to

Re: IGNITE-6879

Roman, Just two small comments from me: 1. I suggest renaming IgniteSpringDataTestSuite to IgniteSpringData2TestSuite: we must be able to test both spring-data and spring-data-2 JARs with single "mvn test" 2. Make sure "Ignite Spring Data" test job in TeamCity is extended to run

[GitHub] ignite pull request #3754: fix to avoid race between auto-activation and exp...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3754 fix to avoid race between auto-activation and explicit activation You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3684: IGNITE-7712 Server-side system property IGNITE_SQ...

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

[GitHub] ignite pull request #3666: IGNITE-7712 Add flag IGNITE_SQL_LAZY_RESULT_SET f...

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

Re: Data Loss while upgrading custom jar from old jar in server and client nodes

Hi, Cache configuration is persisted in db\{consistent-ID}\cache-{cache-name}\cache_data.dat file. It's just CacheConfiguration serialized by JDK marshaller. Try to delete this file and start cache with new configuration (with correct factory class names). All your data will persist as long

[GitHub] ignite pull request #3753: Attempting to fix hanging suite

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3753 Attempting to fix hanging suite You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13667 Alternatively you

[GitHub] ignite pull request #3752: IGNITE-8139

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

[jira] [Created] (IGNITE-8145) Web console: Implement test to check missed new fields in configurations, and SPIs, and...

Vasiliy Sisko created IGNITE-8145: - Summary: Web console: Implement test to check missed new fields in configurations, and SPIs, and... Key: IGNITE-8145 URL: https://issues.apache.org/jira/browse/IGNITE-8145

[jira] [Created] (IGNITE-8144) Web console: UI issue in tables

Pavel Konstantinov created IGNITE-8144: -- Summary: Web console: UI issue in tables Key: IGNITE-8144 URL: https://issues.apache.org/jira/browse/IGNITE-8144 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3751: IGNITE-8143: Modified fetching EXTERNAL_LIBS for ...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/3751 IGNITE-8143: Modified fetching EXTERNAL_LIBS for docker container. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-8143

Re: IGNITE-6879

I`ve finished with new module: https://github.com/apache/ignite/pull/3704 чт, 5 апр. 2018 г. в 12:06, Роман Меерсон : > Ok guys, I`ll made changes but what should we do with examples and with > Spring module version? > > Exemples couldn`t support both versions, so should i

[jira] [Created] (IGNITE-8143) Feching EXTERNAL_LIBS for docker container fails

Roman Shtykh created IGNITE-8143: Summary: Feching EXTERNAL_LIBS for docker container fails Key: IGNITE-8143 URL: https://issues.apache.org/jira/browse/IGNITE-8143 Project: Ignite Issue

Re: IGNITE-6879

Ok guys, I`ll made changes but what should we do with examples and with Spring module version? Exemples couldn`t support both versions, so should i leave upgraded to 2.0 version? Spring module was upgraded to newest version, so should i leave it on newest version? чт, 5 апр. 2018 г. в 0:17,

[jira] [Created] (IGNITE-8142) Web Console: Fix change detection logic on configuration.

Alexey Kuznetsov created IGNITE-8142: Summary: Web Console: Fix change detection logic on configuration. Key: IGNITE-8142 URL: https://issues.apache.org/jira/browse/IGNITE-8142 Project: Ignite