[GitHub] ignite pull request #3529: IGNITE-7698: Page read during replacement should ...

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

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

Hi Igniters! I have investigated the issue [1] and found that stopping node in separate JVM may stuck thread or leave system process alive after test finished. The main reason is *StopGridTask* that we send from node in local JVM to node in separate JVM via remote computing. We send job

[GitHub] ignite pull request #3540: IGNITE-7749 Fixed testDiscoCacheReuseOnNodeJoin t...

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

[GitHub] ignite pull request #3541: IGNITE-7750 Fixed testMultiThreadStatisticsEnable...

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

[jira] [Created] (IGNITE-7785) SQL query with COUNT and UNION in sub-query produces JdbcSQLException

Pavel Vinokurov created IGNITE-7785: --- Summary: SQL query with COUNT and UNION in sub-query produces JdbcSQLException Key: IGNITE-7785 URL: https://issues.apache.org/jira/browse/IGNITE-7785 Project:

[jira] [Created] (IGNITE-7786) Changing baseline topology on big cluster may have error in control.sh utility

Dmitry Sherstobitov created IGNITE-7786: --- Summary: Changing baseline topology on big cluster may have error in control.sh utility Key: IGNITE-7786 URL: https://issues.apache.org/jira/browse/IGNITE-7786

[GitHub] ignite pull request #3556: IGNITE-3077: Test fixed

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/3556 IGNITE-3077: Test fixed You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-3077 Alternatively you can review and apply

Re: TeamCity. Ignite RDD tests

Hi Nikolay, It seems IgniteRDDSpec.IgniteRDD has appeared in configurations it is not expected to run. Please see investigations assigned to you. What can we change to avoid these tests to be included into run other suites? Sincerely, Dmitriy Pavlov пт, 16 февр. 2018 г. в 7:35, Nikolay

[GitHub] ignite pull request #3556: IGNITE-3077: Test fixed

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

Re: TeamCity. Ignite RDD tests

Hello, Dmitriy I'm looked in TeamCity but not sure what should I do. Can you explain it to me, please? В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov пишет: > Hi Nikolay, > > It seems > IgniteRDDSpec.IgniteRDD has appeared in configurations it is not expected > to run. > > Please see

Re: TeamCity. Ignite RDD tests

Hi, Nikolay Please login to TeamCity and choose "My Investigations" [1] in account menu. [1] https://ci.ignite.apache.org/investigations.html?init=1 On Thu, Feb 22, 2018 at 1:25 PM, Vyacheslav Daradur wrote: > Hi, Nikolay > > Please login to TeamCity and choose "My > > >

[jira] [Created] (IGNITE-7787) Better error reporting when issuing PDS corruptions.

Alexei Scherbakov created IGNITE-7787: - Summary: Better error reporting when issuing PDS corruptions. Key: IGNITE-7787 URL: https://issues.apache.org/jira/browse/IGNITE-7787 Project: Ignite

[jira] [Created] (IGNITE-7788) Data loss after cold restart with PDS and cache group change

Alexandr Kuramshin created IGNITE-7788: -- Summary: Data loss after cold restart with PDS and cache group change Key: IGNITE-7788 URL: https://issues.apache.org/jira/browse/IGNITE-7788 Project:

Re: TeamCity. Ignite RDD tests

Hi, Nikolay Please login to TeamCity and choose "My On Thu, Feb 22, 2018 at 1:20 PM, Nikolay Izhikov wrote: > Hello, Dmitriy > > I'm looked in TeamCity but not sure what should I do. > Can you explain it to me, please? > > В Чт, 22/02/2018 в 10:13 +, Dmitry Pavlov

[jira] [Created] (IGNITE-7789) Ignite Client Nodes: failed test IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect()

Sergey Chugunov created IGNITE-7789: --- Summary: Ignite Client Nodes: failed test IgniteClientReconnectApiExceptionTest.testErrorOnDisconnect() Key: IGNITE-7789 URL:

Re: Stop nodes after test by default - IGNITE-6842

Hi all, I've made some changes based on our previous discusstions, please see PR [1]: 1) Remove duplicated code for stopGrid (by index and by name); 2) Add new method that thows exception if not all grids haven't stopped correctly; 3) Change tests that have been affected by this changes; Also,

Re: TeamCity. Ignite RDD tests

It seems that tests I've previously muted were started in wrong configs. Is it possible IgniteRDDSpec.IgniteRDD became unit tests, which is started with code compile? This can be reason these tests appeared in suites which is not related to IgniteRDD, such as Scala Examples. чт, 22 февр. 2018

