[jira] [Updated] (IGNITE-19784) Specific SQL query causes all nodes in cluster down

[ https://issues.apache.org/jira/browse/IGNITE-19784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu updated IGNITE-19784: --- Component/s: python sql Labels: Crash crash server-side (was: ) > Specif

[jira] [Created] (IGNITE-19784) Specific SQL query causes all nodes in cluster down

Isaac Zhu created IGNITE-19784: -- Summary: Specific SQL query causes all nodes in cluster down Key: IGNITE-19784 URL: https://issues.apache.org/jira/browse/IGNITE-19784 Project: Ignite Issue Type

[jira] [Commented] (IGNITE-18715) B+Tree corruption error caused Ignite cluster crash and not able restart

[ https://issues.apache.org/jira/browse/IGNITE-18715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697511#comment-17697511 ] Isaac Zhu commented on IGNITE-18715: [~sergeychugunov] The partition files I have i

[jira] [Created] (IGNITE-18751) JVM crash on Ignite node starting

Isaac Zhu created IGNITE-18751: -- Summary: JVM crash on Ignite node starting Key: IGNITE-18751 URL: https://issues.apache.org/jira/browse/IGNITE-18751 Project: Ignite Issue Type: Bug Co

[jira] [Created] (IGNITE-18715) B+Tree corruption error caused Ignite cluster crash and not able restart

Isaac Zhu created IGNITE-18715: -- Summary: B+Tree corruption error caused Ignite cluster crash and not able restart Key: IGNITE-18715 URL: https://issues.apache.org/jira/browse/IGNITE-18715 Project: Ignit

[jira] [Resolved] (IGNITE-14958) update SQL error "column is not compatible with index definition" after upgrading to 2.10.0

[ https://issues.apache.org/jira/browse/IGNITE-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu resolved IGNITE-14958. Fix Version/s: 2.10 Resolution: Not A Bug We found this is because we store "Date" type in

[jira] [Commented] (IGNITE-14958) update SQL error "column is not compatible with index definition" after upgrading to 2.10.0

[ https://issues.apache.org/jira/browse/IGNITE-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366968#comment-17366968 ] Isaac Zhu commented on IGNITE-14958: Here is the server side stack trace: class or

[jira] [Created] (IGNITE-14958) update SQL error "column is not compatible with index definition" after upgrading to 2.10.0

Isaac Zhu created IGNITE-14958: -- Summary: update SQL error "column is not compatible with index definition" after upgrading to 2.10.0 Key: IGNITE-14958 URL: https://issues.apache.org/jira/browse/IGNITE-14958

[jira] [Commented] (IGNITE-14120) select count * returns multiple rows

[ https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291466#comment-17291466 ] Isaac Zhu commented on IGNITE-14120: Hi Xin, Thanks for the further explanation. H

[jira] [Updated] (IGNITE-14120) select count * returns multiple rows

[ https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu updated IGNITE-14120: --- Description: I have a partitioned table which has 1 backup, the *queryParallelism* is set to 4. T

[jira] [Created] (IGNITE-14120) select count * returns multiple rows

Isaac Zhu created IGNITE-14120: -- Summary: select count * returns multiple rows Key: IGNITE-14120 URL: https://issues.apache.org/jira/browse/IGNITE-14120 Project: Ignite Issue Type: Bug

[jira] [Updated] (IGNITE-13443) distributed left joins errored with "java.lang.ClassCastException"

[ https://issues.apache.org/jira/browse/IGNITE-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu updated IGNITE-13443: --- Component/s: sql > distributed left joins errored with "java.lang.ClassCastException" > ---

[jira] [Created] (IGNITE-13443) distributed left joins errored with "java.lang.ClassCastException"

Isaac Zhu created IGNITE-13443: -- Summary: distributed left joins errored with "java.lang.ClassCastException" Key: IGNITE-13443 URL: https://issues.apache.org/jira/browse/IGNITE-13443 Project: Ignite

[jira] [Commented] (IGNITE-5359) Non-collocated SQL subqueries return wrong results.

[ https://issues.apache.org/jira/browse/IGNITE-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149571#comment-17149571 ] Isaac Zhu commented on IGNITE-5359: --- See the same problem in 2.8.0 I have two partiti

[jira] [Updated] (IGNITE-12974) pyignite client sql query result has wrong columns order in continuous pages

[ https://issues.apache.org/jira/browse/IGNITE-12974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu updated IGNITE-12974: --- Description: When the table has more than 10 columns and the query has more than 1 row to return,

[jira] [Updated] (IGNITE-12975) pyignte sql query should not try to create a cache

[ https://issues.apache.org/jira/browse/IGNITE-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Zhu updated IGNITE-12975: --- Affects Version/s: 2.7.6 > pyignte sql query should not try to create a cache > ---

[jira] [Created] (IGNITE-12975) pyignte sql query should not try to create a cache

Isaac Zhu created IGNITE-12975: -- Summary: pyignte sql query should not try to create a cache Key: IGNITE-12975 URL: https://issues.apache.org/jira/browse/IGNITE-12975 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-12974) pyignite client sql query result has wrong columns order in continuous pages

Isaac Zhu created IGNITE-12974: -- Summary: pyignite client sql query result has wrong columns order in continuous pages Key: IGNITE-12974 URL: https://issues.apache.org/jira/browse/IGNITE-12974 Project: