[GitHub] ignite pull request #5390: IGNITE-10184: Fixed type conflict check test in p...

GitHub user aliskhakov opened a pull request: https://github.com/apache/ignite/pull/5390 IGNITE-10184: Fixed type conflict check test in public schema. You can merge this pull request into a Git repository by running: $ git pull https://github.com/aliskhakov/ignite

[GitHub] ignite pull request #5389: Ignite 2.5.1 p160

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5389 Ignite 2.5.1 p160 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p160 Alternatively you can

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Igor, I think we shouldn't mix management and select syntax. Potentially it can be dangerous. e.g. your example you don't know set of queries which will be cancelled. Also I have not seen such approach in other databases. Yes, the syntax should work from SQL API also. вт, 13 нояб. 2018 г. в

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Denis, Under the hood 'time' will be as startTime, but for system view I planned use duration which will be simple calculated as now - startTime. So, there is't a performance issue. As I understand you mean that the view should contains both running and finished queries. If be honest for the view

[GitHub] ignite pull request #5377: IGNITE-10228 Start multiple caches in parallel ma...

GitHub user voropava reopened a pull request: https://github.com/apache/ignite/pull/5377 IGNITE-10228 Start multiple caches in parallel may lead to the fact that some of the caches won't be registered. …suboptimal batch splitting in U.doInParallel(). You can merge this pull

[GitHub] ignite pull request #5377: IGNITE-10228 Start multiple caches in parallel ma...

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

[GitHub] ignite pull request #5377: IGNITE-10028 Start multiple caches in parallel ma...

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

[GitHub] ignite pull request #5377: IGNITE-10028 Start multiple caches in parallel ma...

GitHub user voropava reopened a pull request: https://github.com/apache/ignite/pull/5377 IGNITE-10028 Start multiple caches in parallel may lead to the fact that some of the caches won't be registered. …suboptimal batch splitting in U.doInParallel(). You can merge this pull

[jira] [Created] (IGNITE-10244) Peer classloading creates a new class on each call for nested compute tasks

Mikhail Cherkasov created IGNITE-10244: -- Summary: Peer classloading creates a new class on each call for nested compute tasks Key: IGNITE-10244 URL: https://issues.apache.org/jira/browse/IGNITE-10244

[GitHub] dspavlov opened a new pull request #69: IGNITE-10243 Chain analysis entry points are get now from preloaded b…

dspavlov opened a new pull request #69: IGNITE-10243 Chain analysis entry points are get now from preloaded b… URL: https://github.com/apache/ignite-teamcity-bot/pull/69 …uilds supporting cancelled This is an automated

[GitHub] ignite pull request #5388: IGNITE-10243 Some comments update

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/5388 IGNITE-10243 Some comments update You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite ignite-10243 Alternatively you can review

[jira] [Created] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll

Dmitriy Pavlov created IGNITE-10243: --- Summary: [TC Bot] Support partially cancelled suites in RunAll Key: IGNITE-10243 URL: https://issues.apache.org/jira/browse/IGNITE-10243 Project: Ignite

[GitHub] ignite pull request #5387: Ignite 2.5.4

GitHub user antkr opened a pull request: https://github.com/apache/ignite/pull/5387 Ignite 2.5.4 Teamcity run PR. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.4 Alternatively you can review

[GitHub] ignite pull request #5386: Ignite 2.4.8 p7

GitHub user aealeksandrov opened a pull request: https://github.com/apache/ignite/pull/5386 Ignite 2.4.8 p7 Pull request was created for team city run. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #5385: Ignite 1.8.22

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

[GitHub] ignite pull request #5367: IGNITE-10227: fix unused imports configuration

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

[GitHub] ignite pull request #5384: Failure handling fix

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

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Denis, If I understand correctly, this is going to be a view, not real storage, so no real duration is going to be stored anywhere - it is going to be calculated dynamically during the SQL execution (please fix me if I wrong here). Best Regards, Igor On Tue, Nov 13, 2018 at 6:52 PM Denis Magda

[jira] [Created] (IGNITE-10242) NPE in GridDhtPartitionDemander#handleSupplyMessage when concurrently rebalancing and stopping cache in same cache group.

Ivan Daschinskiy created IGNITE-10242: - Summary: NPE in GridDhtPartitionDemander#handleSupplyMessage when concurrently rebalancing and stopping cache in same cache group. Key: IGNITE-10242 URL:

[GitHub] ignite pull request #4913: IGNITE-5935: WIP server origin transactions recov...

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

[GitHub] ignite pull request #5326: Test drive Junit4

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

