[jira] [Comment Edited] (IGNITE-13020) Schema change operation failed: Thread got interrupted while trying to acquire table lock.
[
https://issues.apache.org/jira/browse/IGNITE-13020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713946#comment-17713946
]
Chenjian edited comment on IGNITE-13020 at 4/19/23 7:33 AM:
[~jooger] Doubts about the code GridH2Table.lock, the lock logic would lay in
the for loop, why design like this?
Also could you guide me where is the tests about the add/drop columns, I am not
sure H2DynamicColumnsAbstractBasicSelfTest.testAddNullColumn /
testAddNotNullColumn is the right tests I can refer to
was (Author: chenjian2664):
[~jooger] Doubts about the code GridH2Table.lock, the lock logic would lay in
the for loop, why design like this?
> Schema change operation failed: Thread got interrupted while trying to
> acquire table lock.
> --
>
> Key: IGNITE-13020
> URL: https://issues.apache.org/jira/browse/IGNITE-13020
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: JiajunYang
>Priority: Major
>
> Ignite throws sql exception sometimes while do ddl actions concurrently.The
> exception looks like:
> java.sql.SQLException: Schema change operation failed: Thread got
> interrupted while trying to acquire table lock.
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:901)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:231)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:559)
> at
>
> at java.lang.Thread.run(Thread.java:748)
>
> Here is one reproduce case:
> 1.Start a ignite without persitence enabled.
> 2.Use two threads to do ddl operations concurrently.
> 3.Each ddl opertion contains create table and create indices sqls.Send these
> sqls to ignite in one statement.
> 4.Do ddl operations repeatly and then wait for luck.U can add a system.exit
> when u get the exception.
>
> Here is my test code for u reference:
> public class ConcurrentCreateTable {
> private static Connection conn;
> private static Connection conn1;
> public static void main(String[] args) throws Exception {
> initialize();
> new Thread(new Runnable() {
> @Override
> public void run() {
> while (true) {
> try (Statement stmt = conn.createStatement())
> { stmt.execute( "CREATE
> TABLE IF NOT EXISTS city1(ID INTEGER,NAME VARCHAR,NAME1 VARCHAR ,PRIMARY
> KEY(ID)) WITH \"template=replicated\";" +
> "CREATE INDEX IF NOT EXISTS city1_name ON city1(NAME);CREATE INDEX IF NOT
> EXISTS city1_name1 on city1(NAME1);");
> stmt.execute("DROP TABLE IF EXISTS city1");
> System.out.println("XXX"); }
> catch (SQLException e)
> { e.printStackTrace(); }
> }
> }
> }).start();
> new Thread(new Runnable() {
>
> @Override
> public void run() {
> while (true) {
> try (Statement stmt = conn1.createStatement()) \{
> stmt.execute( "CREATE TABLE IF
> NOT EXISTS city2(ID INTEGER,NAME VARCHAR, NAME1 VARCHAR ,PRIMARY KEY(ID))
> WITH \"template=replicated\";" + "CREATE
> INDEX IF NOT EXISTS city2_name ON city2(NAME);CREATE INDEX IF NOT EXISTS
> city2_name1 on city2(NAME1);"); stmt.execute("DROP
> TABLE IF EXISTS city2"); System.out.println("XXX");
> } catch (SQLException e) \{
> e.printStackTrace(); }
> }
> }
> }).start();
> while (true)
> { }
> }
> private static void initialize() throws Exception
> { Class.forName(Config.IGNITE_DRIVER); final Properties props
> = new Properties(); conn =
> DriverManager.getConnection(Config.IGNITE_URL, props); conn1 =
> DriverManager.getConnection(Config.IGNITE_URL, props); }
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-13020) Schema change operation failed: Thread got interrupted while trying to acquire table lock.
[
https://issues.apache.org/jira/browse/IGNITE-13020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713946#comment-17713946
]
Chenjian commented on IGNITE-13020:
---
[~jooger] Doubts about the code GridH2Table.lock, the lock logic would lay in
the for loop, why design like this?
> Schema change operation failed: Thread got interrupted while trying to
> acquire table lock.
> --
>
> Key: IGNITE-13020
> URL: https://issues.apache.org/jira/browse/IGNITE-13020
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: JiajunYang
>Priority: Major
>
> Ignite throws sql exception sometimes while do ddl actions concurrently.The
> exception looks like:
> java.sql.SQLException: Schema change operation failed: Thread got
> interrupted while trying to acquire table lock.
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:901)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:231)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:559)
> at
>
> at java.lang.Thread.run(Thread.java:748)
>
> Here is one reproduce case:
> 1.Start a ignite without persitence enabled.
> 2.Use two threads to do ddl operations concurrently.
> 3.Each ddl opertion contains create table and create indices sqls.Send these
> sqls to ignite in one statement.
> 4.Do ddl operations repeatly and then wait for luck.U can add a system.exit
> when u get the exception.
>
> Here is my test code for u reference:
> public class ConcurrentCreateTable {
> private static Connection conn;
> private static Connection conn1;
> public static void main(String[] args) throws Exception {
> initialize();
> new Thread(new Runnable() {
> @Override
> public void run() {
> while (true) {
> try (Statement stmt = conn.createStatement())
> { stmt.execute( "CREATE
> TABLE IF NOT EXISTS city1(ID INTEGER,NAME VARCHAR,NAME1 VARCHAR ,PRIMARY
> KEY(ID)) WITH \"template=replicated\";" +
> "CREATE INDEX IF NOT EXISTS city1_name ON city1(NAME);CREATE INDEX IF NOT
> EXISTS city1_name1 on city1(NAME1);");
> stmt.execute("DROP TABLE IF EXISTS city1");
> System.out.println("XXX"); }
> catch (SQLException e)
> { e.printStackTrace(); }
> }
> }
> }).start();
> new Thread(new Runnable() {
>
> @Override
> public void run() {
> while (true) {
> try (Statement stmt = conn1.createStatement()) \{
> stmt.execute( "CREATE TABLE IF
> NOT EXISTS city2(ID INTEGER,NAME VARCHAR, NAME1 VARCHAR ,PRIMARY KEY(ID))
> WITH \"template=replicated\";" + "CREATE
> INDEX IF NOT EXISTS city2_name ON city2(NAME);CREATE INDEX IF NOT EXISTS
> city2_name1 on city2(NAME1);"); stmt.execute("DROP
> TABLE IF EXISTS city2"); System.out.println("XXX");
> } catch (SQLException e) \{
> e.printStackTrace(); }
> }
> }
> }).start();
> while (true)
> { }
> }
> private static void initialize() throws Exception
> { Class.forName(Config.IGNITE_DRIVER); final Properties props
> = new Properties(); conn =
> DriverManager.getConnection(Config.IGNITE_URL, props); conn1 =
> DriverManager.getConnection(Config.IGNITE_URL, props); }
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696945#comment-17696945
]
Chenjian commented on IGNITE-18964:
---
[~amashenkov] Would be great thanks if you have sometime to review this.
> Fix sql wildcard to java regex translation when involving consecutive
> wildcard characters
> -
>
> Key: IGNITE-18964
> URL: https://issues.apache.org/jira/browse/IGNITE-18964
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Chenjian
>Assignee: Chenjian
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
> consecutive "_" character correctly.
> eg:
> {code:java}
> If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
> a\\__b_c{code}
>
> Without the fix, user can not get their tables search by escaped table names
> if they created table with more than one consecutive "_"
> Affected version is from 2.9 to 2.14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696780#comment-17696780
]
Chenjian commented on IGNITE-18964:
---
[Yury Gerzhedovich |https://cwiki.apache.org/confluence/display/~jooger]
> Fix sql wildcard to java regex translation when involving consecutive
> wildcard characters
> -
>
> Key: IGNITE-18964
> URL: https://issues.apache.org/jira/browse/IGNITE-18964
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Chenjian
>Assignee: Chenjian
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
> consecutive "_" character correctly.
> eg:
> {code:java}
> If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
> a\\__b_c{code}
>
> Without the fix, user can not get their tables search by escaped table names
> if they created table with more than one consecutive "_"
> Affected version is from 2.9 to 2.14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chenjian updated IGNITE-18964:
--
Description:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
{code:java}
If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
a\\__b_c{code}
Without the fix, user can not get their tables search by escaped table names if
they created table with more than one consecutive "_"
Affected version is from 2.9 to 2.14
was:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
{code:java}
If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
a\\__b_c{code}
Without the fix, user can not get their tables if they created table with more
than one consecutive "_"
Affected version is from 2.9 to 2.14
> Fix sql wildcard to java regex translation when involving consecutive
> wildcard characters
> -
>
> Key: IGNITE-18964
> URL: https://issues.apache.org/jira/browse/IGNITE-18964
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Chenjian
>Assignee: Chenjian
>Priority: Major
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
> consecutive "_" character correctly.
> eg:
> {code:java}
> If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
> a\\__b_c{code}
>
> Without the fix, user can not get their tables search by escaped table names
> if they created table with more than one consecutive "_"
> Affected version is from 2.9 to 2.14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chenjian updated IGNITE-18964:
--
Description:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
{code:java}
If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
a\\__b_c{code}
Without the fix, user can not get their tables if they created table with more
than one consecutive "_"
Affected version is from 2.9 to 2.14
was:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
{code:java}
If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
a\\__b_c{code}
Affected version is from 2.9 to 2.14
> Fix sql wildcard to java regex translation when involving consecutive
> wildcard characters
> -
>
> Key: IGNITE-18964
> URL: https://issues.apache.org/jira/browse/IGNITE-18964
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Chenjian
>Assignee: Chenjian
>Priority: Major
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
> consecutive "_" character correctly.
> eg:
> {code:java}
> If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
> a\\__b_c{code}
>
> Without the fix, user can not get their tables if they created table with
> more than one consecutive "_"
> Affected version is from 2.9 to 2.14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chenjian updated IGNITE-18964:
--
Description:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
{code:java}
If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
a__b_c{code}
Affected version is from 2.9 to 2.14
was:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
If we have a escaped table name {{a\\_\\_b\\_c}} should be translated to
{{a__b_c}} not {{a\\__b_c}}
Affected version is from 2.9 to 2.14
> Fix sql wildcard to java regex translation when involving consecutive
> wildcard characters
> -
>
> Key: IGNITE-18964
> URL: https://issues.apache.org/jira/browse/IGNITE-18964
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Chenjian
>Assignee: Chenjian
>Priority: Major
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
> consecutive "_" character correctly.
> eg:
> {code:java}
> If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
> a__b_c{code}
>
> Affected version is from 2.9 to 2.14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chenjian updated IGNITE-18964:
--
Description:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
{code:java}
If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
a\\__b_c{code}
Affected version is from 2.9 to 2.14
was:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
{code:java}
If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
a__b_c{code}
Affected version is from 2.9 to 2.14
> Fix sql wildcard to java regex translation when involving consecutive
> wildcard characters
> -
>
> Key: IGNITE-18964
> URL: https://issues.apache.org/jira/browse/IGNITE-18964
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Chenjian
>Assignee: Chenjian
>Priority: Major
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
> consecutive "_" character correctly.
> eg:
> {code:java}
> If we have a escaped table name a\\_\\_b_c should be translated to a__b_c not
> a\\__b_c{code}
>
> Affected version is from 2.9 to 2.14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chenjian updated IGNITE-18964:
--
Description:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
If we have a escaped table name {{a\\_\\_b\\_c}} should be translated to
{{a__b_c}} not {{a\\__b_c}}
Affected version is from 2.9 to 2.14
was:
It's a capture corner case for the IGNITE-12687.
The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
consecutive "_" character correctly.
eg:
If we have a escaped table name "a\\__b_c" should be translated to "a__b_c" not
"a__b_c"
Affected version is from 2.9 to 2.14
> Fix sql wildcard to java regex translation when involving consecutive
> wildcard characters
> -
>
> Key: IGNITE-18964
> URL: https://issues.apache.org/jira/browse/IGNITE-18964
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.14
>Reporter: Chenjian
>Assignee: Chenjian
>Priority: Major
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle
> consecutive "_" character correctly.
> eg:
> If we have a escaped table name {{a\\_\\_b\\_c}} should be translated to
> {{a__b_c}} not {{a\\__b_c}}
>
> Affected version is from 2.9 to 2.14
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[ https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18964: -- Description: It's a capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. eg: If we have a escaped table name "a\\__b_c" should be translated to "a__b_c" not "a__b_c" Affected version is from 2.9 to 2.14 was: It's a capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. eg: If we have a escaped table name `a\\_\\_b_c" should be translated to "a__b_c" not "a__b_c" Affected version is from 2.9 to 2.14 > Fix sql wildcard to java regex translation when involving consecutive > wildcard characters > - > > Key: IGNITE-18964 > URL: https://issues.apache.org/jira/browse/IGNITE-18964 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.14 >Reporter: Chenjian >Assignee: Chenjian >Priority: Major > > It's a capture corner case for the IGNITE-12687. > The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle > consecutive "_" character correctly. > eg: > If we have a escaped table name "a\\__b_c" should be translated to "a__b_c" > not "a__b_c" > > Affected version is from 2.9 to 2.14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[ https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18964: -- Description: It's a capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. eg: If we have a escaped table name `a\\_\\_b\\_c" should be translated to "a__b_c" not "a\\__b_c" Affected version is from 2.9 to 2.14 was: It's a capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. Affected version is from 2.9 to 2.14 > Fix sql wildcard to java regex translation when involving consecutive > wildcard characters > - > > Key: IGNITE-18964 > URL: https://issues.apache.org/jira/browse/IGNITE-18964 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.14 >Reporter: Chenjian >Assignee: Chenjian >Priority: Major > > It's a capture corner case for the IGNITE-12687. > The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle > consecutive "_" character correctly. > eg: > If we have a escaped table name `a\\_\\_b\\_c" should be translated to > "a__b_c" not "a\\__b_c" > > Affected version is from 2.9 to 2.14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[ https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18964: -- Description: It's a capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. eg: If we have a escaped table name `a\\_\\_b_c" should be translated to "a__b_c" not "a__b_c" Affected version is from 2.9 to 2.14 was: It's a capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. eg: If we have a escaped table name `a\\_\\_b\\_c" should be translated to "a__b_c" not "a\\__b_c" Affected version is from 2.9 to 2.14 > Fix sql wildcard to java regex translation when involving consecutive > wildcard characters > - > > Key: IGNITE-18964 > URL: https://issues.apache.org/jira/browse/IGNITE-18964 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.14 >Reporter: Chenjian >Assignee: Chenjian >Priority: Major > > It's a capture corner case for the IGNITE-12687. > The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle > consecutive "_" character correctly. > eg: > If we have a escaped table name `a\\_\\_b_c" should be translated to "a__b_c" > not "a__b_c" > > Affected version is from 2.9 to 2.14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
Chenjian created IGNITE-18964: - Summary: Fix sql wildcard to java regex translation when involving consecutive wildcard characters Key: IGNITE-18964 URL: https://issues.apache.org/jira/browse/IGNITE-18964 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.14 Reporter: Chenjian Assignee: Chenjian It's an capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. Affected version is from 2.9 to 2.14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18964) Fix sql wildcard to java regex translation when involving consecutive wildcard characters
[ https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18964: -- Description: It's a capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. Affected version is from 2.9 to 2.14 was: It's an capture corner case for the IGNITE-12687. The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle consecutive "_" character correctly. Affected version is from 2.9 to 2.14 > Fix sql wildcard to java regex translation when involving consecutive > wildcard characters > - > > Key: IGNITE-18964 > URL: https://issues.apache.org/jira/browse/IGNITE-18964 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.14 >Reporter: Chenjian >Assignee: Chenjian >Priority: Major > > It's a capture corner case for the IGNITE-12687. > The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle > consecutive "_" character correctly. > > Affected version is from 2.9 to 2.14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18946) Fix 'REFRESH' command about statistics in the ddl doc
[ https://issues.apache.org/jira/browse/IGNITE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696027#comment-17696027 ] Chenjian commented on IGNITE-18946: --- noted,thanks Aleksey Plekhanov (Jira) 于2023年3月3日 周五下午2:05写道： > Fix 'REFRESH' command about statistics in the ddl doc > - > > Key: IGNITE-18946 > URL: https://issues.apache.org/jira/browse/IGNITE-18946 > Project: Ignite > Issue Type: Bug >Reporter: Chenjian >Assignee: Chenjian >Priority: Trivial > Fix For: 2.15 > > Time Spent: 20m > Remaining Estimate: 0h > > Fix doc about the 'REFRESH' command about the STATISTICS, > see [https://ignite.apache.org/docs/2.14.0/sql-reference/ddl#refresh] > the command should be 'REFRESH STATISTICS' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18946) Fix 'REFRESH' command about statistics in the ddl doc
[ https://issues.apache.org/jira/browse/IGNITE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18946: -- Summary: Fix 'REFRESH' command about statistics in the ddl doc (was: Fix 'REFRESH' command demos in the ddl doc) > Fix 'REFRESH' command about statistics in the ddl doc > - > > Key: IGNITE-18946 > URL: https://issues.apache.org/jira/browse/IGNITE-18946 > Project: Ignite > Issue Type: Bug >Reporter: Chenjian >Assignee: Chenjian >Priority: Trivial > Time Spent: 10m > Remaining Estimate: 0h > > Fix doc about the 'REFRESH' command about the STATISTICS, > see [https://ignite.apache.org/docs/2.14.0/sql-reference/ddl#refresh] > the command should be 'REFRESH STATISTICS' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18388) Ignite drop then add same column has the wrong sematic
[ https://issues.apache.org/jira/browse/IGNITE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18388: -- Priority: Minor (was: Major) > Ignite drop then add same column has the wrong sematic > --- > > Key: IGNITE-18388 > URL: https://issues.apache.org/jira/browse/IGNITE-18388 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14 >Reporter: Chenjian >Assignee: Chenjian >Priority: Minor > Attachments: image-2022-12-13-15-43-58-095.png > > > Dropped the column then added the column with the same name, the value about > the column backend which should not. > Steps to reproduce: > * create table t(id int primary key, x int, y int) > * insert into t values (1, 2, 3) > * select * from t. The result shows as expected 1, 2, 3 > * alter table drop column x. > * select * from t. The result shows as expected 1,3 > * alter table add column x int. > * select * from t. *The result shows NOT as expected 1,3,2. which should > 1,3,NULL.* > > !image-2022-12-13-15-43-58-095.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18946) Fix 'REFRESH' command demos in the ddl doc
Chenjian created IGNITE-18946: - Summary: Fix 'REFRESH' command demos in the ddl doc Key: IGNITE-18946 URL: https://issues.apache.org/jira/browse/IGNITE-18946 Project: Ignite Issue Type: Bug Reporter: Chenjian Fix doc about the 'REFRESH' command about the STATISTICS, see [https://ignite.apache.org/docs/2.14.0/sql-reference/ddl#refresh] the command should be 'REFRESH STATISTICS' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18946) Fix 'REFRESH' command demos in the ddl doc
[ https://issues.apache.org/jira/browse/IGNITE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18946: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Fix 'REFRESH' command demos in the ddl doc > -- > > Key: IGNITE-18946 > URL: https://issues.apache.org/jira/browse/IGNITE-18946 > Project: Ignite > Issue Type: Bug >Reporter: Chenjian >Priority: Trivial > > Fix doc about the 'REFRESH' command about the STATISTICS, > see [https://ignite.apache.org/docs/2.14.0/sql-reference/ddl#refresh] > the command should be 'REFRESH STATISTICS' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18946) Fix 'REFRESH' command demos in the ddl doc
[ https://issues.apache.org/jira/browse/IGNITE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian reassigned IGNITE-18946: - Assignee: Chenjian > Fix 'REFRESH' command demos in the ddl doc > -- > > Key: IGNITE-18946 > URL: https://issues.apache.org/jira/browse/IGNITE-18946 > Project: Ignite > Issue Type: Bug >Reporter: Chenjian >Assignee: Chenjian >Priority: Trivial > > Fix doc about the 'REFRESH' command about the STATISTICS, > see [https://ignite.apache.org/docs/2.14.0/sql-reference/ddl#refresh] > the command should be 'REFRESH STATISTICS' -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-7360) SQL: incorrect date/time values could be inserted
[
https://issues.apache.org/jira/browse/IGNITE-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691329#comment-17691329
]
Chenjian commented on IGNITE-7360:
--
[~avolkov] Just checked, the newer version still has this problem.
Anyone is going to fix this?
If no, can I take this, and could anyone help to point out which test is used
for test insert date type in existing?
> SQL: incorrect date/time values could be inserted
> -
>
> Key: IGNITE-7360
> URL: https://issues.apache.org/jira/browse/IGNITE-7360
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.1
>Reporter: Alex Volkov
>Priority: Minor
>
> According to ansi 99 spec.:
> ||Keyword||Valid values of datetime fields||
> |YEAR|0001 to |
> |MONTH|01 to 12|
> |DAY|Within the range 1 (one) to 31, but further constrained by the value of
> MONTH and YEAR fields, according to the rules for well-formed dates in
> the Gregorian calendar.|
> |HOUR|00 to 23|
> and so on.
> But these values could be inserted:
> *For DATE data type:*
> {code:java}
> 0: jdbc:ignite:thin://127.0.0.1:10800/> create table tmp_table_date_and_time
> (key_field INT PRIMARY KEY,field1 DATE,field2 TIME);
> SQL: create table tmp_table_date_and_time (key_field INT PRIMARY KEY,field1
> DATE,field2 TIME)
> No rows affected (0.028 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> insert into tmp_table_date_and_time
> (key_field,field1,field2) values (2, '1-12-09','13:44:56');
> SQL: insert into tmp_table_date_and_time (key_field,field1,field2) values (2,
> '1-12-09','13:44:56')
> 1 row affected (0.009 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> select * from tmp_table_date_and_time;
> SQL: select * from tmp_table_date_and_time
> IN IncrementalRows 3
> ++++
> | KEY_FIELD| FIELD1 |
> FIELD2 |
> ++++
> | 2 | Sat Dec 09 00:00:00 MSK 1 | 13:44:56
> |
> ++++
> 1 row selected (0.007 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> insert into tmp_table_date_and_time
> (key_field,field1,field2) values (6, '-2017-12-09','13:44:56');
> SQL: insert into tmp_table_date_and_time (key_field,field1,field2) values (6,
> '-2017-12-09','13:44:56')
> 1 row affected (0.011 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> select * from tmp_table_date_and_time;
> SQL: select * from tmp_table_date_and_time
> IN IncrementalRows 3
> ++++
> | KEY_FIELD| FIELD1 |
> FIELD2 |
> ++++
> | 2 | Sat Dec 09 00:00:00 MSK 1 | 13:44:56
> |
> | 6 | Tue Dec 09 00:00:00 MSK 2018 | 13:44:56
> |
> ++++
> 2 rows selected (0.016 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/>
> {code}
> For TIME data type:
> {code:java}
> 0: jdbc:ignite:thin://127.0.0.1:10800/> create table tmp_table_date_and_time
> (key_field INT PRIMARY KEY,field1 DATE,field2 TIME);
> SQL: create table tmp_table_date_and_time (key_field INT PRIMARY KEY,field1
> DATE,field2 TIME)
> No rows affected (0.131 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> insert into tmp_table_date_and_time
> (key_field,field1,field2) values (3, '2017-12-09','25:44:56');
> SQL: insert into tmp_table_date_and_time (key_field,field1,field2) values (3,
> '2017-12-09','25:44:56')
> 1 row affected (0.097 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800/> select * from tmp_table_date_and_time;
> SQL: select * from tmp_table_date_and_time
> IN IncrementalRows 3
> ++++
> | KEY_FIELD| FIELD1 |
> FIELD2 |
> ++++
> | 3 | Sat Dec 09 00:00:00 MSK 2017 | 01:44:56
> |
> ++++
> 1 row selected (0.017 seconds)
> 0: jdbc:ignite:thin://127.0.0.1:10800
[jira] [Commented] (IGNITE-8552) Unable to use date as primary key
[
https://issues.apache.org/jira/browse/IGNITE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691307#comment-17691307
]
Chenjian commented on IGNITE-8552:
--
Hi, [~Pavlukhin] Just checked seems in 2.14 version still has this problem.
{code:java}
Error: class org.apache.ignite.IgniteCheckedException: Failed to complete
exchange process. (state=5,code=1) {code}
Any plan about fixing this?
> Unable to use date as primary key
> -
>
> Key: IGNITE-8552
> URL: https://issues.apache.org/jira/browse/IGNITE-8552
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4
>Reporter: Pavel Vinokurov
>Priority: Major
> Attachments: IGNITE-8552_implemented.patch
>
>
> It' is unable to create cache via ddl:
> create table tab(id date primary key, date_field date);
> Result:
> ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to
> rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in
> the node classpath (use default marshaller to enable binary objects) :
> SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
> at
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18829) Ignite add not-null column to non-empty table does not get default value
Chenjian created IGNITE-18829: - Summary: Ignite add not-null column to non-empty table does not get default value Key: IGNITE-18829 URL: https://issues.apache.org/jira/browse/IGNITE-18829 Project: Ignite Issue Type: Bug Components: sql Reporter: Chenjian Add the not null column to the non-empty table should be given the default values. Reproduce: # create table t (id bigint primary key, a varchar, b int) # insert into t values(1, 'a', 1) # alter t add column x int not null. # select * from t. expected get "1, 'a', 1, 0", but got "1, 'a', 1, NULL" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18102) Ignite does not support create table with dot column
[ https://issues.apache.org/jira/browse/IGNITE-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17647876#comment-17647876 ] Chenjian commented on IGNITE-18102: --- [~zstan] Thanks. [~jooger] Hi boss, can you guide me on this? which test file is in charge of the creating table test? > Ignite does not support create table with dot column > > > Key: IGNITE-18102 > URL: https://issues.apache.org/jira/browse/IGNITE-18102 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Chenjian >Assignee: Chenjian >Priority: Minor > Attachments: image-2022-11-07-17-57-49-255.png, > image-2022-11-07-18-01-49-687.png > > > Ignite does not support create the column with dot. > like create table (... , `a.dot` bigint, ...), using the !columns command > only can see the suffix about the defined name `dot`. > But Ignite allow add column with dot which is not compatible with self. > Eg: > !image-2022-11-07-17-57-49-255.png! > !image-2022-11-07-18-01-49-687.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18102) Ignite does not support create table with dot column
[ https://issues.apache.org/jira/browse/IGNITE-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian reassigned IGNITE-18102: - Assignee: Chenjian > Ignite does not support create table with dot column > > > Key: IGNITE-18102 > URL: https://issues.apache.org/jira/browse/IGNITE-18102 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Chenjian >Assignee: Chenjian >Priority: Minor > Attachments: image-2022-11-07-17-57-49-255.png, > image-2022-11-07-18-01-49-687.png > > > Ignite does not support create the column with dot. > like create table (... , `a.dot` bigint, ...), using the !columns command > only can see the suffix about the defined name `dot`. > But Ignite allow add column with dot which is not compatible with self. > Eg: > !image-2022-11-07-17-57-49-255.png! > !image-2022-11-07-18-01-49-687.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18388) Ignite drop then add same column has the wrong sematic
[ https://issues.apache.org/jira/browse/IGNITE-18388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian reassigned IGNITE-18388: - Assignee: Chenjian > Ignite drop then add same column has the wrong sematic > --- > > Key: IGNITE-18388 > URL: https://issues.apache.org/jira/browse/IGNITE-18388 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14 >Reporter: Chenjian >Assignee: Chenjian >Priority: Major > Attachments: image-2022-12-13-15-43-58-095.png > > > Dropped the column then added the column with the same name, the value about > the column backend which should not. > Steps to reproduce: > * create table t(id int primary key, x int, y int) > * insert into t values (1, 2, 3) > * select * from t. The result shows as expected 1, 2, 3 > * alter table drop column x. > * select * from t. The result shows as expected 1,3 > * alter table add column x int. > * select * from t. *The result shows NOT as expected 1,3,2. which should > 1,3,NULL.* > > !image-2022-12-13-15-43-58-095.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18388) Ignite drop then add same column has the wrong sematic
Chenjian created IGNITE-18388: - Summary: Ignite drop then add same column has the wrong sematic Key: IGNITE-18388 URL: https://issues.apache.org/jira/browse/IGNITE-18388 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.14, 2.13, 2.12, 2.11, 2.10, 2.9, 2.8 Reporter: Chenjian Attachments: image-2022-12-13-15-43-58-095.png Dropped the column then added the column with the same name, the value about the column backend which should not. Steps to reproduce: * create table t(id int primary key, x int, y int) * insert into t values (1, 2, 3) * select * from t. The result shows as expected 1, 2, 3 * alter table drop column x. * select * from t. The result shows as expected 1,3 * alter table add column x int. * select * from t. *The result shows NOT as expected 1,3,2. which should 1,3,NULL.* !image-2022-12-13-15-43-58-095.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18102) Ignite does not support create table with dot column
[ https://issues.apache.org/jira/browse/IGNITE-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644421#comment-17644421 ] Chenjian commented on IGNITE-18102: --- [~jooger] Thanks for the clarification, do you know how to pick up the ticket? I wanna have a try > Ignite does not support create table with dot column > > > Key: IGNITE-18102 > URL: https://issues.apache.org/jira/browse/IGNITE-18102 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Chenjian >Priority: Minor > Attachments: image-2022-11-07-17-57-49-255.png, > image-2022-11-07-18-01-49-687.png > > > Ignite does not support create the column with dot. > like create table (... , `a.dot` bigint, ...), using the !columns command > only can see the suffix about the defined name `dot`. > But Ignite allow add column with dot which is not compatible with self. > Eg: > !image-2022-11-07-17-57-49-255.png! > !image-2022-11-07-18-01-49-687.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18102) Ignite does not support create table with dot column
[ https://issues.apache.org/jira/browse/IGNITE-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenjian updated IGNITE-18102: -- Priority: Minor (was: Major) > Ignite does not support create table with dot column > > > Key: IGNITE-18102 > URL: https://issues.apache.org/jira/browse/IGNITE-18102 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Chenjian >Priority: Minor > Attachments: image-2022-11-07-17-57-49-255.png, > image-2022-11-07-18-01-49-687.png > > > Ignite does not support create the column with dot. > like create table (... , `a.dot` bigint, ...), using the !columns command > only can see the suffix about the defined name `dot`. > But Ignite allow add column with dot which is not compatible with self. > Eg: > !image-2022-11-07-17-57-49-255.png! > !image-2022-11-07-18-01-49-687.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18102) Ignite does not support create table with dot column
[ https://issues.apache.org/jira/browse/IGNITE-18102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642799#comment-17642799 ] Chenjian commented on IGNITE-18102: --- [~jooger] Hi, what's the meaning? Are you considering to investigate this part? > Ignite does not support create table with dot column > > > Key: IGNITE-18102 > URL: https://issues.apache.org/jira/browse/IGNITE-18102 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Chenjian >Priority: Major > Attachments: image-2022-11-07-17-57-49-255.png, > image-2022-11-07-18-01-49-687.png > > > Ignite does not support create the column with dot. > like create table (... , `a.dot` bigint, ...), using the !columns command > only can see the suffix about the defined name `dot`. > But Ignite allow add column with dot which is not compatible with self. > Eg: > !image-2022-11-07-17-57-49-255.png! > !image-2022-11-07-18-01-49-687.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18102) Ignite does not support create table with dot column
Chenjian created IGNITE-18102: - Summary: Ignite does not support create table with dot column Key: IGNITE-18102 URL: https://issues.apache.org/jira/browse/IGNITE-18102 Project: Ignite Issue Type: Bug Components: sql Reporter: Chenjian Attachments: image-2022-11-07-17-57-49-255.png, image-2022-11-07-18-01-49-687.png Ignite does not support create the column with dot. like create table (... , `a.dot` bigint, ...), using the !columns command only can see the suffix about the defined name `dot`. But Ignite allow add column with dot which is not compatible with self. Eg: !image-2022-11-07-17-57-49-255.png! !image-2022-11-07-18-01-49-687.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-14948) Aggregation function `avg` lose precision on decimal column
Chenjian created IGNITE-14948: - Summary: Aggregation function `avg` lose precision on decimal column Key: IGNITE-14948 URL: https://issues.apache.org/jira/browse/IGNITE-14948 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.10 Environment: Mac os 11. JDK8 and JDK11. Reporter: Chenjian Use sql to apply avg function on the decimal fields will lose the precision. eg. create table t1(id bigint primary key, val decimal(30, 10)); insert into t1(id, val) values (1, 1.0), (2, 123456789.987654321); then : select select avg(val) from t1; excepted : 111728394.9938271605 actual returned: 111728394.9938271600 -- This message was sent by Atlassian Jira (v8.3.4#803005)
