[jira] [Created] (IGNITE-14795) Fix test fail: IoStatisticsSelfTest.testPersistentIOGlobalStat

2021-05-27 Thread Sergei Ryzhov (Jira)
Sergei Ryzhov created IGNITE-14795:
--

 Summary: Fix test fail: 
IoStatisticsSelfTest.testPersistentIOGlobalStat 
 Key: IGNITE-14795
 URL: https://issues.apache.org/jira/browse/IGNITE-14795
 Project: Ignite
  Issue Type: Test
Reporter: Sergei Ryzhov
Assignee: Sergei Ryzhov


Fix test fail: IoStatisticsSelfTest.testPersistentIOGlobalStat 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14794) Add JMX command to restore a cache group from the snapshot.

2021-05-27 Thread Pavel Pereslegin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-14794:
--
Fix Version/s: 2.11

>  Add JMX command to restore a cache group from the snapshot.
> 
>
> Key: IGNITE-14794
> URL: https://issues.apache.org/jira/browse/IGNITE-14794
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>  Labels: iep-43
> Fix For: 2.11
>
>
>  Add JMX command to restore a cache group from the snapshot.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14723) Add CLI command to restore a cache group from the snapshot.

2021-05-27 Thread Pavel Pereslegin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-14723:
--
Labels: iep-43  (was: )

> Add CLI command to restore a cache group from the snapshot.
> ---
>
> Key: IGNITE-14723
> URL: https://issues.apache.org/jira/browse/IGNITE-14723
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>  Labels: iep-43
> Fix For: 2.11
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add CLI command to restore a cache group from the snapshot.
> {noformat}
>   Restore snapshot:
> control.(sh|bat) --snapshot restore --start snapshot_name 
> [group1,...groupN]
> Parameters:
>   snapshot_name - Snapshot name.
>   group1,...groupN  - Cache group names.
>   Snapshot restore operation status:
> control.(sh|bat) --snapshot restore --status snapshot_name
> Parameters:
>   snapshot_name  - Snapshot name.
>   Cancel snapshot restore operation:
> control.(sh|bat) --snapshot restore --cancel snapshot_name
> Parameters:
>   snapshot_name  - Snapshot name.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14794) Add JMX command to restore a cache group from the snapshot.

2021-05-27 Thread Pavel Pereslegin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-14794:
--
Labels: iep-43  (was: )

>  Add JMX command to restore a cache group from the snapshot.
> 
>
> Key: IGNITE-14794
> URL: https://issues.apache.org/jira/browse/IGNITE-14794
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>  Labels: iep-43
>
>  Add JMX command to restore a cache group from the snapshot.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14723) Add CLI command to restore a cache group from the snapshot.

2021-05-27 Thread Pavel Pereslegin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-14723:
--
Description: 
Add CLI command to restore a cache group from the snapshot.


{noformat}
  Restore snapshot:
control.(sh|bat) --snapshot restore --start snapshot_name [group1,...groupN]

Parameters:
  snapshot_name - Snapshot name.
  group1,...groupN  - Cache group names.

  Snapshot restore operation status:
control.(sh|bat) --snapshot restore --status snapshot_name

Parameters:
  snapshot_name  - Snapshot name.

  Cancel snapshot restore operation:
control.(sh|bat) --snapshot restore --cancel snapshot_name

Parameters:
  snapshot_name  - Snapshot name.
{noformat}


  was:
Add CLI command to restore a cache group from the snapshot.


{noformat}
  Restore snapshot:
control.(sh|bat) --snapshot restore --start snapshot_name [group1,...groupN]

Parameters:
  snapshot_name - Snapshot name.
  group1,...groupN  - Cache group names.

  Snapshot restore operation status:
control.(sh|bat) --snapshot restore --status snapshot_name

Parameters:
  snapshot_name  - Snapshot name.

  Cancel snapshot restore opeeration:
control.(sh|bat) --snapshot restore --cancel snapshot_name

Parameters:
  snapshot_name  - Snapshot name.
{noformat}



> Add CLI command to restore a cache group from the snapshot.
> ---
>
> Key: IGNITE-14723
> URL: https://issues.apache.org/jira/browse/IGNITE-14723
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.11
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add CLI command to restore a cache group from the snapshot.
> {noformat}
>   Restore snapshot:
> control.(sh|bat) --snapshot restore --start snapshot_name 
> [group1,...groupN]
> Parameters:
>   snapshot_name - Snapshot name.
>   group1,...groupN  - Cache group names.
>   Snapshot restore operation status:
> control.(sh|bat) --snapshot restore --status snapshot_name
> Parameters:
>   snapshot_name  - Snapshot name.
>   Cancel snapshot restore operation:
> control.(sh|bat) --snapshot restore --cancel snapshot_name
> Parameters:
>   snapshot_name  - Snapshot name.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14794) Add JMX command to restore a cache group from the snapshot.

2021-05-27 Thread Pavel Pereslegin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-14794:
--
Ignite Flags: Docs Required  (was: Docs Required,Release Notes Required)

>  Add JMX command to restore a cache group from the snapshot.
> 
>
> Key: IGNITE-14794
> URL: https://issues.apache.org/jira/browse/IGNITE-14794
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>
>  Add JMX command to restore a cache group from the snapshot.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (IGNITE-14794) Add JMX command to restore a cache group from the snapshot.

2021-05-27 Thread Pavel Pereslegin (Jira)
Pavel Pereslegin created IGNITE-14794:
-

 Summary:  Add JMX command to restore a cache group from the 
snapshot.
 Key: IGNITE-14794
 URL: https://issues.apache.org/jira/browse/IGNITE-14794
 Project: Ignite
  Issue Type: Improvement
Reporter: Pavel Pereslegin
Assignee: Pavel Pereslegin


 Add JMX command to restore a cache group from the snapshot.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (IGNITE-14793) Remake serialization of atomic protocol messages

2021-05-27 Thread Vladislav Pyatkov (Jira)
Vladislav Pyatkov created IGNITE-14793:
--

 Summary: Remake serialization of atomic protocol messages
 Key: IGNITE-14793
 URL: https://issues.apache.org/jira/browse/IGNITE-14793
 Project: Ignite
  Issue Type: Improvement
Reporter: Vladislav Pyatkov


Such messages are all RAFT commands and both responses (package is 
{{org.apache.ignite.internal.table.distributed.command}}).
After the issue will be implemented utilities for temporary serialization has 
to be removed ({{CommandUtils}}).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-14793) Remake serialization of atomic protocol messages

2021-05-27 Thread Vladislav Pyatkov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladislav Pyatkov reassigned IGNITE-14793:
--

Assignee: Vladislav Pyatkov

> Remake serialization of atomic protocol messages
> 
>
> Key: IGNITE-14793
> URL: https://issues.apache.org/jira/browse/IGNITE-14793
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
>  Labels: ignite-3
>
> Such messages are all RAFT commands and both responses (package is 
> {{org.apache.ignite.internal.table.distributed.command}}).
> After the issue will be implemented utilities for temporary serialization has 
> to be removed ({{CommandUtils}}).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14755) Meta storage is not public interface, so all classes should be moved to the internal package.

2021-05-27 Thread Alexander Lapin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Lapin updated IGNITE-14755:
-
Reviewer: Alexander Lapin

> Meta storage is not public interface, so all classes should be moved to the 
> internal package.
> -
>
> Key: IGNITE-14755
> URL: https://issues.apache.org/jira/browse/IGNITE-14755
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
>  Labels: iep-61, ignite-3
> Fix For: 3.0.0-alpha2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Meta storage is not public interface, so all classes should be moved to the 
> internal package.
> It affects modules {{ignite-metastorage-client}} and 
> {{ignite-metastorage-common}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-14755) Meta storage is not public interface, so all classes should be moved to the internal package.

2021-05-27 Thread Alexander Lapin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-14755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352603#comment-17352603
 ] 

Alexander Lapin commented on IGNITE-14755:
--

[~agura] LGTM

> Meta storage is not public interface, so all classes should be moved to the 
> internal package.
> -
>
> Key: IGNITE-14755
> URL: https://issues.apache.org/jira/browse/IGNITE-14755
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
>  Labels: iep-61, ignite-3
> Fix For: 3.0.0-alpha2
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Meta storage is not public interface, so all classes should be moved to the 
> internal package.
> It affects modules {{ignite-metastorage-client}} and 
> {{ignite-metastorage-common}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-14792) Calcite. Calcite can't plan an UPDATE if new column value depends on the old

2021-05-27 Thread Konstantin Orlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Orlov reassigned IGNITE-14792:
-

Assignee: Konstantin Orlov

> Calcite. Calcite can't plan an UPDATE if new column value depends on the old
> 
>
> Key: IGNITE-14792
> URL: https://issues.apache.org/jira/browse/IGNITE-14792
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
>
> The test 
> \{{org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest#testInsertUpdateDeleteNonPrimitiveKey}}
>  could be used as reproducer. The only change should be made is this one:
> {code:java}
> @@ -233,7 +233,7 @@
>  
>  assertEqualsCollections(F.asList(0, 0, "Igor", 1), row);
>  
> -query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
> 'Roman' WHERE id = ?", 0);
> +query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
> name || 'Roman' WHERE id = ?", 0);
>  
>  assertEquals(1, query.size());
>  
> {code}
> The exception arises:
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed 
> to plan query.
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:533)
>   at 
> org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:390)
>   at 
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:250)
>   at 
> org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest.testInsertUpdateDeleteNonPrimitiveKey(TableDmlIntegrationTest.java:236)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.RuntimeException: while converting `NAME` || 'Roman'
>   at 
> org.apache.calcite.sql2rel.ReflectiveConvertletTable.lambda$registerNodeTypeMethod$0(ReflectiveConvertletTable.java:86)
>   at 
> org.apache.calcite.sql2rel.SqlNodeToRexConverterImpl.convertCall(SqlNodeToRexConverterImpl.java:62)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:5098)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:4374)
>   at org.apache.calcite.sql.SqlCall.accept(SqlCall.java:139)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.convertExpression(SqlToRelConverter.java:4961)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertUpdate(SqlToRelConverter.java:3867)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3444)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:570)
>   at 
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.rel(IgnitePlanner.java:223)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.PlannerHelper.optimize(PlannerHelper.java:71)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareDml(ExecutionServiceImpl.java:603)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:560)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:513)
>   ... 16 more
> Caused by: java.lang.reflect.InvocationTargetException
>   at 

[jira] [Updated] (IGNITE-14792) Calcite. Calcite can't plan an UPDATE if new column value depends on the old

2021-05-27 Thread Konstantin Orlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Orlov updated IGNITE-14792:
--
Priority: Critical  (was: Major)

> Calcite. Calcite can't plan an UPDATE if new column value depends on the old
> 
>
> Key: IGNITE-14792
> URL: https://issues.apache.org/jira/browse/IGNITE-14792
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Critical
>
> The test 
> \{{org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest#testInsertUpdateDeleteNonPrimitiveKey}}
>  could be used as reproducer. The only change should be made is this one:
> {code:java}
> @@ -233,7 +233,7 @@
>  
>  assertEqualsCollections(F.asList(0, 0, "Igor", 1), row);
>  
> -query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
> 'Roman' WHERE id = ?", 0);
> +query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
> name || 'Roman' WHERE id = ?", 0);
>  
>  assertEquals(1, query.size());
>  
> {code}
> The exception arises:
> {noformat}
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed 
> to plan query.
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:533)
>   at 
> org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:390)
>   at 
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:250)
>   at 
> org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest.testInsertUpdateDeleteNonPrimitiveKey(TableDmlIntegrationTest.java:236)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.RuntimeException: while converting `NAME` || 'Roman'
>   at 
> org.apache.calcite.sql2rel.ReflectiveConvertletTable.lambda$registerNodeTypeMethod$0(ReflectiveConvertletTable.java:86)
>   at 
> org.apache.calcite.sql2rel.SqlNodeToRexConverterImpl.convertCall(SqlNodeToRexConverterImpl.java:62)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:5098)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:4374)
>   at org.apache.calcite.sql.SqlCall.accept(SqlCall.java:139)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.convertExpression(SqlToRelConverter.java:4961)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertUpdate(SqlToRelConverter.java:3867)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3444)
>   at 
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:570)
>   at 
> org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.rel(IgnitePlanner.java:223)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.PlannerHelper.optimize(PlannerHelper.java:71)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareDml(ExecutionServiceImpl.java:603)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:560)
>   at 
> org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:513)
>   ... 16 more
> Caused by: java.lang.reflect.InvocationTargetException
>   at 

[jira] [Updated] (IGNITE-14104) A lot of "Accepted incoming communication connection" when client node is killed

2021-05-27 Thread Alexey Plotnik (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Plotnik updated IGNITE-14104:

Description: 
A lot of 

{code}
INFO 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted
incoming communication connection
{code}

messages appears in logs when client is killed without leaving the cluster 
(kill -9)

User list source:

https://lists.apache.org/thread.html/r610deb908b64047ff3b5f0d35c21bedf0aef9d252d4023c986a47178%40%3Cuser.ignite.apache.org%3E
http://apache-ignite-users.70518.x6.nabble.com/Re-2-8-1-INFO-org-apache-ignite-spi-communication-tcp-TcpCommunicationSpi-Accepted-incoming-communicn-td36096.html

  was:
A lot of 

{code}
INFO 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted
incoming communication connection
{code}

messages appears in logs when client is killed without leaving the cluster 
(kill -9)

User list source:

https://lists.apache.org/thread.html/r610deb908b64047ff3b5f0d35c21bedf0aef9d252d4023c986a47178%40%3Cuser.ignite.apache.org%3E


> A lot of "Accepted incoming communication connection" when client node is 
> killed
> 
>
> Key: IGNITE-14104
> URL: https://issues.apache.org/jira/browse/IGNITE-14104
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Plotnik
>Priority: Minor
>
> A lot of 
> {code}
> INFO 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi [] - Accepted
> incoming communication connection
> {code}
> messages appears in logs when client is killed without leaving the cluster 
> (kill -9)
> User list source:
> https://lists.apache.org/thread.html/r610deb908b64047ff3b5f0d35c21bedf0aef9d252d4023c986a47178%40%3Cuser.ignite.apache.org%3E
> http://apache-ignite-users.70518.x6.nabble.com/Re-2-8-1-INFO-org-apache-ignite-spi-communication-tcp-TcpCommunicationSpi-Accepted-incoming-communicn-td36096.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-14704) Implement runtime code generator as described in IGNITE-14496

2021-05-27 Thread Semyon Danilov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-14704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352548#comment-17352548
 ] 

