[jira] [Commented] (UNOMI-302) Implement Unomi-specific get/delete/createUnomiSegment fields and mutations

["Anatol Sialitski (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/UNOMI-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078029#comment-17078029 ] 

Anatol Sialitski commented on UNOMI-302:
----------------------------------------

will be used the following
```
type Unomi_Segment \{ condition : JSON!, id : ID! view: CDP_View! name : String! }
```
instead of 

```
type Unomi_Segment extends CDP_Segment \{ condition : JSON # profiles: null will be null here }

```

The deleteSegment mutation will be used for both Unomi_Segment and CDP_Segment.

 

That was discussed with [~shuber]

> Implement Unomi-specific get/delete/createUnomiSegment fields and mutations
> ---------------------------------------------------------------------------
>
>                 Key: UNOMI-302
>                 URL: https://issues.apache.org/jira/browse/UNOMI-302
>             Project: Apache Unomi
>          Issue Type: Sub-task
>          Components: core
>    Affects Versions: 2.0.0
>            Reporter: Serge Huber
>            Priority: Major
>             Fix For: 2.0.0
>
>
> As Unomi provides a much more powerful condition system for building segments, we need to add fields and mutations that will support these structures. 
> They should look something like this:
> type Unomi_Segment extends CDP_Segment {
>   condition : JSON
> #  profiles: null will be null here
> }
> input Unomi_SegmentInput {
>   id : ID
>   view : ID!
>   name : String
>   condition: JSON!
> }
> getUnomiSegment(segmentID: ID!) : Unomi_Segment
> ​createOrUpdateUnomiSegment(segment : Unomi_SegmentInput!) : Unomi_Segment
> ​deleteSegment(segmentID : ID!) : Boolean



--
This message was sent by Atlassian Jira
(v8.3.4#803005)