You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Cherkasov (JIRA)" <ji...@apache.org> on 2018/02/09 19:51:00 UTC
[jira] [Assigned] (IGNITE-7663) AssertionError/NPE on "CREATE
SCHEMA"
[ https://issues.apache.org/jira/browse/IGNITE-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Cherkasov reassigned IGNITE-7663:
-----------------------------------------
Assignee: Mikhail Cherkasov
> AssertionError/NPE on "CREATE SCHEMA"
> -------------------------------------
>
> Key: IGNITE-7663
> URL: https://issues.apache.org/jira/browse/IGNITE-7663
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.3
> Reporter: Mikhail Cherkasov
> Assignee: Mikhail Cherkasov
> Priority: Major
> Fix For: 2.5
>
>
> Instead of UnsupportedOperationException exception, we have AssertionError:
> [https://stackoverflow.com/questions/48708238/ignite-database-create-schema-assertionerror]
> Errors mean that we can't continue work and should terminate process because now it is in unknown state and behavior is unpredictable, but I don't think that it's the case, isn't it?
> With disabled assertions, we have NPE there, but anyway, I expect to see UnsupportedOperationException if we try to run SQL that we don't support yet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)