Semyon Danilov commented on IGNITE-14704:
-

Looks good to me!

> Implement runtime code generator as described in IGNITE-14496
> -
>
> Key: IGNITE-14704
> URL: https://issues.apache.org/jira/browse/IGNITE-14704
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> As a proof of concept I implement runtime code generation of *Node and 
> *ConfigurationImpl clases. Motivation behind this decision is described in 
> https://issues.apache.org/jira/browse/IGNITE-14496.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14323) Messaging naming unification

2021-05-27 Thread Sergey Chugunov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Chugunov updated IGNITE-14323:
-
Fix Version/s: (was: 3.0.0-alpha2)
   3.0.0-alpha3

> Messaging naming unification
> 
>
> Key: IGNITE-14323
> URL: https://issues.apache.org/jira/browse/IGNITE-14323
> Project: Ignite
>  Issue Type: Sub-task
>  Components: networking
>Reporter: Sergey Chugunov
>Priority: Minor
> Fix For: 3.0.0-alpha3
>
>
> Naming of methods for message sending in NetworkCluster interface could be 
> unified.
> # *send* method returning CompletableFuture with semantics "send message and 
> wait when remote node replies with result".
> # *sendNoAck* method returning void with semantics "send message to remote 
> node and returns immediately when message is sent to it (written to output 
> connection)"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14567) Implement a snapshot abstraction for RAFT server.

2021-05-27 Thread Valentin Kulichenko (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valentin Kulichenko updated IGNITE-14567:
-
Fix Version/s: (was: 3.0.0-alpha2)
   3.0.0-alpha3

> Implement a snapshot abstraction for RAFT server.
> -
>
> Key: IGNITE-14567
> URL: https://issues.apache.org/jira/browse/IGNITE-14567
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
>  Labels: iep-61, ignite-3
> Fix For: 3.0.0-alpha3
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> In addition to command processing [1] we need a snapshot abstraction allowing 
> for dumping/restoring state machine state.
> [1] org.apache.ignite.raft.client.service.RaftGroupCommandListener



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14269) Design conditional multi update functionality for meta storage client

2021-05-27 Thread Andrey N. Gura (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey N. Gura updated IGNITE-14269:

Fix Version/s: (was: 3.0.0-alpha2)

> Design conditional multi update functionality for meta storage client
> -
>
> Key: IGNITE-14269
> URL: https://issues.apache.org/jira/browse/IGNITE-14269
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
>  Labels: iep-61, ignite-3
>
> Define entities required for implementation of conditional multi updates (aka 
> "transactions") for meta storage.
> Requirements:
> - Design should provide possibility to define conditional updates in 
> if-then-else manner with nested branches.
> - Update always starts with condition.
> - Any nested branch must start with condition. 
> - Update can't precede to condition.
> - Every branch can yield exactly one custom result (limited by number of 
> simple types) and any number of entries. Corresponding expression always must 
> be at the end of branch.
> - Condition for entry revision allows the following comparisons: equal, 
> !equal, less, greater.
> - Condition for entry value allows the following operations (byte-wise): 
> equal, !equal.
> - Update allows the following operations: put, remove, no-op.
> - Condition can not use previously defined condition instance again because 
> it will lead to graph cycle and infinite update execution.
> Assumptions:
> - It seems that conditions and updates entities can be conveniently linked 
> using chaining.
> Simple example (pseudocode):
> {code}
> CompletableFuture> = invoke(valCond(EQUAL, 
> perstEnabled, true)._then(
>  valCond(EQUAL, walEnabled, true)._then(
>  update(walEnabled, true)).
>  _else(
>  update(walEnabled, false))
> )._else(NoopUpdate))
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14296) Classes' names in network module don't need to start with `Network` prefix

2021-05-27 Thread Sergey Chugunov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Chugunov updated IGNITE-14296:
-
Fix Version/s: (was: 3.0.0-alpha2)
   3.0.0-alpha3

