Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <D28F1169.4730%brennon.york@capitalone.com>
References: <D28F1169.4730%brennon.york@capitalone.com>
Date: Thu, 10 Dec 2015 11:32:33 -0800
Message-ID: 
 <CAKaBFBm=0VfL8TKC_9A76RSCFuTKv7qGatJNe7RpJN06-6TVcA@mail.gmail.com>
Subject: Re: Stateful vs Stateless Operators
From: Chandni Singh <chandni@datatorrent.com>
To: dev@apex.incubator.apache.org
Content-Type: multipart/alternative; boundary=089e0168199ebbdb5905269044b3

--089e0168199ebbdb5905269044b3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The @Stateless attribute is not @Inherited.

http://docs.oracle.com/javase/7/docs/api/java/lang/annotation/Inherited.htm=
l

This means that B (if not annotated with Stateless) will be considered
stateful.

Chandni


On Thu, Dec 10, 2015 at 11:24 AM, York, Brennon <Brennon.York@capitalone.co=
m
> wrote:

> How does stateful vs stateless operation work with operators implementing
> a base class? For example, if I have operator A as an abstract class and
> marked as @Stateless, but then have operator B implement operator A and B
> is not stateless, what will the system do? Does it always take the
> implementing operator=E2=80=99s stateful vs stateless determination, does=
 it take
> the base class, something else? Trying to understand and didn=E2=80=99t f=
ind any
> info on it at docs.datatorrent.com or in the codebase.
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The informatio=
n
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intend=
ed
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>

--089e0168199ebbdb5905269044b3--