ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6387) SQL: NOT NULL fields validation with read-through cache store
Date Fri, 29 Sep 2017 12:56:00 GMT

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

Vladimir Ozerov commented on IGNITE-6387:

[~skalashnikov], as discussed, looks like full support of this case doesn't make sense. If
storage is enabled, we do not want to allow {{NOT NULL}} constrains on our cache as it renders
behavior of {{IgniteCache.load*}} operations undefined. It is better to simply disallow Ignite-induced
{{NOT NULL}} constraints and advise user to control this restriction on store level. 
The same is applicable for upcoming {{DEFAULT}}, {{UNIQUE}} and {{CHECK}} keywords.

I propose to save the patch here for historical purposes and close the ticket as "Won't Fix"
for now.

> SQL: NOT NULL fields validation with read-through cache store
> -------------------------------------------------------------
>                 Key: IGNITE-6387
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6387
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Sergey Kalashnikov
>            Assignee: Sergey Kalashnikov
>             Fix For: 2.3
> There is a case left unsolved during implementation of SQL NOT NULL constraints feature.
> It may happen so that cache update operation fails and the value loaded from store is
put into cache.
> This value must also be validated with regards to configured NOT NULL constraints.
> See {{CacheConfiguration.setCacheStoreFactory()}}, {{CacheConfiguration.setReadThrough()}},

This message was sent by Atlassian JIRA

View raw message