> Classes' names in network module don't need to start with `Network` prefix
> --
>
> Key: IGNITE-14296
> URL: https://issues.apache.org/jira/browse/IGNITE-14296
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergey Chugunov
>Priority: Trivial
> Fix For: 3.0.0-alpha3
>
>
> Classes' names in network module are self-explanatory and don't need a 
> special prefix, it could be removed to make the code more compact.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14297) API to unregister HandlerProvider from network module

2021-05-27 Thread Sergey Chugunov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Chugunov updated IGNITE-14297:
-
Fix Version/s: (was: 3.0.0-alpha2)
   3.0.0-alpha3

> API to unregister HandlerProvider from network module
> -
>
> Key: IGNITE-14297
> URL: https://issues.apache.org/jira/browse/IGNITE-14297
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Sergey Chugunov
>Priority: Major
> Fix For: 3.0.0-alpha3
>
>
> At the moment client components can register HandlerProviders in network 
> component but cannot unregister them.
> However this could be important in component lifecycle to properly stop the 
> component.
> API to unregister handler from the network with clear contract about possible 
> races (one thread unregisteres component's handler, another thread sends a 
> message from the same component) should be implemented.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14792) Calcite. Calcite can't plan an UPDATE if new column value depends on the old

2021-05-27 Thread Konstantin Orlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Orlov updated IGNITE-14792:
--
Description: 
The test 
\{{org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest#testInsertUpdateDeleteNonPrimitiveKey}}
 could be used as reproducer. The only change should be made is this one:
{code:java}
@@ -233,7 +233,7 @@
 
 assertEqualsCollections(F.asList(0, 0, "Igor", 1), row);
 
-query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
'Roman' WHERE id = ?", 0);
+query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
name || 'Roman' WHERE id = ?", 0);
 
 assertEquals(1, query.size());
 
{code}
The exception arises:

{noformat}
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
plan query.

at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:533)
at 
org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:390)
at 
org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:250)
at 
org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest.testInsertUpdateDeleteNonPrimitiveKey(TableDmlIntegrationTest.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: while converting `NAME` || 'Roman'
at 
org.apache.calcite.sql2rel.ReflectiveConvertletTable.lambda$registerNodeTypeMethod$0(ReflectiveConvertletTable.java:86)
at 
org.apache.calcite.sql2rel.SqlNodeToRexConverterImpl.convertCall(SqlNodeToRexConverterImpl.java:62)
at 
org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:5098)
at 
org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:4374)
at org.apache.calcite.sql.SqlCall.accept(SqlCall.java:139)
at 
org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.convertExpression(SqlToRelConverter.java:4961)
at 
org.apache.calcite.sql2rel.SqlToRelConverter.convertUpdate(SqlToRelConverter.java:3867)
at 
org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3444)
at 
org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:570)
at 
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.rel(IgnitePlanner.java:223)
at 
org.apache.ignite.internal.processors.query.calcite.exec.PlannerHelper.optimize(PlannerHelper.java:71)
at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareDml(ExecutionServiceImpl.java:603)
at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:560)
at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:513)
... 16 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.calcite.sql2rel.ReflectiveConvertletTable.lambda$registerNodeTypeMethod$0(ReflectiveConvertletTable.java:83)
... 29 more
Caused by: java.lang.AssertionError: Field ordinal 4 is invalid for  type 
'RecordType(OTHER _KEY, OTHER _VAL, VARCHAR EXPR$0)'
at 

[jira] [Created] (IGNITE-14792) Calcite. Calcite can't plan an UPDATE if new column value depends on the old

2021-05-27 Thread Konstantin Orlov (Jira)
Konstantin Orlov created IGNITE-14792:
-

 Summary: Calcite. Calcite can't plan an UPDATE if new column value 
depends on the old
 Key: IGNITE-14792
 URL: https://issues.apache.org/jira/browse/IGNITE-14792
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Konstantin Orlov


The test 
\{{org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest#testInsertUpdateDeleteNonPrimitiveKey}}
 could be used as reproducer. The only change should be made is this one:
{code:java}
@@ -233,7 +233,7 @@
 
 assertEqualsCollections(F.asList(0, 0, "Igor", 1), row);
 
-query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
'Roman' WHERE id = ?", 0);
+query = engine.query(null, "PUBLIC", "UPDATE DEVELOPER d SET name = 
name || 'Roman' WHERE id = ?", 0);
 
 assertEquals(1, query.size());
 
{code}
The exception arises:
{code:java}
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
plan query.class 
org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to plan 
query.
 at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:533)
 at 
org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
 at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:390)
 at 
org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:250)
 at 
org.apache.ignite.internal.processors.query.calcite.integration.TableDmlIntegrationTest.testInsertUpdateDeleteNonPrimitiveKey(TableDmlIntegrationTest.java:236)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498) at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) 
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) 
at 
org.apache.ignite.testframework.junits.GridAbstractTest$7.run(GridAbstractTest.java:2432)
 at java.lang.Thread.run(Thread.java:748)Caused by: java.lang.RuntimeException: 
