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

Posted to dev@nlpcraft.apache.org by "Sergey Kamov (Jira)" <ji...@apache.org> on 2021/05/17 19:52:00 UTC

[jira] [Resolved] (NLPCRAFT-323) Account for metadata in NCResult in REST API and SQL, if necessary.

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

Sergey Kamov resolved NLPCRAFT-323.
-----------------------------------
      Assignee: Aaron Radzinski  (was: Sergey Kamov)
    Resolution: Fixed

ready fro review in NLPCRAFT-319

> Account for metadata in NCResult in REST API and SQL, if necessary.
> -------------------------------------------------------------------
>
>                 Key: NLPCRAFT-323
>                 URL: https://issues.apache.org/jira/browse/NLPCRAFT-323
>             Project: NLPCraft
>          Issue Type: Task
>            Reporter: Aaron Radzinski
>            Assignee: Aaron Radzinski
>            Priority: Major
>             Fix For: 0.8.0
>
>
> NCResult is now extends NCMetadata. We need to add necessary changes to REST API and potentially to SQL storage (if necessary) to account for metadata component in NCResult.



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