[GitHub] ignite pull request #5354: Juni4 fast and rude approach

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

[GitHub] ignite pull request #5383: ignite-8735 Metastorage creates its own index par...

GitHub user SpiderRus opened a pull request: https://github.com/apache/ignite/pull/5383 ignite-8735 Metastorage creates its own index partition You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8735

[GitHub] ignite pull request #5382: IGNITE-10200 GridCacheSetAbstractSelfTest#testMul...

GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/5382 IGNITE-10200 GridCacheSetAbstractSelfTest#testMultipleStructuresInDifferentGroups and some other tests are incorrectly muted You can merge this pull request into a Git repository by running:

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Yury, Please consider the following: - If we record the duration instead of startTime, then the former has to be updated frequently - sounds like a performance red flag. Should we store startTime and endTime instead? This way a query record will be updated twice - when the query is

[GitHub] ignite pull request #5381: IGNITE-10235 Fix error with double cache register...

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5381 IGNITE-10235 Fix error with double cache registering with disabled IGNITE_ALLOW_START_CACHES_IN_PARALLEL option. You can merge this pull request into a Git repository by running: $

[GitHub] ignite pull request #5380: ignite-10223

GitHub user Salatich opened a pull request: https://github.com/apache/ignite/pull/5380 ignite-10223 ignite-10223 Add two new methods in Affinity class which returns List instead of Collection (and should replace them in future) You can merge this pull request into a Git

[GitHub] ignite pull request #5349: IGNITE-10171 Running queries descriptor contins g...

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

[jira] [Created] (IGNITE-10241) MVCC TX: orphaned remote transactions

Igor Seliverstov created IGNITE-10241: - Summary: MVCC TX: orphaned remote transactions Key: IGNITE-10241 URL: https://issues.apache.org/jira/browse/IGNITE-10241 Project: Ignite Issue

[GitHub] ignite pull request #4976: IGNITE-9557: Assert in case of explains of update...

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

[GitHub] asfgit closed pull request #68: IGNITE-9939 ObserverTask logs added

asfgit closed pull request #68: IGNITE-9939 ObserverTask logs added URL: https://github.com/apache/ignite-teamcity-bot/pull/68 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign

[GitHub] ignite pull request #5374: IGNITE-10231

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

[GitHub] ignite pull request #5378: IGNITE-10237 Fixed inspections

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

[GitHub] ignite pull request #5379: IGNITE-10098 TcpCommunicationSpi for .NET misses ...

GitHub user Max-Pudov opened a pull request: https://github.com/apache/ignite/pull/5379 IGNITE-10098 TcpCommunicationSpi for .NET misses some properties You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ololo3000 opened a new pull request #68: IGNITE-9939 ObserverTask logs added

ololo3000 opened a new pull request #68: IGNITE-9939 ObserverTask logs added URL: https://github.com/apache/ignite-teamcity-bot/pull/68 This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] ignite pull request #4919: IGNITE-8639: add test to check fix parse problem ...

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

[jira] [Created] (IGNITE-10240) Web Console: Create a new left menu

Vica Abramova created IGNITE-10240: -- Summary: Web Console: Create a new left menu Key: IGNITE-10240 URL: https://issues.apache.org/jira/browse/IGNITE-10240 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-10239) Web Console: Create a new top menu

Vica Abramova created IGNITE-10239: -- Summary: Web Console: Create a new top menu Key: IGNITE-10239 URL: https://issues.apache.org/jira/browse/IGNITE-10239 Project: Ignite Issue Type:

[GitHub] ignite pull request #4184: IGNITE-8386

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

[jira] [Created] (IGNITE-10238) Intermittent Client Nodes suite hang

Alexey Goncharuk created IGNITE-10238: - Summary: Intermittent Client Nodes suite hang Key: IGNITE-10238 URL: https://issues.apache.org/jira/browse/IGNITE-10238 Project: Ignite Issue

[GitHub] ignite pull request #4613: Ignite-6044

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

[GitHub] ignite pull request #5378: IGNITE-10237 Fixed inspections

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5378 IGNITE-10237 Fixed inspections You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10237 Alternatively you can

[GitHub] ignite pull request #5377: IGNITE-10028 Fixed race on addCacheContext/remove...

GitHub user voropava opened a pull request: https://github.com/apache/ignite/pull/5377 IGNITE-10028 Fixed race on addCacheContext/removeCacheContext, fixed … …suboptimal batch splitting in U.doInParallel(). You can merge this pull request into a Git repository by running:

[jira] [Created] (IGNITE-10237) Inspections build is broken in master