while converting `NAME` || 'Roman' at 
org.apache.calcite.sql2rel.ReflectiveConvertletTable.lambda$registerNodeTypeMethod$0(ReflectiveConvertletTable.java:86)
 at 
org.apache.calcite.sql2rel.SqlNodeToRexConverterImpl.convertCall(SqlNodeToRexConverterImpl.java:62)
 at 
org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:5098)
 at 
org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:4374)
 at org.apache.calcite.sql.SqlCall.accept(SqlCall.java:139) at 
org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.convertExpression(SqlToRelConverter.java:4961)
 at 
org.apache.calcite.sql2rel.SqlToRelConverter.convertUpdate(SqlToRelConverter.java:3867)
 at 
org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3444)
 at 
org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:570)
 at 
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.rel(IgnitePlanner.java:223)
 at 
org.apache.ignite.internal.processors.query.calcite.exec.PlannerHelper.optimize(PlannerHelper.java:71)
 at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareDml(ExecutionServiceImpl.java:603)
 at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:560)
 at 
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:513)
 ... 16 moreCaused by: java.lang.reflect.InvocationTargetException at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498) at 
org.apache.calcite.sql2rel.ReflectiveConvertletTable.lambda$registerNodeTypeMethod$0(ReflectiveConvertletTable.java:83)
 ... 29 moreCaused by: java.lang.AssertionError: Field ordinal 4 is invalid for 
 type 'RecordType(OTHER _KEY, OTHER _VAL, VARCHAR EXPR$0)' at 

[jira] [Closed] (IGNITE-14786) Authentication ducktest should not use internal api

2021-05-27 Thread Mikhail Filatov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Filatov closed IGNITE-14786.


> Authentication ducktest should not use internal api
> ---
>
> Key: IGNITE-14786
> URL: https://issues.apache.org/jira/browse/IGNITE-14786
> Project: Ignite
>  Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Major
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Internal API used in test are different now.
> It's better to replace internal api usage to thin client (official 
> documentation way)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-14779) Calcite. Unblock NULLS FIRST|LAST functionality checks calling from script runner tests.

2021-05-27 Thread Taras Ledkov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-14779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352457#comment-17352457
 ] 

Taras Ledkov commented on IGNITE-14779:
---

[~zstan], the patch is OK with me.

> Calcite. Unblock NULLS FIRST|LAST functionality checks calling from script 
> runner tests.
> 
>
> Key: IGNITE-14779
> URL: https://issues.apache.org/jira/browse/IGNITE-14779
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Labels: calcite
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have numerous tests under _order/test_nulls_first.test_ but they seems to 
> be failed due to *#pragma* specific parameters which are not take into 
> account while calcite tests are running.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-14638) Calcite engine. Support for INTERSECT operator

2021-05-27 Thread Konstantin Orlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-14638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352449#comment-17352449
 ] 

Konstantin Orlov commented on IGNITE-14638:
---

[~alex_pl], I've left a few comments. Please see the PR.

> Calcite engine. Support for INTERSECT operator
> --
>
> Key: IGNITE-14638
> URL: https://issues.apache.org/jira/browse/IGNITE-14638
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Currently, INTERSECT operator is not supported



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (IGNITE-14791) Support byte[] configuration values

2021-05-27 Thread Ivan Bessonov (Jira)
Ivan Bessonov created IGNITE-14791:
--

 Summary: Support byte[] configuration values
 Key: IGNITE-14791
 URL: https://issues.apache.org/jira/browse/IGNITE-14791
 Project: Ignite
  Issue Type: Sub-task
Reporter: Ivan Bessonov


Right now "smallest" array type that we have is int[], it may not be convenient 
for some use-cases.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-12747) Calcite integration. Correlated queries support.

2021-05-27 Thread Stanilovsky Evgeny (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352441#comment-17352441
 ] 

Stanilovsky Evgeny commented on IGNITE-12747:
-

[~korlov] thanks for comments, all done, check it plz ?

