[jira] [Updated] (IGNITE-17052) Thin 3.0: Implement query metadata

[ https://issues.apache.org/jira/browse/IGNITE-17052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17052: Epic Link: IGNITE-16952 > Thin 3.0: Implement query metadata >

[jira] [Updated] (IGNITE-17041) Normalize query entity after it is modified during merge process.

[ https://issues.apache.org/jira/browse/IGNITE-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-17041: Description: It is needed to to normalize query entity after it is modified during MERGE

[jira] [Updated] (IGNITE-17041) Normalize query entity after it is modified during merge process.

[ https://issues.apache.org/jira/browse/IGNITE-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-17041: Description: It is needed to to normalize query entity after it is modified during MERGE

[jira] [Updated] (IGNITE-17041) Normalize query entity after it is modified during merge process.

[ https://issues.apache.org/jira/browse/IGNITE-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-17041: Description: It is needed to to normalize query entity after it is modified during MERGE

[jira] [Updated] (IGNITE-17041) Normalize query entity after it is modified during merge process.

[ https://issues.apache.org/jira/browse/IGNITE-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-17041: Description: It is needed to to normalize query entity after it is modified during MERGE

[jira] [Updated] (IGNITE-15546) Remove java create/alter/dropTable api from within Ignite public API, use DDL instead

[ https://issues.apache.org/jira/browse/IGNITE-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15546: - Description: org.apache.ignite.table.manager.IgniteTables should be moved from Ignite

[jira] [Updated] (IGNITE-15546) Remove java create/alter/dropTable api from within Ignite public API, use DDL instead

[ https://issues.apache.org/jira/browse/IGNITE-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15546: - Ignite Flags: (was: Docs Required,Release Notes Required) > Remove java

[jira] [Updated] (IGNITE-15546) Remove java create/alter/dropTable api from within Ignite public API, use DDL instead

[ https://issues.apache.org/jira/browse/IGNITE-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-15546: - Summary: Remove java create/alter/dropTable api from within Ignite public API, use DDL

[jira] [Assigned] (IGNITE-16963) SQL API: Add batched DML queries support.

[ https://issues.apache.org/jira/browse/IGNITE-16963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-16963: - Assignee: Taras Ledkov > SQL API: Add batched DML queries support. >

[jira] [Created] (IGNITE-17056) Implement rebalance cancel mechanism

Mirza Aliev created IGNITE-17056: Summary: Implement rebalance cancel mechanism Key: IGNITE-17056 URL: https://issues.apache.org/jira/browse/IGNITE-17056 Project: Ignite Issue Type: Task

[jira] [Updated] (IGNITE-17055) Ignite JDBC Driver don't support contract

[ https://issues.apache.org/jira/browse/IGNITE-17055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17055: --- Description: Currently in org.apache.ignite.internal.jdbc.JdbcStatement#execute0

[jira] [Updated] (IGNITE-17055) Ignite JDBC Driver don't support contract

[ https://issues.apache.org/jira/browse/IGNITE-17055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17055: --- Description: Currently in org.apache.ignite.internal.jdbc.JdbcStatement#execute0

[jira] [Created] (IGNITE-17055) Ignite JDBC Driver don't support contract

Mikhail Pochatkin created IGNITE-17055: -- Summary: Ignite JDBC Driver don't support contract Key: IGNITE-17055 URL: https://issues.apache.org/jira/browse/IGNITE-17055 Project: Ignite

[jira] [Commented] (IGNITE-16977) Move DATE/TIME/TIMESTAMP indexes processing from ignite-indexing module to core

[ https://issues.apache.org/jira/browse/IGNITE-16977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543986#comment-17543986 ] Ignite TC Bot commented on IGNITE-16977: {panel:title=Branch: [pull/10046/head] Base: [master]

[jira] [Commented] (IGNITE-17054) Python thin: fix documentation examples

[ https://issues.apache.org/jira/browse/IGNITE-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543982#comment-17543982 ] Igor Sapego commented on IGNITE-17054: -- Ready for review:

[jira] [Created] (IGNITE-17054) Python thin: fix documentation examples

Igor Sapego created IGNITE-17054: Summary: Python thin: fix documentation examples Key: IGNITE-17054 URL: https://issues.apache.org/jira/browse/IGNITE-17054 Project: Ignite Issue Type: Bug

[jira] [Updated] (IGNITE-17041) Normalize query entity after it is modified during merge process.

[ https://issues.apache.org/jira/browse/IGNITE-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-17041: Description: It is needed to to normalize query entity after it is modified during MERGE

[jira] [Updated] (IGNITE-17053) Incorrect configuration of spring-data example

[ https://issues.apache.org/jira/browse/IGNITE-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17053: --- Labels: newbie (was: ise) > Incorrect configuration of spring-data example >

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Description: If you create JPA-repository method with with 'IN' operator (eg.

[jira] [Updated] (IGNITE-17041) Normalize query entity after it is modified during merge process.

[ https://issues.apache.org/jira/browse/IGNITE-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-17041: Description: It is needed to to normalize query entity after it is modified during MERGE

[jira] [Commented] (IGNITE-15834) Read Repair should support arrays and collections as values

[ https://issues.apache.org/jira/browse/IGNITE-15834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543946#comment-17543946 ] Ignite TC Bot commented on IGNITE-15834: {panel:title=Branch: [pull/10047/head] Base: [master]

[jira] [Assigned] (IGNITE-17053) Incorrect configuration of spring-data example

[ https://issues.apache.org/jira/browse/IGNITE-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov reassigned IGNITE-17053: -- Assignee: Ilya Shishkov > Incorrect configuration of spring-data example >

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Description: If you create JPA-repository method with with 'IN' operator (eg.

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Attachment: IncorrectInOperator.patch > Incorrect parsing of 'IN' clause in

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Attachment: (was: IncorrectInOperator.patch) > Incorrect parsing of 'IN' clause in

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Attachment: IncorrectInOperator.patch > Incorrect parsing of 'IN' clause in

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Attachment: (was: IncorrectInOperator.patch) > Incorrect parsing of 'IN' clause in

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Description: If you create JPA-repository method with with 'IN' operator (eg.

[jira] [Commented] (IGNITE-16650) Exclude ignite-log4j, log4j 1.2.17

[ https://issues.apache.org/jira/browse/IGNITE-16650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543944#comment-17543944 ] Maxim Muzafarov commented on IGNITE-16650: -- During the migration to the log4j2 we can also

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Description: If you create JPA-repository method with with 'IN' operator (eg.

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Attachment: IncorrectInOperator.patch > Incorrect parsing of 'IN' clause in

[jira] [Updated] (IGNITE-17053) Incorrect configuration of spring-data example

[ https://issues.apache.org/jira/browse/IGNITE-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17053: --- Description: After removing of spring-data-2.2-ext, {{SpringDataExample}} will fail to

[jira] [Updated] (IGNITE-17053) Incorrect configuration of spring-data example

[ https://issues.apache.org/jira/browse/IGNITE-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17053: --- Labels: ise (was: ) > Incorrect configuration of spring-data example >

[jira] [Created] (IGNITE-17053) Incorrect configuration of spring-data example

Ilya Shishkov created IGNITE-17053: -- Summary: Incorrect configuration of spring-data example Key: IGNITE-17053 URL: https://issues.apache.org/jira/browse/IGNITE-17053 Project: Ignite Issue

[jira] [Updated] (IGNITE-17053) Incorrect configuration of spring-data example

[ https://issues.apache.org/jira/browse/IGNITE-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17053: --- Description: After removing of spring-data-2.2-ext, {{SpringDataExample}} will fail to

[jira] [Created] (IGNITE-17052) Thin 3.0: Implement query metadata

Pavel Tupitsyn created IGNITE-17052: --- Summary: Thin 3.0: Implement query metadata Key: IGNITE-17052 URL: https://issues.apache.org/jira/browse/IGNITE-17052 Project: Ignite Issue Type:

[jira] [Updated] (IGNITE-16962) SQL API: Implement query metadata

[ https://issues.apache.org/jira/browse/IGNITE-16962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16962: Summary: SQL API: Implement query metadata (was: SQL API: Implement query metadata.) >

[jira] [Updated] (IGNITE-16962) SQL API: Implement query metadata.

[ https://issues.apache.org/jira/browse/IGNITE-16962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16962: Description: Implement query result metadata. * Add public classes for SQL types (if

[jira] [Updated] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

[ https://issues.apache.org/jira/browse/IGNITE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-17051: --- Labels: ise (was: ) > Incorrect parsing of 'IN' clause in IgniteQueryGenerator >

[jira] [Created] (IGNITE-17051) Incorrect parsing of 'IN' clause in IgniteQueryGenerator

Ilya Shishkov created IGNITE-17051: -- Summary: Incorrect parsing of 'IN' clause in IgniteQueryGenerator Key: IGNITE-17051 URL: https://issues.apache.org/jira/browse/IGNITE-17051 Project: Ignite

[jira] [Updated] (IGNITE-17048) Some failing tests make other tests fail too

[ https://issues.apache.org/jira/browse/IGNITE-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-17048: Description: Looks like after some tests fail, they do not correctly free the used

[jira] [Commented] (IGNITE-17043) Performance degradation in Marshaller

[ https://issues.apache.org/jira/browse/IGNITE-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543909#comment-17543909 ] Semyon Danilov commented on IGNITE-17043: - Merged to the master branch > Performance

[jira] [Created] (IGNITE-17050) Bump commons-io version

Nikolay Izhikov created IGNITE-17050: Summary: Bump commons-io version Key: IGNITE-17050 URL: https://issues.apache.org/jira/browse/IGNITE-17050 Project: Ignite Issue Type: Improvement

[jira] [Assigned] (IGNITE-17050) Bump commons-io version

[ https://issues.apache.org/jira/browse/IGNITE-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned IGNITE-17050: Assignee: Nikolay Izhikov > Bump commons-io version > --- >

[jira] [Commented] (IGNITE-17043) Performance degradation in Marshaller

[ https://issues.apache.org/jira/browse/IGNITE-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543897#comment-17543897 ] Ignite TC Bot commented on IGNITE-17043: {panel:title=Branch: [pull/10045/head] Base: [master]

[jira] [Assigned] (IGNITE-16478) RocksDB returns unexpected cursor.hasNext equals false after leader is changed

[ https://issues.apache.org/jira/browse/IGNITE-16478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov reassigned IGNITE-16478: - Assignee: Denis Chudov > RocksDB returns unexpected cursor.hasNext equals false after

[jira] [Created] (IGNITE-17049) Move ignite-spark modules to the Ignite Extensions project

Maxim Muzafarov created IGNITE-17049: Summary: Move ignite-spark modules to the Ignite Extensions project Key: IGNITE-17049 URL: https://issues.apache.org/jira/browse/IGNITE-17049 Project: Ignite

[jira] [Updated] (IGNITE-14972) Thin 3.0: Implement SQL API for java thin client

[ https://issues.apache.org/jira/browse/IGNITE-14972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14972: - Component/s: sql > Thin 3.0: Implement SQL API for java thin client >

[jira] [Updated] (IGNITE-14972) Thin 3.0: Implement SQL API for java thin client

[ https://issues.apache.org/jira/browse/IGNITE-14972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14972: - Labels: ignite-3 (was: ignite-3 sql) > Thin 3.0: Implement SQL API for java thin client >

[jira] [Updated] (IGNITE-14972) Thin 3.0: Implement SQL API for java thin client

[ https://issues.apache.org/jira/browse/IGNITE-14972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14972: - Labels: ignite-3 sql (was: ignite-3) > Thin 3.0: Implement SQL API for java thin client >

[jira] [Updated] (IGNITE-14972) Thin 3.0: Implement SQL API for java thin client

[ https://issues.apache.org/jira/browse/IGNITE-14972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14972: - Component/s: (was: sql) > Thin 3.0: Implement SQL API for java thin client >

[jira] [Commented] (IGNITE-17043) Performance degradation in Marshaller

[ https://issues.apache.org/jira/browse/IGNITE-17043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17543868#comment-17543868 ] Semyon Danilov commented on IGNITE-17043: - A little benchmark for fill vs. unsafe

[jira] [Updated] (IGNITE-16964) SQL API: Implement async SQL API

[ https://issues.apache.org/jira/browse/IGNITE-16964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16964: -- Ignite Flags: (was: Docs Required,Release Notes Required) > SQL API: Implement async SQL

[jira] [Updated] (IGNITE-16965) SQL API: Implement synchronous SQL API.

[ https://issues.apache.org/jira/browse/IGNITE-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16965: -- Ignite Flags: (was: Docs Required,Release Notes Required) > SQL API: Implement synchronous

[jira] [Updated] (IGNITE-17048) Some failing tests make other tests fail too

[ https://issues.apache.org/jira/browse/IGNITE-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-17048: - Description: Looks like after some tests fail, they do not correctly free the

[jira] [Created] (IGNITE-17048) Some failing tests make other tests fail too

Aleksandr Polovtcev created IGNITE-17048: Summary: Some failing tests make other tests fail too Key: IGNITE-17048 URL: https://issues.apache.org/jira/browse/IGNITE-17048 Project: Ignite

[jira] [Resolved] (IGNITE-17007) TxAbstractTest#testBalance is flaky

[ https://issues.apache.org/jira/browse/IGNITE-17007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin resolved IGNITE-17007. -- Resolution: Duplicate > TxAbstractTest#testBalance is flaky >

[jira] [Updated] (IGNITE-16965) SQL API: Implement synchronous SQL API.

[ https://issues.apache.org/jira/browse/IGNITE-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-16965: -- Description: Implement session and session builder interfaces (excl. async/reactive)

[jira] [Updated] (IGNITE-14913) Add cache statistics switch to control script

[ https://issues.apache.org/jira/browse/IGNITE-14913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Shishkov updated IGNITE-14913: --- Description: Currently, enabling or disabling cache metrics collection is available only