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: <CAOi1F6Uy0br5Q=6GJcjvqbW0Yb38W2NyxaxoWe8N4VQDiLe0XQ@mail.gmail.com>
References: <CAOi1F6Uy0br5Q=6GJcjvqbW0Yb38W2NyxaxoWe8N4VQDiLe0XQ@mail.gmail.com>
From: Chinmay Kolhatkar <chinmay@apache.org>
Date: Thu, 20 Oct 2016 22:23:06 +0530
Message-ID: <CABAipVaByh=WdxLuTk1srj_4vb=G1YYfTsUVfAz7ipHL6YjRZw@mail.gmail.com>
Subject: Re: Make cli support high-level API and SQL
To: dev@apex.apache.org
Content-Type: multipart/alternative; boundary=001a113d4f2887bc1d053f4ec23c
archived-at: Thu, 20 Oct 2016 16:53:10 -0000

--001a113d4f2887bc1d053f4ec23c
Content-Type: text/plain; charset=UTF-8

Are you talking about apex cli (the one present in apex-core) to support
both?

As both high-level API and SQL are in malhar, wouldn't there be circular
dependency issue?

Beside the possible issues, this is a great idea.

Though, I'll suggest to have a seperate cli for high level and SQL in
malhar itself first and then later make that loadable/callable from apexcli.


On Thu, Oct 20, 2016 at 10:19 PM, Siyuan Hua <siyuan@datatorrent.com> wrote:

> Given we already have first version of high-level API and SQL PR is getting
> close to be merged. And also we have ability to launch application
> grammatically. I think it's nice to have our cli support both high-level
> API and SQL directly so people can simply prototype what they need and/or
> try out Apex with more flexibility.
>
> Any thoughts?
>
>
> Regards,
> Siyuan
>

--001a113d4f2887bc1d053f4ec23c--