[jira] [Commented] (IGNITE-14157) SQL. Calcite: Returns the name of the variable for count operations as the column name

2021-02-20 Thread Konstantin Orlov (Jira)


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

Konstantin Orlov commented on IGNITE-14157:
---

LGTM!

> SQL. Calcite: Returns the name of the variable for count operations as the 
> column name
> --
>
> Key: IGNITE-14157
> URL: https://issues.apache.org/jira/browse/IGNITE-14157
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Fedor Malchikov 
>Assignee: Yury Gerzhedovich
>Priority: Major
>  Labels: calcite
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Example:
> {code:sql}
> CREATE TABLE t1 ( id INT NOT NULL, int_col INT, PRIMARY KEY (id));
> SELECT COUNT(*) FROM t1;
> ++
> | EXPR$0 |
> ++
> ++
> {code}
> H2 return as expected:
> {code:java}
>  SELECT COUNT(*) FROM t1;
> ++
> |COUNT(*)|
> ++
> | 0  |
> ++
> {code}



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


[jira] [Created] (IGNITE-14216) control.sh --cache list . --seq: NullPointerException

2021-02-20 Thread Surkov Aleksandr (Jira)
Surkov Aleksandr created IGNITE-14216:
-

 Summary: control.sh --cache list . --seq: NullPointerException
 Key: IGNITE-14216
 URL: https://issues.apache.org/jira/browse/IGNITE-14216
 Project: Ignite
  Issue Type: Bug
  Components: control.sh
Affects Versions: 2.9.1
Reporter: Surkov Aleksandr
 Attachments: full-stack-trace.txt

Executing the following command throws an error: _control.sh --cache list . 
--seq_


  
  



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


[jira] [Commented] (IGNITE-14157) SQL. Calcite: Returns the name of the variable for count operations as the column name

2021-02-20 Thread Yury Gerzhedovich (Jira)


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

Yury Gerzhedovich commented on IGNITE-14157:


[~korlov] thanks for the review. I've resolved all comments. Could you please 
do review it again?

> SQL. Calcite: Returns the name of the variable for count operations as the 
> column name
> --
>
> Key: IGNITE-14157
> URL: https://issues.apache.org/jira/browse/IGNITE-14157
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Fedor Malchikov 
>Assignee: Yury Gerzhedovich
>Priority: Major
>  Labels: calcite
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Example:
> {code:sql}
> CREATE TABLE t1 ( id INT NOT NULL, int_col INT, PRIMARY KEY (id));
> SELECT COUNT(*) FROM t1;
> ++
> | EXPR$0 |
> ++
> ++
> {code}
> H2 return as expected:
> {code:java}
>  SELECT COUNT(*) FROM t1;
> ++
> |COUNT(*)|
> ++
> | 0  |
> ++
> {code}



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


[jira] [Commented] (IGNITE-13557) Logging improvements for PDS memory restore process

2021-02-20 Thread Kirill Tkalenko (Jira)


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

Kirill Tkalenko commented on IGNITE-13557:
--

[~ibessonov] I made one change, the result is suites: 
https://ci.ignite.apache.org/viewLog.html?buildId=5884310;

> Logging improvements for PDS memory restore process
> ---
>
> Key: IGNITE-13557
> URL: https://issues.apache.org/jira/browse/IGNITE-13557
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Sergey Chugunov
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> During partition state restore phase of restoring memory state from disk 
> Ignite logs a lot of useful information on debug level but very little on 
> info.
> In many situations more detailed information can be useful for identification 
> of performance issues but printing info about all partitions is impractical 
> as it produces too much logs.
> The following improvements are possible though:
> # To identify any imbalance between partitions and find bigger-than-average 
> partitions we should gather statistics for each partition during restore 
> (part size and time it took to restore it). After restore we'll print 
> information about average time and top five partitions that took the most 
> time to restore.
> # To make progress of restoring visible we should print short message with 
> intermediate progress information periodically. This should be applied when 
> restore starts taking too long time (e.g. if restore hasn't finished in 5 
> minutes start printing progress each minute).



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


[jira] [Assigned] (IGNITE-14163) SQL. Calcite: Error: Failed to plan query. (state=50000,code=1)

2021-02-20 Thread Konstantin Orlov (Jira)


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

Konstantin Orlov reassigned IGNITE-14163:
-

Assignee: Konstantin Orlov

> SQL. Calcite:  Error: Failed to plan query. (state=5,code=1)
> 
>
> Key: IGNITE-14163
> URL: https://issues.apache.org/jira/browse/IGNITE-14163
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Fedor Malchikov 
>Assignee: Konstantin Orlov
>Priority: Blocker
> Attachments: caches.xml, create_env.txt, data-reg.xml, ignite.log, 
> server.xml, sqlline.log
>
>
> Problem reproduced on inner , right,  right outer joins and unions, but not 
> affected left\ left outer joins. 
> For test db creation please use create_env.txt.
> {code:SQL}
> SELECT t17_1.int_col1, t17_2.int_col1, t17_1.id FROM t17_1 INNER JOIN t17_2 
> ON t17_1.id=t17_2.id WHERE t17_1.int_col2  
> IN(0,1,-2,3,-5,7,-11,13,-17,19,-23,29,-31,37,-41,43,-47,53,-59,61,-67,71,-73,79,-83,89,-97)
>  OR t17_1.int_col1 > 10 ORDER BY t17_1.id;
> {code}
> {code:java}
> Error: Failed to plan query. (state=5,code=1)
> java.sql.SQLException: Failed to plan query.
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:1009)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:234)
>   at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:560)
>   at sqlline.Commands.execute(Commands.java:823)
>   at sqlline.Commands.sql(Commands.java:733)
>   at sqlline.SqlLine.dispatch(SqlLine.java:795)
>   at sqlline.SqlLine.runCommands(SqlLine.java:1706)
>   at sqlline.Commands.run(Commands.java:1317)
>   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 
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
>   at sqlline.SqlLine.dispatch(SqlLine.java:791)
>   at sqlline.SqlLine.initArgs(SqlLine.java:595)
>   at sqlline.SqlLine.begin(SqlLine.java:643)
>   at sqlline.SqlLine.start(SqlLine.java:373)
>   at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
> Ignite log:
> {code:java}
> [20:50:31,206][SEVERE][client-connector-#142][JdbcRequestHandler] Failed to 
> execute SQL query [reqId=392, req=JdbcQueryExecuteRequest [schemaName=PUBLIC, 
> pageSize=1024, maxRows=0, sqlQry=SELECT t17_1.int_col1, t17_2.int_col1, 
> t17_1.id FROM t17_1 INNER JOIN t17_2 ON t17_1.id=t17_2.id WHERE 
> t17_1.int_col1  
> IN(0,1,-2,3,-5,7,-11,13,-17,19,-23,29,-31,37,-41,43,-47,53,-59,61,-67,71,-73,79,-83,89,-97)
>  OR t17_1.int_col1 > 10 ORDER BY t17_1.id, args=Object[] [], 
> stmtType=ANY_STATEMENT_TYPE, autoCommit=true, partResReq=false, 
> explicitTimeout=false, super=JdbcRequest [type=2, reqId=392]]]
> 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:522)
>   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:379)
>   at 
> org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:248)
>   at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.querySqlFields(JdbcRequestHandler.java:790)
>   at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:673)
>   at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:341)
>   at 
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:278)
>   at 
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:202)
>   at 
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:56)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
>   at 
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
>   at 
> 

[jira] [Commented] (IGNITE-14157) SQL. Calcite: Returns the name of the variable for count operations as the column name

2021-02-20 Thread Konstantin Orlov (Jira)


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

Konstantin Orlov commented on IGNITE-14157:
---

Hi, [~jooger]! Overall looks good except a few minor remarks. Please see the PR 
for details.

> SQL. Calcite: Returns the name of the variable for count operations as the 
> column name
> --
>
> Key: IGNITE-14157
> URL: https://issues.apache.org/jira/browse/IGNITE-14157
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Fedor Malchikov 
>Assignee: Yury Gerzhedovich
>Priority: Major
>  Labels: calcite
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Example:
> {code:sql}
> CREATE TABLE t1 ( id INT NOT NULL, int_col INT, PRIMARY KEY (id));
> SELECT COUNT(*) FROM t1;
> ++
> | EXPR$0 |
> ++
> ++
> {code}
> H2 return as expected:
> {code:java}
>  SELECT COUNT(*) FROM t1;
> ++
> |COUNT(*)|
> ++
> | 0  |
> ++
> {code}



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