Re: Stop nodes after test by default - IGNITE-6842

Hi Maxim, Thank you. To my mind stopAllGrids call should be kept in afterTestsStop(). If developer forgot to call super(), he will see exception from beforeTestsStart() added by you. If you think patch is ready to be reviewed, please change JIRA status to "Patch Available". Optionally you can

[GitHub] ignite pull request #3558: IGNITE-6890 General way for handling Ignite failu...

GitHub user anton-vinogradov opened a pull request: https://github.com/apache/ignite/pull/3558 IGNITE-6890 General way for handling Ignite failures (NodeInvalidator… … should be replaced with IgniteFailureProcessor) Signed-off-by: Anton Vinogradov You

Re: TeamCity. Ignite RDD tests

Dmitriy. OK, I get it. Looks like scala-test-plugin I added in IGNITE-7042 doesn't handle `-Dtest=XXX` properly. I will investigate and fixed it. В Чт, 22/02/2018 в 10:28 +, Dmitry Pavlov пишет: > It seems that tests I've previously muted were started in wrong configs. > > Is it possible

[jira] [Created] (IGNITE-7793) SQL does not work if value has index filed which name equals to affinity key name

Mikhail Cherkasov created IGNITE-7793: - Summary: SQL does not work if value has index filed which name equals to affinity key name Key: IGNITE-7793 URL: https://issues.apache.org/jira/browse/IGNITE-7793

[GitHub] ignite pull request #3559: IGNITE-6552 ability to set WAL history size in MB...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/3559 IGNITE-6552 ability to set WAL history size in MBytes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6552

[GitHub] ignite pull request #3560: IGNITE-7698: Fixed test hangup, avoid to double l...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3560 IGNITE-7698: Fixed test hangup, avoid to double lock page in case of … …restore is done. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #3557: IGNITE-7763: Fixed C++ Win32 test failures

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3557 IGNITE-7763: Fixed C++ Win32 test failures You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7763 Alternatively

[jira] [Created] (IGNITE-7790) All critical errors health should be covered by IgniteFailureProcessor

Anton Vinogradov created IGNITE-7790: Summary: All critical errors health should be covered by IgniteFailureProcessor Key: IGNITE-7790 URL: https://issues.apache.org/jira/browse/IGNITE-7790

[jira] [Created] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()

Sergey Chugunov created IGNITE-7791: --- Summary: Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated() Key: IGNITE-7791 URL:

[GitHub] ignite pull request #3463: IGNITE-7489 Factor total allocated pages in data ...

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

[jira] [Created] (IGNITE-7792) IgniteDatabaseSharedManager refactoring

Igor Seliverstov created IGNITE-7792: Summary: IgniteDatabaseSharedManager refactoring Key: IGNITE-7792 URL: https://issues.apache.org/jira/browse/IGNITE-7792 Project: Ignite Issue Type:

Re: [Apache Ignite Survey] Closed, results are attached

Hi Denis, Interesting results, thank you. Unfortunately Ignite Persistence came twice in used features. And it becomes a a little bit unclear which measurement should be considered correct: max, min, or average. Sincerely, Dmitriy Pavlov чт, 22 февр. 2018 г. в 4:17, Dmitriy Setrakyan

[jira] [Created] (IGNITE-7797) Adopt yardstick tests for the new version of kNN classification algorithm

Aleksey Zinoviev created IGNITE-7797: Summary: Adopt yardstick tests for the new version of kNN classification algorithm Key: IGNITE-7797 URL: https://issues.apache.org/jira/browse/IGNITE-7797

[jira] [Created] (IGNITE-7796) Adopt kNN classification example to the new datasets

Aleksey Zinoviev created IGNITE-7796: Summary: Adopt kNN classification example to the new datasets Key: IGNITE-7796 URL: https://issues.apache.org/jira/browse/IGNITE-7796 Project: Ignite

Re: Welcome email: Kalashnikov

Thank you Dmitry, here are the details, Username:ruchircFull name:ruchir choudhryEmail:ruchirchoudhry23 at gmail dot com Regards, Ruchir On Wed, Feb 21, 2018 at 11:31 PM, Dmitry Pavlov wrote: > Hi Ruchir, > > You can sign up to apache JIRA by yourself. > > Could you

[GitHub] ignite pull request #3563: Ignite gg 13518

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

