Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
MIME-Version: 1.0
In-Reply-To: <CAD0KA=N+0vzJtxhvJzoW5tmiDfA4xVipBDQq6R5qR5ssgD+bEw@mail.gmail.com>
References: <CAD0KA=N+0vzJtxhvJzoW5tmiDfA4xVipBDQq6R5qR5ssgD+bEw@mail.gmail.com>
From: Tushar Gosavi <tushar@datatorrent.com>
Date: Tue, 17 Jan 2017 09:10:15 +0530
Message-ID: <CAD0KA=N1V_rCJnaap8bVo_-bQb8YV=CYh4KHk4rNsKn6OW7VAw@mail.gmail.com>
Subject: Re: Extending DAG API for accessing objects in DAG.
To: dev@apex.apache.org
Content-Type: text/plain; charset=UTF-8
archived-at: Tue, 17 Jan 2017 03:40:21 -0000

I have opened https://issues.apache.org/jira/browse/APEXCORE-604 for this.
If there is no objection I will open an pull request for it.

- Tushar.


On Mon, Jan 9, 2017 at 4:44 PM, Tushar Gosavi <tushar@datatorrent.com> wrote:
> Hi All,
>
> I am planing extend the DAG api to export internals of the DAG.
> Current DAG does not provide a way to get the list of operators and
> streams with their attributes. Also streamMeta does not provide
> API to access end ports.
>
> This type of information is needed when external translator (like
> Samoa) are constructing the DAG,
> and we need to apply some transformation or configure the DAG before
> it is run. Planing to extend
> DAG API with following.
>
> InputPortMeta
>     public Operator.InputPort<?> getPortObject();
> OutputPortMeta
>     public Operator.OutputPort<?> getPortObject();
> streamMeta
>     public <T extends OutputPortMeta> T getSource();
>     public <T extends InputPortMeta> Collection<T> getSinks();
> DAG
>     public abstract <T extends OperatorMeta> Collection<T> getOperators();
>     public abstract <T extends StreamMeta> Collection<T> getStreams();
>
> Regards,
> - Tushar.