[jira] [Commented] (IGNITE-13557) Logging improvements for PDS memory restore process

2021-02-20 Thread Ivan Bessonov (Jira)


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

Ivan Bessonov commented on IGNITE-13557:


[~ktkale...@gridgain.com] code looks good, thank you!

> Logging improvements for PDS memory restore process
> ---
>
> Key: IGNITE-13557
> URL: https://issues.apache.org/jira/browse/IGNITE-13557
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Sergey Chugunov
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> During partition state restore phase of restoring memory state from disk 
> Ignite logs a lot of useful information on debug level but very little on 
> info.
> In many situations more detailed information can be useful for identification 
> of performance issues but printing info about all partitions is impractical 
> as it produces too much logs.
> The following improvements are possible though:
> # To identify any imbalance between partitions and find bigger-than-average 
> partitions we should gather statistics for each partition during restore 
> (part size and time it took to restore it). After restore we'll print 
> information about average time and top five partitions that took the most 
> time to restore.
> # To make progress of restoring visible we should print short message with 
> intermediate progress information periodically. This should be applied when 
> restore starts taking too long time (e.g. if restore hasn't finished in 5 
> minutes start printing progress each minute).



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


[jira] [Commented] (IGNITE-14176) Calcite improvements. Pk and Affinity key indexes are not considered for planning.

2021-02-20 Thread Stanilovsky Evgeny (Jira)


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

Stanilovsky Evgeny commented on IGNITE-14176:
-

[~tledkov-gridgain] [~korlov] [~jooger] patch is ready, checkstyle ok, tests ok.

> Calcite improvements. Pk and Affinity key indexes are not considered for 
> planning.
> --
>
> Key: IGNITE-14176
> URL: https://issues.apache.org/jira/browse/IGNITE-14176
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Labels: calcite
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> pk and affinity key indexes are not taken into account in planning phase.



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


[jira] [Issue Comment Deleted] (IGNITE-14214) Incorrect merge query when using oracle dialect

2021-02-20 Thread Yaroslav Molochkov (Jira)


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

Yaroslav Molochkov updated IGNITE-14214:

Comment: was deleted

(was: [~tledkov-gridgain], hello! Could you please take look?)

> Incorrect merge query when using oracle dialect
> ---
>
> Key: IGNITE-14214
> URL: https://issues.apache.org/jira/browse/IGNITE-14214
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.10, 2.9.1
>Reporter: Yaroslav Molochkov
>Assignee: Yaroslav Molochkov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If table contains only keys (e.g. relationship table) then returned query 
> contains empty update fields and resulting syntax is incorrect. 
> Consider the following example:
> org.apache.ignite.cache.store.jdbc.dialect.OracleDialect#mergeQuery accepts 
> key and val collections. The problem is relevant if val collection is empty.
> {code:java}
> return String.format("MERGE INTO %s t" +
> " USING (SELECT %s FROM dual) v" +
> "  ON %s" +
> " WHEN MATCHED THEN" +
> "  UPDATE SET %s" +
> " WHEN NOT MATCHED THEN" +
> "  INSERT (%s) VALUES (%s)", fullTblName, selCols, match, setCols, 
> colsLst, valuesCols);
> {code}



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


[jira] [Commented] (IGNITE-14214) Incorrect merge query when using oracle dialect

2021-02-20 Thread Yaroslav Molochkov (Jira)


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

Yaroslav Molochkov commented on IGNITE-14214:
-

[~tledkov-gridgain], hello! Could you please take look?

> Incorrect merge query when using oracle dialect
> ---
>
> Key: IGNITE-14214
> URL: https://issues.apache.org/jira/browse/IGNITE-14214
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.10, 2.9.1
>Reporter: Yaroslav Molochkov
>Assignee: Yaroslav Molochkov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If table contains only keys (e.g. relationship table) then returned query 
> contains empty update fields and resulting syntax is incorrect. 
> Consider the following example:
> org.apache.ignite.cache.store.jdbc.dialect.OracleDialect#mergeQuery accepts 
> key and val collections. The problem is relevant if val collection is empty.
> {code:java}
> return String.format("MERGE INTO %s t" +
> " USING (SELECT %s FROM dual) v" +
> "  ON %s" +
> " WHEN MATCHED THEN" +
> "  UPDATE SET %s" +
> " WHEN NOT MATCHED THEN" +
> "  INSERT (%s) VALUES (%s)", fullTblName, selCols, match, setCols, 
> colsLst, valuesCols);
> {code}



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


