Mailing-List: contact dev-help@asterixdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.apache.org
From: abdullah alamoudi <bamousaa@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: MultiTransactionJobletEventListenerFactory
Date: Thu, 16 Nov 2017 13:01:09 -0800
References: <CAE1xAnvZZWrgu6HiQs-qXV0PRsWLr44bm3kqVfj5swha9ffUcg@mail.gmail.com>
To: dev@asterixdb.apache.org
In-Reply-To: <CAE1xAnvZZWrgu6HiQs-qXV0PRsWLr44bm3kqVfj5swha9ffUcg@mail.gmail.com>
Message-Id: <F59038D4-DE9A-45DE-B952-B2BC2C982875@gmail.com>
archived-at: Thu, 16 Nov 2017 21:01:23 -0000

I am curious as to how feed will work without this?

~Abdullah.
> On Nov 16, 2017, at 12:43 PM, Steven Jacobs <sjaco002@ucr.edu> wrote:
> 
> Hi all,
> We currently have MultiTransactionJobletEventListenerFactory, which allows
> for one Hyracks job to run multiple Asterix transactions together.
> 
> This class is only used by feeds, and feeds are in process of changing to
> no longer need this feature. As part of the work in pre-deploying job
> specifications to be used by multiple hyracks jobs, I've been working on
> removing the transaction id from the job specifications, as we use a new
> transaction for each invocation of a deployed job.
> 
> There is currently no clear way to remove the transaction id from the job
> spec and keep the option for MultiTransactionJobletEventListenerFactory.
> 
> The question for the group is, do we see a need to maintain this class that
> will no longer be used by any current code? Or, an other words, is there a
> strong possibility that in the future we will want multiple transactions to
> share a single Hyracks job, meaning that it is worth figuring out how to
> maintain this class?
> 
> Steven