Alexey Goncharuk created IGNITE-10237: - Summary: Inspections build is broken in master Key: IGNITE-10237 URL: https://issues.apache.org/jira/browse/IGNITE-10237 Project: Ignite Issue

[jira] [Created] (IGNITE-10236) MVCC: Create "Cache 3" test suite for MVCC mode.

Andrew Mashenkov created IGNITE-10236: - Summary: MVCC: Create "Cache 3" test suite for MVCC mode. Key: IGNITE-10236 URL: https://issues.apache.org/jira/browse/IGNITE-10236 Project: Ignite

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Yuriy, Would not it be more convenient fro user to write a request in a free form, like KILL QUERY WHERE ... For example, KILL QUERY WHERE duration > 15000 Or is it going to be too hard to implement? Also, is this syntax going to work only from thin clients, or if it just designed for them,

[jira] [Created] (IGNITE-10235) Cache registered in QueryManager twice if parallel caches start is disabled

Pavel Kovalenko created IGNITE-10235: Summary: Cache registered in QueryManager twice if parallel caches start is disabled Key: IGNITE-10235 URL: https://issues.apache.org/jira/browse/IGNITE-10235

[GitHub] ignite pull request #5376: IGNITE 10233 Skip assertion check of topology in ...

GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5376 IGNITE 10233 Skip assertion check of topology in cachedAffinity() if cluster not activated. You can merge this pull request into a Git repository by running: $ git pull

Re: Assign task and getting rights

Hi Alexandr, Welcome to The Apache Software Foundation and to Apache Ignite Community. Now you are able to assign a ticket. Looking forward to your contributions. Should you have any questions, don't hesitate to ask here. A link which may help you to understand the process

[GitHub] ignite pull request #5370: GG-14435 condition was changed in assertion.

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

[jira] [Created] (IGNITE-10234) ML: Create a skeleton for model inference in Apache Ignite

Anton Dmitriev created IGNITE-10234: --- Summary: ML: Create a skeleton for model inference in Apache Ignite Key: IGNITE-10234 URL: https://issues.apache.org/jira/browse/IGNITE-10234 Project: Ignite

[jira] [Created] (IGNITE-10233) GridAffinityAssignmentCache#cachedAffinity() should not check topology version in assertion, if cluster not activated.

Sergey Antonov created IGNITE-10233: --- Summary: GridAffinityAssignmentCache#cachedAffinity() should not check topology version in assertion, if cluster not activated. Key: IGNITE-10233 URL:

Assign task and getting rights

Hello! I would like to help with task IGNITE-10223 . Please assign it to me, my jira account is Salatich. Best regards, Aleksandr Salatich

[GitHub] ignite pull request #5375: IGNITE-7822: hotfix: push down query model range ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/5375 IGNITE-7822: hotfix: push down query model range separately for each relation in case statement contains subquery that must be splitted You can merge this pull request into a Git

Re: Service grid redesign

Denis, Yakov, feel free to contact me directly in case of questions. Thanks! On Sun, Nov 11, 2018 at 10:09 PM Denis Mekhanikov wrote: > > Guys, > > I'd like to take a look at the changes before they are merged. > I'll do my best to finish the review before the end of the upcoming week. > >

[jira] [Created] (IGNITE-10232) Enhance success indication in UI

Alexander Kalinin created IGNITE-10232: -- Summary: Enhance success indication in UI Key: IGNITE-10232 URL: https://issues.apache.org/jira/browse/IGNITE-10232 Project: Ignite Issue Type:

[GitHub] ignite pull request #5286: Ignite 1.7.22

Github user Max-Pudov closed the pull request at: https://github.com/apache/ignite/pull/5286 ---

[GitHub] ignite pull request #4164: IGNITE-6295

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

Re: proposed design for thin client SQL management and monitoring (view running queries and kill it)

Igniters, Some comments for my original email's. The proposal related to part of IEP-29 . What purpose are we pursuing of the proposal? We want to be able check which queries running right now through

[GitHub] ignite pull request #5250: IGNITE-10134 fix bug in --cache list --config com...

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

[GitHub] ignite pull request #5374: IGNITE-10231

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

[GitHub] ignite pull request #5254: IGNITE-10141: Cache 3 tests optimization

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

[GitHub] ignite pull request #5373: IGNITE-6295

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

[jira] [Created] (IGNITE-10231) SQL: Extract partition pruning logic from splitter

Vladimir Ozerov created IGNITE-10231: Summary: SQL: Extract partition pruning logic from splitter Key: IGNITE-10231 URL: https://issues.apache.org/jira/browse/IGNITE-10231 Project: Ignite