[jira] [Commented] (IGNITE-13557) Logging improvements for PDS memory restore process

2021-02-20 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-13557:


{panel:title=Branch: [pull/8751/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8751/head] Base: [master] : New Tests 
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS 1{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5883636]]
* {color:#013220}IgnitePdsTestSuite: 
RestorePartitionStateTest.testLogTopPartitions - PASSED{color}
* {color:#013220}IgnitePdsTestSuite: 
RestorePartitionStateTest.testTopRestorePartitionsToString - PASSED{color}
* {color:#013220}IgnitePdsTestSuite: 
RestorePartitionStateTest.testProcessedPartitionComparator - PASSED{color}
* {color:#013220}IgnitePdsTestSuite: RestorePartitionStateTest.testTrimToSize - 
PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5883667buildTypeId=IgniteTests24Java8_RunAll]

> Logging improvements for PDS memory restore process
> ---
>
> Key: IGNITE-13557
> URL: https://issues.apache.org/jira/browse/IGNITE-13557
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Reporter: Sergey Chugunov
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> During partition state restore phase of restoring memory state from disk 
> Ignite logs a lot of useful information on debug level but very little on 
> info.
> In many situations more detailed information can be useful for identification 
> of performance issues but printing info about all partitions is impractical 
> as it produces too much logs.
> The following improvements are possible though:
> # To identify any imbalance between partitions and find bigger-than-average 
> partitions we should gather statistics for each partition during restore 
> (part size and time it took to restore it). After restore we'll print 
> information about average time and top five partitions that took the most 
> time to restore.
> # To make progress of restoring visible we should print short message with 
> intermediate progress information periodically. This should be applied when 
> restore starts taking too long time (e.g. if restore hasn't finished in 5 
> minutes start printing progress each minute).



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


[jira] [Commented] (IGNITE-5266) .NET: Support LongCount in LINQ

2021-02-20 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-5266:
---

{panel:title=Branch: [pull/8817/head] Base: [master] : Possible Blockers 
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5884157]]

{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5884100]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoveryCommunicationFailureTest.testDefaultCommunicationFailureResolver1
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}[Missing Tests]{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5884163]]

