Mailing-List: contact issues-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Date: Thu, 6 Aug 2015 18:11:04 +0000 (UTC)
From: =?utf-8?Q?Ra=C3=BAl_Kripalani_=28JIRA=29?= <jira@apache.org>
To: issues@ignite.incubator.apache.org
Message-ID: <JIRA.12852651.1438884622000.392553.1438884664537@Atlassian.JIRA>
In-Reply-To: <JIRA.12852651.1438884622000@Atlassian.JIRA>
References: <JIRA.12852651.1438884622000@Atlassian.JIRA>
 <JIRA.12852651.1438884622141@arcas>
Subject: [jira] [Created] (IGNITE-1210) MongoDB Tailable Cursor Data
 Streamer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Ra=C3=BAl Kripalani created IGNITE-1210:
--------------------------------------

             Summary: MongoDB Tailable Cursor Data Streamer
                 Key: IGNITE-1210
                 URL: https://issues.apache.org/jira/browse/IGNITE-1210
             Project: Ignite
          Issue Type: New Feature
          Components: streaming
            Reporter: Ra=C3=BAl Kripalani
            Assignee: Ra=C3=BAl Kripalani


[Tailable cursors|http://docs.mongodb.org/manual/tutorial/create-tailable-c=
ursor/] in MongoDB are a mechanism to push data proactively from capped col=
lections into clients, thereby avoiding the usage of polling methods.

It should be an easy streamer to implement, although MongoDB reserves its r=
ight to close the cursor at any given point in time, therefore the client m=
ust implement logic to reconnect transparently and to remember where it lef=
t off in order to consume from that point onwards.

The camel-mongodb component of the Apache Camel project offers this functio=
nality so one can use it as a reference and implement similar logic for Ign=
ite.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)