Re: PHP/Python versions for Thin Clients

Thanks Pavel, this makes sense now. On Tue, May 15, 2018 at 5:30 AM, Pavel Petroshenko wrote: > Hi Dmitriy, > > PHP 5.6 and 7.0 are going to be end-of-life shortly [1]. So the minimal > version for the Thin Client is going to be either 7.1 or 7.2 (I would > finalize this

[jira] [Created] (IGNITE-8489) Web Console: Landing page do not show images under Retina display

Alexey Kuznetsov created IGNITE-8489: Summary: Web Console: Landing page do not show images under Retina display Key: IGNITE-8489 URL: https://issues.apache.org/jira/browse/IGNITE-8489 Project:

[jira] [Created] (IGNITE-8488) Web console: scroll bar doesn't work inside cluster selector component

Pavel Konstantinov created IGNITE-8488: -- Summary: Web console: scroll bar doesn't work inside cluster selector component Key: IGNITE-8488 URL: https://issues.apache.org/jira/browse/IGNITE-8488

Re: PHP/Python versions for Thin Clients

Hi Dmitriy, PHP 5.6 and 7.0 are going to be end-of-life shortly [1]. So the minimal version for the Thin Client is going to be either 7.1 or 7.2 (I would finalize this along with the PHP Thin Client API proposal). As for Python, there is still some legacy code on 2.7, the oldest active 2.x

Null check removal in IGNITE-5779

Hello, In Ignite-5779 patch, CassandraSessionImpl.java line 289 a null check for row has been removed (before the change:

Re: Thin clients features wiki page

Igor, thanks for putting together the page. As for the immediate improvements, I'm backing up Alexey's suggestions. This page deserves to be moved to the readme.io. We'll do that once it's sorted out how to group the thin clients' documentation. -- Denis On Mon, May 14, 2018 at 12:39 PM,

Re: Suggestion about Docker Swarm Services and Scaling Ignite automatically

Jonathan, Thanks for the extensive summary. Personally, I like the manager node approach because it's built in Docker Swarm and doesn't require 3rd party dependencies. Moreover, it reminds me the way we supported Kubernetes where Ignite pods request IP addresses from a Kubernetes master.

Re: tracking SQL queries in 2.5

On Mon, May 14, 2018 at 3:55 PM, Vladimir Ozerov wrote: > Hi Dima, > > This is not that simple unfortunately. We need to build the whole > infrastructure for cache-less SQL queries. This is not very complex, but > require considerable efforts. Let's do that in AI 2.6 scope.

[GitHub] ignite pull request #3996: -

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/3996 - You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-8381 Alternatively you can review and apply these changes as the

Re: stopAllGrids() used by default and further steps

Yes. В Пн, 14/05/2018 в 20:48 +0300, Dmitry Pavlov пишет: > Hi Nikolay, > > Would you have a minute to finalize this review? > > Sincerely, > Dmitriy Pavlov > > пт, 4 мая 2018 г. в 16:05, Maxim Muzafarov : > > Dmitry, > > > > Task of migration to JUnit 4/5 sounds very

Thin clients features wiki page

Hello Igniters, I've created a new page in wiki, that summarizes a features availability of thin clients. It should help us to plan development of thin clients while also helping out users to understand a state of clients. Check it out and tell me what you think. And if there are some mistakes,

Re: NodeJS thin client: full API

Alexey, If a lib is contributed to Ignite (accepted to its main sources like the node.js thin client), then the documentation has to be in a single place which is readme.io for now. Having the docs both on readme.io and in sources is confusing and harder to maintain. If a lib doesn't not a part

Re: Tests coverage report of Ignite 2.5 core module

Hi Dmitry, You are right this is not a sorting, this is a ranking by two parameters where both of them equal in priority. For such task in math, we have an idea of "dominating subset". It simply too understand by example: P1, P2 E1 2, 2 E2 1, 2 E3 2, 1 E4 1, 1 Here element E1 dominate

Re: Tests coverage report of Ignite 2.5 core module

Hi Alexander, I did not quite understand how this list of top tests was obtained. It does not look like sorted. Can you clarify? Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 20:48, Александр Меньшиков : > Vyacheslav, > I have made a simple ranking for your data for

Re: Tests coverage report of Ignite 2.5 core module

Vyacheslav, I have made a simple ranking for your data for highlighting classes which more than other needs testing. Please take a look at the list which I have done (36 classes): https://drive.google.com/file/d/1RJrtnN77MeEWLTShFzqaLInCdOSb9WdC/view?usp=sharing Below you can read how did it in

Re: stopAllGrids() used by default and further steps

Hi Nikolay, Would you have a minute to finalize this review? Sincerely, Dmitriy Pavlov пт, 4 мая 2018 г. в 16:05, Maxim Muzafarov : > Dmitry, > > Task of migration to JUnit 4/5 sounds very interesting for me, but I'm not > sure that I will have time for it in the next few

Re: method arguments code style

Hi Vyacheslav, plugin was published in AI wiki, feel free to create ticket to add method code style check. Actually I'm not sure it is easy to validate code style in plugin, but I guess you know it better. Sincerely, Dmitriy Pavlov вт, 8 мая 2018 г. в 21:47, Vyacheslav Daradur

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Hi Dmitriy G, could you please pick up this review? Sincerely, Dmitriy Pavlov чт, 10 мая 2018 г. в 15:50, Александр Меньшиков : > Hi, > > I have fixed problem with the test > CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime. > > Please review and merge if

Re: One more round for PR review

Hi Alexey K, could you please check that all proposals were applied? Sincerely, Dmitriy Pavlov чт, 10 мая 2018 г. в 22:59, Igor Rudyak : > Hi guys, > > I addressed all the comments and need one more round of review for the PR: > https://github.com/apache/ignite/pull/3940 > >

[GitHub] ignite pull request #3995: IGNITE-8486: Updated ConcurrentLinkedDeque8 to ma...

GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3995 IGNITE-8486: Updated ConcurrentLinkedDeque8 to match the latest version in JSR 166 repo. You can merge this pull request into a Git repository by running: $ git pull

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hi Nikolay, I don't mean we should release TDE without WAL, I mean we can consider phase-1 as minmal mergeable chunk of functionality, which does not fail tests and contains meaningfull set of changes for TDE. Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 17:45, Nikolay Izhikov

[GitHub] ignite pull request #3994: IGNITE-8487 tmpfs is employed by ZooKeeper tests

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

Re: supporting different configuration format json,yaml...

Dmitry, We rely on Spring Framework when we start Ignite node from XML configuration. Spring doesn't easily support another formats of configuration files. I think, the main reason for this is built-in ability to validate configuration via XML Schema. We can surely hack this around (I bet

[GitHub] ignite pull request #3994: IGNITE-8487 tmpfs is employed by ZooKeeper tests

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3994 IGNITE-8487 tmpfs is employed by ZooKeeper tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: abbrevation rules plugin

Anton, thank you for pointing to this. I've updated wiki page with build and references: https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules and attached jar file https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=57901460 Thanks to Vyacheslav plugin

[jira] [Created] (IGNITE-8487) ZookeeperDiscoverySpi tests should use tmpfs on public TC

Sergey Chugunov created IGNITE-8487: --- Summary: ZookeeperDiscoverySpi tests should use tmpfs on public TC Key: IGNITE-8487 URL: https://issues.apache.org/jira/browse/IGNITE-8487 Project: Ignite

[GitHub] ignite pull request #3992: IGNITE-8469: add memory leak test case

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

Re: abbrevation rules plugin

Jar already attached to issue :) see https://issues.apache.org/jira/browse/IGNITE-5698 пн, 14 мая 2018 г. в 19:05, Dmitry Pavlov : > Hi Folks, > > I suggest to keep it in https://github.com/dspavlov/ignite-abbrev-plugin > for > the beginning. Late we can consider Apache

Re: Disable WAL for several cache groups within one exchange

Ivan, enableWal/disableWal will return false in case enabling/disabling was caused not by this call. For example it will return false in case wal already enabled/disabled. Example: boolean res1 = srv.cluster().enableWal(CACHE_NAME); boolean res2 = srv.cluster().enableWal(CACHE_NAME); assert

[jira] [Created] (IGNITE-8486) Update ConcurrentLinkedDeque in Ignite's master repository to the latest JDK version

Stanislav Lukyanov created IGNITE-8486: -- Summary: Update ConcurrentLinkedDeque in Ignite's master repository to the latest JDK version Key: IGNITE-8486 URL: https://issues.apache.org/jira/browse/IGNITE-8486

Re: abbrevation rules plugin

Hi Folks, I suggest to keep it in https://github.com/dspavlov/ignite-abbrev-plugin for the beginning. Late we can consider Apache repo. But for wiki I need some distribution to attach first. Vyacheslav, could you remind me if we already have one? пн, 14 мая 2018 г. в 19:00, Anton Vinogradov

Re: Tests coverage report of Ignite 2.5 core module

Hi Vyacheslav, Great job! I specifically happy to see jacoco.csv file into the archive. I think I can range classes by some complex criterion, like coverage/complexity. That classes could be the first in the queue for testing. 2018-05-14 17:49 GMT+03:00 Vyacheslav Daradur :

Re: abbrevation rules plugin

Hi Igniters, Vyacheslav, I had discussion about this plugin. As GridGain representative I approve change of file headers and making this tool fully opensource. So please proceed with distributive build. Best Regards, Dmitriy Palvov On Mon, May 14, 2018 at 6:28 PM Dmitry Pavlov

Re: async operation is not fair async

Alexey, Could you please add more description information for this task? [1] Perhaps, base steps for implementation. [1] https://issues.apache.org/jira/browse/IGNITE-8475 On Mon, May 14, 2018 at 4:58 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Another +1 for the true

Re: Tests coverage report of Ignite 2.5 core module

TestSuites weren't used. Set of tests classes was created as result of finding not abstract classes which names contain '*Test*' except '*TestCase*' in '/src/test/java/org/apache/ignite' as Maven does [1]. Each tests class was executed and covered separately. You can see used tests classes in

Re: Transparent Data Encryption (TDE) in Apache Ignite

Dmitry. From my point of view, WAL encryption should be done in Phase-1. We should provide only production ready features to the users, isn't it? Ticket for a phase-1 created - https://issues.apache.org/jira/browse/IGNITE-8485 I'm starting working on it and expecting to implement it in a couple

[jira] [Created] (IGNITE-8485) TDE - Phase-1

Nikolay Izhikov created IGNITE-8485: --- Summary: TDE - Phase-1 Key: IGNITE-8485 URL: https://issues.apache.org/jira/browse/IGNITE-8485 Project: Ignite Issue Type: Sub-task

[GitHub] ignite pull request #3988: IGNITE-5965 fix Flaky failure of GridServiceProce...

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

Re: Transparent Data Encryption (TDE) in Apache Ignite

Hi Nickolay, Thank you for sharing results. I would suggest to make phase 1 as small as possible, for example, skipping WAL encryption or something like that. It would not be full TDE implementation, but will allow us to move by small steps, it also allows us to merge smaller changes to master.

Re: Tests coverage report of Ignite 2.5 core module

Ok, thank you. I missed that I should download the archive first. I've found for example that method truncate in FSyncWalManager is not covered. Which test suites were executed? пн, 14 мая 2018 г. в 17:16, Vyacheslav Daradur : > Hi, Dmitry, > > Download and unpack the

Re: Tests coverage report of Ignite 2.5 core module

Hi, Dmitry, Download and unpack the archive first: https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip On Mon, May 14, 2018 at 5:12 PM, Dmitry Pavlov wrote: > Hi Vyacheslav, > >

[GitHub] ignite pull request #3976: IGNITE-8456: Print warning if IGNITE_HOME & WORK ...

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

Re: Tests coverage report of Ignite 2.5 core module

Hi Vyacheslav, https://www.dropbox.com/s/rdgs1svvojm757x/ignite-2.5-core-module-tests-coverage-report-rev-d83f1ec.zip?dl=0_subpath=%2Fcoverage-report%2Findex.html says error 400 for me. Sincerely, Dmitriy Pavlov пн, 14 мая 2018 г. в 17:06, Vyacheslav Daradur : > Hi,

[jira] [Created] (IGNITE-8484) Web Console lacks 'collocated' flag on SQL query tab

Ilya Kasnacheev created IGNITE-8484: --- Summary: Web Console lacks 'collocated' flag on SQL query tab Key: IGNITE-8484 URL: https://issues.apache.org/jira/browse/IGNITE-8484 Project: Ignite

Re: async operation is not fair async

Another +1 for the true asynchronous approach. I remember a while ago one of the Ignite users raised a similar question regarding the *async method being blocked on establishing a TCP connection. As far as deadlocks go, I have a counter-example. Currently, we check the thread-local chain only for

[GitHub] ignite pull request #3993: IGNITE-8238: Operation can fails with unexpected ...

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/3993 IGNITE-8238: Operation can fails with unexpected RuntimeException when node is stopping. For [IGNITE-8238](https://issues.apache.org/jira/browse/IGNITE-8238) You can merge this pull request into

[GitHub] ignite pull request #2776: IGNITE-6502: Print warning if -Djava.net.preferIP...

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

Re: async operation is not fair async

Andrey, Do you prefer change behavior at runtime? I guess will be better have different methods for getting cache instance with fair and not fair sync. On Mon, May 14, 2018 at 3:39 PM, Andrey Gura wrote: > +1 for fair async operations. > > But I don't like idea use

Re: Apache Ignite 2.5 release

Igniters, we are ready to start process of releasing Apache Ignite 2.5. So code freeze. No more commits to ignite-2.5 branch. Thanks! On Thu, May 10, 2018 at 8:02 PM, Andrey Gura wrote: > Igniters, > > Almost all issues for Apache Ignite 2.5 release are fixed. Issues that >

Re: tracking SQL queries in 2.5

Hi Dima, This is not that simple unfortunately. We need to build the whole infrastructure for cache-less SQL queries. This is not very complex, but require considerable efforts. Let's do that in AI 2.6 scope. On Sat, May 12, 2018 at 4:36 PM, Dmitriy Setrakyan wrote: >

Re: async operation is not fair async

+1 for fair async operations. But I don't like idea use withFairSync() method. We added xxxAsync() methods recently and withAsync() is deprecated. I think we should just make methods are async in nature and provide ability of switching to the old behaviour using flag or property. On Fri, May

[jira] [Created] (IGNITE-8482) Skip 2-phase partition release wait in case of activation or dynamic caches start

Pavel Kovalenko created IGNITE-8482: --- Summary: Skip 2-phase partition release wait in case of activation or dynamic caches start Key: IGNITE-8482 URL: https://issues.apache.org/jira/browse/IGNITE-8482

[jira] [Created] (IGNITE-8483) Per partition TTL pending tree for in-memory caches.

Andrew Mashenkov created IGNITE-8483: Summary: Per partition TTL pending tree for in-memory caches. Key: IGNITE-8483 URL: https://issues.apache.org/jira/browse/IGNITE-8483 Project: Ignite

[GitHub] ignite pull request #3992: IGNITE-8469: add memory leak test case

GitHub user Mmuzaf opened a pull request: https://github.com/apache/ignite/pull/3992 IGNITE-8469: add memory leak test case You can merge this pull request into a Git repository by running: $ git pull https://github.com/Mmuzaf/ignite leak-ignite-8469 Alternatively you can

[GitHub] ignite pull request #3991: 50 time run test

GitHub user voipp opened a pull request: https://github.com/apache/ignite/pull/3991 50 time run test You can merge this pull request into a Git repository by running: $ git pull https://github.com/voipp/ignite IGNITE-8161 Alternatively you can review and apply these changes

Re: Integration with JHipster

Hi, Ignite already can be used as Spring Cache and Hibernate L2 cache. Only this two options are provided by JHipster. So JHipster documentaton update should be enough. On Sat, May 12, 2018 at 7:09 PM, Dmitriy Setrakyan wrote: > Igniters, > > Jhipster is a very popular

[jira] [Created] (IGNITE-8481) VisorValidateIndexesJob works very slowly in case of many partitions/keys for each partition.

Alexei Scherbakov created IGNITE-8481: - Summary: VisorValidateIndexesJob works very slowly in case of many partitions/keys for each partition. Key: IGNITE-8481 URL:

[GitHub] ignite pull request #3990: IGNITE-8474 skipForExchangeMerge property changed...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3990 IGNITE-8474 skipForExchangeMerge property changed to 'true' You can merge this pull request into a Git repository by running: $ git pull

Re: SqlLine script and Java9

Tested, review and merged to master and ignite-2.5 branches (thanks to Andrey Gura for operativeness). > On 14 May 2018, at 11:40, Petr Ivanov wrote: > > Prepared patch [1], review and testing is required. > > > [1] https://github.com/apache/ignite/pull/3989 >

[jira] [Created] (IGNITE-8480) Broken Ignite Examples test Support Spring Data 2.0

Dmitriy Pavlov created IGNITE-8480: -- Summary: Broken Ignite Examples test Support Spring Data 2.0 Key: IGNITE-8480 URL: https://issues.apache.org/jira/browse/IGNITE-8480 Project: Ignite

[GitHub] ignite pull request #3775: IGNITE-8138 Uptime output with days

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

[GitHub] ignite pull request #3972: Ignite 8138 2

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

Re: NodeJS thin client: full API

- Let's rename SqlDataProcessingExample.js to just SqlExample.js and describe it as an example that shows primary APIs to use with Ignite as with an SQL database. - Let's rename SqlQueryExample.js to SqlQueryEntiriesExample.js. Updated.

[GitHub] ignite pull request #3975: IGNITE-8422 Improve tests

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

[jira] [Created] (IGNITE-8479) Web console: query text is empty on opening query section

Pavel Konstantinov created IGNITE-8479: -- Summary: Web console: query text is empty on opening query section Key: IGNITE-8479 URL: https://issues.apache.org/jira/browse/IGNITE-8479 Project: Ignite

[GitHub] ignite pull request #3692: Suspend resume benchmark

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

Re: SqlLine script and Java9

Prepared patch [1], review and testing is required. [1] https://github.com/apache/ignite/pull/3989 > On 14 May 2018, at 10:35, Petr Ivanov wrote: > > Filed the ticket [1], will fix. > > > [1]

[GitHub] ignite pull request #3989: IGNITE-8478 SqlLine run failure on Java 9

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3989 IGNITE-8478 SqlLine run failure on Java 9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8478 Alternatively

[GitHub] ignite pull request #2975: Ignite-6083 Null value has appeared in entry proc...

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

Re: SqlLine script and Java9

Filed the ticket [1], will fix. [1] https://issues.apache.org/jira/browse/IGNITE-8478 > On 12 May 2018, at 20:10, Dmitriy Setrakyan wrote: > > Igniters, > > Any reason SqlLine tool shipped with Ignite does not work

[jira] [Created] (IGNITE-8478) SqlLine run failure on Java 9

Peter Ivanov created IGNITE-8478: Summary: SqlLine run failure on Java 9 Key: IGNITE-8478 URL: https://issues.apache.org/jira/browse/IGNITE-8478 Project: Ignite Issue Type: Task