You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@samza.apache.org by Milinda Pathirage <mp...@umail.iu.edu> on 2015/02/16 22:59:19 UTC

Stream SQL for Samza Query Language Guide and Design

Hi Chris and Yi,

Most of the query language definitions  and examples in
https://issues.apache.org/jira/secure/attachment/12690583/StreamSQLforSAMZA-v0.1.docx.docx
(document attached to https://issues.apache.org/jira/browse/SAMZA-390) are
no longer valid because we moved to extended SQL  supported in Calcite. So
we need to change the document to reflect the changes.

Also I found that, having a document with several basic stream SQL samples
will be useful when developing the query planning and physical plan
generation logic.

How about moving above document to a wiki page or somewhere we can do
shared editing?

Thanks
Milinda

-- 
Milinda Pathirage

PhD Student | Research Assistant
School of Informatics and Computing | Data to Insight Center
Indiana University

twitter: milindalakmal
skype: milinda.pathirage
blog: http://milinda.pathirage.org

Re: Stream SQL for Samza Query Language Guide and Design

Posted by Chris Riccomini <cr...@apache.org>.
Hey all,

Just closing the loop on this. I've migrated the wiki to:

  https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza

The website has been updated accordingly.

Cheers,
Chris

On Wed, Feb 18, 2015 at 2:45 PM, Chris Riccomini <cr...@apache.org>
wrote:

> Hey all,
>
> I've setup a request with INFRA to migrate to CWiki:
>
> https://issues.apache.org/jira/browse/INFRA-9176
>
> Cheers,
> Chris
>
> On Tue, Feb 17, 2015 at 9:57 AM, Yi Pan <ni...@gmail.com> wrote:
>
>> I shared the same pain with wiki before. Either cwiki or Markdown sounds
>> good to me.
>>
>> -Yi
>>
>> On Tue, Feb 17, 2015 at 9:53 AM, Chris Riccomini <cr...@apache.org>
>> wrote:
>>
>> > Hey Milinda,
>> >
>> > Yea, I agree. Confluence is better than Moin Moin. If others agree, I
>> think
>> > we should just switch to Confluence.
>> >
>> > So, shall we block on Wiki upgrade? Probably will take a couple of days.
>> > What do others thing about migrating to Confluence for wiki?
>> >
>> > Cheers,
>> > Chris
>> >
>> > On Tue, Feb 17, 2015 at 9:48 AM, Milinda Pathirage <
>> mpathira@umail.iu.edu>
>> > wrote:
>> >
>> > > Hi Chris,
>> > >
>> > > I am okay with Markdown.
>> > >
>> > > But we have the option of using cwiki (https://cwiki.apache.org). I
>> have
>> > > used it in the past for Axis project. It's pretty flexible, with
>> respect
>> > to
>> > > user management and I think its better than wiki deployed at
>> > > wiki.apache.org.
>> > > For an example, you can give permission to a user who is not a
>> committer
>> > > (of the project that owns the space) to edit certain pages in a space
>> > (Each
>> > > project can have its own space). Also it has commenting.
>> > >
>> > > On the other hand, JIRA may be  better  because we can track
>> everything
>> > in
>> > > a single place.
>> > >
>> > > Thanks
>> > > Milinda
>> > >
>> > >
>> > >
>> > > On Tue, Feb 17, 2015 at 12:16 PM, Chris Riccomini <
>> criccomini@apache.org
>> > >
>> > > wrote:
>> > >
>> > > > Hey Milinda,
>> > > >
>> > > > We can do wiki, but Apache's wiki is pretty locked down, sadly.
>> You'll
>> > > have
>> > > > to get an account for it.
>> > > >
>> > > > What if we just convert it to Markdown (like SAMZA-516), and attach
>> to
>> > > the
>> > > > patch? This will make it versioned, and editable. Comments can
>> happen
>> > in
>> > > > the JIRA. I'm OK either way, but the wiki has been a little
>> cumbersome
>> > in
>> > > > the past.
>> > > >
>> > > > Cheers,
>> > > > Chris
>> > > >
>> > > > On Mon, Feb 16, 2015 at 1:59 PM, Milinda Pathirage <
>> > > mpathira@umail.iu.edu>
>> > > > wrote:
>> > > >
>> > > > > Hi Chris and Yi,
>> > > > >
>> > > > > Most of the query language definitions  and examples in
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/attachment/12690583/StreamSQLforSAMZA-v0.1.docx.docx
>> > > > > (document attached to
>> > https://issues.apache.org/jira/browse/SAMZA-390)
>> > > > are
>> > > > > no longer valid because we moved to extended SQL  supported in
>> > Calcite.
>> > > > So
>> > > > > we need to change the document to reflect the changes.
>> > > > >
>> > > > > Also I found that, having a document with several basic stream SQL
>> > > > samples
>> > > > > will be useful when developing the query planning and physical
>> plan
>> > > > > generation logic.
>> > > > >
>> > > > > How about moving above document to a wiki page or somewhere we
>> can do
>> > > > > shared editing?
>> > > > >
>> > > > > Thanks
>> > > > > Milinda
>> > > > >
>> > > > > --
>> > > > > Milinda Pathirage
>> > > > >
>> > > > > PhD Student | Research Assistant
>> > > > > School of Informatics and Computing | Data to Insight Center
>> > > > > Indiana University
>> > > > >
>> > > > > twitter: milindalakmal
>> > > > > skype: milinda.pathirage
>> > > > > blog: http://milinda.pathirage.org
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Milinda Pathirage
>> > >
>> > > PhD Student | Research Assistant
>> > > School of Informatics and Computing | Data to Insight Center
>> > > Indiana University
>> > >
>> > > twitter: milindalakmal
>> > > skype: milinda.pathirage
>> > > blog: http://milinda.pathirage.org
>> > >
>> >
>>
>
>

Re: Stream SQL for Samza Query Language Guide and Design

Posted by Chris Riccomini <cr...@apache.org>.
Hey all,

I've setup a request with INFRA to migrate to CWiki:

https://issues.apache.org/jira/browse/INFRA-9176

Cheers,
Chris

On Tue, Feb 17, 2015 at 9:57 AM, Yi Pan <ni...@gmail.com> wrote:

> I shared the same pain with wiki before. Either cwiki or Markdown sounds
> good to me.
>
> -Yi
>
> On Tue, Feb 17, 2015 at 9:53 AM, Chris Riccomini <cr...@apache.org>
> wrote:
>
> > Hey Milinda,
> >
> > Yea, I agree. Confluence is better than Moin Moin. If others agree, I
> think
> > we should just switch to Confluence.
> >
> > So, shall we block on Wiki upgrade? Probably will take a couple of days.
> > What do others thing about migrating to Confluence for wiki?
> >
> > Cheers,
> > Chris
> >
> > On Tue, Feb 17, 2015 at 9:48 AM, Milinda Pathirage <
> mpathira@umail.iu.edu>
> > wrote:
> >
> > > Hi Chris,
> > >
> > > I am okay with Markdown.
> > >
> > > But we have the option of using cwiki (https://cwiki.apache.org). I
> have
> > > used it in the past for Axis project. It's pretty flexible, with
> respect
> > to
> > > user management and I think its better than wiki deployed at
> > > wiki.apache.org.
> > > For an example, you can give permission to a user who is not a
> committer
> > > (of the project that owns the space) to edit certain pages in a space
> > (Each
> > > project can have its own space). Also it has commenting.
> > >
> > > On the other hand, JIRA may be  better  because we can track everything
> > in
> > > a single place.
> > >
> > > Thanks
> > > Milinda
> > >
> > >
> > >
> > > On Tue, Feb 17, 2015 at 12:16 PM, Chris Riccomini <
> criccomini@apache.org
> > >
> > > wrote:
> > >
> > > > Hey Milinda,
> > > >
> > > > We can do wiki, but Apache's wiki is pretty locked down, sadly.
> You'll
> > > have
> > > > to get an account for it.
> > > >
> > > > What if we just convert it to Markdown (like SAMZA-516), and attach
> to
> > > the
> > > > patch? This will make it versioned, and editable. Comments can happen
> > in
> > > > the JIRA. I'm OK either way, but the wiki has been a little
> cumbersome
> > in
> > > > the past.
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > > > On Mon, Feb 16, 2015 at 1:59 PM, Milinda Pathirage <
> > > mpathira@umail.iu.edu>
> > > > wrote:
> > > >
> > > > > Hi Chris and Yi,
> > > > >
> > > > > Most of the query language definitions  and examples in
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/attachment/12690583/StreamSQLforSAMZA-v0.1.docx.docx
> > > > > (document attached to
> > https://issues.apache.org/jira/browse/SAMZA-390)
> > > > are
> > > > > no longer valid because we moved to extended SQL  supported in
> > Calcite.
> > > > So
> > > > > we need to change the document to reflect the changes.
> > > > >
> > > > > Also I found that, having a document with several basic stream SQL
> > > > samples
> > > > > will be useful when developing the query planning and physical plan
> > > > > generation logic.
> > > > >
> > > > > How about moving above document to a wiki page or somewhere we can
> do
> > > > > shared editing?
> > > > >
> > > > > Thanks
> > > > > Milinda
> > > > >
> > > > > --
> > > > > Milinda Pathirage
> > > > >
> > > > > PhD Student | Research Assistant
> > > > > School of Informatics and Computing | Data to Insight Center
> > > > > Indiana University
> > > > >
> > > > > twitter: milindalakmal
> > > > > skype: milinda.pathirage
> > > > > blog: http://milinda.pathirage.org
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Milinda Pathirage
> > >
> > > PhD Student | Research Assistant
> > > School of Informatics and Computing | Data to Insight Center
> > > Indiana University
> > >
> > > twitter: milindalakmal
> > > skype: milinda.pathirage
> > > blog: http://milinda.pathirage.org
> > >
> >
>

Re: Stream SQL for Samza Query Language Guide and Design

Posted by Yi Pan <ni...@gmail.com>.
I shared the same pain with wiki before. Either cwiki or Markdown sounds
good to me.

-Yi

On Tue, Feb 17, 2015 at 9:53 AM, Chris Riccomini <cr...@apache.org>
wrote:

> Hey Milinda,
>
> Yea, I agree. Confluence is better than Moin Moin. If others agree, I think
> we should just switch to Confluence.
>
> So, shall we block on Wiki upgrade? Probably will take a couple of days.
> What do others thing about migrating to Confluence for wiki?
>
> Cheers,
> Chris
>
> On Tue, Feb 17, 2015 at 9:48 AM, Milinda Pathirage <mp...@umail.iu.edu>
> wrote:
>
> > Hi Chris,
> >
> > I am okay with Markdown.
> >
> > But we have the option of using cwiki (https://cwiki.apache.org). I have
> > used it in the past for Axis project. It's pretty flexible, with respect
> to
> > user management and I think its better than wiki deployed at
> > wiki.apache.org.
> > For an example, you can give permission to a user who is not a committer
> > (of the project that owns the space) to edit certain pages in a space
> (Each
> > project can have its own space). Also it has commenting.
> >
> > On the other hand, JIRA may be  better  because we can track everything
> in
> > a single place.
> >
> > Thanks
> > Milinda
> >
> >
> >
> > On Tue, Feb 17, 2015 at 12:16 PM, Chris Riccomini <criccomini@apache.org
> >
> > wrote:
> >
> > > Hey Milinda,
> > >
> > > We can do wiki, but Apache's wiki is pretty locked down, sadly. You'll
> > have
> > > to get an account for it.
> > >
> > > What if we just convert it to Markdown (like SAMZA-516), and attach to
> > the
> > > patch? This will make it versioned, and editable. Comments can happen
> in
> > > the JIRA. I'm OK either way, but the wiki has been a little cumbersome
> in
> > > the past.
> > >
> > > Cheers,
> > > Chris
> > >
> > > On Mon, Feb 16, 2015 at 1:59 PM, Milinda Pathirage <
> > mpathira@umail.iu.edu>
> > > wrote:
> > >
> > > > Hi Chris and Yi,
> > > >
> > > > Most of the query language definitions  and examples in
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/attachment/12690583/StreamSQLforSAMZA-v0.1.docx.docx
> > > > (document attached to
> https://issues.apache.org/jira/browse/SAMZA-390)
> > > are
> > > > no longer valid because we moved to extended SQL  supported in
> Calcite.
> > > So
> > > > we need to change the document to reflect the changes.
> > > >
> > > > Also I found that, having a document with several basic stream SQL
> > > samples
> > > > will be useful when developing the query planning and physical plan
> > > > generation logic.
> > > >
> > > > How about moving above document to a wiki page or somewhere we can do
> > > > shared editing?
> > > >
> > > > Thanks
> > > > Milinda
> > > >
> > > > --
> > > > Milinda Pathirage
> > > >
> > > > PhD Student | Research Assistant
> > > > School of Informatics and Computing | Data to Insight Center
> > > > Indiana University
> > > >
> > > > twitter: milindalakmal
> > > > skype: milinda.pathirage
> > > > blog: http://milinda.pathirage.org
> > > >
> > >
> >
> >
> >
> > --
> > Milinda Pathirage
> >
> > PhD Student | Research Assistant
> > School of Informatics and Computing | Data to Insight Center
> > Indiana University
> >
> > twitter: milindalakmal
> > skype: milinda.pathirage
> > blog: http://milinda.pathirage.org
> >
>

Re: Stream SQL for Samza Query Language Guide and Design

Posted by Chris Riccomini <cr...@apache.org>.
Hey Milinda,

Yea, I agree. Confluence is better than Moin Moin. If others agree, I think
we should just switch to Confluence.

So, shall we block on Wiki upgrade? Probably will take a couple of days.
What do others thing about migrating to Confluence for wiki?

Cheers,
Chris

On Tue, Feb 17, 2015 at 9:48 AM, Milinda Pathirage <mp...@umail.iu.edu>
wrote:

> Hi Chris,
>
> I am okay with Markdown.
>
> But we have the option of using cwiki (https://cwiki.apache.org). I have
> used it in the past for Axis project. It's pretty flexible, with respect to
> user management and I think its better than wiki deployed at
> wiki.apache.org.
> For an example, you can give permission to a user who is not a committer
> (of the project that owns the space) to edit certain pages in a space (Each
> project can have its own space). Also it has commenting.
>
> On the other hand, JIRA may be  better  because we can track everything in
> a single place.
>
> Thanks
> Milinda
>
>
>
> On Tue, Feb 17, 2015 at 12:16 PM, Chris Riccomini <cr...@apache.org>
> wrote:
>
> > Hey Milinda,
> >
> > We can do wiki, but Apache's wiki is pretty locked down, sadly. You'll
> have
> > to get an account for it.
> >
> > What if we just convert it to Markdown (like SAMZA-516), and attach to
> the
> > patch? This will make it versioned, and editable. Comments can happen in
> > the JIRA. I'm OK either way, but the wiki has been a little cumbersome in
> > the past.
> >
> > Cheers,
> > Chris
> >
> > On Mon, Feb 16, 2015 at 1:59 PM, Milinda Pathirage <
> mpathira@umail.iu.edu>
> > wrote:
> >
> > > Hi Chris and Yi,
> > >
> > > Most of the query language definitions  and examples in
> > >
> > >
> >
> https://issues.apache.org/jira/secure/attachment/12690583/StreamSQLforSAMZA-v0.1.docx.docx
> > > (document attached to https://issues.apache.org/jira/browse/SAMZA-390)
> > are
> > > no longer valid because we moved to extended SQL  supported in Calcite.
> > So
> > > we need to change the document to reflect the changes.
> > >
> > > Also I found that, having a document with several basic stream SQL
> > samples
> > > will be useful when developing the query planning and physical plan
> > > generation logic.
> > >
> > > How about moving above document to a wiki page or somewhere we can do
> > > shared editing?
> > >
> > > Thanks
> > > Milinda
> > >
> > > --
> > > Milinda Pathirage
> > >
> > > PhD Student | Research Assistant
> > > School of Informatics and Computing | Data to Insight Center
> > > Indiana University
> > >
> > > twitter: milindalakmal
> > > skype: milinda.pathirage
> > > blog: http://milinda.pathirage.org
> > >
> >
>
>
>
> --
> Milinda Pathirage
>
> PhD Student | Research Assistant
> School of Informatics and Computing | Data to Insight Center
> Indiana University
>
> twitter: milindalakmal
> skype: milinda.pathirage
> blog: http://milinda.pathirage.org
>

Re: Stream SQL for Samza Query Language Guide and Design

Posted by Milinda Pathirage <mp...@umail.iu.edu>.
Hi Chris,

I am okay with Markdown.

But we have the option of using cwiki (https://cwiki.apache.org). I have
used it in the past for Axis project. It's pretty flexible, with respect to
user management and I think its better than wiki deployed at wiki.apache.org.
For an example, you can give permission to a user who is not a committer
(of the project that owns the space) to edit certain pages in a space (Each
project can have its own space). Also it has commenting.

On the other hand, JIRA may be  better  because we can track everything in
a single place.

Thanks
Milinda



On Tue, Feb 17, 2015 at 12:16 PM, Chris Riccomini <cr...@apache.org>
wrote:

> Hey Milinda,
>
> We can do wiki, but Apache's wiki is pretty locked down, sadly. You'll have
> to get an account for it.
>
> What if we just convert it to Markdown (like SAMZA-516), and attach to the
> patch? This will make it versioned, and editable. Comments can happen in
> the JIRA. I'm OK either way, but the wiki has been a little cumbersome in
> the past.
>
> Cheers,
> Chris
>
> On Mon, Feb 16, 2015 at 1:59 PM, Milinda Pathirage <mp...@umail.iu.edu>
> wrote:
>
> > Hi Chris and Yi,
> >
> > Most of the query language definitions  and examples in
> >
> >
> https://issues.apache.org/jira/secure/attachment/12690583/StreamSQLforSAMZA-v0.1.docx.docx
> > (document attached to https://issues.apache.org/jira/browse/SAMZA-390)
> are
> > no longer valid because we moved to extended SQL  supported in Calcite.
> So
> > we need to change the document to reflect the changes.
> >
> > Also I found that, having a document with several basic stream SQL
> samples
> > will be useful when developing the query planning and physical plan
> > generation logic.
> >
> > How about moving above document to a wiki page or somewhere we can do
> > shared editing?
> >
> > Thanks
> > Milinda
> >
> > --
> > Milinda Pathirage
> >
> > PhD Student | Research Assistant
> > School of Informatics and Computing | Data to Insight Center
> > Indiana University
> >
> > twitter: milindalakmal
> > skype: milinda.pathirage
> > blog: http://milinda.pathirage.org
> >
>



-- 
Milinda Pathirage

PhD Student | Research Assistant
School of Informatics and Computing | Data to Insight Center
Indiana University

twitter: milindalakmal
skype: milinda.pathirage
blog: http://milinda.pathirage.org

Re: Stream SQL for Samza Query Language Guide and Design

Posted by Chris Riccomini <cr...@apache.org>.
Hey Milinda,

We can do wiki, but Apache's wiki is pretty locked down, sadly. You'll have
to get an account for it.

What if we just convert it to Markdown (like SAMZA-516), and attach to the
patch? This will make it versioned, and editable. Comments can happen in
the JIRA. I'm OK either way, but the wiki has been a little cumbersome in
the past.

Cheers,
Chris

On Mon, Feb 16, 2015 at 1:59 PM, Milinda Pathirage <mp...@umail.iu.edu>
wrote:

> Hi Chris and Yi,
>
> Most of the query language definitions  and examples in
>
> https://issues.apache.org/jira/secure/attachment/12690583/StreamSQLforSAMZA-v0.1.docx.docx
> (document attached to https://issues.apache.org/jira/browse/SAMZA-390) are
> no longer valid because we moved to extended SQL  supported in Calcite. So
> we need to change the document to reflect the changes.
>
> Also I found that, having a document with several basic stream SQL samples
> will be useful when developing the query planning and physical plan
> generation logic.
>
> How about moving above document to a wiki page or somewhere we can do
> shared editing?
>
> Thanks
> Milinda
>
> --
> Milinda Pathirage
>
> PhD Student | Research Assistant
> School of Informatics and Computing | Data to Insight Center
> Indiana University
>
> twitter: milindalakmal
> skype: milinda.pathirage
> blog: http://milinda.pathirage.org
>