[
https://issues.apache.org/jira/browse/IGNITE-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148795#comment-16148795
]
Semen Boikov commented on IGNITE-5648:
--------------------------------------
Hi Sergey,
I did review, in general looks good, I have some comments:
- I think test should be improved: we need test operations executed from both
clients and server, test with near cache enabled, test for
cache.invoke/invokeAll, for tx cache need test both updates without txStart and
inside txStart with all concurrency/isolation settings (you can use
CacheOptimisticTransactionsWithFilterTest as an example)
- it seems validation for 'invoke' in atomic cache is not implemented
- it seems validation for'LOCAL atomic cache is not implemented
- I think 'GridCacheContext.isQueryEnabled' will return false if cache is
started without queries, and index is created dynamically. Is this possible?
Thanks!
> DDL: NOT NULL constraint support for CREATE TABLE operator
> ----------------------------------------------------------
>
> Key: IGNITE-5648
> URL: https://issues.apache.org/jira/browse/IGNITE-5648
> Project: Ignite
> Issue Type: New Feature
> Components: sql
> Affects Versions: 2.0
> Reporter: Denis Magda
> Assignee: Sergey Kalashnikov
> Fix For: 2.3
>
>
> This is an umbrella ticket intended to aggregate all the activities related
> to {{NOT NULL}} constraint support for {{CREATE TABLE}} commands.
> {code}
> CREATE TABLE legs(legid INT NOT NULL);
> {code}
> Ignite must prevent setting {{legid}} to {{null}} value.
> The feature has to be supported for:
> * ODBC and JDBC drivers.
> * Native APIs (Java, .NET, C++)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
