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 3C8BD200D4D for ; Sun, 3 Dec 2017 22:11:27 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3AF03160C0B; Sun, 3 Dec 2017 21:11:27 +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 8121C160BF8 for ; Sun, 3 Dec 2017 22:11:26 +0100 (CET) Received: (qmail 72331 invoked by uid 500); 3 Dec 2017 21:11:25 -0000 Mailing-List: contact dev-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 dev@ignite.apache.org Delivered-To: moderator for dev@ignite.apache.org Received: (qmail 50590 invoked by uid 99); 3 Dec 2017 20:48:01 -0000 X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.98 X-Spam-Level: * X-Spam-Status: No, score=1.98 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=trimble-com.20150623.gappssmtp.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=trimble-com.20150623.gappssmtp.com; s=20150623; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc; bh=yjwRcJKbyZRT8eeJQij3+53Dxr1j5NUp/e+x4usNx7Y=; b=qnXDgKazKxuwveP2g8Lnh5lcTl9YA6AwRn4zRNJlKaslZCNcFP8Q76OsX7Mb1o/iiT 6+Mc1AO9g9QqiggQfhiPIocYjZtRCmZcUmGQkOVVC9Ntw/8bbs9dKLFW3INace+z4hPD DQ7vBi4IN1XFzXO+EG3K38W3f4YvNISRXT1qWV2iPrLAYTSKw+tmWECgGUS3iMmILLYx r1sHCuZZJQrucR9WA2MZCtAlT5b2VOdbXhsPb4Q51frGuoUMMK70VkwOorHWr7v9xciA qYqEWF1v8i3W/H1qN8Qk8G7j5qojiqYKiNv121Wi7lX0AE6weuItapj659LFrk+kMJX0 RKUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc; bh=yjwRcJKbyZRT8eeJQij3+53Dxr1j5NUp/e+x4usNx7Y=; b=ZC9W6jln5cvwojmrNhc28OUEWyWEtJ1xrkuXgvFLME3PXqWKtAQDj1j28sKfZvr9Si 7fdywmahNsaCtcHGluK+BNoNpBLbpxGUktge0ARB+lhnkKaiOzuwnWKdkKsspqik3fDA IZbPcoFbuMjUElYR2bz5VMQBSK22FXWhl1uNUhm7Iaw5vw/sZlVi46dstUO90RvCzTey 40N+0OgAuMoltbB+DkYB6tO3dr4FcQE+0GS42j1w3gpNJMZTJQbWtZnh/E/IO+9RDhTr qAdqbMSlzC44IhKG6HlYWY26BTpOA8FG1yf4QZoZ/PaMTU7IYGeQ023XzMy+qn9Kzq/J 58GA== X-Gm-Message-State: AJaThX7suvqAhniZcPWyxLpFltiIMvdNXyyFnSQdtenUrDfPRyxPSC6y BjzD0P8H/41d9SD1FvZoOmUV7Quuw0lONuX83K1Apg== X-Google-Smtp-Source: AGs4zMY1x5zDYwC1uOgGNNI2tAPM9fyRrZ3AAy5PID1u9IDUCgGivjw5VR6N2dsXknwKTuBzqutkSd7mqr2x5k8FJO8= X-Received: by 10.80.182.5 with SMTP id b5mr27341114ede.227.1512334076796; Sun, 03 Dec 2017 12:47:56 -0800 (PST) From: Raymond Wilson References: <394d4c0ab5452bbe4031e86934b5b7fa@mail.gmail.com> <1512082152617-0.post@n6.nabble.com> <1512088209320-0.post@n6.nabble.com> <5a2179ea.42142e0a.e7eaf.97ad@mx.google.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQM+HKl698LWKg1As8xAqjz+0BtRlAIkhhmzAleSGnUCVM6BqQLB9ClgAmbuIBgB3cJCoQCqxijwn+ij9DA= Date: Mon, 4 Dec 2017 09:47:42 +1300 Message-ID: Subject: RE: Does the Ignite C# client support distributed queues? To: user@ignite.apache.org Cc: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c0e39506e3029055f75b769" archived-at: Sun, 03 Dec 2017 21:11:27 -0000 --94eb2c0e39506e3029055f75b769 Content-Type: text/plain; charset="UTF-8" Hi Pavel, Is there a document that captures all the current gaps? Thanks, Raymond. *From:* Pavel Tupitsyn [mailto:ptupitsyn@apache.org] *Sent:* Monday, December 4, 2017 6:27 AM *To:* user@ignite.apache.org *Cc:* dev@ignite.apache.org *Subject:* Re: Does the Ignite C# client support distributed queues? Hi Raymond, There is no exact schedule, but we always strive to keep .NET API up to speed with Java. Usually new features are added right in the same release (persistence in 2.1, for example). Pavel On Sat, Dec 2, 2017 at 9:51 AM, Raymond Wilson wrote: Hi Alexey, I think I need to be logged-in to vote for it. How do I get a credential to do that? Can you speak to my second question regards the plan for functional equivalence between C# & Java clients? Thanks, Raymond. *From:* Alexey Popov [mailto:tank2.alex@gmail.com] *Sent:* Saturday, December 2, 2017 4:49 AM *To:* user@ignite.apache.org *Cc:* dev@ignite.apache.org *Subject:* RE: Does the Ignite C# client support distributed queues? Hi Raymond, You are right, distributed queues require changes at Ignite core. https://issues.apache.org/jira/browse/IGNITE-2701 It was created almost 1 year ago. Please vote for this feature. As far as I know there is no plan/schedule for it. Thank you, Alexey *From: *Raymond Wilson *Sent: *Friday, December 1, 2017 5:58 AM *To: *user@ignite.apache.org *Cc: *dev@ignite.apache.org *Subject: *RE: Does the Ignite C# client support distributed queues? Looking at it I see it's blocked by 2701 (which has additional dependencies, all of which say they are blocked by 2701). I understand there is an intention to bring the C# client up to par with the Java client. Is there a ticket/schedule yet for this? Raymond. -----Original Message----- From: vkulichenko [mailto:valentin.kulichenko@gmail.com ] Sent: Friday, December 1, 2017 1:30 PM To: user@ignite.apache.org Subject: RE: Does the Ignite C# client support distributed queues? Oops, I read wrong! This is not supported. There is a ticket, but it doesn't seem to be active at the moment: https://issues.apache.org/jira/browse/IGNITE-1417 -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/ --94eb2c0e39506e3029055f75b769--