You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2023/10/13 15:17:00 UTC

[jira] [Updated] (IGNITE-20599) Implement a 'NOT_TOMBSTONE' operation in the meta storage dsl.

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

Mirza Aliev updated IGNITE-20599:
---------------------------------
    Summary: Implement a 'NOT_TOMBSTONE' operation in the meta storage dsl.  (was: Implement a 'not' operation in the meta storage dsl.)

> Implement a 'NOT_TOMBSTONE' operation in the meta storage dsl.
> --------------------------------------------------------------
>
>                 Key: IGNITE-20599
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20599
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Sergey Uttsel
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> In https://issues.apache.org/jira/browse/IGNITE-20561 we need to create a condition for a ms invoke with negation. We could do this two ways:
> {code:java}
> and(
>     notExists(dataNodes(zoneId)),
>     notTombstone(dataNodes(zoneId))
> ){code}
> or
> {code:java}
> not(
>     or(
>         exists(dataNodes(zoneId)),
>         tombstone(dataNodes(zoneId))
>     )
> ){code}
> But there are no `notTombstone` or `not` methods in the meta storage dsl.
>  
> I propose to implement `not` operation because it is more general approach and it can be reused with other conditions.
> *Definition of done*
> `not` operation  is implemented.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)