You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2021/11/28 11:37:00 UTC

[jira] [Updated] (IGNITE-16007) Make sure the KeyValueView contracts are consistent throughout other views

     [ https://issues.apache.org/jira/browse/IGNITE-16007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Scherbakov updated IGNITE-16007:
---------------------------------------
    Description: 
After IGNITE-15085 contracts were changed for some table API methods like putIfAbsent and replaceXXX to disallow null values.

It is necessary to:
 # make all other table views consistent with the contract.
 # ensure other methods like put* are forbidden to accept null values as well.

  was:
After IGNITE-15085 contracts were changed for some table API methods like putIfAbsent and *replace* to disallow null values.

It is necessary to:
 # make all other table views consistent with the contract.
 # ensure other methods like put* are forbidden to accept null values as well.


> Make sure the KeyValueView contracts are consistent throughout other views
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-16007
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16007
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Scherbakov
>            Priority: Major
>              Labels: ignite-3
>
> After IGNITE-15085 contracts were changed for some table API methods like putIfAbsent and replaceXXX to disallow null values.
> It is necessary to:
>  # make all other table views consistent with the contract.
>  # ensure other methods like put* are forbidden to accept null values as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)