{panel}
{panel:title=Branch: [pull/8817/head] Base: [master] : New Tests 
(168)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Scala (Examples){color} [[tests 
18|https://ci.ignite.apache.org/viewLog.html?buildId=5883703]]
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarSharedRDDExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarWorldShortestMapReduceExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarTaskExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarSnowflakeSchemaExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarPingPongExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarCacheExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarCacheEntryProcessorExample - 
PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarPrimeExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarSharedRDDExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarClosureExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarCreditRiskExample - PASSED{color}
... and 7 new tests

{color:#8b}Platform .NET (Long Running){color} [[tests 
17|https://ci.ignite.apache.org/viewLog.html?buildId=5883747]]
* {color:#013220}exe: ExamplesTest.TestLocalNode(ServicesExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(AtomicLongExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(AtomicReferenceExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(AtomicSequenceExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(BinaryModeExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(ClientReconnectExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(ClosureExample) - PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(ContinuousQueryExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(DataStreamerExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(EntryProcessorExample) - 
PASSED{color}
* {color:#013220}exe: ExamplesTest.TestLocalNode(EventsExample) - PASSED{color}
... and 6 new tests

{color:#8b}Platform .NET{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5884138]]
* {color:#013220}exe: ProjectFilesTest.CheckConfigFilesExist - PASSED{color}

{color:#8b}Dev Utils{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5883759]]
* {color:#013220}DevUtilsTestSuite: 
IgniteWalConverterSensitiveDataTest.testNotPrintRecordsByDefault - PASSED{color}
* {color:#013220}DevUtilsTestSuite: 
IgniteWalConverterSensitiveDataTest.testShowSensitiveData - PASSED{color}

{color:#8b}[Missing Tests]{color} [[tests 
130|https://ci.ignite.apache.org/viewLog.html?buildId=5884163]]
* {color:#013220}org.apache.ignite.util.GridQueueSelfTest.testQueue - 
PASSED{color}
* 
{color:#013220}org.apache.ignite.util.GridSpinReadWriteLockSelfTest.testMonitorState
 - PASSED{color}
* 
{color:#013220}org.apache.ignite.util.GridSpinReadWriteLockSelfTest.testReadLockReentry
 - PASSED{color}
* 
{color:#013220}org.apache.ignite.util.GridStringBuilderFactorySelfTest.testStringBuilderFactory
 - PASSED{color}
* 
{color:#013220}org.apache.ignite.util.GridSpinReadWriteLockSelfTest.testLockDowngrade
 - PASSED{color}
* 
{color:#013220}org.apache.ignite.util.GridSpinReadWriteLockSelfTest.testWriteLockReentry
 - PASSED{color}
* 
{color:#013220}org.apache.ignite.util.mbeans.GridMBeanSelfTest.testMissedNameMBeanInfo
 - PASSED{color}
* 

[jira] [Resolved] (IGNITE-14156) SQL. Calcite: Does not return the count result if there are 0 elements in the table.

2021-02-20 Thread Taras Ledkov (Jira)


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

Taras Ledkov resolved IGNITE-14156.
---
Resolution: Fixed

The patch is OK with me.
Merged to the branch 
[sql-calcite|https://github.com/apache/ignite/commit/781bd1443e25164fca6923e3e3038f61a6a1a471].

>  SQL. Calcite: Does not return the count result if there are 0 elements in 
> the table.
> -
>
> Key: IGNITE-14156
> URL: https://issues.apache.org/jira/browse/IGNITE-14156
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Fedor Malchikov 
>Assignee: Yury Gerzhedovich
>Priority: Major
>  Labels: calcite
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Example:
> {code:sql}
> CREATE TABLE t1 ( id INT NOT NULL, int_col INT, PRIMARY KEY (id));
> SELECT COUNT(*) FROM t1;
> ++
> | EXPR$0 |
> ++
> ++
> {code}
> H2 return:
> {code:java}
>  SELECT COUNT(*) FROM t1;
> ++
> |COUNT(*)|
> ++
> | 0  |
> ++
> {code}
> if add some elements, then calcite return value:
> {code:SQL}
> SELECT COUNT(*) FROM t1;
> ++
> | EXPR$0 |
> ++
> | 5  |
> ++
> {code}



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


[jira] [Issue Comment Deleted] (IGNITE-5266) .NET: Support LongCount in LINQ

2021-02-20 Thread Pavel Tupitsyn (Jira)


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

Pavel Tupitsyn updated IGNITE-5266:
---
Comment: was deleted

(was: {panel:title=Branch: [pull/8817/head] Base: [master] : Possible Blockers 
(19)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5883705]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore_NonCoordinator2
 - Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore_NonCoordinator1
 - Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore2 - 
Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore1 - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Queries 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5883694]]
* IgniteBinaryCacheQueryTestSuite2: 
DynamicEnableIndexingBasicSelfTest.testEnableDynamicIndexing[hasNear=false,nodeIdx=2,cacheMode=PARTITIONED,atomicityMode=ATOMIC]
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5883743]]
* exe: 
PluginTest.IgnitionStart_ValidPluginConfiguration_StartsAndReturnsWorkingPlugin 
- Test has low fail rate in base branch 0,0% and is not flaky
* exe: PeerAssemblyLoadingTest.TestDisabledPeerLoading - Test has low fail rate 
in base branch 0,0% and is not flaky
* exe: PeerAssemblyLoadingTest.TestSingleAssembly - Test has low fail rate in 
base branch 0,0% and is not flaky
* exe: PeerAssemblyLoadingVersioningTest.TestMultipleVersionsOfSameAssembly - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}PDS 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5883739]]
* IgnitePdsTestSuite: 
IgnitePdsDestroyCacheWithoutCheckpointsTest.testDestroyGroupCachesAbruptlyWithoutCheckpoints
 - Test has low fail rate in base branch 1,3% and is not flaky
* IgnitePdsTestSuite: 
IgnitePdsDestroyCacheWithoutCheckpointsTest.testDestroyCachesAbruptlyWithoutCheckpoints
 - Test has low fail rate in base branch 1,3% and is not flaky

{color:#d04437}Cassandra Store{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5883756]]
* org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite: 
org.apache.ignite.tests.IgnitePersistentStorePrimitiveTest. - History for base 
branch is absent.

{color:#d04437}[Missing Tests]{color} [[tests 6 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5883768]]
* 
org.apache.ignite.loadtests.direct.newnodes.GridSingleSplitsNewNodesMulticastLoadTest.testLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.session.GridSessionLoadTest.testSessionLoad 
- History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.multisplit.GridMultiSplitsRedeployLoadTest.testLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.redeploy.GridSingleSplitsRedeployLoadTest.testLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.stealing.GridStealingLoadTest.testStealingLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.multisplit.GridMultiSplitsLoadTest.testLoad 
- History for base branch is absent.

{panel}
{panel:title=Branch: [pull/8817/head] Base: [master] : New Tests 
(95)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Scala (Examples){color} [[tests 
18|https://ci.ignite.apache.org/viewLog.html?buildId=5883703]]
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarSharedRDDExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarWorldShortestMapReduceExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarTaskExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarSnowflakeSchemaExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarPingPongExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarCacheExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarCacheEntryProcessorExample - 
PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 

[jira] [Commented] (IGNITE-5266) .NET: Support LongCount in LINQ

2021-02-20 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-5266:
---

{panel:title=Branch: [pull/8817/head] Base: [master] : Possible Blockers 
(19)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5883705]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore_NonCoordinator2
 - Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore_NonCoordinator1
 - Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore2 - 
Test has low fail rate in base branch 0,0% and is not flaky
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testConnectionRestore1 - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Queries 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5883694]]
* IgniteBinaryCacheQueryTestSuite2: 
DynamicEnableIndexingBasicSelfTest.testEnableDynamicIndexing[hasNear=false,nodeIdx=2,cacheMode=PARTITIONED,atomicityMode=ATOMIC]
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Platform .NET{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=5883743]]
* exe: 
PluginTest.IgnitionStart_ValidPluginConfiguration_StartsAndReturnsWorkingPlugin 
- Test has low fail rate in base branch 0,0% and is not flaky
* exe: PeerAssemblyLoadingTest.TestDisabledPeerLoading - Test has low fail rate 
in base branch 0,0% and is not flaky
* exe: PeerAssemblyLoadingTest.TestSingleAssembly - Test has low fail rate in 
base branch 0,0% and is not flaky
* exe: PeerAssemblyLoadingVersioningTest.TestMultipleVersionsOfSameAssembly - 
Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}PDS 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5883739]]
* IgnitePdsTestSuite: 
IgnitePdsDestroyCacheWithoutCheckpointsTest.testDestroyGroupCachesAbruptlyWithoutCheckpoints
 - Test has low fail rate in base branch 1,3% and is not flaky
* IgnitePdsTestSuite: 
IgnitePdsDestroyCacheWithoutCheckpointsTest.testDestroyCachesAbruptlyWithoutCheckpoints
 - Test has low fail rate in base branch 1,3% and is not flaky

{color:#d04437}Cassandra Store{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5883756]]
* org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite: 
org.apache.ignite.tests.IgnitePersistentStorePrimitiveTest. - History for base 
branch is absent.

{color:#d04437}[Missing Tests]{color} [[tests 6 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5883768]]
* 
org.apache.ignite.loadtests.direct.newnodes.GridSingleSplitsNewNodesMulticastLoadTest.testLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.session.GridSessionLoadTest.testSessionLoad 
- History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.multisplit.GridMultiSplitsRedeployLoadTest.testLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.redeploy.GridSingleSplitsRedeployLoadTest.testLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.stealing.GridStealingLoadTest.testStealingLoad
 - History for base branch is absent.
* 
org.apache.ignite.loadtests.direct.multisplit.GridMultiSplitsLoadTest.testLoad 
- History for base branch is absent.

{panel}
{panel:title=Branch: [pull/8817/head] Base: [master] : New Tests 
(95)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}Scala (Examples){color} [[tests 
18|https://ci.ignite.apache.org/viewLog.html?buildId=5883703]]
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarSharedRDDExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarWorldShortestMapReduceExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarTaskExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesSelfTest.testScalarSnowflakeSchemaExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarPingPongExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarCacheExample - PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: 
ScalarExamplesMultiNodeSelfTest.testScalarCacheEntryProcessorExample - 
PASSED{color}
* {color:#013220}ScalarExamplesSelfTestSuite: