Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B446A200CEF for ; Mon, 4 Sep 2017 11:34:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B2DE0164657; Mon, 4 Sep 2017 09:34:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 05434164642 for ; Mon, 4 Sep 2017 11:34:02 +0200 (CEST) Received: (qmail 87588 invoked by uid 500); 4 Sep 2017 09:34:02 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 87579 invoked by uid 99); 4 Sep 2017 09:34:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2017 09:34:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8ECD9D2EED for ; Mon, 4 Sep 2017 09:34:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id tLYnc9SuHqrr for ; Mon, 4 Sep 2017 09:34:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C535F5F257 for ; Mon, 4 Sep 2017 09:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 577CAE0217 for ; Mon, 4 Sep 2017 09:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 119B523F0D for ; Mon, 4 Sep 2017 09:34:00 +0000 (UTC) Date: Mon, 4 Sep 2017 09:34:00 +0000 (UTC) From: "Pavel Tupitsyn (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-6244) .NET: Thin client: ScanQuery MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 04 Sep 2017 09:34:03 -0000 [ https://issues.apache.org/jira/browse/IGNITE-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-6244: ----------------------------------- Description: Implement ScanQuery in thin client. Challenges: * Query cursor. This will require some kind of HandleRegistry on Java side, so we can pass an ID back to client (see {{OdbcRequestHandler.qryCursors}} as an example). * Predicate. Thin client is not .NET-specific. We need a way to support predicates in (at least) Java and .NET, there should be some platform id. was: Implement ScanQuery in thin client. Challenges: * Query cursor. This will require some kind of HandleRegistry on Java side, so we can pass an ID back to client. * Predicate. Thin client is not .NET-specific. We need a way to support predicates in (at least) Java and .NET, there should be some platform id. > .NET: Thin client: ScanQuery > ---------------------------- > > Key: IGNITE-6244 > URL: https://issues.apache.org/jira/browse/IGNITE-6244 > Project: Ignite > Issue Type: Improvement > Components: platforms > Reporter: Pavel Tupitsyn > Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.3 > > > Implement ScanQuery in thin client. > Challenges: > * Query cursor. This will require some kind of HandleRegistry on Java side, so we can pass an ID back to client (see {{OdbcRequestHandler.qryCursors}} as an example). > * Predicate. Thin client is not .NET-specific. We need a way to support predicates in (at least) Java and .NET, there should be some platform id. -- This message was sent by Atlassian JIRA (v6.4.14#64029)