[GitHub] ignite pull request #5345: IGNITE-10052: merged to 2.7

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/5345 IGNITE-10052: merged to 2.7 Added MVCC Tx logical WAL records. Fix PDS recover from WAL. Tests added. You can merge this pull request into a Git repository by running: $ git pull

Re: Becoming a contributor

Hi Stephen, This is good news! Added you to the list, please move on ;) -- Denis On Wed, Nov 7, 2018 at 2:31 AM Stephen Darlington < stephen.darling...@gridgain.com> wrote: > Hi, > > I’ve started to work on a couple of tickets: > > https://issues.apache.org/jira/browse/IGNITE-10155 >

Re: [DISCUSSION] The process of creating an Ignite Enhancement Proposal

Maxim, I am not quite understand what is the problem with "many major enhancements per IEP" and terms such as "optimization" or so. The very goal of initial IEP process was to accumulate global ideas, so that one may quickly understand potentially hot areas around the product. This is about

Re: SQL management and monitoring improvements

Yuri, That's an excellent idea, thank you for driving it. What is not explained is how to leverage from all that stat. For instance, how can I know a total number of SELECTs, or a total number of SELECTs happened yesterday for specific data sets. Do believe that it's feasible and just not

[GitHub] ignite pull request #5346: IGNITE-10105: Release notes for 2.7

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

[GitHub] ignite pull request #5346: IGNITE-10105: Release notes for 2.7

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/5346 IGNITE-10105: Release notes for 2.7 You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-10105 Alternatively you can

Becoming a contributor

Hi, I’ve started to work on a couple of tickets: https://issues.apache.org/jira/browse/IGNITE-10155 https://issues.apache.org/jira/browse/IGNITE-1436 It would be great if I could be added to the list of contributors so I can assign the tickets to myself. Thanks, Stephen

[GitHub] ignite pull request #5214: IGNITE-9975 Set partition counters to 0 when rese...

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

Re: Service grid redesign

I prepared a description of the implemented solution and attached it to the issue [1]. This should help during a review. Should I post the document into wiki or IEP? I'd like to ask Ignite's experts review the solution [1] [2], please? [1] https://issues.apache.org/jira/browse/IGNITE-9607 [2]

SQL management and monitoring improvements

Hi Igniters! I think we can improve Ignite management and monitoring instruments related to SQL. I've prepared draft of IEP-29: SQL management and monitoring . What do you think about it? May be do you

[jira] [Created] (IGNITE-10155) Yardstick should allow modifier when starting servers

Stephen Darlington created IGNITE-10155: --- Summary: Yardstick should allow modifier when starting servers Key: IGNITE-10155 URL: https://issues.apache.org/jira/browse/IGNITE-10155 Project: Ignite

[GitHub] ignite pull request #5332: IGNITE-10156 Fixed converting DynamicCacheDescrip...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5332 IGNITE-10156 Fixed converting DynamicCacheDescriptor to StoredCacheDa… …ta during saving You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5330: Ignite 9870

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

[jira] [Created] (IGNITE-10157) Fix inspections failures in GridTestUtils

Ivan Bessonov created IGNITE-10157: -- Summary: Fix inspections failures in GridTestUtils Key: IGNITE-10157 URL: https://issues.apache.org/jira/browse/IGNITE-10157 Project: Ignite Issue Type:

[GitHub] ignite pull request #5330: Ignite 9870

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

[GitHub] ignite pull request #5329: IGNITE-10108: Refactored a test to avoid passing ...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/5329 IGNITE-10108: Refactored a test to avoid passing anonymous classes on… … compute. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5331: GG-13597 Fixed converting DynamicCacheDescriptor ...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/5331 GG-13597 Fixed converting DynamicCacheDescriptor to StoredCacheData d… …uring saving You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5331: GG-13597 Fixed converting DynamicCacheDescriptor ...

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

[jira] [Created] (IGNITE-10159) IgniteCacheAbstractQuerySelfTest.testObjectQueryWithSwap fails non-null assertion at localPeek

Oleg Ignatenko created IGNITE-10159: --- Summary: IgniteCacheAbstractQuerySelfTest.testObjectQueryWithSwap fails non-null assertion at localPeek Key: IGNITE-10159 URL:

[jira] [Created] (IGNITE-10160) Add unique identifier for all SQL queries

