[
https://issues.apache.org/jira/browse/IGNITE-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Kalashnikov updated IGNITE-6387:
---------------------------------------
Description:
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()}}
was:
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}}
> 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
>
> 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)
