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

[aliskhakov]

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 ignite-10184

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5390.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5390


commit ccbac72bc2dd454cb47f15dbe2a968490d025fe1
Author: Albert Iskhakov 
Date:   2018-11-13T08:51:04Z

IGNITE-10184: Fixed type conflict check test in public schema.

commit b92930c5e5082ad319c4128e7e4054a224d365c8
Author: Albert Iskhakov 
Date:   2018-11-13T17:54:43Z

IGNITE-10184: Unnecessary checks are removed.

commit caa1234c4fe3818d6368db0c0bf023491a6bc9d4
Author: Albert Iskhakov 
Date:   2018-11-13T18:02:36Z

IGNITE-10184: Fixed the order of imports.




---

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

[antonovsergey93]

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 review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5389.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5389


commit 1505b240c03e9fb626a6abf0009f37b0f2c105d5
Author: Slava Koptilin 
Date:   2018-07-16T13:40:56Z

IGNITE-1094 Fixed hanging during cache initialization

Signed-off-by: Andrey Gura 

commit 54a33672ab1c673fff7145610c8aedce9539abef
Author: Sergey Chugunov 
Date:   2018-07-16T14:27:49Z

IGNITE-8897 Node with longer BaselineHistory joining the cluster causes 
cluster stopping. - Fixes #4357.

Signed-off-by: Dmitriy Pavlov 

(cherry-picked from commit#e7c3566d11d6276b18a8c54e7b7f9bf3f9b3126a)

commit 43cf9b1897bd0f01f7f0e93fda6a24d7efd2115d
Author: Ivan Daschinskiy 
Date:   2018-07-16T14:18:21Z

IGNITE-8820 Add ability to accept changing txTimeoutOnPartitionMapExchange 
while waiting for pending transactions. - Fixes #4217.

Signed-off-by: Ivan Rakov 

(cherry picked from commit 09ce06c)

commit bac613b50c06dec633ff415ba3b8927730a228be
Author: Dmitriy Govorukhin 
Date:   2018-07-06T16:09:57Z

IGNITE-8827 Disable WAL during apply updates on recovery

Signed-off-by: Andrey Gura 

(cherry picked from commit 8adff24)

commit b18f5a7158cd7d04d8d4477e77854871bd4371e3
Author: ezagumennov 
Date:   2018-07-16T14:15:05Z

IGNITE-8745 Add ability to monitor TCP discovery ring information - Fixes 
#4256.

Signed-off-by: Ivan Rakov 

commit 489acccb2408ffb1ef103e94040a1c268fba2d31
Author: Dmitriy Govorukhin 
Date:   2018-07-17T13:48:43Z

IGNITE-8684 Fixed infinite loop of partition single/full messages when 
partition state does not change - Fixes #4287.

(cherry picked from commit dd47fab)

commit 7437c1a2060393891b69463865fdd1e843715232
Author: Dmitriy Govorukhin 
Date:   2018-07-17T14:23:28Z

Merge remote-tracking branch 'professional/ignite-2.5.1-master' into 
ignite-2.5.1-master

commit 0ae822cba971687256f7b8843e5ff61b7f6dc936
Author: Ivan Daschinskiy 
Date:   2018-07-17T13:52:22Z

IGNITE-8975 Invalid initialization of compressed archived WAL segment when 
WAL compression is switched off. - Fixes #4345.

Signed-off-by: Ivan Rakov 

(cherry picked from commit 46db052)

commit b5ce4f44fd767c178daa9b05590368b0e9e648cd
Author: Eduard Shangareev 
Date:   2018-07-12T16:26:48Z

IGNITE-8955 Fix of test after Checkpoint can't get write lock if massive 
eviction on node start started

(cherry picked from commit 584a88d)
Signed-off-by: EdShangGG 

commit 4e3d700056eb83403a25ccff4eed19d540e5e54d
Author: DmitriyGovorukhin 
Date:   2018-07-18T13:16:58Z

IGNITE-8929 Do not disable WAL if node does not have MOVING partitions. 
Fixes #4372

(cherry picked from commit 2b22933)

commit 4ac50fdc42b3df41bcf2054a0e8f7264929fd2e1
Author: Eduard Shangareev 
Date:   2018-07-20T14:22:52Z

IGNITE-9039 Fixed non-releasing pinned page on throttling fallback - Fixes 
#4390.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 0b0)

commit afeaeea37a687c7329ae98a1a1925abf7727a812
Author: Evgeny Stanilovskiy 
Date:   2018-07-23T08:56:21Z

IGNITE-8892 Fixed OOME when scan query is used for a big partition - Fixes 
#4391.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit a164296)

commit 47d299c4961143f27d1f8aaa0d8c8e26b8ade7ed
Author: Evgeny Stanilovskiy 
Date:   2018-07-23T08:56:21Z

IGNITE-8892 Fixed OOME when scan query is used for a big partition - Fixes 
#4391.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit a164296)

commit a6a09865f776453ed88c093f4a58852ecb7efb0e
Author: Andrey V. Mashenkov 
Date:   2018-07-23T09:39:17Z

Merge remote-tracking branch 'origin/ignite-2.5.1-master' into 
ignite-2.5.1-master

commit e2695cd960b7f0cbbba545ef60645ea964f3d7fa
Author: Dmitriy Govorukhin 
Date:   2018-07-23T08:25:49Z

IGNITE-9042 Fixed partial tranasaction state wheh transaction is timed out 
- Fixes #4397.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 33f485a)

commit 702c31859251738b187e8db2a8155264f39b8b52
Author: Ivan Daschinskiy 
Date:   2018-07-23T12:29:08Z

IGNITE-8820 Fix rollback logic when tx is initiated from client. - Fixes 
#4399.

Signed-off-by: Alexey Goncharuk 

(cherry picked from commit 5794eb0)

commit 32777e77797f4cf3260d42d4ca408336247d4e55
Author: Dmitriy Govorukhin 
Date:   2018-07-23T15:01:37Z

IGNITE-9049 Fixed write of SWITCH_SEGMENT_RECORD at the end of a segment 
file - Fixes 

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 г. в 14:20, Igor Sapego :

> 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, but will also be usable from basic SQL API?
>
> Best Regards,
> Igor
>
>
> On Tue, Nov 13, 2018 at 12:15 PM Юрий  wrote:
>
> > Igniters,
> >
> > Some comments for my original email's.
> >
> > The proposal related to part of IEP-29
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > .
> >
> > What purpose are we pursuing of the proposal?
> > We want to be able check which queries running right now through thin
> > clients. Get some information related to the queries and be able to
> cancel
> > a query if it required for some reasons.
> > So, we need interface to get a running queries. For the goal we propose
> > running_queries system view. The view contains unique query identifier
> > which need to pass to kill query command to cancel the query.
> >
> > What do you think about fields of the running queries view? May be some
> > useful fields we could easy add to the view.
> >
> > Also let's discuss syntax of cancellation of query. I propose to use
> MySQL
> > like syntax as easy to understand and shorter then Oracle and Postgres
> > syntax ( detailed information in IEP-29
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > ).
> >
> >
> >
> > пн, 12 нояб. 2018 г. в 19:28, Юрий :
> >
> > > Igniters,
> > >
> > > Below is a proposed design for thin client SQL management and
> monitoring
> > > to cancel a queries.
> > >
> > > 1) Ignite expose system SQL view with name *running_queries*
> > > proposed columns: *node_id, query_id, sql, schema_name, connection_id,
> > > duration*.
> > >
> > > node_id - initial node of request
> > > query_id - unique id of query on node
> > > sql - text of query
> > > schema name - name of sql schema
> > > connection_id - id of client connection from
> > ClientListenerConnectionContext
> > > class
> > > duration - duration in millisecond from start of query
> > >
> > >
> > > Ignite will gather info about running queries from each of nodes and
> > > collect it during user query. We already have most of the information
> at
> > GridRunningQueryInfo
> > > on each of nodes.
> > >
> > > Instead of duration we can use start_time, but I think duration will be
> > > simple to use due to it not depend on a timezone.
> > >
> > >
> > > 2) Propose to use following syntax to kill a running query:
> > >
> > > *KILL QUERY node_Id query_id*
> > >
> > >
> > > Both parameters node_id and query_id can be get through running_queries
> > > system view.
> > >
> > > When a node receive such request it can be run locally in case node
> have
> > > given node_id or send message to node with given id. Because node have
> > > information about local running queries then can cancel it - it already
> > > implemented in GridReduceQueryExecutor.cancelQueries(qryId) method.
> > >
> > > Comments are welcome.
> > > --
> > > Живи с улыбкой! :D
> > >
> >
> >
> > --
> > Живи с улыбкой! :D
> >
>


-- 
Живи с улыбкой! :D

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 I was going to use just queries
running right now. For finished queries I thought about another view with
another set of fields which should include I/O related ones. Is it works?

For "KILL QUERY node_id query_id"  node_id required as part of unique key
of query and help understand Ignite which node start the distributed query.
Use both parameters will allow cheap generate unique key across all nodes.
Node which started a query can cancel it on all nodes participate nodes.
So, to stop any queries initially we need just send the cancel request to
node who started the query. This mechanism is already in Ignite.

Native SQL APIs will automatically support the futures after implementing
for thin clients. So we are good here.



вт, 13 нояб. 2018 г. в 18:52, Denis Magda :

> 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 started and terminated.
>- In the IEP you've mentioned I/O related fields that should help to
>grasp why a query runs that slow. Should they be stored in this view?
>- "KILL QUERY query_id" is more than enough. Let's not add "node_id"
>unless it's absolutely required. Our queries are distributed and
> executed
>across several nodes that's why the node_id parameter is redundant.
>- This API needs to be supported across all our interfaces. We can start
>with JDBC/ODBC and thin clients and then support for the native SQL APIs
>(Java, Net, C++)
>- Please share examples of SELECTs in the IEP that would show how to
>find long running queries, queries that cause a lot of I/O troubles.
>
> --
> Denis
>
> On Tue, Nov 13, 2018 at 1:15 AM Юрий  wrote:
>
> > Igniters,
> >
> > Some comments for my original email's.
> >
> > The proposal related to part of IEP-29
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > .
> >
> > What purpose are we pursuing of the proposal?
> > We want to be able check which queries running right now through thin
> > clients. Get some information related to the queries and be able to
> cancel
> > a query if it required for some reasons.
> > So, we need interface to get a running queries. For the goal we propose
> > running_queries system view. The view contains unique query identifier
> > which need to pass to kill query command to cancel the query.
> >
> > What do you think about fields of the running queries view? May be some
> > useful fields we could easy add to the view.
> >
> > Also let's discuss syntax of cancellation of query. I propose to use
> MySQL
> > like syntax as easy to understand and shorter then Oracle and Postgres
> > syntax ( detailed information in IEP-29
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > ).
> >
> >
> >
> > пн, 12 нояб. 2018 г. в 19:28, Юрий :
> >
> > > Igniters,
> > >
> > > Below is a proposed design for thin client SQL management and
> monitoring
> > > to cancel a queries.
> > >
> > > 1) Ignite expose system SQL view with name *running_queries*
> > > proposed columns: *node_id, query_id, sql, schema_name, connection_id,
> > > duration*.
> > >
> > > node_id - initial node of request
> > > query_id - unique id of query on node
> > > sql - text of query
> > > schema name - name of sql schema
> > > connection_id - id of client connection from
> > ClientListenerConnectionContext
> > > class
> > > duration - duration in millisecond from start of query
> > >
> > >
> > > Ignite will gather info about running queries from each of nodes and
> > > collect it during user query. We already have most of the information
> at
> > GridRunningQueryInfo
> > > on each of nodes.
> > >
> > > Instead of duration we can use start_time, but I think duration will be
> > > simple to use due to it not depend on a timezone.
> > >
> > >
> > > 2) Propose to use following syntax to kill a running query:
> > >
> > > *KILL QUERY node_Id query_id*
> > >
> > >
> > > Both parameters node_id and query_id can be get through running_queries
> > > system view.
> > >
> > > When a node receive such request it can be run locally in case node
> have
> > > given node_id or send message to node with given id. Because node have
> > > information about local running queries then can cancel it - it already
> > > implemented in GridReduceQueryExecutor.cancelQueries(qryId) method.
> > >
> > > Comments are welcome.
> > > --
> > > Живи с улыбкой! :D
> > >
> >
> >
> > --
> > Живи с 

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

[voropava]

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 request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10228

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5377.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5377


commit 3a146d54ca6eef07a90fafc1ac4ce6f0deeda5a6
Author: Pavel Voronkin 
Date:   2018-08-14T18:20:50Z

IGNITE-10028 Fixed race on addCacheContext/removeCacheContext, fixed 
suboptimal batch splitting in U.doInParallel().

commit 8c93ced97960a85fd4d2a24e1fdefaa3e75bebda
Author: Pavel Voronkin 
Date:   2018-08-14T18:20:50Z

IGNITE-10028 Review fixes.




---

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

[voropava]

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...

[voropava]

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...

[voropava]

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 request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-10228

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5377.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5377


commit 3a146d54ca6eef07a90fafc1ac4ce6f0deeda5a6
Author: Pavel Voronkin 
Date:   2018-08-14T18:20:50Z

IGNITE-10028 Fixed race on addCacheContext/removeCacheContext, fixed 
suboptimal batch splitting in U.doInParallel().

commit 8c93ced97960a85fd4d2a24e1fdefaa3e75bebda
Author: Pavel Voronkin 
Date:   2018-08-14T18:20:50Z

IGNITE-10028 Review fixes.




---

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

[Mikhail Cherkasov (JIRA)]

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
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.7
Reporter: Mikhail Cherkasov
 Attachments: JustServer.java, MyCall.java, NestedCall.java, Test.java

If a compute task has embedded compute tasks, embeded task will be loaded by 
peer class loading as a new class on each call, which leads to metadata OOM.

Reproducer is attached. Make sure that you run ignite nodes with 
-XX:MaxMetaspaceSize=64m , by default JVM doesn't limit meta space size.

So what happens:
 # client sends compute taks MyCall to server_1
 # server_1 execute MyCall and MyCall sends NestedCall task to server_2
 # server_2 loads NestedCall as a new class and execute it
 # repeat it's again and on second iteration server_2 will load NestedCall as 
new class again, after few iterations this will lead to OOM



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[GitBox]

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 message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[dspavlov]

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 and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5388.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5388


commit 94501e760be99cb01bf43b2b98ef46b2783c6456
Author: Dmitriy Pavlov 
Date:   2018-11-13T22:21:30Z

IGNITE-10243 Some comments update for produce difference with master.




---

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

[Dmitriy Pavlov (JIRA)]

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
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


For case, there is no TC run (RunAll) for the branch with normal status we can 
check if there are any with canceled status.

If canceled status (unknown) appeared on the latest build in suite's rebuilds 
sequence, we can use the latest build successful.

If there is only one build in rebuilds sequence and it was canceled => use this 
one as a possible blocker for PR report.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5387: Ignite 2.5.4

[antkr]

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 and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5387.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5387


commit 78cf3861a5980646e67a5e48fb883b52bd73bb38
Author: Alexey Kuznetsov 
Date:   2018-08-23T05:37:28Z

IGNITE-9337 Refactored from single group to collection of groups.

(cherry picked from commit 68374ad52eede916129b82ef769e680ad2bd1a70)

commit 56bf7fc5b96de14998b6a23528149685be68e5f9
Author: Andrey V. Mashenkov 
Date:   2018-08-23T17:44:39Z

IGNITE-9363 Jetty tests forget to stop nodes on finished. - Fixes #4609.

Signed-off-by: Dmitriy Pavlov 

(cherry picked from commit e0c034e)
Signed-off-by: Andrey V. Mashenkov 

commit 8eaefaacea0711b0dcc3fb52193373ddcfba5692
Author: Alexey Kuznetsov 
Date:   2018-08-24T11:10:23Z

IGNITE-9337 Added support to passing "null" in collections.

(cherry picked from commit 9b000978c84357d0198d5fd09e310a9cb4ea2aa3)

commit 309633e70cfb7c53ae61f2a298443ec07c6bf2aa
Author: Pavel Kovalenko 
Date:   2018-08-24T14:02:46Z

IGNITE-8920 - Fixed transaction hanging on Runtime exceptions during 
commit. - Unified StorageException and PersistentStorageIOException. - BPlus 
tree behavior is overridable in tests. - Refactored AccountTransferAmountTest 
to make it possible to develop any transaction failover based on it. - Fixes 
#4432.

Signed-off-by: Dmitriy Pavlov 
(cherry picked from commit dde936ace5eb0618edc360ca05006d76e810add8)

commit 5d4accaa6249055c00bfe90fd2a29eeb77135912
Author: AMedvedev 
Date:   2018-08-24T15:15:05Z

IGNITE-8971 Make GridRestProcessor propagate error message - Fixes #4604.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit a4e144cc3616f2430843934cf844b4ac29841ba0)

commit d571da636f3be5e67d8e97348c624ffc815eeb73
Author: Ilya Kasnacheev 
Date:   2018-08-24T21:35:55Z

IGNITE-9374 Replace expired 1-yr certs with new 3-yr ones. - Fixes #4617.

Signed-off-by: Dmitriy Pavlov 

commit e14f5948d845e63e86b35e40e52075ef16a03e42
Author: Ivan Daschinskiy 
Date:   2018-08-27T15:54:56Z

IGNITE-9183: SQL: fixed UUID handling from DDL statements. This closes 
#4483.

(cherry picked from commit a98dcb93ba45f9d2b69585a84653f2e0174ba2a4)

commit 93558cd27288ef9160ba2857781029014ada81f6
Author: Denis Mekhanikov 
Date:   2018-08-28T14:46:29Z

IGNITE-9389 Avoid deadlock on cache#close(). - Fixes #4626.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 13060f8e0b6ce32321961c50eab079bc5afeda17)

commit 0dee497dc34c144886be24c1f589777edf3f0476
Author: Roman Guseinov 
Date:   2018-08-28T11:41:09Z

IGNITE-9367: Fixed crash in ODBC on executing query with closed connection

This closes #4621

commit 07b97176c18eff0bf641966fd2585e9294b3b68b
Author: kcmvp 
Date:   2018-07-09T21:04:23Z

IGNITE-8956 Fix of javadoc build failure. - Fixes #4328.

Signed-off-by: Dmitriy Pavlov 
(cherry picked from commit cb38b5d196c7adf27f5e727de039bfc8604abf82)

commit 50d5ab9e7f31000d2aa7cd16b67f4990ec5d170c
Author: Alexey Goncharuk 
Date:   2018-08-30T08:35:53Z

IGNITE-9326 Fixed deferred serialization error handling for EntryProcessor 
result - Fixes #4588.

Signed-off-by: Alexey Goncharuk 

commit 7e298d9f468e3cca6bc5727a501b4e4eaae06fed
Author: Alexey Goncharuk 
Date:   2018-08-30T09:39:22Z

IGNITE-9429 Fixed flaky GridCacheReplicatedDataStructuresFailoverSelfTest

commit 5bb65d5884a3057fa216295b2d405d11eef88da1
Author: Anton Kalashnikov 
Date:   2018-08-31T09:21:43Z

IGNITE-9424 Set proper partition for key during insert - Fixes #4645.

commit bcccf0498e08f8bd0c33fa48cc51164580f0b034
Author: Vasiliy Sisko 
Date:   2018-08-31T10:49:55Z

IGNITE-8568 Web Console: Added support for "Collocated" query mode on 
"Queries" screen.

(cherry picked from commit d1b3882)

commit 2e5c3f8f0d5de4f3b4c61b003496d485cf136a7a
Author: vd-pyatkov 
Date:   2018-08-31T15:41:58Z

IGNITE-9448 Update ZooKeeper version to 3.4.13 - Fixes #4661.

Signed-off-by: Alexey Goncharuk 
(cherry picked from commit 4d736fc20a6e667e841201ad2205f1440546191b)

commit d368789670ac5e2a303cb346c638889c1ce2161d
Author: vsisko 
Date:   2018-08-27T07:15:18Z

IGNITE-9370 Fixed execution of REST commands in demo mode.

(cherry picked from commit e8f1aff)

commit f38bdddfa2f34c76692bcd0a31becff1cc4385e3
Author: Ilya Kasnacheev 
Date:   2018-09-03T13:50:05Z

IGNITE-8886: Binary: fixed footer offset calculation when raw data is 
present. This closes #4643.

commit 3558fb8c83446aca18

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

[aealeksandrov]

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 ignite-2.4.8-p7

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5386.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5386


commit 37c8033c72ac4fd1ec1e419ba68142c4fe11ad8b
Author: tledkov-gridgain 
Date:   2018-03-13T09:37:29Z

IGNITE-7860: JDBC thin: changed default socket buffer size to 64Kb. This 
closes #3600.

commit 130adcf29ddb61f8e9baa784b81454d3ed7c3b75
Author: Pavel Tupitsyn 
Date:   2018-01-26T08:48:14Z

IGNITE-7530 .NET: Fix GetAll memory usage and performance in binary mode

This closes #3436

commit 824004909b23a9a7d599500967af34103acb8c47
Author: Igor Sapego 
Date:   2018-01-30T12:56:17Z

IGNITE-6810: Implemented SSL support for ODBC.

This closes #3361

commit 82da0b5e9dc2ee2339c3fb1023e35d415bf1b647
Author: Pavel Kuznetsov 
Date:   2018-02-07T12:37:52Z

IGNITE-6217: Added benchmark to compare JDBC vs native SQL

This closes #2558

commit 701c6f141f6812ad7bc050a86266e696cf5863ed
Author: tledkov-gridgain 
Date:   2018-02-08T12:29:42Z

IGNITE-6625: JDBC thin: support SSL connection to Ignite node

This closes #3233

commit 2d729bf5c6f6fca9d07be2d57850642ba4b55004
Author: tledkov-gridgain 
Date:   2018-02-09T11:08:15Z

IGNITE-6625: SSL support for thin JDBC: additional fix test; change error 
message

commit 8994f847d7f5f15db73706d9210cdccb1cf3fb26
Author: devozerov 
Date:   2018-02-12T13:34:24Z

IGNITE-7003: Fixed faulty test 
WalModeChangeAdvancedSelfTest.testJoinCoordinator.

commit b142712264007d7397d1594541681a4a7e3d4b93
Author: Igor Sapego 
Date:   2018-02-26T12:02:07Z

IGNITE-7362: Fixed PDO ODBC integration issue

commit a2b2aee52cc65d01f2ecaf9462adc4bd368438ea
Author: Igor Sapego 
Date:   2018-02-28T10:23:12Z

IGNITE-7763: Fixed 32bit tests configurations to prevent OOM

This closes #3557

commit 652f3c4cdbaad40f5de25b06f0c13710aa7f2fd9
Author: Pavel Kuznetsov 
Date:   2018-03-13T12:46:36Z

IGNITE-7531: Data load benchmarks. This closes #3571.

commit 9337a53d9fcd62af87f6760080d350b43e275105
Author: tledkov-gridgain 
Date:   2018-03-16T11:38:38Z

IGNITE-7879: Fixed splitter logic for DISTINCT with subqueries. This closes 
#3634.

commit 7bec8b13cb373002d2a6b1b268d410338259bac2
Author: Igor Sapego 
Date:   2018-03-19T11:17:33Z

IGNITE-7811: Implemented connection failover for ODBC

This closes #3643

commit e512e5e0a2602df0ecfb69b2b5efabce836b04db
Author: Igor Sapego 
Date:   2018-03-20T10:37:02Z

IGNITE-7888: Implemented login timeout for ODBC.

This closes #3657

commit 211fca3a55e84b78ff0c1af04d91e25d6fc846c4
Author: devozerov 
Date:   2018-03-20T11:13:46Z

IGNITE-7984: SQL: improved deadlock handling in DML. This closes #3655.

commit bcd2888d27afe65f1a060e35b99a05ea420979c7
Author: Roman Guseinov 
Date:   2018-02-16T09:57:26Z

IGNITE-7192: Implemented JDBC support FQDN to multiple IPs

This closes #3439

commit d2659d0ec9f6e1a0b905fc7bf23b65fd5522c80a
Author: Alexander Paschenko 
Date:   2018-03-14T09:23:37Z

IGNITE-7253: JDBC thin driver: implemented streaming. This closes #3499. 
This closes #3591.

commit bc9018ef8b116f81b8e06d2ff7651ba2b6c7beae
Author: tledkov-gridgain 
Date:   2018-03-19T08:01:26Z

IGNITE-7029: JDBC thin driver now supports multiple IP addresses with 
transparent failover. This closes #3585.

commit 587022862fd5bdbb076ab6207ae6fd9bc7583c13
Author: Sergey Chugunov 
Date:   2018-03-16T16:24:17Z

IGNITE-7964 rmvId is stored to MetaStorage metapage during operations - 
Fixes #3645.

