ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Kalashnikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6350) SQL: Forbid NOT NULL constraints usage for a cache with configured read-through cache store
Date Fri, 15 Sep 2017 08:24:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167521#comment-16167521
] 

Sergey Kalashnikov commented on IGNITE-6350:
--------------------------------------------

added check for cache interceptor to the same patch (the changes are very similar)

> SQL: Forbid NOT NULL constraints usage for a cache with configured read-through cache
store
> -------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-6350
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6350
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Sergey Kalashnikov
>            Assignee: Sergey Kalashnikov
>             Fix For: 2.3
>
>
> We need to throw an exception when user attempts to create or alter a table with a field
declared as NOT NULL in a case the corresponding cache configuration employs read-through
cache store {{CacheConfiguration.setReadThrough()}}.
> These features seem to not fit together quite well, so we skip the support at the moment
and the check will keep things consistent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message