Yury Gerzhedovich created IGNITE-10160: -- Summary: Add unique identifier for all SQL queries Key: IGNITE-10160 URL: https://issues.apache.org/jira/browse/IGNITE-10160 Project: Ignite

[GitHub] ignite pull request #5334: IGNITE-10118: JDBC v2 getSchema fix.

GitHub user pavel-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/5334 IGNITE-10118: JDBC v2 getSchema fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10118

[jira] [Created] (IGNITE-10154) Critical worker liveness check configuration is non-trivial and inconsistent

Artem Budnikov created IGNITE-10154: --- Summary: Critical worker liveness check configuration is non-trivial and inconsistent Key: IGNITE-10154 URL: https://issues.apache.org/jira/browse/IGNITE-10154

[GitHub] ignite pull request #5330: Ignite 9870

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

[jira] [Created] (IGNITE-10156) Invalid convertation DynamicCacheDescriptor to StoredCacheData

Anton Kalashnikov created IGNITE-10156: -- Summary: Invalid convertation DynamicCacheDescriptor to StoredCacheData Key: IGNITE-10156 URL: https://issues.apache.org/jira/browse/IGNITE-10156

[GitHub] ignite pull request #5330: IGNITE-9870 GridDhtPartitionsFullMessage#prepareM...

GitHub user voropava reopened a pull request: https://github.com/apache/ignite/pull/5330 IGNITE-9870 GridDhtPartitionsFullMessage#prepareMarshal compression parallelization. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5333: IGNITE-10157 Removed 2 extra @SuppressWarnings th...

GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/5333 IGNITE-10157 Removed 2 extra @SuppressWarnings that suppressed nothing. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10158) Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted

Oleg Ignatenko created IGNITE-10158: --- Summary: Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted Key: IGNITE-10158 URL: https://issues.apache.org/jira/browse/IGNITE-10158

[jira] [Created] (IGNITE-10153) [TC Bot] Implement tests running time report

Sergey Chugunov created IGNITE-10153: Summary: [TC Bot] Implement tests running time report Key: IGNITE-10153 URL: https://issues.apache.org/jira/browse/IGNITE-10153 Project: Ignite

[GitHub] SomeFire commented on a change in pull request #60: IGNITE-10146 Refresh missing from Git prs while full reindex

SomeFire commented on a change in pull request #60: IGNITE-10146 Refresh missing from Git prs while full reindex URL: https://github.com/apache/ignite-teamcity-bot/pull/60#discussion_r231416964 ## File path:

[GitHub] SomeFire commented on a change in pull request #60: IGNITE-10146 Refresh missing from Git prs while full reindex

SomeFire commented on a change in pull request #60: IGNITE-10146 Refresh missing from Git prs while full reindex URL: https://github.com/apache/ignite-teamcity-bot/pull/60#discussion_r231416889 ## File path:

[jira] [Created] (IGNITE-10161) Be able to cancel any query by query id

Yury Gerzhedovich created IGNITE-10161: -- Summary: Be able to cancel any query by query id Key: IGNITE-10161 URL: https://issues.apache.org/jira/browse/IGNITE-10161 Project: Ignite Issue

[GitHub] ignite pull request #5336: IGNITE-10159: IgniteCacheAbstractQuerySelfTest.te...

GitHub user avplatonov opened a pull request: https://github.com/apache/ignite/pull/5336 IGNITE-10159: IgniteCacheAbstractQuerySelfTest.testObjectQueryWithSwap fails non-null assertion at localPeek You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10165) Gather query stats and expose interfaces to access it

Yury Gerzhedovich created IGNITE-10165: -- Summary: Gather query stats and expose interfaces to access it Key: IGNITE-10165 URL: https://issues.apache.org/jira/browse/IGNITE-10165 Project: Ignite

[jira] [Created] (IGNITE-10167) MVCC-compatible IgniteCache.localEntries

Ivan Pavlukhin created IGNITE-10167: --- Summary: MVCC-compatible IgniteCache.localEntries Key: IGNITE-10167 URL: https://issues.apache.org/jira/browse/IGNITE-10167 Project: Ignite Issue

Re: Service grid redesign

Hi I think wiki is better than any attached docs. Could you please create a page? ср, 7 нояб. 2018 г., 14:39 Vyacheslav Daradur : > I prepared a description of the implemented solution and attached it > to the issue [1]. > > This should help during a review. Should I post the document into wiki

[jira] [Created] (IGNITE-10162) IgniteCacheAtomicQuerySelfTest#testTwoObjectsTextSearch fails with IgniteCheckedException: Failed to find SQL table for type: ObjectValue

Oleg Ignatenko created IGNITE-10162: --- Summary: IgniteCacheAtomicQuerySelfTest#testTwoObjectsTextSearch fails with IgniteCheckedException: Failed to find SQL table for type: ObjectValue Key: IGNITE-10162 URL:

[jira] [Created] (IGNITE-10163) Support query cancel for JDBC, ODBC and thin clients

Yury Gerzhedovich created IGNITE-10163: -- Summary: Support query cancel for JDBC, ODBC and thin clients Key: IGNITE-10163 URL: https://issues.apache.org/jira/browse/IGNITE-10163 Project: Ignite

[jira] [Created] (IGNITE-10164) Support query cancel for ODBC and thin clients

Yury Gerzhedovich created IGNITE-10164: -- Summary: Support query cancel for ODBC and thin clients Key: IGNITE-10164 URL: https://issues.apache.org/jira/browse/IGNITE-10164 Project: Ignite

[GitHub] ignite pull request #5335: IGNITE-10148. Add yardstick AWS configs

GitHub user isuntsov-gridgain opened a pull request: https://github.com/apache/ignite/pull/5335 IGNITE-10148. Add yardstick AWS configs Added yardstick AWS (S3, ELB) configs. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Created] (IGNITE-10168) SQL security monitoring

Yury Gerzhedovich created IGNITE-10168: -- Summary: SQL security monitoring Key: IGNITE-10168 URL: https://issues.apache.org/jira/browse/IGNITE-10168 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-10166) JDBC session level IO stats ON/OFF

Yury Gerzhedovich created IGNITE-10166: -- Summary: JDBC session level IO stats ON/OFF Key: IGNITE-10166 URL: https://issues.apache.org/jira/browse/IGNITE-10166 Project: Ignite Issue

[jira] [Created] (IGNITE-10169) Show tests and problems values on graphs

Nikolai Kulagin created IGNITE-10169: Summary: Show tests and problems values on graphs Key: IGNITE-10169 URL: https://issues.apache.org/jira/browse/IGNITE-10169 Project: Ignite Issue

Re: Wiki permissions to publish a new design document

Vyacheslav, I've added permission. Please check if it's working. ср, 7 нояб. 2018 г. в 17:31, Vyacheslav Daradur : > Hi, Igniters! > > I need permissions to publish a new design document describes Service > Grid implementation details. > > Could someone grant me permissions? > > Wiki's

Re: Wiki permissions to publish a new design document

Dmitriy, it works! Thank you so much! On Wed, Nov 7, 2018 at 5:38 PM Dmitriy Pavlov wrote: > > Vyacheslav, I've added permission. Please check if it's working. > > ср, 7 нояб. 2018 г. в 17:31, Vyacheslav Daradur : > > > Hi, Igniters! > > > > I need permissions to publish a new design document

[jira] [Created] (IGNITE-10170) .NET: Services.ServicesTestAsync fails

Ilya Suntsov created IGNITE-10170: - Summary: .NET: Services.ServicesTestAsync fails Key: IGNITE-10170 URL: https://issues.apache.org/jira/browse/IGNITE-10170 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #5313: IGNITE-10149: Make ignite-tf.sh executable by def...

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

[GitHub] ignite pull request #5249: IGNITE-10133: Switch to per-node TensorFlow worke...

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

[GitHub] ignite pull request #5344: IGNITE-10158 Some tests in IgniteCacheAbstractQue...

GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5344 IGNITE-10158 Some tests in IgniteCacheAbstractQuerySelfTest are incorrectly muted You can merge this pull request into a Git repository by running: $ git pull

Wiki permissions to publish a new design document

Hi, Igniters! I need permissions to publish a new design document describes Service Grid implementation details. Could someone grant me permissions? Wiki's registered e-mail: daradu...@gmail.com -- Best Regards, Vyacheslav D.

Re: Service grid redesign

Dmitriy, I published documentation in wiki: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95654584 Thank you! On Wed, Nov 7, 2018 at 5:10 PM Dmitriy Pavlov wrote: > > Hi I think wiki is better than any attached docs. Could you please create a > page? > > ср, 7 нояб. 2018 г.,

[jira] [Created] (IGNITE-10173) Gradually move unit tests from Junit 3 to newer version

Oleg Ignatenko created IGNITE-10173: --- Summary: Gradually move unit tests from Junit 3 to newer version Key: IGNITE-10173 URL: https://issues.apache.org/jira/browse/IGNITE-10173 Project: Ignite

[jira] [Created] (IGNITE-10174) migrate examples tests from Junit 3 to 4

Oleg Ignatenko created IGNITE-10174: --- Summary: migrate examples tests from Junit 3 to 4 Key: IGNITE-10174 URL: https://issues.apache.org/jira/browse/IGNITE-10174 Project: Ignite Issue

[jira] [Created] (IGNITE-10175) migrate core module tests from Junit 3 to 4

Oleg Ignatenko created IGNITE-10175: --- Summary: migrate core module tests from Junit 3 to 4 Key: IGNITE-10175 URL: https://issues.apache.org/jira/browse/IGNITE-10175 Project: Ignite Issue

[jira] [Created] (IGNITE-10176) migrate non-core modules tests from Junit 3 to 4

Oleg Ignatenko created IGNITE-10176: --- Summary: migrate non-core modules tests from Junit 3 to 4 Key: IGNITE-10176 URL: https://issues.apache.org/jira/browse/IGNITE-10176 Project: Ignite

[jira] [Created] (IGNITE-10178) change tests that fail("Ignite JIRA ticket URL") to @Ignore("Ignite JIRA ticket URL")

Oleg Ignatenko created IGNITE-10178: --- Summary: change tests that fail("Ignite JIRA ticket URL") to @Ignore("Ignite JIRA ticket URL") Key: IGNITE-10178 URL: https://issues.apache.org/jira/browse/IGNITE-10178

[jira] [Created] (IGNITE-10177) cleanup Junit 3 from the project

Oleg Ignatenko created IGNITE-10177: --- Summary: cleanup Junit 3 from the project Key: IGNITE-10177 URL: https://issues.apache.org/jira/browse/IGNITE-10177 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-10179) Change new tests root to use @BeforeClass and @AfterClass instead of isFirstTest() and isLastTest()

Oleg Ignatenko created IGNITE-10179: --- Summary: Change new tests root to use @BeforeClass and @AfterClass instead of isFirstTest() and isLastTest() Key: IGNITE-10179 URL:

[jira] [Created] (IGNITE-10180) Investigate migration from Junit 4 to 5

Oleg Ignatenko created IGNITE-10180: --- Summary: Investigate migration from Junit 4 to 5 Key: IGNITE-10180 URL: https://issues.apache.org/jira/browse/IGNITE-10180 Project: Ignite Issue Type:

Re: Is it time to move forward to JUnit4 (5)?

Hello, I created JIRA task for this move, with detailed explanation and step-by-step subtasks, your comments are welcome: - https://issues.apache.org/jira/browse/IGNITE-10173 In brief, the plan is to gradually migrate the part of tests that still uses Junit 3 (hundreds if not thousands of those

[jira] [Created] (IGNITE-10171) Running queries descriptor (GridRunningQueryInfo) contains generated SQL text instead of original SQL text

Aleksey Plekhanov created IGNITE-10171: -- Summary: Running queries descriptor (GridRunningQueryInfo) contains generated SQL text instead of original SQL text Key: IGNITE-10171 URL:

[GitHub] zzzadruga opened a new pull request #61: IGNITE-10169 Show tests and problems values on graphs

zzzadruga opened a new pull request #61: IGNITE-10169 Show tests and problems values on graphs URL: https://github.com/apache/ignite-teamcity-bot/pull/61 IGNITE-10169 Show tests and problems values on graphs instead of the build start date

[jira] [Created] (IGNITE-10172) Enabling cache statistics on a large cluster with a large number of caches can affect performance

Aleksey Plekhanov created IGNITE-10172: -- Summary: Enabling cache statistics on a large cluster with a large number of caches can affect performance Key: IGNITE-10172 URL:

[GitHub] ignite pull request #5333: IGNITE-10157 Removed 2 extra @SuppressWarnings th...

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

[DISCUSSION] The process of creating an Ignite Enhancement Proposal

Igniters, I think, our community have accumulated enough experience with the process of Ignite Enhancement Proposal (IEP) of introducing the major changes into the Apache Ignite. Now we have to take one step forward and make every major change and\or improvement clear not only for community