> Calcite integration. Correlated queries support.
> 
>
> Key: IGNITE-12747
> URL: https://issues.apache.org/jira/browse/IGNITE-12747
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Igor Seliverstov
>Assignee: Andrey Mashenkov
>Priority: Critical
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Rewrite correlated subqueries.
> Useful links:
> [https://zhuanlan.zhihu.com/p/60380557]
> [https://zhuanlan.zhihu.com/p/62338250]
> [https://zhuanlan.zhihu.com/p/66227661]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-14658) [IEP-35] SSL metrics

2021-05-27 Thread Nikolay Izhikov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352433#comment-17352433
 ] 

Nikolay Izhikov commented on IGNITE-14658:
--

[~PetrovMikhail] Sounds reasonable. Please, go forward with implementation.

> [IEP-35] SSL metrics
> 
>
> Key: IGNITE-14658
> URL: https://issues.apache.org/jira/browse/IGNITE-14658
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Mikhail Petrov
>Priority: Major
>  Labels: IEP-35
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The following SSL metrics required:
> * Count of SSL sessions.
> * Count of rejected SSL sessions.
> * Handshake time metric.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14746) Improve row layout. Omit offset for the first varlen.

2021-05-27 Thread Yury Gerzhedovich (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Gerzhedovich updated IGNITE-14746:
---
Component/s: sql

> Improve row layout. Omit offset for the first varlen.
> -
>
> Key: IGNITE-14746
> URL: https://issues.apache.org/jira/browse/IGNITE-14746
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
>  Labels: iep-54, ignite-3
> Fix For: 3.0.0-alpha3
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Actually, there is no need to write varlen offset for the very first varlen 
> column.
> Therefore, vartable can be skipped if a single varlen column is defined for 
> key and/or value.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Reopened] (IGNITE-14544) Calcite engine. Support DISTINCT aggregates

2021-05-27 Thread Taras Ledkov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Taras Ledkov reopened IGNITE-14544:
---

> Calcite engine. Support DISTINCT aggregates
> ---
>
> Key: IGNITE-14544
> URL: https://issues.apache.org/jira/browse/IGNITE-14544
> Project: Ignite
>  Issue Type: Bug
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Now, DISTINCT aggregates not implemented.
> (e.g. {{SELECT COUNT (DISTINCT lastName) FROM person}})
> Tests:
> {{aggregate/aggregates/test_count.test}}
> {{aggregate/aggregates/test_avg.test}}
> {{aggregate/aggregates/test_distinct_aggr.test}}
> {{aggregate/aggregates/test_distinct_string_agg.test}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-14658) [IEP-35] SSL metrics

2021-05-27 Thread Mikhail Petrov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352358#comment-17352358
 ] 

Mikhail Petrov commented on IGNITE-14658:
-

It's proposed to add the following new metrics:

sslHandshakeDurationHistogram - provides the histogram of SSL handshake 
duration c.
sslRejectedSessionsCount - provides the number of rejected connections due to 
SSL errors (not exported if ssl is disabled).
sslEnabled - indicates whether SSL is enabled for the connector
activeSessionsCount - provides the number of active TCP sessions

Each of the mentioned above metrics will be added to the following metric 
groups that relate to different connectors (SSL is configured separately for 
each of them)

(NEW) client.connector.tcp - for metrics related to thin client connector SSL 
metrics.
(NEW) client.connector.rest.tcp - for metrics related to REST TCP client 
connector SSL metrics.
communication.tcp - for metrics related to node communicatonconnector SSL 
metrics.


It's also proposed to add the following metrics to discovery metric group - 
io.discovery.sslRejectedConnectionsMetric - tracks number of join connections 
that were rejected due to SSL errors ((not exported if ssl is disabled))
io.discovery.sslEnabled - tracks whether SSL is enabled for the discovery

> [IEP-35] SSL metrics
> 
>
> Key: IGNITE-14658
> URL: https://issues.apache.org/jira/browse/IGNITE-14658
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Mikhail Petrov
>Priority: Major
>  Labels: IEP-35
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The following SSL metrics required:
> * Count of SSL sessions.
> * Count of rejected SSL sessions.
> * Handshake time metric.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14790) Replace a storage map in RAFT partition listener to the persistence storage

2021-05-27 Thread Vladislav Pyatkov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladislav Pyatkov updated IGNITE-14790:
---
Description: 
The map is using as a temporary solution until storage will be implemented.
Here we need to implement the RAFT listener through the persistent layer:

{code:java}
/**
 * Storage.
 * This is a temporary solution, it will apply until persistence layer 
would not be implemented.
 * TODO: Replace in the future.
 */
private ConcurrentHashMap storage = new 
ConcurrentHashMap<>();
{code}


  was:
The map is using as a temporary solution until storage will be implemented.
Here we need to implement the RAFT listener through the persistent layer:

{code:java}
/**
 * Storage.
 * This is a temporary solution, it will apply until persistence layer 
would not be implemented.
 * TODO: Replace in the future.
 */
private ConcurrentHashMap storage = new 
ConcurrentHashMap<>();
{code}



