[
https://issues.apache.org/jira/browse/IGNITE-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174411#comment-16174411
]
ASF GitHub Bot commented on IGNITE-6387:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/2709
IGNITE-6387: Added NOT NULL sql constraint validation for values loaded
from cache store
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6387
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2709.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2709
----
commit 7430804b391334338d43ddcc2c7c9f9ca9a0285e
Author: skalashnikov <[email protected]>
Date: 2017-09-18T08:32:52Z
IGNITE-6387: added sql constraint validation for values loaded from cache
store.
commit aa3f8b9ee0fdad852ffdfd9142ee42435c7288ec
Author: skalashnikov <[email protected]>
Date: 2017-09-21T07:57:10Z
Merge branch 'master' of https://github.com/apache/ignite into ignite-6387
----
> 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: Bug
> 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()}}, {{QueryEntity.setNotNullFields()}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
