Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0926B17BED for ; Sun, 13 Sep 2015 00:21:46 +0000 (UTC) Received: (qmail 4859 invoked by uid 500); 13 Sep 2015 00:21:45 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 4815 invoked by uid 500); 13 Sep 2015 00:21:45 -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 4751 invoked by uid 99); 13 Sep 2015 00:21:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Sep 2015 00:21:45 +0000 Date: Sun, 13 Sep 2015 00:21:45 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-1370?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D147= 42272#comment-14742272 ]=20 ASF GitHub Bot commented on IGNITE-1370: ---------------------------------------- GitHub user raulk opened a pull request: https://github.com/apache/ignite/pull/85 IGNITE-1370 Streamers: Implement multiple tuple extractor. With adjustments discussed in ticket. You can merge this pull request into a Git repository by running: $ git pull https://github.com/raulk/incubator-ignite feature/ignite-137= 0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/85.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #85 =20 ---- commit 4d9734a0842f0a46310c1f6261fdf42371db8705 Author: Raul Kripalani Date: 2015-09-03T22:31:08Z IGNITE-1370 Streamers: Implement multiple tuple extractor. commit 8b5e078cf60c7176e5b3f2aefc558ba819dcad0a Author: Raul Kripalani Date: 2015-09-13T00:18:34Z IGNITE-1370 Deprecate StreamTupleExtractor in favor of new *Single*Stre= amTupleExtractor. ---- > StreamTupleExtractor should allow extracting multiple tuples from a singl= e event > -------------------------------------------------------------------------= ------- > > Key: IGNITE-1370 > URL: https://issues.apache.org/jira/browse/IGNITE-1370 > Project: Ignite > Issue Type: Improvement > Components: streaming > Affects Versions: ignite-1.4 > Reporter: Ra=C3=BAl Kripalani > Assignee: Ra=C3=BAl Kripalani > > Currently the {{StreamTupleExtractor}} interface contains a single method= : > {code} > public Map.Entry extract(T msg); > {code} > Which only allows extracting a single Entry from an incoming event. > In real life, it could be that an event contains multiple entries.=20 -- This message was sent by Atlassian JIRA (v6.3.4#6332)