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

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2020/06/15 11:04:00 UTC

[jira] [Issue Comment Deleted] (IGNITE-13031) .NET: SqlFieldsQuery as ContinuousQuery.InitialQuery

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

Pavel Tupitsyn updated IGNITE-13031:
------------------------------------
    Comment: was deleted

(was: [~isapego] merged to master: 10f4d95076e2229fae9c6e7b2d1b42700623c88e)

> .NET: SqlFieldsQuery as ContinuousQuery.InitialQuery
> ----------------------------------------------------
>
>                 Key: IGNITE-13031
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13031
>             Project: Ignite
>          Issue Type: New Feature
>          Components: platforms
>    Affects Versions: 2.8
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Critical
>              Labels: .NET
>             Fix For: 2.9
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> SqlQuery has been deprecated in favor of SqlFieldsQuery, but ContinuousQuery in Ignite.NET does not allow SqlFieldsQuery as InitialQuery. 
> Java API allows that, so we have to derive SqlFieldsQuery from QueryBase and make it work.
> The problem will arise when SqlFieldsQuery does not return _key & _val - see how Java handles this.



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