[GitHub] ignite pull request #3564: Ignite gg 13518

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

[jira] [Created] (IGNITE-7795) Correct handling partitions restored in RENTING state

Pavel Kovalenko created IGNITE-7795: --- Summary: Correct handling partitions restored in RENTING state Key: IGNITE-7795 URL: https://issues.apache.org/jira/browse/IGNITE-7795 Project: Ignite

[GitHub] ignite pull request #3565: IGNITE-7702: Adopt kNN classifcation to the new d...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3565 IGNITE-7702: Adopt kNN classifcation to the new datasets You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7702

[GitHub] ignite pull request #3555: IGNITE-7780 Fixed test ClientConnectorConfigurati...

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

Re: IgniteDataStreamer silently fails on a server node

> I set > org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl#DFLT_MAX_REMAP_CNT > to zero and see test fails now. Anton, thank you very much! I've prepared PR [1] to fix issue [2]. TC looks OK. Looks like it was introduced by commit 53802d8b46f8ee09d51ba84267f65dc6f7e73a2f

[GitHub] ignite pull request #3532: IGNITE-7686: Fix of PDS Direct IO failure: Ignite...

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

[GitHub] ignite pull request #3562: Ignite 1.7.19

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

[GitHub] ignite pull request #3560: IGNITE-7698: Fixed test hangup, avoid to double l...

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

Re: Change TC trigger from Run All to per-project basis

Hi Pavel, regarding point 1, I've created draft here https://cwiki.apache.org/confluence/display/IGNITE/Continuous+Integration I'll create new topic once it will be ready. SIncerely, Dmitriy Pavlov ср, 21 февр. 2018 г. в 10:26, Pavel Tupitsyn : > Dmitry, thanks for the

[GitHub] ignite pull request #3566: Ignite 7686-2: Licenses fix

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3566 Ignite 7686-2: Licenses fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7686-2 Alternatively you can

Re: [Apache Ignite Survey] Closed, results are attached

Oops, anyway, it's not a big deal. Let's sum them up :) On Thu, Feb 22, 2018 at 8:10 AM, Dmitry Pavlov wrote: > Hi Denis, > > Interesting results, thank you. > > Unfortunately Ignite Persistence came twice in used features. > > And it becomes a a little bit unclear which

Re: Welcome email: Kalashnikov

Hi Ruchir, You're in. Now you can any ticket you'd like. -- Denis On Thu, Feb 22, 2018 at 10:43 AM, Ruchir Choudhry < ruchirchoudhr...@gmail.com> wrote: > Thank you Dmitry, > > > here are the details, > > Username:ruchircFull name:ruchir choudhryEmail:ruchirchoudhry23 at gmail > dot com >

[jira] [Created] (IGNITE-7798) Give user an ability to check driver metrics in Cassandra store

Valentin Kulichenko created IGNITE-7798: --- Summary: Give user an ability to check driver metrics in Cassandra store Key: IGNITE-7798 URL: https://issues.apache.org/jira/browse/IGNITE-7798

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

Turik, All, The IP clearance form is ready [1], and the final vote on general@incubator is on the go [2]. Once the vote passes (72 hours), I'll finalize the process letting you know when the code can be merged. [1] http://incubator.apache.org/ip-clearance/ga-grid-ignite.html [2]

Not the best name for WAL on/off command in SQL

Vladimir, Anton, I've been reviewing the docs of WAL on/off capabilities [1] added to 2.4 and personally think that LOGGING/NOLOGGING is not the best name to turn WAL on/off with ALTER TABLE [2]. May I suggest to name it in a more human-friendly fashion such as: ALTER TABLE table

Re: Not the best name for WAL on/off command in SQL

Denis, I am not sure I like the underscore. I believe Vladimir took the command name from other RDBMS systems, but I will let him comment. D. On Thu, Feb 22, 2018 at 4:27 PM, Denis Magda wrote: > Vladimir, Anton, > > I've been reviewing the docs of WAL on/off capabilities

[GitHub] ignite pull request #3561: Ignite 1.7 master

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

[GitHub] ignite pull request #3495: ignite-7193: IgniteReflectionFactory should prope...

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

[jira] [Created] (IGNITE-7794) Marshaller mappings are not saved to disk on joining nodes

Denis Mekhanikov created IGNITE-7794: Summary: Marshaller mappings are not saved to disk on joining nodes Key: IGNITE-7794 URL: https://issues.apache.org/jira/browse/IGNITE-7794 Project: Ignite