Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 630F218990 for ; Thu, 3 Sep 2015 23:36:51 +0000 (UTC) Received: (qmail 32326 invoked by uid 500); 3 Sep 2015 23:36:51 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 32282 invoked by uid 500); 3 Sep 2015 23:36:51 -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 Received: (qmail 32271 invoked by uid 99); 3 Sep 2015 23:36:51 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2015 23:36:51 +0000 Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id B491F1A0144 for ; Thu, 3 Sep 2015 23:36:50 +0000 (UTC) Received: by lbcao8 with SMTP id ao8so2514284lbc.3 for ; Thu, 03 Sep 2015 16:36:49 -0700 (PDT) X-Gm-Message-State: ALoCoQl4/uq5kn3BSsFu1i8nK787+nGBB3cDfO/NjVPG2MaeTdmjWBAv6BHCkUfS4vsr9IWEFoRI X-Received: by 10.152.23.38 with SMTP id j6mr513834laf.47.1441323409328; Thu, 03 Sep 2015 16:36:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.74.135 with HTTP; Thu, 3 Sep 2015 16:36:29 -0700 (PDT) X-Originating-IP: [85.155.76.117] From: Raul Kripalani Date: Fri, 4 Sep 2015 00:36:29 +0100 Message-ID: Subject: Implemented IGNITE-1370 Streamers: Implement multiple tuple extractor To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary=089e0160b6f0d1e5fb051ee0414d --089e0160b6f0d1e5fb051ee0414d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I have enhanced the Streaming API with a new StreamMultipleTupleExtractor to allow users to extract multiple tuples from a single message/event. I also added a unit test inside the SocketStreamer tests. Pull request: https://github.com/apache/ignite/pull/67. My preference would have been to extend the StreamTupleExtractor interface with a boolean supportsMultiple() method and an Map extractMultiple(T msg) method, but this is impossible to do in Java 7 without breaking the API. It would have been possible with default methods if we were using Java 8 language features. As a result, I had to create another interface and add a new field in StreamAdapter accordingly. Regards, *Ra=C3=BAl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk --089e0160b6f0d1e5fb051ee0414d--