[jira] [Created] (IGNITE-16254) Optimize (un)marshalling of primitives in object fields
Roman Puchkovskiy created IGNITE-16254: -- Summary: Optimize (un)marshalling of primitives in object fields Key: IGNITE-16254 URL: https://issues.apache.org/jira/browse/IGNITE-16254 Project: Ignite Issue Type: Improvement Components: networking Reporter: Roman Puchkovskiy Assignee: Roman Puchkovskiy Fix For: 3.0.0-alpha4 Currently, during both marshalling and unmarshalling of primitives from/to fields an intermediary boxed object might be allocated on the heap. We can use Unsafe to avoid this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15368) s390x support to Apache Ignite TeamCity CI
[ https://issues.apache.org/jira/browse/IGNITE-15368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472456#comment-17472456 ] Vibhuti Sawant commented on IGNITE-15368: - Hi [~vveider] Would like to check if there are any updates on who will be signing the T? Thanks. > s390x support to Apache Ignite TeamCity CI > --- > > Key: IGNITE-15368 > URL: https://issues.apache.org/jira/browse/IGNITE-15368 > Project: Ignite > Issue Type: Wish >Affects Versions: 2.10 >Reporter: Anuja Jakhade >Assignee: Petr Ivanov >Priority: Major > > Hi, > I wanted to know details about the TeamCity CI used by Apache Ignite. > Is it possible to add s390x support to the CI? > I had raised a PR for adding s390x support in Travis. But got to know that > Travis is meant only for pull checks. > https://github.com/apache/ignite/pull/7931 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (IGNITE-16252) The Apache Ignite logo & cluster graphic in the README appear as broken images
[ https://issues.apache.org/jira/browse/IGNITE-16252 ] Brennan Fox deleted comment on IGNITE-16252: -- was (Author: JIRAUSER283362): The [ticket creation guidelines|https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-TicketCreation] suggest I should assign this to nyself and set it to In Progress. Unfortunately, I do not have permissions to do so. I'd appreciate someone helping me out. > The Apache Ignite logo & cluster graphic in the README appear as broken images > -- > > Key: IGNITE-16252 > URL: https://issues.apache.org/jira/browse/IGNITE-16252 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Brennan Fox >Priority: Minor > Labels: newbie > Attachments: before.png > > > The Apache Ignite logo & cluster graphic in the README appear as broken images > Steps to reproduce: > * Navigate to [https://github.com/apache/ignite] > * Look at the README > Issue - The images appear as broken images (see screenshot) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16253) CPP Thin:IgniteSQLException:Failed to wrap object into H2 value.[B cannot be cast to java.lang.Byte
YuJue Li created IGNITE-16253: - Summary: CPP Thin:IgniteSQLException:Failed to wrap object into H2 value.[B cannot be cast to java.lang.Byte Key: IGNITE-16253 URL: https://issues.apache.org/jira/browse/IGNITE-16253 Project: Ignite Issue Type: Bug Components: thin client Affects Versions: 2.11.1 Reporter: YuJue Li Fix For: 2.13 Attachments: igniteThinTest.zip the reproducer see attachment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16252) The Apache Ignite logo & cluster graphic in the README appear as broken images
[ https://issues.apache.org/jira/browse/IGNITE-16252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472403#comment-17472403 ] Brennan Fox commented on IGNITE-16252: -- The [ticket creation guidelines|https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-TicketCreation] suggest I should assign this to nyself and set it to In Progress. Unfortunately, I do not have permissions to do so. I'd appreciate someone helping me out. > The Apache Ignite logo & cluster graphic in the README appear as broken images > -- > > Key: IGNITE-16252 > URL: https://issues.apache.org/jira/browse/IGNITE-16252 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Brennan Fox >Priority: Minor > Labels: newbie > Attachments: before.png > > > The Apache Ignite logo & cluster graphic in the README appear as broken images > Steps to reproduce: > * Navigate to [https://github.com/apache/ignite] > * Look at the README > Issue - The images appear as broken images (see screenshot) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15864) CPP Thin: Implement asynchronous network events handling
[ https://issues.apache.org/jira/browse/IGNITE-15864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472333#comment-17472333 ] Igor Sapego commented on IGNITE-15864: -- [~ptupitsyn], [~ivandasch] thanks for the review. Merging to master. > CPP Thin: Implement asynchronous network events handling > > > Key: IGNITE-15864 > URL: https://issues.apache.org/jira/browse/IGNITE-15864 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.11 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.13 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > Currently, C++ thin client handles all network operations synchronously. I.e > after sending a request to a server it blocks entire socket until it receives > response. Let's implement asynchronous socket events handling in separate > connection or connection pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15864) CPP Thin: Implement asynchronous network events handling
[
https://issues.apache.org/jira/browse/IGNITE-15864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472332#comment-17472332
]
Ignite TC Bot commented on IGNITE-15864:
{panel:title=Branch: [pull/9713/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9713/head] Base: [master] : New Tests
(1035)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
1026|https://ci.ignite.apache.org/viewLog.html?buildId=6359964]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 1015 new tests
{color:#8b}Platform C++ CMake (Win x64 / Release){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6360361]]
* {color:#013220}IgniteThinClientTest: IgniteClientTestSuite:
IgniteClientReconnect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutAllGetAll
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutGet -
PASSED{color}
{color:#8b}Platform C++ CMake (Linux Clang){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6360358]]
* {color:#013220}IgniteThinClientTest: IgniteClientTestSuite:
IgniteClientReconnect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutAllGetAll
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutGet -
PASSED{color}
{color:#8b}Platform C++ CMake (Linux){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6360359]]
* {color:#013220}IgniteThinClientTest: IgniteClientTestSuite:
IgniteClientReconnect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutAllGetAll
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutGet -
PASSED{color}
{panel}
[TeamCity *- Run :: CPP*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6359966buildTypeId=IgniteTests24Java8_RunCpp]
> CPP Thin: Implement asynchronous network events handling
>
>
> Key: IGNITE-15864
> URL: https://issues.apache.org/jira/browse/IGNITE-15864
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.11
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently, C++ thin client handles all network operations synchronously. I.e
> after sending a request to a server it blocks entire socket until it receives
> response. Let's implement asynchronous socket events handling in separate
> connection or connection pool.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16252) The Apache Ignite logo & cluster graphic in the README appear as broken images
[ https://issues.apache.org/jira/browse/IGNITE-16252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brennan Fox updated IGNITE-16252: - Ignite Flags: Docs Required (was: Docs Required,Release Notes Required) > The Apache Ignite logo & cluster graphic in the README appear as broken images > -- > > Key: IGNITE-16252 > URL: https://issues.apache.org/jira/browse/IGNITE-16252 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Brennan Fox >Priority: Minor > Labels: newbie > Attachments: before.png > > > The Apache Ignite logo & cluster graphic in the README appear as broken images > Steps to reproduce: > * Navigate to [https://github.com/apache/ignite] > * Look at the README > Issue - The images appear as broken images (see screenshot) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16252) The Apache Ignite logo & cluster graphic in the README appear as broken images
[ https://issues.apache.org/jira/browse/IGNITE-16252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brennan Fox updated IGNITE-16252: - Ignite Flags: (was: Docs Required) > The Apache Ignite logo & cluster graphic in the README appear as broken images > -- > > Key: IGNITE-16252 > URL: https://issues.apache.org/jira/browse/IGNITE-16252 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Brennan Fox >Priority: Minor > Labels: newbie > Attachments: before.png > > > The Apache Ignite logo & cluster graphic in the README appear as broken images > Steps to reproduce: > * Navigate to [https://github.com/apache/ignite] > * Look at the README > Issue - The images appear as broken images (see screenshot) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16252) The Apache Ignite logo & cluster graphic in the README appear as broken images
[ https://issues.apache.org/jira/browse/IGNITE-16252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472268#comment-17472268 ] Brennan Fox commented on IGNITE-16252: -- PR opened - https://github.com/apache/ignite/pull/9718 > The Apache Ignite logo & cluster graphic in the README appear as broken images > -- > > Key: IGNITE-16252 > URL: https://issues.apache.org/jira/browse/IGNITE-16252 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Brennan Fox >Priority: Minor > Labels: newbie > Attachments: before.png > > > The Apache Ignite logo & cluster graphic in the README appear as broken images > Steps to reproduce: > * Navigate to [https://github.com/apache/ignite] > * Look at the README > Issue - The images appear as broken images (see screenshot) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16252) The Apache Ignite logo & cluster graphic in the README appear as broken images
Brennan Fox created IGNITE-16252: Summary: The Apache Ignite logo & cluster graphic in the README appear as broken images Key: IGNITE-16252 URL: https://issues.apache.org/jira/browse/IGNITE-16252 Project: Ignite Issue Type: Bug Components: documentation Reporter: Brennan Fox Attachments: before.png The Apache Ignite logo & cluster graphic in the README appear as broken images Steps to reproduce: * Navigate to [https://github.com/apache/ignite] * Look at the README Issue - The images appear as broken images (see screenshot) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16251) .NET: Improve startup debug logging when locating JVM and classpath
Pavel Tupitsyn created IGNITE-16251: --- Summary: .NET: Improve startup debug logging when locating JVM and classpath Key: IGNITE-16251 URL: https://issues.apache.org/jira/browse/IGNITE-16251 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.13 Log more details when locating JVM (*GetJvmDllPaths*) and classpath. In particular, log errors from *Shell.ExecuteSafe* to understand what has gone wrong. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16223) Log query id for long running query.
[ https://issues.apache.org/jira/browse/IGNITE-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472152#comment-17472152 ] Nikolay Izhikov commented on IGNITE-16223: -- Good catch guys. Thanks for fix. > Log query id for long running query. > > > Key: IGNITE-16223 > URL: https://issues.apache.org/jira/browse/IGNITE-16223 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Fix For: 2.13 > > Time Spent: 40m > Remaining Estimate: 0h > > Currently, the long running query warning does not have a query ID. > Therefore, it is not possible to run the KILL QUERY command because of this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16250) Use direct marshaller and user object serialization instead of JDK serialization for networking
Semyon Danilov created IGNITE-16250: --- Summary: Use direct marshaller and user object serialization instead of JDK serialization for networking Key: IGNITE-16250 URL: https://issues.apache.org/jira/browse/IGNITE-16250 Project: Ignite Issue Type: Task Reporter: Semyon Danilov Assignee: Semyon Danilov Fix For: 3.0.0-alpha4 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16169) Bugyard feedback #37: Return missing page to latest
[ https://issues.apache.org/jira/browse/IGNITE-16169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472106#comment-17472106 ] Igor Gusev commented on IGNITE-16169: - [~nsafonov] Please see if we can merge the PR. > Bugyard feedback #37: Return missing page to latest > --- > > Key: IGNITE-16169 > URL: https://issues.apache.org/jira/browse/IGNITE-16169 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.11 >Reporter: Nikita A. Safonov >Assignee: Nikita A. Safonov >Priority: Major > Labels: documentaion, documentation > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > This page [https://ignite.apache.org/docs/2.10.0/persistence/snapshots#] is > missing in the latest version of docs. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16170) Bugyard feedback #38-#41: Fix broken links in the docs
[ https://issues.apache.org/jira/browse/IGNITE-16170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472087#comment-17472087 ] Igor Gusev commented on IGNITE-16170: - [~nsafonov] please review and merge the PR. > Bugyard feedback #38-#41: Fix broken links in the docs > -- > > Key: IGNITE-16170 > URL: https://issues.apache.org/jira/browse/IGNITE-16170 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.11 >Reporter: Nikita A. Safonov >Assignee: Igor Gusev >Priority: Major > Labels: documentaion, documentation > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > The following links in the latest version of docs return the 404 error (from > the [https://ignite.apache.org/docs/latest/clustering/baseline-topology#] > page): > * [https://ignite.apache.org/docs/latest/control-script#activating-cluster] > * > [https://ignite.apache.org/docs/latest/control-script#activation-deactivation-and-topology-management] > * [https://ignite.apache.org/docs/latest/control-script] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16249) Some SQL query logs should be WARN instead of ERROR.
[
https://issues.apache.org/jira/browse/IGNITE-16249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov reassigned IGNITE-16249:
-
Assignee: Andrey Mashenkov
> Some SQL query logs should be WARN instead of ERROR.
>
>
> Key: IGNITE-16249
> URL: https://issues.apache.org/jira/browse/IGNITE-16249
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
>
> User experience a lot of messages logged at error level, however, they must
> be logged at warn level. Because the failure is recoverable and relates to a
> particular user request.
>
> {noformat}
> [2021-12-01T14:29:49,635][ERROR][client-connector-#102%nebula-node%][ClientListenerNioListener]
> Failed to process client request
> [req=o.a.i.i.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest@6d1b5aac]
> org.apache.ignite.transactions.TransactionDuplicateKeyException: Duplicate
> key during INSERT [key=]
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.dmlDoInsert(DmlUtils.java:206)
>
> at
> org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.processSelectResult(DmlUtils.java:169)
>
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateNonTransactional(IgniteH2Indexing.java:3190)
>
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdate(IgniteH2Indexing.java:3034)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateDistributed(IgniteH2Indexing.java:2961)
>
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeDml(IgniteH2Indexing.java:1310)
> ..
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2794)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2750)
>
> at
> org.apache.ignite.internal.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest.process(ClientCacheSqlFieldsQueryRequest.java:147)
> .{noformat}
> {noformat}
> [15:38:19,355][SEVERE][client-connector-#124][ClientListenerNioListener]
> Failed to process client request
> [req=o.a.i.i.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest@18a76b4]
> class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
> to parse query. Column "TBL.COL1" not found; SQL statement:
> select * from TBL where COL1 = [42122-197]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2375)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:2076)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1895)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2223)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2218)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:35)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2725)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$0(GridQueryProcessor.java:2240)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2260)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2211)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2137)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2093)
> at
> org.apache.ignite.internal.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest.process(ClientCacheSqlFieldsQueryRequest.java:106)
> at
> org.apache.ignite.internal.processors.platform.client.ClientRequestHandler.handle(ClientRequestHandler.java:51)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:183)
> ..
> Caused by: org.h2.jdbc.JdbcSQLException: Column "TBL.COL1" not found; SQL
> statement:
> select * from TBL where COL1 =
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
> at org.h2.message.DbException.get(DbException.java:179)
> at
[jira] [Commented] (IGNITE-16208) .NET: Thin 3.0: Transactions
[ https://issues.apache.org/jira/browse/IGNITE-16208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472058#comment-17472058 ] Pavel Tupitsyn commented on IGNITE-16208: - Merged to main: 8555619c206b283ba7593927592599d3719f2f53 > .NET: Thin 3.0: Transactions > > > Key: IGNITE-16208 > URL: https://issues.apache.org/jira/browse/IGNITE-16208 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 40m > Remaining Estimate: 0h > > Implement transactions in .NET thin client. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16249) Some SQL query logs should be WARN instead of ERROR.
Andrey Mashenkov created IGNITE-16249:
-
Summary: Some SQL query logs should be WARN instead of ERROR.
Key: IGNITE-16249
URL: https://issues.apache.org/jira/browse/IGNITE-16249
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Andrey Mashenkov
User experience a lot of messages logged at error level, however, they must be
logged at warn level. Because the failure is recoverable and relates to a
particular user request.
{noformat}
[2021-12-01T14:29:49,635][ERROR][client-connector-#102%nebula-node%][ClientListenerNioListener]
Failed to process client request
[req=o.a.i.i.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest@6d1b5aac]
org.apache.ignite.transactions.TransactionDuplicateKeyException: Duplicate key
during INSERT [key=]
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.dmlDoInsert(DmlUtils.java:206)
at
org.apache.ignite.internal.processors.query.h2.dml.DmlUtils.processSelectResult(DmlUtils.java:169)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateNonTransactional(IgniteH2Indexing.java:3190)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdate(IgniteH2Indexing.java:3034)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeUpdateDistributed(IgniteH2Indexing.java:2961)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeDml(IgniteH2Indexing.java:1310)
..
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2794)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2750)
at
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest.process(ClientCacheSqlFieldsQueryRequest.java:147)
.{noformat}
{noformat}
[15:38:19,355][SEVERE][client-connector-#124][ClientListenerNioListener] Failed
to process client request
[req=o.a.i.i.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest@18a76b4]
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to
parse query. Column "TBL.COL1" not found; SQL statement:
select * from TBL where COL1 = [42122-197]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2375)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:2076)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1895)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2223)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$3.applyx(GridQueryProcessor.java:2218)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:35)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2725)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$0(GridQueryProcessor.java:2240)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2260)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2211)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2137)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2093)
at
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheSqlFieldsQueryRequest.process(ClientCacheSqlFieldsQueryRequest.java:106)
at
org.apache.ignite.internal.processors.platform.client.ClientRequestHandler.handle(ClientRequestHandler.java:51)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:183)
..
Caused by: org.h2.jdbc.JdbcSQLException: Column "TBL.COL1" not found; SQL
statement:
select * from TBL where COL1 =
at org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at
org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:150)
at org.h2.command.dml.Select.prepare(Select.java:858)
at org.h2.command.Parser.prepareCommand(Parser.java:283)
at org.h2.engine.Session.prepareLocal(Session.java:611)
at org.h2.engine.Session.prepareCommand(Session.java:549)
at
[jira] [Updated] (IGNITE-16248) Ignite-extensions: CDC tests fails after IGNITE-15558
[ https://issues.apache.org/jira/browse/IGNITE-16248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-16248: Description: It is needed to fix CDC tests that start to fail after IGNITE-15558. The main reason of failures is that after IGNITE-15558 IteratorParametersBuilder#pageSize is set in CdcMain#consumeSegment. Since DataStorageConfiguration#pageSize default variable is 0, IteratorParametersBuilder#validate throws an exception considering that page size must be at least 4 kB. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E was: It is needed to fix CDC tests that start to fail after IGNITE-15558. The main reason of failures is that after IGNITE-15558 IteratorParametersBuilder#pageSize is started to be set in CdcMain#consumeSegment. Since DataStorageConfiguration#pageSize default variable is 0, IteratorParametersBuilder#validate throws an exception considering that page size must be at least 4 kB. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E > Ignite-extensions: CDC tests fails after IGNITE-15558 > - > > Key: IGNITE-16248 > URL: https://issues.apache.org/jira/browse/IGNITE-16248 > Project: Ignite > Issue Type: Test >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to fix CDC tests that start to fail after IGNITE-15558. > The main reason of failures is that after IGNITE-15558 > IteratorParametersBuilder#pageSize is set in CdcMain#consumeSegment. > Since DataStorageConfiguration#pageSize default variable is 0, > IteratorParametersBuilder#validate throws an exception considering that page > size must be at least 4 kB. > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16248) Ignite-extensions: CDC tests fails after IGNITE-15558
[ https://issues.apache.org/jira/browse/IGNITE-16248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-16248: Description: It is needed to fix CDC tests that start to fail after IGNITE-15558. The main reason of failures is that after IGNITE-15558 IteratorParametersBuilder#pageSize is started to be set in CdcMain#consumeSegment. Since DataStorageConfiguration#pageSize default variable is 0, IteratorParametersBuilder#validate throws an exception considering that page size must be at least 4 kB. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E was: It is needed to fix CDC tests that start to fail after IGNITE-15558. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E > Ignite-extensions: CDC tests fails after IGNITE-15558 > - > > Key: IGNITE-16248 > URL: https://issues.apache.org/jira/browse/IGNITE-16248 > Project: Ignite > Issue Type: Test >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to fix CDC tests that start to fail after IGNITE-15558. > The main reason of failures is that after IGNITE-15558 > IteratorParametersBuilder#pageSize is started to be set in > CdcMain#consumeSegment. > Since DataStorageConfiguration#pageSize default variable is 0, > IteratorParametersBuilder#validate throws an exception considering that page > size must be at least 4 kB. > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-16248) Ignite-extensions: CDC tests fails after IGNITE-15558
[ https://issues.apache.org/jira/browse/IGNITE-16248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov reassigned IGNITE-16248: --- Assignee: Mikhail Petrov > Ignite-extensions: CDC tests fails after IGNITE-15558 > - > > Key: IGNITE-16248 > URL: https://issues.apache.org/jira/browse/IGNITE-16248 > Project: Ignite > Issue Type: Test >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > > It is needed to fix CDC tests that start to fail after IGNITE-15558. > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16248) Ignite-extensions: CDC tests fails after IGNITE-15558
Mikhail Petrov created IGNITE-16248: --- Summary: Ignite-extensions: CDC tests fails after IGNITE-15558 Key: IGNITE-16248 URL: https://issues.apache.org/jira/browse/IGNITE-16248 Project: Ignite Issue Type: Test Reporter: Mikhail Petrov It is needed to fix CDC tests that start to fail after IGNITE-15558. https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Cdc=buildTypeHistoryList_IgniteExtensions_Tests=%3Cdefault%3E -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16164) Implement (un)marshalling of arbitrary objects
[ https://issues.apache.org/jira/browse/IGNITE-16164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471983#comment-17471983 ] Roman Puchkovskiy commented on IGNITE-16164: Thanks for your review > Implement (un)marshalling of arbitrary objects > -- > > Key: IGNITE-16164 > URL: https://issues.apache.org/jira/browse/IGNITE-16164 > Project: Ignite > Issue Type: Sub-task >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15566) Calcite. Join with correlated subqueries returns wrong result.
[
https://issues.apache.org/jira/browse/IGNITE-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-15566:
--
Assignee: Aleksey Plekhanov
> Calcite. Join with correlated subqueries returns wrong result.
> --
>
> Key: IGNITE-15566
> URL: https://issues.apache.org/jira/browse/IGNITE-15566
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Evgeny Stanilovsky
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: calcite, calcite2-required, calcite3-required, ignite-3
>
> Example from ScriptRunner :
> {noformat}
> query IIT
> SELECT * FROM test WHERE EXISTS(SELECT * FROM test2 WHERE test.a=test2.a AND
> test.b<>test2.c) AND NOT EXISTS(SELECT * FROM test2 WHERE test.a=test2.a AND
> test.b
> 122 b
> query IIT
> SELECT * FROM test WHERE NOT EXISTS(SELECT * FROM test2 WHERE test.a=test2.a
> AND test.b test.a=test2.a AND test.b>test2.c AND test2.a=12) ORDER BY a;
>
> 111 a
> 133 c
> {noformat}
> {noformat}
> /join/inner/test_eq_ineq_join.test[_ignore]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-16220) Update Ignite dependency jackson-mapper-asl in zookeeper
[ https://issues.apache.org/jira/browse/IGNITE-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Zadubinin updated IGNITE-16220: Description: Change dependencies in ignite-extensions: * from org.codehaus.jackson : jackson-mapper-asl : 1.9.13 to com.fasterxml.jackson.core : jackson-databind : 2.13.1 * from org.codehaus.jackson : jackson-core-asl : 1.9.13 to com.fasterxml.jackson.core : jackson-core : 2.13.1 due to vulnerability CVE-2019-10172 was: Change dependencies in ignite-extensions: * from org.codehaus.jackson : jackson-mapper-asl : 1.9.13 to com.fasterxml.jackson.core : jackson-databind : 2.13.1 * from org.codehaus.jackson : jackson-core-asl : 1.9.13 to com.fasterxml.jackson.core : jackson-core : 2.13.1 > Update Ignite dependency jackson-mapper-asl in zookeeper > > > Key: IGNITE-16220 > URL: https://issues.apache.org/jira/browse/IGNITE-16220 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Zadubinin >Assignee: Igor Zadubinin >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Change dependencies in ignite-extensions: > * from org.codehaus.jackson : jackson-mapper-asl : 1.9.13 to > com.fasterxml.jackson.core : jackson-databind : 2.13.1 > * from org.codehaus.jackson : jackson-core-asl : 1.9.13 to > com.fasterxml.jackson.core : jackson-core : 2.13.1 > due to vulnerability CVE-2019-10172 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16220) Update Ignite dependency jackson-mapper-asl in zookeeper
[ https://issues.apache.org/jira/browse/IGNITE-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Zadubinin updated IGNITE-16220: Description: Change dependencies in ignite-extensions: * from org.codehaus.jackson : jackson-mapper-asl : 1.9.13 to com.fasterxml.jackson.core : jackson-databind : 2.13.1 * from org.codehaus.jackson : jackson-core-asl : 1.9.13 to com.fasterxml.jackson.core : jackson-core : 2.13.1 was:Change Ignite dependency from jackson-mapper-asl 1.9.13 to Jackson Databind 2.13.1 > Update Ignite dependency jackson-mapper-asl in zookeeper > > > Key: IGNITE-16220 > URL: https://issues.apache.org/jira/browse/IGNITE-16220 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Zadubinin >Assignee: Igor Zadubinin >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Change dependencies in ignite-extensions: > * from org.codehaus.jackson : jackson-mapper-asl : 1.9.13 to > com.fasterxml.jackson.core : jackson-databind : 2.13.1 > * from org.codehaus.jackson : jackson-core-asl : 1.9.13 to > com.fasterxml.jackson.core : jackson-core : 2.13.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-15864) CPP Thin: Implement asynchronous network events handling
[ https://issues.apache.org/jira/browse/IGNITE-15864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471972#comment-17471972 ] Pavel Tupitsyn commented on IGNITE-15864: - [~isapego] Looks good to me, please see a few minor comments on GitHub. > CPP Thin: Implement asynchronous network events handling > > > Key: IGNITE-15864 > URL: https://issues.apache.org/jira/browse/IGNITE-15864 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.11 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.13 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, C++ thin client handles all network operations synchronously. I.e > after sending a request to a server it blocks entire socket until it receives > response. Let's implement asynchronous socket events handling in separate > connection or connection pool. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16220) Update Ignite dependency jackson-mapper-asl in zookeeper
[ https://issues.apache.org/jira/browse/IGNITE-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Zadubinin updated IGNITE-16220: Ignite Flags: (was: Docs Required,Release Notes Required) > Update Ignite dependency jackson-mapper-asl in zookeeper > > > Key: IGNITE-16220 > URL: https://issues.apache.org/jira/browse/IGNITE-16220 > Project: Ignite > Issue Type: Improvement >Reporter: Igor Zadubinin >Assignee: Igor Zadubinin >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Change Ignite dependency from jackson-mapper-asl 1.9.13 to Jackson Databind > 2.13.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16208) .NET: Thin 3.0: Transactions
[ https://issues.apache.org/jira/browse/IGNITE-16208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471948#comment-17471948 ] Igor Sapego commented on IGNITE-16208: -- [~ptupitsyn] looks good to me. > .NET: Thin 3.0: Transactions > > > Key: IGNITE-16208 > URL: https://issues.apache.org/jira/browse/IGNITE-16208 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Affects Versions: 3.0.0-alpha3 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > > Implement transactions in .NET thin client. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16162) StripedDisruptor should clean up its queues on shutdown
[ https://issues.apache.org/jira/browse/IGNITE-16162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471941#comment-17471941 ] Vladislav Pyatkov commented on IGNITE-16162: LGTM > StripedDisruptor should clean up its queues on shutdown > --- > > Key: IGNITE-16162 > URL: https://issues.apache.org/jira/browse/IGNITE-16162 > Project: Ignite > Issue Type: Improvement >Affects Versions: 3.0.0-alpha3 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Minor > Labels: ignite-3 > > StripedDisruptor maintains a collection of ring buffers > (StripedDisruptor.queues) that are not cleared on shutdown. It does not seem > to me that clearing is absolutely required step, but it allows to partially > mitigate the issue IGNITE-16161 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16223) Log query id for long running query.
[
https://issues.apache.org/jira/browse/IGNITE-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471922#comment-17471922
]
Ignite TC Bot commented on IGNITE-16223:
{panel:title=Branch: [pull/9704/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9704/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6358562buildTypeId=IgniteTests24Java8_RunAll]
> Log query id for long running query.
>
>
> Key: IGNITE-16223
> URL: https://issues.apache.org/jira/browse/IGNITE-16223
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, the long running query warning does not have a query ID.
> Therefore, it is not possible to run the KILL QUERY command because of this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-16170) Bugyard feedback #38-#41: Fix broken links in the docs
[ https://issues.apache.org/jira/browse/IGNITE-16170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Gusev reassigned IGNITE-16170: --- Assignee: Igor Gusev (was: Nikita A. Safonov) > Bugyard feedback #38-#41: Fix broken links in the docs > -- > > Key: IGNITE-16170 > URL: https://issues.apache.org/jira/browse/IGNITE-16170 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.11 >Reporter: Nikita A. Safonov >Assignee: Igor Gusev >Priority: Major > Labels: documentaion, documentation > Fix For: 2.11 > > > The following links in the latest version of docs return the 404 error (from > the [https://ignite.apache.org/docs/latest/clustering/baseline-topology#] > page): > * [https://ignite.apache.org/docs/latest/control-script#activating-cluster] > * > [https://ignite.apache.org/docs/latest/control-script#activation-deactivation-and-topology-management] > * [https://ignite.apache.org/docs/latest/control-script] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (IGNITE-15312) ITNodeTest.testPreVote is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin resolved IGNITE-15312.
--
Resolution: Cannot Reproduce
This test successfully passed more than 100 times:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6359247?buildTab=tests=testPreVote
> ITNodeTest.testPreVote is flaky
>
>
> Key: IGNITE-15312
> URL: https://issues.apache.org/jira/browse/IGNITE-15312
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Vyacheslav Koptilin
>Priority: Blocker
> Labels: ignite-3
> Attachments: ITNodeTest.testPreVote.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> org.opentest4j.AssertionFailedErrororg.opentest4j.AssertionFailedError:
> expected: but was: at
> org.apache.ignite.raft.jraft.core.ITNodeTest.waitLatch(ITNodeTest.java:3534)
> at
> org.apache.ignite.raft.jraft.core.ITNodeTest.testPreVote(ITNodeTest.java:1774)
> {code}
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunIntegrationTests/6133110
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-15312) ITNodeTest.testPreVote is flaky
[
https://issues.apache.org/jira/browse/IGNITE-15312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin reassigned IGNITE-15312:
Assignee: Vyacheslav Koptilin
> ITNodeTest.testPreVote is flaky
>
>
> Key: IGNITE-15312
> URL: https://issues.apache.org/jira/browse/IGNITE-15312
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Vyacheslav Koptilin
>Priority: Blocker
> Labels: ignite-3
> Attachments: ITNodeTest.testPreVote.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> org.opentest4j.AssertionFailedErrororg.opentest4j.AssertionFailedError:
> expected: but was: at
> org.apache.ignite.raft.jraft.core.ITNodeTest.waitLatch(ITNodeTest.java:3534)
> at
> org.apache.ignite.raft.jraft.core.ITNodeTest.testPreVote(ITNodeTest.java:1774)
> {code}
> https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunIntegrationTests/6133110
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15810) Rename ignite-calcite module to ignite-sql-engine at Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-15810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15810: -- Fix Version/s: 3.0.0-alpha4 > Rename ignite-calcite module to ignite-sql-engine at Ignite 3.0 > > > Key: IGNITE-15810 > URL: https://issues.apache.org/jira/browse/IGNITE-15810 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Andrey Mashenkov >Priority: Major > Labels: calcite, calcite3-required, ignite-3 > Fix For: 3.0.0-alpha4 > > Time Spent: 10m > Remaining Estimate: 0h > > Let's rename the ignite-calcite module to ignite-sql-engine at Ignite 3.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-14794) Add JMX command and metrics for automatic snapshot restore operation.
[
https://issues.apache.org/jira/browse/IGNITE-14794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-14794:
--
Description:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
||Name||Type||
|start time|long|
|end time|long|
|request ID|string|
|snapshot name|string|
|total partitions|int|
|processed partitions|int|
|error message|string|
was:
Add JMX command to restore a cache group from the snapshot.
Suggested methods
{code:java}
@MXBeanDescription("Restore cluster-wide snapshot.")
public void restoreSnapshot(
@MXBeanParameter(name = "snpName", description = "Snapshot name.")
String name,
@MXBeanParameter(name = "cacheGroupNames", description = "Optional
comma-separated list of cache group names.") String cacheGroupNames);
@MXBeanDescription("Cancel previously started snapshot restore operation.")
public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
description = "Snapshot name.") String name);
{code}
Since the automatic snapshot restore operation can take a long time, we must be
able to track its progress using metrics.
Suggested metrics:
||Name||Type||
|start time|long|
|end time|long|
|request ID|string|
|snapshot name|string|
|total partitions|long|
|processed partitions|long|
|error message|string|
> Add JMX command and metrics for automatic snapshot restore operation.
> --
>
> 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, ise
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add JMX command to restore a cache group from the snapshot.
> Suggested methods
> {code:java}
> @MXBeanDescription("Restore cluster-wide snapshot.")
> public void restoreSnapshot(
> @MXBeanParameter(name = "snpName", description = "Snapshot name.")
> String name,
> @MXBeanParameter(name = "cacheGroupNames", description = "Optional
> comma-separated list of cache group names.") String cacheGroupNames);
> @MXBeanDescription("Cancel previously started snapshot restore
> operation.")
> public void cancelSnapshotRestore(@MXBeanParameter(name = "snpName",
> description = "Snapshot name.") String name);
> {code}
> Since the automatic snapshot restore operation can take a long time, we must
> be able to track its progress using metrics.
> Suggested metrics:
> ||Name||Type||
> |start time|long|
> |end time|long|
> |request ID|string|
> |snapshot name|string|
> |total partitions|int|
> |processed partitions|int|
> |error message|string|
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15864) CPP Thin: Implement asynchronous network events handling
[
https://issues.apache.org/jira/browse/IGNITE-15864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471840#comment-17471840
]
Ignite TC Bot commented on IGNITE-15864:
{panel:title=Branch: [pull/9713/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9713/head] Base: [master] : New Tests
(1035)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
1026|https://ci.ignite.apache.org/viewLog.html?buildId=6358963]]
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite: SelectTwoValues
- PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectSingleValue - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
CreateTableInsertSelect - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SqlFieldsQueryTestSuite:
SelectTwoValuesInDifferentOrder - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
... and 1015 new tests
{color:#8b}Platform C++ CMake (Win x64 / Release){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6358964]]
* {color:#013220}IgniteThinClientTest: IgniteClientTestSuite:
IgniteClientReconnect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutAllGetAll
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutGet -
PASSED{color}
{color:#8b}Platform C++ CMake (Linux Clang){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6358961]]
* {color:#013220}IgniteThinClientTest: IgniteClientTestSuite:
IgniteClientReconnect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutAllGetAll
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutGet -
PASSED{color}
{color:#8b}Platform C++ CMake (Linux){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6358962]]
* {color:#013220}IgniteThinClientTest: IgniteClientTestSuite:
IgniteClientReconnect - PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutAllGetAll
- PASSED{color}
* {color:#013220}IgniteThinClientTest: SslTestSuite: SslCacheClientPutGet -
PASSED{color}
{panel}
[TeamCity *- Run :: CPP*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6358965buildTypeId=IgniteTests24Java8_RunCpp]
> CPP Thin: Implement asynchronous network events handling
>
>
> Key: IGNITE-15864
> URL: https://issues.apache.org/jira/browse/IGNITE-15864
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.11
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, C++ thin client handles all network operations synchronously. I.e
> after sending a request to a server it blocks entire socket until it receives
> response. Let's implement asynchronous socket events handling in separate
> connection or connection pool.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15733) Eventually failure of baseline registration.
[ https://issues.apache.org/jira/browse/IGNITE-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471814#comment-17471814 ] Evgeny Stanilovsky commented on IGNITE-15733: - [~ibessonov] thanks for review and sorry for long pause, i fix partially your comments, can u found a bit time for review ? Thanks ! > Eventually failure of baseline registration. > > > Key: IGNITE-15733 > URL: https://issues.apache.org/jira/browse/IGNITE-15733 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.11 >Reporter: Evgeny Stanilovsky >Assignee: Evgeny Stanilovsky >Priority: Major > Attachments: _Community_Edition_Cache_9_18998_cut.log > > Time Spent: 2h 50m > Remaining Estimate: 0h > > All info can be found in attached log: > briefly: Cluster of 2 nodes with persistence, sequentially start nodes, > activate, stop nodes using org.apache.ignite.Ignite#close, start nodes, > activate: > expected : > 1 node : Cluster ID and tag has been read from metastorage: null > 2 node : Cluster ID and tag has been read from metastorage: null > stop > start > 1 node: Cluster ID and tag has been read from metastorage: ClusterIdAndTag > [id=some_id, tag=some_tag] > 2 node: Cluster ID and tag has been read from metastorage: ClusterIdAndTag > [id=some_id, tag=some_tag] > but obtained (check attach) > > 1 node : Cluster ID and tag has been read from metastorage: null > 2 node : Cluster ID and tag has been read from metastorage: null > stop > start > 1 node: Cluster ID and tag has been read from metastorage: null > 2 node: Cluster ID and tag has been read from metastorage: ClusterIdAndTag > [id=some_id, tag=some_tag] > and as a result : > _Joining node has conflicting distributed metastorage data_ > [^_Community_Edition_Cache_9_18998_cut.log] > this test MetricsConfigurationTest.testNodeRestart [1] is flaky > [1][https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache9/6220901?buildTab=tests=MetricsConfigurationTes=tests=passed=org.apache.ignite.testsuites.IgniteCacheTestSuite9%3A+=org.apache.ignite.internal.metric=build%3A%28id%3A6220901%29%2Cid%3A576406] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-16235) Races between query execution and table creation
[ https://issues.apache.org/jira/browse/IGNITE-16235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471789#comment-17471789 ] Vladislav Pyatkov edited comment on IGNITE-16235 at 1/10/22, 9:23 AM: -- For the delay of events from Metastorage the _WatchListenerInhibitor_ is used. was (Author: v.pyatkov): For the delay of events from Metastorage the WatchListenerInhibitor is used. > Races between query execution and table creation > > > Key: IGNITE-16235 > URL: https://issues.apache.org/jira/browse/IGNITE-16235 > Project: Ignite > Issue Type: Test > Components: sql >Reporter: Konstantin Orlov >Assignee: Evgeny Stanilovsky >Priority: Major > > While the IGNITE-16090 fixes the issue, the provided patch lacks of proper > integration test that would verify the fix automatically. So we need to add > the test with follow scenario: > - cluster of 2 or more nodes is started > - create a table and immediately run a query upon that table > To reveal the original issue, we need to delay ditributed event of a table > creation on the node somehow in order to make the query be executed before > the table structures were created. > I believe this is not the only such a test, so we need a general approach to > write tests to verify the cluster behaviour in a concurrent environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16235) Races between query execution and table creation
[ https://issues.apache.org/jira/browse/IGNITE-16235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471789#comment-17471789 ] Vladislav Pyatkov commented on IGNITE-16235: For the delay of events from Metastorage the WatchListenerInhibitor is used. > Races between query execution and table creation > > > Key: IGNITE-16235 > URL: https://issues.apache.org/jira/browse/IGNITE-16235 > Project: Ignite > Issue Type: Test > Components: sql >Reporter: Konstantin Orlov >Assignee: Evgeny Stanilovsky >Priority: Major > > While the IGNITE-16090 fixes the issue, the provided patch lacks of proper > integration test that would verify the fix automatically. So we need to add > the test with follow scenario: > - cluster of 2 or more nodes is started > - create a table and immediately run a query upon that table > To reveal the original issue, we need to delay ditributed event of a table > creation on the node somehow in order to make the query be executed before > the table structures were created. > I believe this is not the only such a test, so we need a general approach to > write tests to verify the cluster behaviour in a concurrent environment. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16247) Ignite-extensions: Update version of Ignite dependency to 2.13.0
Mikhail Petrov created IGNITE-16247: --- Summary: Ignite-extensions: Update version of Ignite dependency to 2.13.0 Key: IGNITE-16247 URL: https://issues.apache.org/jira/browse/IGNITE-16247 Project: Ignite Issue Type: Improvement Reporter: Mikhail Petrov Assignee: Mikhail Petrov It is needed to update version of Ignite dependency to 2.13.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IGNITE-15810) Rename ignite-calcite module to ignite-sql-engine at Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-15810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich reassigned IGNITE-15810: -- Assignee: Andrey Mashenkov (was: Vladimir Ermakov) > Rename ignite-calcite module to ignite-sql-engine at Ignite 3.0 > > > Key: IGNITE-15810 > URL: https://issues.apache.org/jira/browse/IGNITE-15810 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Andrey Mashenkov >Priority: Major > Labels: calcite, calcite3-required, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Let's rename the ignite-calcite module to ignite-sql-engine at Ignite 3.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16231) Use any() for tracking updates of schema
[
https://issues.apache.org/jira/browse/IGNITE-16231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471769#comment-17471769
]
Vladislav Pyatkov commented on IGNITE-16231:
When we start using _any()_ instead of explicit subscription for a table
registration schema, the configuration listener invokes each time when the
table creation (before it happened only when the table has already created).
In the result, we will be able to use only event ({_}TableEvent.ALTER{_}) for
subscribe to register a new table schema (it required to modify logic in
{_}SqlQueryProcessor{_}).
> Use any() for tracking updates of schema
>
>
> Key: IGNITE-16231
> URL: https://issues.apache.org/jira/browse/IGNITE-16231
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Labels: ignite-3
>
> In the ticket (IGNITE-15409), configuration began to provide API where any
> unknown part of configuration key can be replaced to any() function. It is
> convenient when subscribing of any nested sub-configuration, although the
> specific root has not created yet.
> This API makes sense for subscribing of schemas for table. Look at the
> comments in the code:
> {code:java}
> // TODO: IGNITE-15409 Listener with any placeholder should be used instead.
> ((ExtendedTableConfiguration) tablesCfg.tables().get(tblName)).schemas()
> .listenElements(new ConfigurationNamedListListener<>() {
> @Override
> public @NotNull CompletableFuture onCreate(@NotNull
> ConfigurationNotificationEvent schemasCtx) {...}
> }
> {code}
> Need to rewrite the code in order to use `any()` and remove the comment.
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (IGNITE-15648) JDBC driver for 3.0: Add integration tests that depend on the data layer.
[ https://issues.apache.org/jira/browse/IGNITE-15648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gerzhedovich reassigned IGNITE-15648: -- Assignee: Konstantin Orlov (was: Vladimir Ermakov) > JDBC driver for 3.0: Add integration tests that depend on the data layer. > -- > > Key: IGNITE-15648 > URL: https://issues.apache.org/jira/browse/IGNITE-15648 > Project: Ignite > Issue Type: Improvement > Components: jdbc, sql >Reporter: Vladimir Ermakov >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Subj -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IGNITE-16223) Log query id for long running query.
[ https://issues.apache.org/jira/browse/IGNITE-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471746#comment-17471746 ] Yury Gerzhedovich commented on IGNITE-16223: [~amashenkov], LGTM, except minor comments in PR. > Log query id for long running query. > > > Key: IGNITE-16223 > URL: https://issues.apache.org/jira/browse/IGNITE-16223 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Fix For: 2.13 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, the long running query warning does not have a query ID. > Therefore, it is not possible to run the KILL QUERY command because of this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-16246) CDC extensions documentation
Nikolay Izhikov created IGNITE-16246: Summary: CDC extensions documentation Key: IGNITE-16246 URL: https://issues.apache.org/jira/browse/IGNITE-16246 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Nikolay Izhikov Assignee: Nikolay Izhikov Fix For: 2.12 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-16246) CDC extensions documentation
[ https://issues.apache.org/jira/browse/IGNITE-16246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-16246: - Fix Version/s: (was: 2.12) > CDC extensions documentation > > > Key: IGNITE-16246 > URL: https://issues.apache.org/jira/browse/IGNITE-16246 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-59 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