commit 006ef4d15e4faedb6dfce6ce9637602055b97293
Author: tledkov-gridgain 
Date:   2018-03-22T11:47:06Z

IGNITE-7436: Simple username/password authentication. This closes #3483.

commit 1c7f59c90514670e802d9d07544b00b7562fe6d2
Author: Pavel Tupitsyn 
Date:   2018-01-30T09:48:16Z

.NET: Fix build status icon in README

commit 162df61b305fccfc55e186d07351727f35b55179
Author: Pavel Tupitsyn 
Date:   2018-02-01T11:53:16Z

IGNITE-7561 .NET: Add IServices.GetDynamicServiceProxy

This closes #3457

commit 9a0328ebbc9d52f8e96898a384fa45743d2efa5b
Author: Pavel Tupitsyn 
Date:   2018-02-02T12:01:27Z

.NET: Update README regarding C++ interop and thin client

commit b804cfea51c87724b45b40de4fd58d300c049be1
Author: Pavel Tupitsyn 
Date:   2018-01-31T09:39:19Z

.NET: Suppress API parity check for SSL in ClientConnectorConfiguration

commit 6f8014de7250c4c0d87cbc8764afae4a225f654b
Author: apopov 
Date:   2018-02-13T10:13:15Z

IGNITE-3111 .NET can be now configured SSL without 

[GitHub] ignite pull request #5385: Ignite 1.8.22

[ezhuravl]

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 these changes as the patch at:

https://github.com/apache/ignite/pull/5385.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5385


commit 4ffc3acfa1bc43bea8c79bfd1864787c15cfc4de
Author: Alexey Goncharuk 
Date:   2017-06-20T04:59:09Z

IGNITE-5528 - IS_EVICT_DISABLED flag is not cleared on cache store 
exception.

commit 9036ad239d68eff663bc73a81baab2826b054d9a
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:25:31Z

Added MBean for system cache executors.

commit ed34a5dc681ea8f284f4d25c5575ad46569cc600
Author: Andrey V. Mashenkov 
Date:   2017-06-21T15:33:55Z

Partial fix of IGNITE-5562.

commit d427021f329292fb69d348ba949ad1f8f1e9089e
Author: Andrey V. Mashenkov 
Date:   2017-06-21T16:30:27Z

IGNITE-5552: ServiceProcessor recalculates all service assignments even if 
there is a pending topology change.

commit f1b9cdc0716a1b23f54d68ce0fe19eb85107567d
Author: Alexey Goncharuk 
Date:   2017-06-14T18:37:54Z

GG-12354: Partial fix of IGNITE-5473: Introduce troubleshooting logger.

commit beb2409cfe2045789443d47de735d879961d371e
Author: Andrey V. Mashenkov 
Date:   2017-06-23T09:26:06Z

GG-12352: Forcible node drop makes cluster instable in some cases.
Disable forcible node drop by default.

commit 802f18fc250cbae8959192c78bb28dc525ed3cf7
Author: AMRepo 
Date:   2017-06-22T21:24:57Z

Fix compilation

commit 39d2dec85a3c571dfdb1cd6189b53ae2413a5d22
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:41:30Z

Merge branch 'ignite-1.7.12-b2' into ignite-1.8.8

# Conflicts:
#   modules/core/src/main/java/org/apache/ignite/internal/GridTopic.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/GridIoMessageFactory.java
#   
modules/core/src/main/java/org/apache/ignite/internal/managers/communication/IgniteIoTestMessage.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheAdapter.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/service/GridServiceProcessor.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/task/GridTaskThreadContextKey.java
#   
modules/core/src/main/java/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.java
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgniteCacheTestSuite5.java

commit 96445156143b46b664f785b353463dd435ac342d
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:42:44Z

Merge remote-tracking branch 'origin/ignite-1.8.8' into ignite-1.8.8

# Conflicts:
#   
modules/core/src/test/java/org/apache/ignite/testsuites/IgniteCacheTestSuite5.java

commit 7c569f15a80ab9301c21011d2c9159e311e46cef
Author: Andrey V. Mashenkov 
Date:   2017-06-23T10:48:10Z

Merge remote-tracking branch 'origin/ignite-1.8.7.p1' into ignite-1.8.8

commit bfec212b1ece0e9e791de6dfb642324834fa77ca
Author: AMRepo 
Date:   2017-06-22T21:24:57Z

Partially reverted GG-12352.

commit 1abc14fdc4e39d8245c3e50fb2cf3d183df08021
Author: AMRepo 
Date:   2017-06-22T21:24:57Z

Partially reverted GG-12352.

commit cb95f7aa729fda19b4c3b7a5ada903a1e1bc2eab
Author: Andrey V. Mashenkov 
Date:   2017-06-23T16:08:00Z

Merge remote-tracking branch 'origin/ignite-1.7.12' into ignite-1.7.12

commit 897f4c00c4945eda3f9f4a41d064ded2f6f27ccc
Author: sboikov 
Date:   2017-06-27T09:55:11Z

gg-12133 Deadlock for metadata update from GridCacheMapEntry.innerUpdate

commit 90e96db22dbb7a341bfe1a8130b6dc16d5d8ae81
Author: agura 
Date:   2017-06-27T11:43:06Z

Compilation is fixed.

commit 3f33a902ed0d0a3e27be548209fe8e7933da57a9
Author: Andrey V. Mashenkov 
Date:   2017-06-26T09:27:58Z

Minor fix for GG-12197 "Ignore events for discarded update in CLOCK mode".

commit 3668b91817c1da7958cc3d7c4dddf890a2237772
Author: Andrey V. Mashenkov 
Date:   2017-06-27T07:34:42Z

Partially reverted GG-12352.

commit 172f41c489c0ca5b7613163cd325b0c01d5b28b1
Author: sboikov 
Date:   2017-06-27T09:55:11Z

gg-12133 Deadlock for metadata update from GridCacheMapEntry.innerUpdate

(cherry picked from commit 897f4c0)

commit 0521b7780756788d92bfa35ef00f56b5bb01367d
Author: Andrey V. Mashenkov 
Date:   2017-06-27T17:43:07Z

GG-12370: Fixed massive NODE_FAILED events lead to excessive momentary 
memory consumption.

commit 6abe5bf5bd732bf9f79df577e159243520dd5c0b
Au

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

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5367


---

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

[agura]

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 apply these changes as the patch at:

https://github.com/apache/ignite/pull/5384.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5384


commit 26909bee39d419b7f4cd8dced461f26442a8232a
Author: Andrey Gura 
Date:   2018-11-13T17:25:11Z

Failure handling fix




---

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

[Igor Sapego]

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  wrote:

> 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 started and terminated.
>- In the IEP you've mentioned I/O related fields that should help to
>grasp why a query runs that slow. Should they be stored in this view?
>- "KILL QUERY query_id" is more than enough. Let's not add "node_id"
>unless it's absolutely required. Our queries are distributed and
> executed
>across several nodes that's why the node_id parameter is redundant.
>- This API needs to be supported across all our interfaces. We can start
>with JDBC/ODBC and thin clients and then support for the native SQL APIs
>(Java, Net, C++)
>- Please share examples of SELECTs in the IEP that would show how to
>find long running queries, queries that cause a lot of I/O troubles.
>
> --
> Denis
>
> On Tue, Nov 13, 2018 at 1:15 AM Юрий  wrote:
>
> > Igniters,
> >
> > Some comments for my original email's.
> >
> > The proposal related to part of IEP-29
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > .
> >
> > What purpose are we pursuing of the proposal?
> > We want to be able check which queries running right now through thin
> > clients. Get some information related to the queries and be able to
> cancel
> > a query if it required for some reasons.
> > So, we need interface to get a running queries. For the goal we propose
> > running_queries system view. The view contains unique query identifier
> > which need to pass to kill query command to cancel the query.
> >
> > What do you think about fields of the running queries view? May be some
> > useful fields we could easy add to the view.
> >
> > Also let's discuss syntax of cancellation of query. I propose to use
> MySQL
> > like syntax as easy to understand and shorter then Oracle and Postgres
> > syntax ( detailed information in IEP-29
> > <
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> > >
> > ).
> >
> >
> >
> > пн, 12 нояб. 2018 г. в 19:28, Юрий :
> >
> > > Igniters,
> > >
> > > Below is a proposed design for thin client SQL management and
> monitoring
> > > to cancel a queries.
> > >
> > > 1) Ignite expose system SQL view with name *running_queries*
> > > proposed columns: *node_id, query_id, sql, schema_name, connection_id,
> > > duration*.
> > >
> > > node_id - initial node of request
> > > query_id - unique id of query on node
> > > sql - text of query
> > > schema name - name of sql schema
> > > connection_id - id of client connection from
> > ClientListenerConnectionContext
> > > class
> > > duration - duration in millisecond from start of query
> > >
> > >
> > > Ignite will gather info about running queries from each of nodes and
> > > collect it during user query. We already have most of the information
> at
> > GridRunningQueryInfo
> > > on each of nodes.
> > >
> > > Instead of duration we can use start_time, but I think duration will be
> > > simple to use due to it not depend on a timezone.
> > >
> > >
> > > 2) Propose to use following syntax to kill a running query:
> > >
> > > *KILL QUERY node_Id query_id*
> > >
> > >
> > > Both parameters node_id and query_id can be get through running_queries
> > > system view.
> > >
> > > When a node receive such request it can be run locally in case node
> have
> > > given node_id or send message to node with given id. Because node have
> > > information about local running queries then can cancel it - it already
> > > implemented in GridReduceQueryExecutor.cancelQueries(qryId) method.
> > >
> > > Comments are welcome.
> > > --
> > > Живи с улыбкой! :D
> > >
> >
> >
> > --
> > Живи с улыбкой! :D
> >
>

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

[Ivan Daschinskiy (JIRA)]

Ivan Daschinskiy created IGNITE-10242:
-

 Summary: NPE in GridDhtPartitionDemander#handleSupplyMessage when 
concurrently rebalancing and stopping cache in same cache group.
 Key: IGNITE-10242
 URL: https://issues.apache.org/jira/browse/IGNITE-10242
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.6, 2.5
Reporter: Ivan Daschinskiy
 Fix For: 2.8


NPE in GridDhtPartitionDemander#handleSupplyMessage occurs when concurrently 
rebalancing and stopping cache in same cache group. Reproducer is attached


{noformat}
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.preloadEntry(GridDhtPartitionDemander.java:893)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.handleSupplyMessage(GridDhtPartitionDemander.java:772)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleSupplyMessage(GridDhtPreloader.java:331)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:411)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:401)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1058)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:583)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)

{noformat}








--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[pavlukhin]

Github user pavlukhin closed the pull request at:

https://github.com/apache/ignite/pull/4913


---

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

[pavlukhin]

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

[pavlukhin]

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...

[SpiderRus]

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

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5383.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5383


commit 69f6404a05473221e3dba0c13990e521a19c61f9
Author: Alexey Stelmak 
Date:   2018-11-13T16:12:12Z

Metasotage pages fix




---

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

[oignatenko]

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:

$ git pull https://github.com/gridgain/apache-ignite ignite-10200

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5382.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5382


commit 1eeca908a8076a8317947dac8a46845964d1d7ea
Author: Oleg Ignatenko 
Date:   2018-08-23T13:13:28Z

IGNITE-9348 ML examples improvements
- wip (logging improved)
-- verified with diffs overview, executing the examples and studying 
execution logs

commit e50b89c392568ba9b93935c4fa6c7f7f93f5ec6f
Author: Oleg Ignatenko 
Date:   2018-08-23T14:45:57Z

Revert "IGNITE-9348 ML examples improvements"

This reverts commit 1eeca908a8076a8317947dac8a46845964d1d7ea.

commit 474024b4c5bbdb3c0a4ed2f0a66238c8054c6674
Author: Oleg Ignatenko 
Date:   2018-08-23T14:57:34Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9642b233b5701bdad47ebea163079160227c582a
Author: Oleg Ignatenko 
Date:   2018-08-28T14:01:11Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 7fc16d013ab725d2ff2e1a1b042c983f11d0c4d4
Author: Oleg Ignatenko 
Date:   2018-08-28T15:13:02Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit d2caba67b156674f051f50faebeafe0871bf0914
Author: Oleg Ignatenko 
Date:   2018-08-29T13:14:07Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 16775dff51d71ea68b4a3dea98be552130c493ed
Author: Oleg Ignatenko 
Date:   2018-08-30T09:00:56Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit aedb59929974fe205b949225c1a338c68c60cfc8
Author: Oleg Ignatenko 
Date:   2018-08-30T09:42:38Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 39c6482fcdca506aa33011ed21c98060b4a8c68b
Author: Oleg Ignatenko 
Date:   2018-08-30T11:28:05Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 33b32a2760a6559c78283b927e3191180d8ed9e1
Author: Oleg Ignatenko 
Date:   2018-08-30T12:31:16Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9531028ddd1aef9e95f7e8c8b528086739bbb1b0
Author: Oleg Ignatenko 
Date:   2018-08-30T14:06:34Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 28f22c6e2fffcb82717ba5da7be2cfd39715c4e3
Author: Oleg Ignatenko 
Date:   2018-08-30T16:41:51Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit aacac88db519187413b0fc5ff9d0e55b8f8cff22
Author: Oleg Ignatenko 
Date:   2018-08-31T10:12:32Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 897f920dde46022849b13f9fb86dba8e54119a56
Author: Oleg Ignatenko 
Date:   2018-08-31T13:57:14Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 114c79e54c1b316006ccc3ff22d20d902f9313df
Author: Oleg Ignatenko 
Date:   2018-08-31T17:39:16Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit fd6b659bb8be1992618ce4ce91f568a0988b3afa
Author: Oleg Ignatenko 
Date:   2018-09-02T06:11:42Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 6ae6d1d3cf9743d8d466be0330511ddc8589e944
Author: Oleg Ignatenko 
Date:   2018-09-03T10:27:35Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit e8b27dbd3d0c1cbdb7a7659175f5c7bb447482bf
Author: Oleg Ignatenko 
Date:   2018-09-04T09:49:44Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 622c82efdd0aa182fadea6b7ffa5d4615521a3f5
Author: Oleg Ignatenko 
Date:   2018-09-05T10:50:28Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit fb844fe3751e2e8ae87e6b8030b0e4bd659df9c2
Author: Oleg Ignatenko 
Date:   2018-09-05T11:45:58Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 480ed78869277d7e32f725ab71bec9621f1ac03a
Author: Oleg Ignatenko 
Date:   2018-09-06T07:52:55Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit c99762498f617c0e98ea3062a43c0b30092166ef
Author: Oleg Ignatenko 
Date:   2018-09-06T14:45:04Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 2e17175225c72f747d370b5fee96f8be69d6d2cb
Author: Oleg Ignatenko 
Date:   2018-09-06T17:33:54Z

Merge branch 'master' of https://github.com/apache/ignite into master-ml

commit 9ebcd9a2fe5966b0bf42a95484395867c15d863f
Author: Oleg Ignatenko 
Date:   2

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

[Denis Magda]

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 started and terminated.
   - In the IEP you've mentioned I/O related fields that should help to
   grasp why a query runs that slow. Should they be stored in this view?
   - "KILL QUERY query_id" is more than enough. Let's not add "node_id"
   unless it's absolutely required. Our queries are distributed and executed
   across several nodes that's why the node_id parameter is redundant.
   - This API needs to be supported across all our interfaces. We can start
   with JDBC/ODBC and thin clients and then support for the native SQL APIs
   (Java, Net, C++)
   - Please share examples of SELECTs in the IEP that would show how to
   find long running queries, queries that cause a lot of I/O troubles.

--
Denis

On Tue, Nov 13, 2018 at 1:15 AM Юрий  wrote:

> Igniters,
>
> Some comments for my original email's.
>
> The proposal related to part of IEP-29
> <
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> >
> .
>
> What purpose are we pursuing of the proposal?
> We want to be able check which queries running right now through thin
> clients. Get some information related to the queries and be able to cancel
> a query if it required for some reasons.
> So, we need interface to get a running queries. For the goal we propose
> running_queries system view. The view contains unique query identifier
> which need to pass to kill query command to cancel the query.
>
> What do you think about fields of the running queries view? May be some
> useful fields we could easy add to the view.
>
> Also let's discuss syntax of cancellation of query. I propose to use MySQL
> like syntax as easy to understand and shorter then Oracle and Postgres
> syntax ( detailed information in IEP-29
> <
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> >
> ).
>
>
>
> пн, 12 нояб. 2018 г. в 19:28, Юрий :
>
> > Igniters,
> >
> > Below is a proposed design for thin client SQL management and monitoring
> > to cancel a queries.
> >
> > 1) Ignite expose system SQL view with name *running_queries*
> > proposed columns: *node_id, query_id, sql, schema_name, connection_id,
> > duration*.
> >
> > node_id - initial node of request
> > query_id - unique id of query on node
> > sql - text of query
> > schema name - name of sql schema
> > connection_id - id of client connection from
> ClientListenerConnectionContext
> > class
> > duration - duration in millisecond from start of query
> >
> >
> > Ignite will gather info about running queries from each of nodes and
> > collect it during user query. We already have most of the information at
> GridRunningQueryInfo
> > on each of nodes.
> >
> > Instead of duration we can use start_time, but I think duration will be
> > simple to use due to it not depend on a timezone.
> >
> >
> > 2) Propose to use following syntax to kill a running query:
> >
> > *KILL QUERY node_Id query_id*
> >
> >
> > Both parameters node_id and query_id can be get through running_queries
> > system view.
> >
> > When a node receive such request it can be run locally in case node have
> > given node_id or send message to node with given id. Because node have
> > information about local running queries then can cancel it - it already
> > implemented in GridReduceQueryExecutor.cancelQueries(qryId) method.
> >
> > Comments are welcome.
> > --
> > Живи с улыбкой! :D
> >
>
>
> --
> Живи с улыбкой! :D
>

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

[antonovsergey93]

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:

$ git pull https://github.com/gridgain/apache-ignite ignite-10235

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5381.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5381


commit 075ee9c25a61b0018d67324a9fd9bf8654f22f4a
Author: Sergey Antonov 
Date:   2018-11-13T14:59:40Z

IGNITE-10235 Fix error with double cache registering with disabled
IGNITE_ALLOW_START_CACHES_IN_PARALLEL option.




---

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

[Salatich]

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 repository by running:

$ git pull https://github.com/Salatich/ignite ignite-10223

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5380.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5380


commit fee281e8acb4438061bc911cdfb687039f7e3430
Author: Aleksandr Salatich 
Date:   2018-11-13T14:42:01Z

ignite-10223
Add two new methods in Affinity class which returns List instead of 
Collection (and should replace them in future)




---

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

[asfgit]

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 (JIRA)]

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 Type: Bug
  Components: mvcc
Reporter: Igor Seliverstov
 Fix For: 2.8


test occasionally fails with following error:
{code:java}
[2018-11-13 
15:03:44,240][ERROR][sys-#19392%mvcc.CacheMvccPartitionedSqlCoordinatorFailoverTest0%][GridDhtPartitionsExchangeFuture]
 Failed to notify listener: 
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2@22ae2fbd
java.lang.ClassCastException: 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxRemote 
cannot be cast to 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal
 at 
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.rollbackMvccTxOnCoordinatorChange(IgniteTxManager.java:327)
 at 
org.apache.ignite.internal.processors.cache.mvcc.MvccProcessorImpl.onExchangeDone(MvccProcessorImpl.java:394)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2095)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3391)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3157)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2773)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:139)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2578)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2566)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:395)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2566)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1747)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:144)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:377)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:335)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3194)
 at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3173)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:100)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:294)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)
{code}
Seems there is an issue with committing/rolling back transactions on topology 
changes because we expect all transactions hold

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

[asfgit]

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

[GitBox]

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 pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
index 7716ba14..feb37047 100644
--- 
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
+++ 
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
@@ -18,12 +18,14 @@
 package org.apache.ignite.ci.observer;
 
 import java.util.ArrayList;
+import com.fasterxml.jackson.databind.ObjectMapper;
 import java.util.Collection;
 import java.util.HashSet;
 import java.util.List;
 import java.util.Set;
 import java.util.TimerTask;
 import javax.cache.Cache;
+import java.util.stream.Collectors;
 import javax.inject.Inject;
 import org.apache.ignite.Ignite;
 import org.apache.ignite.IgniteCache;
@@ -37,6 +39,7 @@
 import org.apache.ignite.ci.user.ICredentialsProv;
 import org.apache.ignite.ci.web.model.Visa;
 import org.apache.ignite.ci.web.model.hist.VisasHistoryStorage;
+import org.apache.ignite.internal.util.typedef.X;
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
 
@@ -112,9 +115,22 @@ protected String runObserverTask() {
 int notFinishedBuilds = 0;
 Set ticketsNotified = new HashSet<>();
 
+ObjectMapper objectMapper = new ObjectMapper();
+
+List rmvdVisas = new ArrayList<>();
+
+List queuedVisas = new ArrayList<>();
+
 for (Cache.Entry entry : compactInfos()) {
 CompactBuildsInfo compactInfo = entry.getKey();
 
+try {
+queuedVisas.add(objectMapper.writeValueAsString(compactInfo));
+}
+catch (Exception e) {
+return "Exception while JSON parsing";
+}
+
 BuildsInfo info = compactInfo.toBuildInfo(strCompactor);
 
 checkedBuilds += info.buildsCount();
@@ -147,10 +163,24 @@ protected String runObserverTask() {
 if (visa.isSuccess()) {
 ticketsNotified.add(info.ticket);
 
-compactInfos().remove(compactInfo);
+try {
+   rmvdVisas.add(objectMapper.writeValueAsString(compactInfo));
+}
+catch (Exception e) {
+return "Exception while JSON parsing";
+}
+
+try {
+compactInfos().remove(compactInfo);
+}
+catch (Exception e) {
+   return X.getFullStackTrace(e);
+}
 }
 }
 
-return "Checked " + checkedBuilds + " not finished " + 
notFinishedBuilds + " notified: " + ticketsNotified;
+return "Checked " + checkedBuilds + " not finished " + 
notFinishedBuilds + " notified: " + ticketsNotified +
+" Visas in queue: [" + 
queuedVisas.stream().collect(Collectors.joining(", ")) +
+"] Visas to rmv: [" + 
rmvdVisas.stream().collect(Collectors.joining(", ")) + ']';
 }
 }


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[devozerov]

Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/5374


---

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

[asfgit]

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 ...

[Max-Pudov]

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 ignite-10098

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5379.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5379


commit d28462c523af7ba9463d3be15c882cdc2f2c5b09
Author: Max-Pudov 
Date:   2018-11-13T13:21:32Z

IGNITE-10098 TcpCommunicationSpi for .NET misses some properties of java 
TcpCommunicationSpi




---

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

[GitBox]

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, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

[asfgit]

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 (JIRA)]

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: Improvement
  Components: UI, wizards
Reporter: Vica Abramova






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Vica Abramova (JIRA)]

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: Improvement
  Components: UI, wizards
Reporter: Vica Abramova






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[asfgit]

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 (JIRA)]

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 Type: Test
 Environment: There are occasional hangs of Client Nodes suite in 
master. A quick peek at the thread dumps reveals an interesting deadlock (only 
relevant parts of the thread dump are left):
{code}
"disco-notifier-worker-#634%internal.IgniteClientReconnectApiExceptionTest0%" 
#791 prio=5 os_prio=0 tid=0x7f990c12d800 nid=0x11b9 waiting on condition 
[0x7f991a0eb000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:178)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:141)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:656)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$1.metadata(CacheObjectBinaryProcessorImpl.java:206)
at 
org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1293)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2007)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:286)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:185)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1984)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:703)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:188)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:874)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1764)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:313)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:101)
at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:81)
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10131)
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10160)
at 
org.apache.ignite.internal.GridEventConsumeHandler.p2pUnmarshal(GridEventConsumeHandler.java:390)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1362)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:111)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:203)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:194)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:725)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:602)
- locked <0x0007b62859b8> (a java.lang.Object)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4$$Lambda$17/432384581.run(Unknown
 Source)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2665)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2703)
at 
org.apache.ignite.internal.uti

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

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4613


---

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

[agoncharuk]

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 review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5378.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5378


commit 2b4a6f6b258da7e0d19d7a1b6fcc31b5c5990896
Author: Alexey Goncharuk 
Date:   2018-11-13T11:51:53Z

IGNITE-10237 Fixed inspections




---

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

[voropava]

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:

$ git pull https://github.com/gridgain/apache-ignite ignite-10228

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5377.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5377


commit 3a146d54ca6eef07a90fafc1ac4ce6f0deeda5a6
Author: Pavel Voronkin 
Date:   2018-08-14T18:20:50Z

IGNITE-10028 Fixed race on addCacheContext/removeCacheContext, fixed 
suboptimal batch splitting in U.doInParallel().




---

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

[Alexey Goncharuk (JIRA)]

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 Type: Test
Reporter: Alexey Goncharuk






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Andrew Mashenkov (JIRA)]

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
  Issue Type: Sub-task
  Components: mvcc
Reporter: Andrew Mashenkov
Assignee: Andrew Mashenkov


Create MVCC version of IgniteCacheTestSuite2 and add it to TC.

All non-relevant tests should be marked as ignored.
Failed tests should be muted and tickets should be created for unknown failure 
reasons.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Igor Sapego]

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, but will also be usable from basic SQL API?

Best Regards,
Igor


On Tue, Nov 13, 2018 at 12:15 PM Юрий  wrote:

> Igniters,
>
> Some comments for my original email's.
>
> The proposal related to part of IEP-29
> <
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> >
> .
>
> What purpose are we pursuing of the proposal?
> We want to be able check which queries running right now through thin
> clients. Get some information related to the queries and be able to cancel
> a query if it required for some reasons.
> So, we need interface to get a running queries. For the goal we propose
> running_queries system view. The view contains unique query identifier
> which need to pass to kill query command to cancel the query.
>
> What do you think about fields of the running queries view? May be some
> useful fields we could easy add to the view.
>
> Also let's discuss syntax of cancellation of query. I propose to use MySQL
> like syntax as easy to understand and shorter then Oracle and Postgres
> syntax ( detailed information in IEP-29
> <
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> >
> ).
>
>
>
> пн, 12 нояб. 2018 г. в 19:28, Юрий :
>
> > Igniters,
> >
> > Below is a proposed design for thin client SQL management and monitoring
> > to cancel a queries.
> >
> > 1) Ignite expose system SQL view with name *running_queries*
> > proposed columns: *node_id, query_id, sql, schema_name, connection_id,
> > duration*.
> >
> > node_id - initial node of request
> > query_id - unique id of query on node
> > sql - text of query
> > schema name - name of sql schema
> > connection_id - id of client connection from
> ClientListenerConnectionContext
> > class
> > duration - duration in millisecond from start of query
> >
> >
> > Ignite will gather info about running queries from each of nodes and
> > collect it during user query. We already have most of the information at
> GridRunningQueryInfo
> > on each of nodes.
> >
> > Instead of duration we can use start_time, but I think duration will be
> > simple to use due to it not depend on a timezone.
> >
> >
> > 2) Propose to use following syntax to kill a running query:
> >
> > *KILL QUERY node_Id query_id*
> >
> >
> > Both parameters node_id and query_id can be get through running_queries
> > system view.
> >
> > When a node receive such request it can be run locally in case node have
> > given node_id or send message to node with given id. Because node have
> > information about local running queries then can cancel it - it already
> > implemented in GridReduceQueryExecutor.cancelQueries(qryId) method.
> >
> > Comments are welcome.
> > --
> > Живи с улыбкой! :D
> >
>
>
> --
> Живи с улыбкой! :D
>

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

[Pavel Kovalenko (JIRA)]

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
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.8
Reporter: Pavel Kovalenko
 Fix For: 2.8


In case of disabled property IGNITE_ALLOW_START_CACHES_IN_PARALLEL callback 
that registers cache in QueryManager invoked twice which leads to impossibility 
to start cache if it was recovered before join to topology.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[antonovsergey93]

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 https://github.com/gridgain/apache-ignite ignite-10233

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5376.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5376


commit 865fe140a8736afa920a1899ff9ef6b3bd53f0d1
Author: Sergey Antonov 
Date:   2018-11-13T10:59:58Z

IGNITE-10233 Skip assertion if cluster not activated.




---

Re: Assign task and getting rights

[Dmitriy Pavlov]

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
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Sincerely,
Dmitriy Pavlov

вт, 13 нояб. 2018 г. в 13:45, Александр :

> 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 #5370: GG-14435 condition was changed in assertion.

[antonovsergey93]

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 (JIRA)]

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
  Issue Type: Sub-task
  Components: ml
Affects Versions: 2.8
Reporter: Anton Dmitriev
Assignee: Anton Dmitriev
 Fix For: 2.8


To support model inference in Apache Ignite for our models as well as for 
loaded foreign models we need a common inference workflow. 

This workflow should isolate model _inference/using_ from model 
_training/saving_. User should be able to:
* *Load/Unload any possible model (that can be represented as a function).*
_This part assumes that user specifies any underlying model, a bridge that 
allows to interact with it and a signature of the model (accepted parameters, 
returned value)._

* *Access a list of loaded models.*
_Used should be able to access a list of loaded models, models that can be used 
for inference without any additional manipulations. In terms of future Cloud 
part it will be a table of models user can use in Web UI and start using it._

* *Start/Stop distributed infrastructure for inference utilizing cluster 
resources.*
_Single inference is actually a single function call. We want to utilize all 
cluster resources, so we need to replicate the model and start services that 
are ready to use the model for inference on every node._

* *Perform inference on top of started infrastructure.*
_There are should be a gateway that allows to use a single entry point to 
perform inference utilizing started on the previous step distributed service 
infrastructure._



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Sergey Antonov (JIRA)]

Sergey Antonov created IGNITE-10233:
---

 Summary: GridAffinityAssignmentCache#cachedAffinity() should not 
check topology version in assertion, if cluster not activated. 
 Key: IGNITE-10233
 URL: https://issues.apache.org/jira/browse/IGNITE-10233
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Antonov
Assignee: Sergey Antonov


It's needed for our proprietary plugin.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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 ...

[tledkov-gridgain]

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 repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7822

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/5375.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5375


commit 19e2deb36e0e79dee23a92ca80f5bbb19fedbd81
Author: tledkov-gridgain 
Date:   2018-03-14T14:53:27Z

IGNITE-7822: add test

commit 99a0d5684bc8e01e11397a401e7a9af0ee7bf892
Author: tledkov-gridgain 
Date:   2018-03-15T09:00:06Z

IGNITE-7822: save the progress

commit 01cc5e6cb79bf796aeacbe8ed164ca98ee1e38f4
Author: tledkov-gridgain 
Date:   2018-03-15T10:15:59Z

Merge branch '_master' into ignite-7822

commit 1040abe13ee5062a0f0f08cd3b85ac3f469971a2
Author: tledkov-gridgain 
Date:   2018-03-16T08:28:31Z

IGNITE-7822: save the progress

commit cb3f8d3d61e900cfa6c15c4a9727025ffedd4872
Author: tledkov-gridgain 
Date:   2018-03-16T09:39:16Z

IGNITE-7822: save the progress

commit feb16bfbdc188bf055edd8cb2b5b02c0cd0fada9
Author: tledkov-gridgain 
Date:   2018-03-16T09:54:29Z

Merge branch '_master' into ignite-7822

commit e3e6097b6aff4901ed462d0de6afd696e1794efc
Author: tledkov-gridgain 
Date:   2018-03-16T12:34:47Z

IGNITE-7822: save the progress

commit 14ed9376c10cc6d3431a5cbd953df13522cc7c87
Author: tledkov-gridgain 
Date:   2018-04-03T11:23:35Z

Merge branch 'master' into ignite-7822

# Conflicts:
#   
modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/SqlPushDownFunctionTest.java

commit cbe65e919fe9fac9c212835704e21a6970777662
Author: tledkov-gridgain 
Date:   2018-04-03T11:35:17Z

ignite-7822: save the progress

commit e76148cab1c3d98f89590aeab5bc54324d828e8a
Author: tledkov-gridgain 
Date:   2018-05-23T14:51:26Z

Merge branch '_master' into ignite-7822

commit 8b0dbfcc20d0a04a5def87d86963763c6742ba98
Author: tledkov 
Date:   2018-11-09T10:16:19Z

Merge branch '_master' into ignite-7822

commit 1b310e01c68a114c3f9dd1e5cb317a9a40dd7db2
Author: tledkov 
Date:   2018-11-09T15:32:40Z

IGNITE-7822: extract test

commit d9c754ddeffeb221a683a261d202aeee354a8e4d
Author: tledkov 
Date:   2018-11-12T12:20:46Z

Merge branch '_master' into ignite-7822

commit 1ff1f38849c5c9757c2879c73175d5eb04396952
Author: tledkov 
Date:   2018-11-13T10:30:14Z

IGNITE-7822: hotfix: push down query model range separately for each 
relation in case statement contains  subquery that must be splitted




---

Re: Service grid redesign

[Vyacheslav Daradur]

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.
>
> Thanks!
> Denis
>
> сб, 10 нояб. 2018 г. в 14:25, Nikolay Izhikov :
>
> > Hello, Vladimir.
> >
> > I'm agree with you.
> >
> > Can we write the list of reviewers for this feature?
> > Without a date or similar.
> > Just a list of experts who should review this feature.
> >
> > В Сб, 10/11/2018 в 14:01 +0300, Vladimir Ozerov пишет:
> > > Igniters,
> > >
> > > This is very huge thing with complex algorithms behind. We should not
> > merge
> > > it to the product unless several additional thorough reviews are ready,
> > > irrespectively of how long will it take. We are about quality, not speed.
> > >
> > > сб, 10 нояб. 2018 г. в 1:30, Denis Magda :
> > >
> > > > Vyacheslav,
> > > >
> > > > What are the cases when the service can be redeployed? Affinity,
> > failure,
> > > > etc., right. It would be good to list all the cases on the wiki and
> > then
> > > > our tech writers will get everything documented.
> > > >
> > > > --
> > > > Denis
> > > >
> > > > On Thu, Nov 8, 2018 at 11:06 PM Vyacheslav Daradur <
> > daradu...@gmail.com>
> > > > wrote:
> > > >
> > > > > Denis,
> > > > >
> > > > > Services reassignment process takes into account previous assignments
> > > > > to avoid redundant redeployments.
> > > > > So, in the described case, ServiceA won't be moved from node1 to
> > node2.
> > > > > On Fri, Nov 9, 2018 at 4:41 AM Denis Magda 
> > wrote:
> > > > > >
> > > > > > Vyacheslav,
> > > > > >
> > > > > > First of all, thanks for archiving this milestone and rolling out
> > these
> > > > >
> > > > > new
> > > > > > capabilities.
> > > > > >
> > > > > > Speaking of the topology change events [1], does the new
> > architecture
> > > > >
> > > > > avoid
> > > > > > a running service redeployment when a new node joins? For instance,
> > > >
> > > > let's
> > > > > > say I have ServiceA running node1, then node2 joins and I don't
> > want
> > > >
> > > > the
> > > > > > service to be redeployed to any other node.
> > > > > >
> > > > > > [1]
> > > > > >
> > > >
> > > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95654584#ServiceGridredesign.Phase1.Implementationdetails.-Topologychange
> > > > > >
> > > > > > --
> > > > > > Denis
> > > > > >
> > > > > > On Wed, Nov 7, 2018 at 7:04 AM Vyacheslav Daradur <
> > daradu...@gmail.com
> > > > > > wrote:
> > > > > >
> > > > > > > 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 <
> > dpavlov@gmail.com
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Hi I think wiki is better than any attached docs. Could you
> > please
> > > > > > >
> > > > > > > create a
> > > > > > > > page?
> > > > > > > >
> > > > > > > > ср, 7 нояб. 2018 г., 14:39 Vyacheslav Daradur <
> > daradu...@gmail.com
> > > > >
> > > > > :
> > > > > > > >
> > > > > > > > > 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] https://github.com/apache/ignite/pull/4434
> > > > > > > > > On Wed, Oct 31, 2018 at 5:04 PM Vyacheslav Daradur <
> > > > > > >
> > > > > > > daradu...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hi, Igniters! Good news!
> > > > > > > > > >
> > > > > > > > > > Service Grid Redesign Phase 1 - is in Patch Available now.
> > > > > > > > > >
> > > > > > > > > > Nikolay Izhikov has reviewed implementation.
> > > > > > > > > >
> > > > > > > > > > However, we need additional review from other Ignite
> > experts.
> > > > > > > > > >
> > > > > > > > > > Here is an umbrella ticket [1] and PR [2].
> > > > > > > > > >
> > > > > > > > > > Could someone step in and do the review?
> > > > > > > > > >
> > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9607
> > > > > > > > > > [2] https://github.com/apache/ignite/pull/4434
> > > > > > > > > > On Sat, Aug 18, 2018 at 11:44 AM Denis Mekhanikov <
> > > > > > >
> > > > > > > dmekhani...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Pavel, could you assist?
> > > > > > > > > > >
> > > > > > > > > > > Does it make sense for .Net to specify service class name
> > > > >
> > > > > instead
>

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

[Alexander Kalinin (JIRA)]

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: Improvement
  Components: wizards
Reporter: Alexander Kalinin
Assignee: Alexander Kalinin


Currently we are indicating success of an action with help of success toasts. 
The problem with them is that they are poorly visible and can be missed by the 
user, 

We need some better indication of success and here are possible variants:

1) No indication at all. Like in desktop applications. No error indication 
means success,

2) Chage the position of a toast message. Currently it's being showed in top 
right corner. We can adjusted postion of the toast to make it more noticable.

3) Indicate success near the action button or some alert zone. Something like a 
text message or tooltip near the form

4) Indication inside the button. Button incapsulates indication like here 
.[https://coreui.io/docs/components/loading-buttons/,] 
https://loading.io/button/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #5286: Ignite 1.7.22

[Max-Pudov]

Github user Max-Pudov closed the pull request at:

https://github.com/apache/ignite/pull/5286


---

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

[devozerov]

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 thin
clients. Get some information related to the queries and be able to cancel
a query if it required for some reasons.
So, we need interface to get a running queries. For the goal we propose
running_queries system view. The view contains unique query identifier
which need to pass to kill query command to cancel the query.

What do you think about fields of the running queries view? May be some
useful fields we could easy add to the view.

Also let's discuss syntax of cancellation of query. I propose to use MySQL
like syntax as easy to understand and shorter then Oracle and Postgres
syntax ( detailed information in IEP-29

).



пн, 12 нояб. 2018 г. в 19:28, Юрий :

> Igniters,
>
> Below is a proposed design for thin client SQL management and monitoring
> to cancel a queries.
>
> 1) Ignite expose system SQL view with name *running_queries*
> proposed columns: *node_id, query_id, sql, schema_name, connection_id,
> duration*.
>
> node_id - initial node of request
> query_id - unique id of query on node
> sql - text of query
> schema name - name of sql schema
> connection_id - id of client connection from ClientListenerConnectionContext
> class
> duration - duration in millisecond from start of query
>
>
> Ignite will gather info about running queries from each of nodes and
> collect it during user query. We already have most of the information at 
> GridRunningQueryInfo
> on each of nodes.
>
> Instead of duration we can use start_time, but I think duration will be
> simple to use due to it not depend on a timezone.
>
>
> 2) Propose to use following syntax to kill a running query:
>
> *KILL QUERY node_Id query_id*
>
>
> Both parameters node_id and query_id can be get through running_queries
> system view.
>
> When a node receive such request it can be run locally in case node have
> given node_id or send message to node with given id. Because node have
> information about local running queries then can cancel it - it already
> implemented in GridReduceQueryExecutor.cancelQueries(qryId) method.
>
> Comments are welcome.
> --
> Живи с улыбкой! :D
>


-- 
Живи с улыбкой! :D

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

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5250


---

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

[devozerov]

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 these changes as the patch at:

https://github.com/apache/ignite/pull/5374.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5374


commit edaaed1daa13a3f069e5422916e5659e8e897a8b
Author: devozerov 
Date:   2018-11-13T08:26:30Z

Done.




---

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

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/5254


---

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

[devozerov]

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 these changes as the patch at:

https://github.com/apache/ignite/pull/5373.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5373


commit 5defccc2898049b1f40cb97873bc53e8e95e594d
Author: devozerov 
Date:   2018-06-09T09:34:02Z

Implemented base logic, need to run tests.

commit b8b2e076d2e34f81eb73f34cb5308d2000883bde
Author: devozerov 
Date:   2018-06-09T12:35:27Z

WIP on tests.

commit 5f145ba97f8ec41b14fd31c5a52fc9de46ef2134
Author: devozerov 
Date:   2018-11-13T07:55:07Z

Merge branch 'master' into ignite-6295

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java

commit 8825aeeca9e2c6ca734dd5b648a29874f5d78b66
Author: devozerov 
Date:   2018-11-13T08:01:02Z

Merge.

commit 75a4fe4c217439d0c98f86736869173a49b75257
Author: devozerov 
Date:   2018-11-13T08:01:43Z

WIP.




---

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

[Vladimir Ozerov (JIRA)]

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
  Issue Type: Task
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.8


We will need this in multiple places outside of splitter. Ideally, it should be 
H2-agnostic.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)