[
https://issues.apache.org/jira/browse/IGNITE-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158726#comment-16158726
]
Semen Boikov commented on IGNITE-5648:
--------------------------------------
[~skalashnikov],
- I think handling for invoke in atomic cache should be improved: now in case
of validation error operation is still considered as update with previous
value, actually it should be no-op. You can change
AtomicCacheUpdateClosure.runEntryProcessor to return null in case of validation
error and further treat null as no-op
- for atomic cache entryProcessor can be also invoked in
'GridDhtAtomicCache.updateWithBatch', this method is executed for invokeAll if
CacheStore is enabled (the same for GridLocalAtomicCache.updateWithBatch)
- also regarding my question about 'GridCacheContext.isQueryEnabled': I was
asking about dynamic index, not table, creation. Is it possible to create cache
without indexes and add index later. Will GridCacheContext.isQueryEnabled work
in this case?
> 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)