> Replace a storage map in RAFT partition listener to the persistence storage
> ---
>
> Key: IGNITE-14790
> URL: https://issues.apache.org/jira/browse/IGNITE-14790
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
>
> The map is using as a temporary solution until storage will be implemented.
> Here we need to implement the RAFT listener through the persistent layer:
> {code:java}
> /**
>  * Storage.
>  * This is a temporary solution, it will apply until persistence layer 
> would not be implemented.
>  * TODO: Replace in the future.
>  */
> private ConcurrentHashMap storage = new 
> ConcurrentHashMap<>();
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (IGNITE-14790) Replace a storage map in RAFT partition listener to the persistence storage

2021-05-27 Thread Vladislav Pyatkov (Jira)
Vladislav Pyatkov created IGNITE-14790:
--

 Summary: Replace a storage map in RAFT partition listener to the 
persistence storage
 Key: IGNITE-14790
 URL: https://issues.apache.org/jira/browse/IGNITE-14790
 Project: Ignite
  Issue Type: Improvement
Reporter: Vladislav Pyatkov


The map is using as a temporary solution until storage will be implemented.
Here we need to implement the RAFT listener through the persistent layer:

{code:java}
/**
 * Storage.
 * This is a temporary solution, it will apply until persistence layer 
would not be implemented.
 * TODO: Replace in the future.
 */
private ConcurrentHashMap storage = new 
ConcurrentHashMap<>();
{code}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-14790) Replace a storage map in RAFT partition listener to the persistence storage

2021-05-27 Thread Vladislav Pyatkov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladislav Pyatkov reassigned IGNITE-14790:
--

Assignee: Vladislav Pyatkov

> Replace a storage map in RAFT partition listener to the persistence storage
> ---
>
> Key: IGNITE-14790
> URL: https://issues.apache.org/jira/browse/IGNITE-14790
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
>
> The map is using as a temporary solution until storage will be implemented.
> Here we need to implement the RAFT listener through the persistent layer:
> {code:java}
> /**
>  * Storage.
>  * This is a temporary solution, it will apply until persistence layer 
> would not be implemented.
>  * TODO: Replace in the future.
>  */
> private ConcurrentHashMap storage = new 
> ConcurrentHashMap<>();
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-14723) Add CLI command to restore a cache group from the snapshot.

2021-05-27 Thread Pavel Pereslegin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-14723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-14723:
--
Description: 
Add CLI command to restore a cache group from the snapshot.


{noformat}
  Restore snapshot:
control.(sh|bat) --snapshot restore --start snapshot_name [group1,...groupN]

Parameters:
  snapshot_name - Snapshot name.
  group1,...groupN  - Cache group names.

  Snapshot restore operation status:
control.(sh|bat) --snapshot restore --status snapshot_name

Parameters:
  snapshot_name  - Snapshot name.

  Cancel snapshot restore opeeration:
control.(sh|bat) --snapshot restore --cancel snapshot_name

Parameters:
  snapshot_name  - Snapshot name.
{noformat}


  was:
Add CLI command to restore a cache group from the snapshot.


{noformat}
restore all public caches from snapshot1
control.(sh|bat) --snapshot restore --start snapshot1

restore cache1 and cache2 from snapshot1
control.(sh|bat) --snapshot restore --start snapshot1 cache1,cache2

display status of restore operation
control.(sh|bat) --snapshot restore --status

cancel restore operation on cluster
control.(sh|bat) --snapshot restore --stop
{noformat}



> Add CLI command to restore a cache group from the snapshot.
> ---
>
> Key: IGNITE-14723
> URL: https://issues.apache.org/jira/browse/IGNITE-14723
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.11
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add CLI command to restore a cache group from the snapshot.
> {noformat}
>   Restore snapshot:
> control.(sh|bat) --snapshot restore --start snapshot_name 
> [group1,...groupN]
> Parameters:
>   snapshot_name - Snapshot name.
>   group1,...groupN  - Cache group names.
>   Snapshot restore operation status:
> control.(sh|bat) --snapshot restore --status snapshot_name
> Parameters:
>   snapshot_name  - Snapshot name.
>   Cancel snapshot restore opeeration:
> control.(sh|bat) --snapshot restore --cancel snapshot_name
> Parameters:
>   snapshot_name  - Snapshot name.
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-14739) Enable a permanent wal recording of transactions states records.

2021-05-27 Thread Alexey Scherbakov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-14739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352330#comment-17352330
 ] 

Alexey Scherbakov commented on IGNITE-14739:


[~zstan]

LGTM

 

> Enable a permanent wal recording of transactions states records.
> 
>
> Key: IGNITE-14739
> URL: https://issues.apache.org/jira/browse/IGNITE-14739
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.10
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Attachments: screenshot-1.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> After [1] was merged, i suggest to enable transactions states wal logging on 
> a permanent basis. This will allow to correctly restore transactional states 
> after partial or whole nodes crash. 
> [1] https://issues.apache.org/jira/browse/IGNITE-6324



--
This message was sent by Atlassian Jira
(v8.3.4#803005)