I have updated the wiki based on Dan's comment.
Changes with api:
*On "AsyncEventQueueFactory" interface - *
*AsyncEventQueueFactory pauseEventDispatchToListener(); *// This causes
AEQ to be created with paused state.
On Fri, Aug 16, 2019 at 4:36 PM Anilkumar Gingade
wrote:
> Dan,
>
> If
Dan,
If you look into the API; the AEQ will be created with the pause state. The
user (application) has to call resume to dispatch the events.
It will be slightly different from GatewaySender behavior; where
GatewaySender will be created with run mode and then application has to
call pause on
Hi Anil,
While I like the idea of matching the API of GatewaySender, I'm not sure I
see how this solves the problem. Is it required of the user to call pause
on the AsyncEventQueue as soon as it is created? How would someone do that
when creating AEQs with xml or cluster configuration? Maybe it
Does anyone know what the next step is? Do we need a release manager to
proceed?
On Tue, Aug 13, 2019 at 1:57 PM John Blum wrote:
> Sorry, corrections below...
>
> On Tue, Aug 13, 2019 at 1:54 PM John Blum wrote:
>
> > Stated slightly a different way...
> >
> > If *SBDG 1.2 *were to be
Thanks. It's done now.
On Fri, Aug 16, 2019 at 2:46 PM Nabarun Nag wrote:
> +1
>
> On Fri, Aug 16, 2019 at 2:45 PM Anilkumar Gingade
> wrote:
>
> > +1 to include
> >
> > On Fri, Aug 16, 2019 at 2:41 PM Anthony Baker wrote:
> >
> > > +1 from me. When you need to do an offline export, it’s
+1
On Fri, Aug 16, 2019 at 2:45 PM Anilkumar Gingade
wrote:
> +1 to include
>
> On Fri, Aug 16, 2019 at 2:41 PM Anthony Baker wrote:
>
> > +1 from me. When you need to do an offline export, it’s usually
> > important. Not being able to export *all* the data might lead to data
> loss.
> >
> >
+1 to include
On Fri, Aug 16, 2019 at 2:41 PM Anthony Baker wrote:
> +1 from me. When you need to do an offline export, it’s usually
> important. Not being able to export *all* the data might lead to data loss.
>
> Anthony
>
>
> > On Aug 16, 2019, at 2:06 PM, Udo Kohlmeyer wrote:
> >
> > +1
+1 from me. When you need to do an offline export, it’s usually important.
Not being able to export *all* the data might lead to data loss.
Anthony
> On Aug 16, 2019, at 2:06 PM, Udo Kohlmeyer wrote:
>
> +1 to include
>
>
> On 8/16/19 12:43 PM, Eric Shu wrote:
>> Hi,
>>
>> I'd like to
Proposal to support controlling capability with event dispatch to
AsyncEventQueue Listener.
Wiki proposal page:
https://cwiki.apache.org/confluence/display/GEODE/%5BDraft%5D+Controlling+event+dispatch+to+AsyncEventListener
Here is the details from the wiki page:
*Problem*
*The Geode system
+1 to include
On 8/16/19 12:43 PM, Eric Shu wrote:
Hi,
I'd like to include the following commit (
https://gitbox.apache.org/repos/asf?p=geode.git;h=aa33060) into Geode 1.10
release.
The commit fixes the issue that a user tries to use export offline data to
a snapshot file but failed. This
Hi,
I'd like to include the following commit (
https://gitbox.apache.org/repos/asf?p=geode.git;h=aa33060) into Geode 1.10
release.
The commit fixes the issue that a user tries to use export offline data to
a snapshot file but failed. This issue exists from release 1.1.0. However,
it is a
11 matches
Mail list logo
