@Tarush, you're very welcome to join the effort.

On Thu, Apr 6, 2017 at 7:22 AM, tarush grover <tarushappt...@gmail.com>
wrote:

> Hi,
>
> Can I be also part of this feature development.
>
> Regards,
> Tarush Grover
>
> On Thu, Apr 6, 2017 at 3:17 AM, Ted Yu <yuzhih...@gmail.com> wrote:
>
> > I compiled BEAM-301 branch with calcite 1.12 - passed.
> >
> > Julian tries to not break existing things, but he will if there's a
> reason
> > to do so :-)
> >
> > On Wed, Apr 5, 2017 at 2:36 PM, Mingmin Xu <mingm...@gmail.com> wrote:
> >
> > > @Ted, thanks for the note. I intend to stick with one version, Beam
> 0.6.0
> > > and Calcite 1.11 so far, unless impacted by API change. Before it's
> > merged
> > > back to master, will upgrade to the latest version.
> > >
> > > On Wed, Apr 5, 2017 at 2:14 PM, Ted Yu <yuzhih...@gmail.com> wrote:
> > >
> > > > Working in feature branch is good - you may want to periodically sync
> > up
> > > > with master.
> > > >
> > > > I noticed that you are using 1.11.0 of calcite.
> > > > 1.12 is out, FYI
> > > >
> > > > On Wed, Apr 5, 2017 at 2:05 PM, Mingmin Xu <mingm...@gmail.com>
> wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I'm working on https://issues.apache.org/jira/browse/BEAM-301(Add
> a
> > > Beam
> > > > > SQL DSL). The skeleton is already in
> > > > > https://github.com/XuMingmin/beam/tree/BEAM-301, using Java SDK in
> > the
> > > > > back-end. The goal is to provide a SQL interface over Beam, based
> on
> > > > > Calcite, including:
> > > > > 1). a translator to create Beam pipeline from SQL,
> > > > > (SELECT/INSERT/FILTER/GROUP-BY/JOIN/...);
> > > > > 2). an interactive client to submit queries;  (All-SQL mode)
> > > > > 3). a SQL API which reduce the work to create a Pipeline; (Semi-SQL
> > > mode)
> > > > >
> > > > > As we see many folks are interested in this feature, would like to
> > > > create a
> > > > > feature branch to have more involvement.
> > > > > Looking for comments and feedback.
> > > > >
> > > > > Thanks!
> > > > > ----
> > > > > Mingmin
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > ----
> > > Mingmin
> > >
> >
>



-- 
----
Mingmin

Reply via email to