Re: Podling Report Reminder - June 2017

[Jignesh Patel]

I’ve been thinking of other ways to get the word out. 

There are few current and ex-Wisconsin folks in the Bay area this summer. 

Question for all: Are there any forums in the Bay area that may be good to 
think about presenting this summer? IMHO, it would also be good to target 
specific meetups and companies that might be potential synergistic partners.

I can prepare the slides.

Any Bay area residents who want to volunteer to give a talk? I think I can find 
$s for incidental reimbursements and conference costs (if they are not 
outrageously high).

Cheers,
Jignesh 

On 6/1/17, 10:28 AM, "Julian Hyde"  wrote:

Quickstep community,

Now we have a first release, it is clear to me — and I hope to you — that 
the big challenge for Quickstep is growing a community outside of Madison. I 
think we need to come up with a plan to address this so that it can be in this 
quarter’s report, and we can measure progress at the time of the next quarterly 
report. What do you think?

Julian

> On Jun 1, 2017, at 4:43 AM, johndam...@apache.org wrote:
> 
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 21 June 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 07).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/June2017
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC

Re: Podling Report Reminder - June 2017

[Jignesh Patel]

A starting point for the podling report is now at: 
https://wiki.apache.org/incubator/June2017#preview. Feel free to make any 
changes or suggest them. 

Cheers,
Jignesh 

On 6/1/17, 6:43 AM, "johndam...@apache.org"  wrote:

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 21 June 2017, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 07).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/June2017

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Report Reminder - June 2017

[Jignesh Patel]

Good idea Julian! Would love to get your suggestions. We do have some folks 
from Quickstep graduate recently, and they may continue to be involved. So, 
that could be one of the steps. 

I think a good way to get a community is if we can find someone to adopt the 
technology and actually use it. Anyone has ideas on partners that might be a 
good fit for this? We can then think of making a visit and giving an talk to 
explore this fit. 

Other ideas are also welcome – this is a hard issue!

Cheers,
Jignesh 

On 6/1/17, 10:28 AM, "Julian Hyde"  wrote:

Quickstep community,

Now we have a first release, it is clear to me — and I hope to you — that 
the big challenge for Quickstep is growing a community outside of Madison. I 
think we need to come up with a plan to address this so that it can be in this 
quarter’s report, and we can measure progress at the time of the next quarterly 
report. What do you think?

Julian

> On Jun 1, 2017, at 4:43 AM, johndam...@apache.org wrote:
> 
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 21 June 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 07).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/June2017
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC

New Committer: Tianrun Li

[Jignesh Patel]

The Project Management Committee (PMC) for Apache (incubating) Qucikstep

has invited Tianrun Li to become a committer and we are pleased 

to announce that he has accepted.

 

Welcome Tianrun! 

 

Being a committer enables easier contribution to the

project since there is no need to go via the patch

submission process. This should enable better productivity.

Being a PMC member enables assistance with the management

and to guide the direction of the project.

 

Cheers,

Jignesh 

Re: [VOTE] Apache Incubating Quickstep 0.1.0 RC7

[Jignesh Patel]

+1 from me too. 

Cheers,
Jignesh

On 3/21/17, 6:27 PM, "Julian Hyde"  wrote:

+1 (binding)

Downloaded, checked hashes, checked L, disclaimer, ran rat.

For next release, please add headers on all .md, .git*, .sh and .patch 
files. That will reduce the number of rat exceptions.

Julian


> On Mar 20, 2017, at 9:42 AM, Harshad Deshmukh  wrote:
> 
> +1 from me.
> 
> Apart from release metadata:
> 
> Build passes on Ubuntu 14.04 using gcc 4.9.4
> 
> All tests pass.
> 
> No style issues.
> 
> Thanks Marc for putting together RC7!
> 
> 
> On 03/20/2017 10:26 AM, Josh Elser wrote:
>> +1
>> 
>> * Verified commits since rc6
>> * sigs/xsums still OK
>> 
>> For your $release.next:
>>  - gflags still listed in LICENSE unnecessarily (I don't see it bundled)
>> 
>> Thanks for including sha256/512 hashes as well!
>> 
>> - Josh
>> 
>> On 2017-03-19 18:57 (-0400), Marc Spehlmann  
wrote:
>>> This vote is for approval of the Quickstep-0.1.0 RC7.
>>> 
>>> We had a few minor changes since RC6. They were changes to the LICENSE 
and
>>> NOTICE
>>> file, as well as updating some headers. These should not have made
>>> functional changes.
>>> 
>>> Voters should download, unpack, build, and test the package before 
voting.
>>> 
>>> A +1 vote means that the package passes all tests and meets Apache
>>> guidelines.
>>> A -1 vote should be accompanied with a short reason.
>>> 
>>> Votes will remain open for 2 days in light of this being a very similar
>>> candidate
>>> to the last one.
>>> 
>>> ___
>>> 
>>> The commit to be voted upon:
>>> 
https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep.git;a=shortlog;h=refs/tags/v0.1.0-rc7
 
>>> 
>>> The artifacts to be voted on are located here:
>>> https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC7/
>>> 
>>> Release artifacts are signed with the following key:
>>> https://people.apache.org/keys/committer/spehl
>>> 
>>> Please vote on releasing this package as Apache Incubating Quickstep 
0.1.0.
>>> 
> 
> -- 
> Thanks,
> Harshad
> 

Re: [VOTE] Apache Incubating Quickstep 0.1.0 RC7

[Jignesh Patel]

+1 from me. 



On 3/19/17, 5:57 PM, "Marc Spehlmann"  wrote:

This vote is for approval of the Quickstep-0.1.0 RC7.

We had a few minor changes since RC6. They were changes to the LICENSE and
NOTICE
file, as well as updating some headers. These should not have made
functional changes.

Voters should download, unpack, build, and test the package before voting.

A +1 vote means that the package passes all tests and meets Apache
guidelines.
A -1 vote should be accompanied with a short reason.

Votes will remain open for 2 days in light of this being a very similar
candidate
to the last one.

___

The commit to be voted upon:

https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep.git;a=shortlog;h=refs/tags/v0.1.0-rc7

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC7/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/spehl

Please vote on releasing this package as Apache Incubating Quickstep 0.1.0.

Re: tmb compile error

[Jignesh Patel]

Sadly TMB is not optional ☹ 

On 3/6/17, 4:17 PM, "Marc Spehlmann"  wrote:

Hi all,
Anyone know if tmb is an optional component? I was putting together release
artifacts for 0.1.0rc6 and got this compile warn->error on an ubuntu
machine. It seems that a variable which was previously used is no longer
used.

tmb is a third party library. Zuyu, you mentioned it would be better to
turn off warning->error flags for third party. What do you think would be
prudent in this case?

compiler:
cxxdev@e1428abc6dae:~/incubator-quickstep/build$ cc --version
cc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

error:
[ 13%] Building CXX object
third_party/tmb/CMakeFiles/tmb.dir/src/message_bus.cc.o

/home/cxxdev/incubator-quickstep/release/svn-quickstep-dev/0.1.0/RC6/apache-quickstep-incubating-0.1.0/third_party/src/tmb/src/message_bus.cc:43:19:
error: ‘tmb::tmb_receive_poll_interval_dummy’ defined but not used
[-Werror=unused-variable]
 static const bool tmb_receive_poll_interval_dummy =
gflags::RegisterFlagValidator(
   ^
cc1plus: error: unrecognized command line option
‘-Wno-return-type-c-linkage’ [-Werror]
cc1plus: all warnings being treated as errors
third_party/tmb/CMakeFiles/tmb.dir/build.make:62: recipe for target
'third_party/tmb/CMakeFiles/tmb.dir/src/message_bus.cc.o' failed
make[2]: *** [third_party/tmb/CMakeFiles/tmb.dir/src/message_bus.cc.o]
Error 1
CMakeFiles/Makefile2:1172: recipe for target
'third_party/tmb/CMakeFiles/tmb.dir/all' failed
make[1]: *** [third_party/tmb/CMakeFiles/tmb.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

Re: Podling Report - Seeking feedback

[Jignesh Patel]

Thanks Roman and Julian. 

Huge thank you to Harshad for taking the lead on peparing this podling report!

Cheers,
Jignesh 

On 3/3/17, 7:54 PM, "Roman Shaposhnik" <shaposh...@gmail.com on behalf of 
ro...@shaposhnik.org> wrote:

Signed off as well!

On Fri, Mar 3, 2017 at 4:21 PM, Julian Hyde <jh...@apache.org> wrote:
> Thanks for writing the report.
>
> I replaced #3 with "No releases so far." and signed off.
>
> Julian
>
>
>
> On Fri, Mar 3, 2017 at 12:31 PM, Roman Shaposhnik <ro...@shaposhnik.org> 
wrote:
>> I still think that #3 on the graduation blockers list should be "Lack
>> of releases so far"
>>
>> If there's no disagreement -- I'll change it.
>>
>> Thanks,
>> Roman.
>>
>> On Thu, Mar 2, 2017 at 5:44 PM, Jignesh Patel <jmp.quicks...@gmail.com> 
wrote:
>>> Thanks Harshad for taking the lead on this!
>>>
>>> I have also uploaded this on: 
https://wiki.apache.org/incubator/March2017. We can make changes to the wiki if 
there is feedback from the mentors. Let us know.
>>>
>>> Cheers,
>>> Jignesh
>>>
>>> On 3/2/17, 5:36 PM, "Harshad Deshmukh" <hars...@cs.wisc.edu> wrote:
>>>
>>> Hello mentors,
>>>
>>> May I request you to review the following podling report? Thanks for
>>> your time.
>>>
>>> *   Your project name
>>> Apache (incubating) Quickstep
>>>
>>> *   A brief description of your project, which assumes no knowledge 
of
>>>  the project or necessarily of its field
>>> Apache Quickstep is high-performance database engine designed to 
exploit
>>> the full potential
>>> of hardware that is packed in modern computing boxes (servers and 
laptops).
>>> The initial version targets single-node in-memory environments.
>>>
>>> *   A list of the three most important issues to address in the move
>>>  towards graduation.
>>> 1) Building a Quickstep community
>>> 2) More adoption of the Quickstep technology
>>> 3) Making the technology easier to understand and use
>>>
>>> *   Any issues that the Incubator PMC or ASF Board might wish/need 
to be
>>>  aware of
>>> None
>>>
>>> *   How has the community developed since the last report
>>>
>>> Members of the community have become more aware about the release 
process.
>>>
>>> The details about the release process are well documented so that 
future
>>> releases will be smooth and more frequent.
>>>
>>> *   How has the project developed since the last report.
>>>
>>> We will have our first release this month. Since the last report,
>>>
>>> 1) We have made several changes to the code base.
>>> Some highlights are: Cleaning up the third party library code as 
per the
>>> Apache hygiene, improve the code performance by adding several novel
>>> features.
>>>
>>> 2) Preparation for release -
>>> Created scripts and step by step procedural documentation for how to
>>> make a Quickstep release.
>>>
>>> Scripts have been added to the main repo while documentation is on
>>> confluence.
>>>
>>> We went through several release candidates.
>>>
>>> During this period, we identified some usability issues on our 
supported
>>> platforms and fixed them.
>>>
>>> *   How does the podling rate their own maturity.
>>>
>>> Preparation for the first release is under way and the release is
>>> expected to happen in this month.
>>>
>>> --
>>>
>>> Thanks,
>>> Harshad
>>>
>>>
>>>
>>>

Re: Podling Report - Seeking feedback

[Jignesh Patel]

Thanks Harshad for taking the lead on this!

I have also uploaded this on: https://wiki.apache.org/incubator/March2017. We 
can make changes to the wiki if there is feedback from the mentors. Let us know.

Cheers,
Jignesh 

On 3/2/17, 5:36 PM, "Harshad Deshmukh"  wrote:

Hello mentors,

May I request you to review the following podling report? Thanks for 
your time.

*   Your project name
Apache (incubating) Quickstep

*   A brief description of your project, which assumes no knowledge of
 the project or necessarily of its field
Apache Quickstep is high-performance database engine designed to exploit 
the full potential
of hardware that is packed in modern computing boxes (servers and laptops).
The initial version targets single-node in-memory environments.

*   A list of the three most important issues to address in the move
 towards graduation.
1) Building a Quickstep community
2) More adoption of the Quickstep technology
3) Making the technology easier to understand and use

*   Any issues that the Incubator PMC or ASF Board might wish/need to be
 aware of
None

*   How has the community developed since the last report

Members of the community have become more aware about the release process.

The details about the release process are well documented so that future 
releases will be smooth and more frequent.

*   How has the project developed since the last report.

We will have our first release this month. Since the last report,

1) We have made several changes to the code base.
Some highlights are: Cleaning up the third party library code as per the 
Apache hygiene, improve the code performance by adding several novel 
features.

2) Preparation for release -
Created scripts and step by step procedural documentation for how to 
make a Quickstep release.

Scripts have been added to the main repo while documentation is on 
confluence.

We went through several release candidates.

During this period, we identified some usability issues on our supported 
platforms and fixed them.

*   How does the podling rate their own maturity.

Preparation for the first release is under way and the release is 
expected to happen in this month.

-- 

Thanks,
Harshad

Re: [VOTE] incubator-quickstep-0.1.0RC5

[Jignesh Patel]

+1 from me!

On 3/1/17, 10:48 PM, "Jianqiao"  wrote:

+1. I'm good with the release.

Best,
Jianqiao

2017-03-01 17:21 GMT-06:00 HAKAN MEMISOGLU :

> Hi Marc,
>
> +1 from me. It works with Docker.
>
> However I also get an error when I try to build it with Mac.
> The linker cannot find some symbols that protoc uses.
>
> > On Mar 1, 2017, at 4:30 PM, Marc Spehlmann 
> wrote:
> >
> > Jianqiao and I worked today to merge some PRs that we thought should go
> in
> > the first release. Accordingly we have created another candidate.
> >
> > As per Apache, *we require 3 +1 votes* from project members to make this
> an
> > official release.
> >
> > Before voting, please test the release (build, run ctest). For a guide 
on
> > how to test, GOTO release/README.md
> >
> > This vote will remain open for 72 hours or until we find issues that we
> can
> > quickly correct and create another candidate.
> >
> > more details on
> >
> > https://cwiki.apache.org/confluence/display/QUICKSTEP/How+To+Release
> >
> > --Marc
>
>

Re: Release Managers?

[Jignesh Patel]

Thanks Julian for answers to both questions! 

Cheers,
Jignesh 

On 2/12/17, 12:39 AM, "Julian Hyde" <jhyde.apa...@gmail.com> wrote:

I don't know whether it's even possible for more than one person to sign 
the release.

The way to make the release more "trustworthy" is to strengthen the release 
manager's web of trust. Have a key signing party [1] and sign each other's 
keys. 

If the one person who signs the release is well established in the Apache 
web of trust then the release is clearly a genuine product of the Apache 
Software Foundation. 

Regarding the report. It's possible that you're now scheduled to report 
only once per quarter. Projects are only monthly when they start out. 

Julian

[1] https://en.m.wikipedia.org/wiki/Key_signing_party



Sent from my iPad
> On Feb 11, 2017, at 2:04 PM, Jignesh Patel <jmp.quicks...@gmail.com> 
wrote:
> 
> Hi folks: We are nearly ready to do a release. Anyone else wants to sign 
the release along with me? 
> 
> 
> 
> Also, I haven’t seen an email about providing input for the usual Podling 
report? Anyone else has seen this? I hope I haven’t missed it.
> 
> 
> 
> Cheers,
> 
> Jignesh  
> 

Release Managers?

[Jignesh Patel]

Hi folks: We are nearly ready to do a release. Anyone else wants to sign the 
release along with me? 

 

Also, I haven’t seen an email about providing input for the usual Podling 
report? Anyone else has seen this? I hope I haven’t missed it.

 

Cheers,

Jignesh  

Re: Editing documentation for release: BUILDING.md

[Jignesh Patel]

Marc,

Should we get rid of curl from the build instructions? We don’t need it with 
the current instruction flow. 

Cheers,
Jignesh 

On 2/7/17, 6:43 PM, "Marc Spehlmann"  wrote:

For example, here is the edited doc:

https://github.com/cramja/incubator-quickstep/blob/refactor-building/BUILDING.md#prerequisites

On Tue, Feb 7, 2017 at 6:28 PM, Marc Spehlmann 
wrote:

> Any objections if I remove the 'Getting cmake' section? It seems long, and
> like information that a database programmer would probably already
> know/google and quickly find out.
>
> Instead I can link to cmake's webpage in the prereq section
>
> On Tue, Feb 7, 2017 at 6:25 PM, Marc Spehlmann 
> wrote:
>
>> Re-reading BUILDING.md, it seems like this doc might be a victim of being
>> added to iteratively over time without consideration to the overall
>> structure. I am purposing to par down some of the language and shift the
>> sections around in a flow that a novice quickstep user would probably 
want:
>>
>> 0 a header with TOC
>> 1 basic building instructions
>> 2 common flags we use for quick troubleshooting
>> 3 List of advanced cmake flags
>> 4 appendix of other, uncommon features
>>- building on windows
>>- vagrant
>>
>> I'll make a PR with these changes, but does anyone have an initial
>> objection to the change in structure?
>>
>
>

Re: Editing documentation for release: BUILDING.md

[Jignesh Patel]

Great changes! +1 for replacing the current building doc with this one. 

Cheers,
Jignesh 

On 2/7/17, 6:43 PM, "Marc Spehlmann"  wrote:

For example, here is the edited doc:

https://github.com/cramja/incubator-quickstep/blob/refactor-building/BUILDING.md#prerequisites

On Tue, Feb 7, 2017 at 6:28 PM, Marc Spehlmann 
wrote:

> Any objections if I remove the 'Getting cmake' section? It seems long, and
> like information that a database programmer would probably already
> know/google and quickly find out.
>
> Instead I can link to cmake's webpage in the prereq section
>
> On Tue, Feb 7, 2017 at 6:25 PM, Marc Spehlmann 
> wrote:
>
>> Re-reading BUILDING.md, it seems like this doc might be a victim of being
>> added to iteratively over time without consideration to the overall
>> structure. I am purposing to par down some of the language and shift the
>> sections around in a flow that a novice quickstep user would probably 
want:
>>
>> 0 a header with TOC
>> 1 basic building instructions
>> 2 common flags we use for quick troubleshooting
>> 3 List of advanced cmake flags
>> 4 appendix of other, uncommon features
>>- building on windows
>>- vagrant
>>
>> I'll make a PR with these changes, but does anyone have an initial
>> objection to the change in structure?
>>
>
>

Re: release: third_party/

[Jignesh Patel]

I think it was Zuyu. Zuyu – can you comment? 

Cheers,
Jignesh 

On 1/5/17, 12:56 PM, "Harshad Deshmukh"  wrote:

If I recall correctly, one of the Quickstep developers wrote the python 
script.


On 01/05/2017 11:43 AM, Marc Spehlmann wrote:
> That seems to be the repo with the LLVM code for implementing IWYU. I 
think
> what we have in our repo is scripts ontop of that library. I'm wondering
> where the scripts came from.
>
> Thanks,
> Marc
>
> On Thu, Jan 5, 2017 at 10:50 AM, Harshad Deshmukh 
> wrote:
>
>> Hi Marc,
>>
>> How about this one for IWYU?
>>
>> https://github.com/include-what-you-use/include-what-you-use
>> /blob/master/LICENSE.TXT
>>
>>
>> On 01/05/2017 10:43 AM, Marc Spehlmann wrote:
>>
>>> I double checked the libraries in thirdy_party. They adhere to Apache's
>>> 3rd
>>> party requirement as they are all apache 2 or opensourced by Google. The
>>> only issue I saw was that IWYU has no documentation. Anyone know of its
>>> source?
>>>
>>> Library
>>>
>>> Ver
>>>
>>> License
>>>
>>> Notes
>>>
>>> benchmark
>>>
>>> Apache 2.0
>>>
>>> cpplint
>>>
>>> Google
>>>
>>> Header states that reuse is unconditional so long as the copyright 
header
>>> stays intact.
>>>
>>> Farmhash
>>>
>>> Google
>>>
>>> No restrictions so long as COPYING file is preserved. See COPYING
>>>
>>> gflags
>>>
>>> Google
>>>
>>> No restrictions so long as COPYING file is preserved. See COPYING
>>>
>>> glog
>>>
>>> Google
>>>
>>> No restrictions so long as COPYING file is preserved. See COPYING
>>>
>>> gtest
>>>
>>> Google
>>>
>>> No restrictions so long as COPYING file is preserved. See COPYING in
>>> subprojects.
>>>
>>> gperftools
>>>
>>> Google
>>>
>>> No restrictions so long as COPYING file is preserved.
>>>
>>> iwyu
>>>
>>>
>>> No license present
>>>
>>> linenoise
>>>
>>> Google
>>>
>>> No restrictions so long as LICENSE file is preserved.
>>>
>>> protobuf
>>>
>>> Google
>>>
>>> No restrictions so long as LICENSE file is preserved.
>>>
>>> RE2
>>>
>>> Google
>>>
>>> No restrictions so long as LICENSE file is preserved.
>>>
>>> tmb
>>>
>>> Apache 2.0
>>>
>>> README: TMB is part of the Quickstep project (copyright Pivotal 
Software,
>>> Inc.) and is distributed under the same license terms.
>>>
>>>
>> --
>> Thanks,
>> Harshad
>>
>>

-- 
Thanks,
Harshad

Re: blog

[Jignesh Patel]

Nice. Thanks Marc!

On 12/11/16, 11:54 AM, "Marc Spehlmann"  wrote:

Hey, we have a jekyll blog and a first blog article now! It can be viewed

here http://apache.github.io/incubator-quickstep/

It's a page automatically generated by github. We can probably change the
URL somehow, not sure off hand though.

Editting instructions are included in the readme here

https://github.com/apache/incubator-quickstep/tree/gh-pages

If anyone wants to touch up the css or layout, have at it. I'm no web
design expert, I rely on the pre-built themes.

Anyone can write a post, all you need to know is markdown.

Happy blogging!

Re: Working towards a release

[Jignesh Patel]

Fellow Quickstep-pers: AFAIK we are good on all the items under 3.X in the 
release guidelines at: https://incubator.apache.org/guides/release.html

 

Next step, Section 1.1. We need a list of release managers. The reasons for 
signing a release are listed at: 
http://www.apache.org/dev/release-signing.html#motivation, and summarized as: 
“… users can make sure that what they received has not been modified in any way 
…“

 

We need to create a file that contains “… the public key signatures of the 
release managers (and optionally other committers) for the project …” 

 

I’m tossing my had in to be part of this group of release managers. Any 
objections? 

 

Anyone else wants to join the list of release managers? The more the merrier, 
and some groups have many of the active committers sign.

 

Cheers,

Jignesh 

 

On 12/4/16, 9:46 AM, "Marc Spehlmann" <spehl.apa...@gmail.com> wrote:

 

    I know that Julian mentioned writing some blog posts. I'd like to write

    one. Maybe we could distill the recent paper, or talk about a specific

    component? Or just talk about all the recent improvements which got our

    performance way up before the paper.

    

 

 

    On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jmp.quicks...@gmail.com>

    wrote:

    

> Thanks Harshad for volunteering!

    >

    > Re. 3.5, I think the generated files are ok.

    >

    > We can sync up after you come back. Happy Travels.

    >

    > Cheers,

    > Jignesh

    >

    > On 12/3/16, 7:25 AM, "Harshad Deshmukh" <hars...@cs.wisc.edu> wrote:

    >

    > A question on 3.5 - We have preprocessed parser and lexer files in the

    > parser module. Should we remove them?

Re: site

[Jignesh Patel]

+1 from me. Go for it! 

Cheers,
Jignesh 


On 12/7/16, 3:52 PM, "Marc Spehlmann"  wrote:

I noticed that we have a site @
https://github.com/apache/incubator-quickstep-site

and that it is hosted at

http://quickstep.incubator.apache.org/

Does anyone know/care if I modify this website?

In particular, I was thinking to make a blog using jekyll - a markdown
based blogging framework which github builds natively into each repo that
gets created. I've used jekyll before- it's great.

The site would have an index page like the current one, then a link the the
blog page which is a paginated index of blog entries. Entries would be
written by us in markdown and then the jekyll framework does the conversion
to HTML.

So if anyone has info related to this, please reply.

--Marc

Re: Working towards a release

[Jignesh Patel]

Marc: 

That is great! Would be great to just write a post about what Quickstep is, 
what it can do, and how someone can give it a spin. 

Cheers,
Jignesh 

On 12/4/16, 9:46 AM, "Marc Spehlmann" <spehl.apa...@gmail.com> wrote:

I know that Julian mentioned writing some blog posts. I'd like to write
one. Maybe we could distill the recent paper, or talk about a specific
component? Or just talk about all the recent improvements which got our
performance way up before the paper.

On Sat, Dec 3, 2016 at 5:04 PM, Jignesh Patel <jmp.quicks...@gmail.com>
wrote:

> Thanks Harshad for volunteering!
>
> Re. 3.5, I think the generated files are ok.
>
> We can sync up after you come back. Happy Travels.
>
> Cheers,
> Jignesh
>
> On 12/3/16, 7:25 AM, "Harshad Deshmukh" <hars...@cs.wisc.edu> wrote:
>
> A question on 3.5 - We have preprocessed parser and lexer files in the
> parser module. Should we remove them?
>
>
>
>
>

Re: building on OSX 10.12.1

[Jignesh Patel]

It would be nice though to get things working on native MacOS. 

Saket, not sure if you have gotten around to trying to move up the protobuf 
libraries. If you have, did it work? 

Cheers,
Jignesh 

On 11/29/16, 10:36 AM, "Marc Spehlmann"  wrote:

Follow up:

Saket is working on updating the submodules so that we can compile native
on osx sierra.

I found out that running in a docker container can work. Make your MacOS
quickstep folder available to docker as a read only volume. Then create a
build folder somewhere local to docker and build away. This works well for
right now.

Best, Marc

On Fri, Nov 25, 2016 at 8:22 PM, Marc Spehlmann 
wrote:

> I tried running docker with the latest ubuntu. That works, though sadly
> the mounted volume feature of docker doesn't seem to work correctly, in
> that i get build errors when I try to build in a shared volume.
>
> There's also virtual box. Or just plain old ubuntu. Clion works well in
> ubuntu anyways.
>
> As for updating the module, yes, Harshad and I could chat in person next
> monday.
>
> On Wed, Nov 23, 2016 at 8:27 PM, J Patel  wrote:
>
>> I think the right way to do this is to move to the latest version of 
their
>> libraries. Things like syscall are now deprecated in OSX.
>>
>> I think Zuyu and Harshad may have some insights on how to do this right.
>>
>> On Tue, Nov 22, 2016 at 8:49 PM Marc Spehlmann 
>> wrote:
>>
>> > That link appears to be broken. Do you mind copying the text?
>> >
>> > On Tue, Nov 22, 2016 at 8:24 PM, Navneet Sankara 
>> wrote:
>> >
>> > > Probably this macOS Sierra issue:
>> > > https://lists.apache.org/thread.html/81e200d3599f519009ebe54674f4aa
>> > > 96c71f3e22ccbacaf9e5198332@
>> > > 
>> > >
>> > > On Tue, Nov 22, 2016, 19:50 Marc Spehlmann 
>> > wrote:
>> > >
>> > > > Hello quickstep,
>> > > > I'm getting compile errors with the third party libraries. I have
>> some
>> > of
>> > > > these installed on my system (protobuf). Is there a flag to tell
>> CMake
>> > to
>> > > > use the system library instead of building the bundled one?
>> > > >
>> > >
>> >
>>
>
>

Re: Working towards a release

[Jignesh Patel]

Thanks Harshad for volunteering!  

Re. 3.5, I think the generated files are ok. 

We can sync up after you come back. Happy Travels. 

Cheers,
Jignesh 

On 12/3/16, 7:25 AM, "Harshad Deshmukh"  wrote:

A question on 3.5 - We have preprocessed parser and lexer files in the 
parser module. Should we remove them?

Re: QueryHandle Ownership During a Query Execution

[Jignesh Patel]

Hi Zuyu,

This makes sense to me. I think Harshad has some work on concurrent query 
execution in a branch, so would be good to get his input too. Perhaps, we could 
move to a unified design to allow concurrent query execution? 

Cheers,
Jignesh 

On 11/19/16, 10:48 PM, "Zuyu Zhang"  wrote:

Hi guys,

I would like to discuss some design changes regarding the QueryHandle
ownership during the life of serving a query.

I would propose to let QueryManager owns QueryHandle during the query
execution phase, instead of the main thread in QuickstepCli.

For those who are not familiar, QueryHandle is the central data structure
to hold the query id, the optimized query execution plan, and query
priority or like. And QueryManager is the key data structure to hold the
query execution state.

For now, the main thread in QuickstepCli manages the QueryHandle, and only
processes one query at a time. This situation, however, does not scale for
the distributed version which will have multiple DistributedClis submit
queries for concurrent execution.

By moving QueryHandle ownership to QueryManager, it fits well in both the
single-node and the distributed version. In addition, it becomes much
easier to do the clean-ups by Foreman-managed components upon the
completion of the query execution, instead of that Foreman notices the main
thread to do so.

Cheers,
Zuyu

Re: Xcode 8

[Jignesh Patel]

Hi Hakan: This helped, move things forward. But, glog still generates and error 
“clang: error: no such file or directory: ' -Wno-deprecated-declarations '
 
Also, similar changes are needed for gpertools and protobuf as they also make 
calls that are deprecated in XCode 8. 

Also … (new) MacBook ordered for you. I’m taking the easy way out ☺ 

Cheers,
Jignesh 

PS: Can you summarize the changes you made in the glog-fix-apple branch for 
glog? 


On 10/29/16, 1:26 AM, "Hakan Memisoglu" <hakanmemiso...@apache.org> wrote:

Hi Jignesh,

I do not have a Macbook to test the fix, but can you try 
'glog-fix-apple' branch?


On 10/28/2016 02:12 PM, Jignesh Patel wrote:
> As some of you probably know, the code does not compile when you upgrade 
to XCode 8. An example error message is:
>
>   
>
> quickstep/third_party/glog/src/raw_logging.cc:153:3: 'syscall' is 
deprecated: first deprecated in macOS 10.12 - syscall(2) is unsupported; please 
switch to a supported interface. For SYS_kdebug_trace use kdebug_signpost().
>
>   
>
> So, don’t rush to upgrade to XCode 8.
>
>   
>
> Cheers,
>
> Jignesh
>
>

Re: SplitRow Now fixed

[Jignesh Patel]

Thanks Marc for the quick fix! 

Cheers,
Jignesh 

On 11/1/16, 4:26 PM, "Marc Spehlmann"  wrote:

Hello, we were experiencing issues with the splitrow store which amounted
to an overestimate of the amount of tuples we could insert into the block.
This has been fixed in #125 and I tried loading SSB with splitrow, it works
fine.

The issue was appearing in SSB and not TPCH because TPCH only uses fixed
length (CHAR) attributes while SSB uses variable (VARCHAR). This brought up
another discussion of which Char type to use in the TPCH benchmark- we
might need to modify the scripts.

Best,
Marc

Xcode 8

[Jignesh Patel]

As some of you probably know, the code does not compile when you upgrade to 
XCode 8. An example error message is:

 

quickstep/third_party/glog/src/raw_logging.cc:153:3: 'syscall' is deprecated: 
first deprecated in macOS 10.12 - syscall(2) is unsupported; please switch to a 
supported interface. For SYS_kdebug_trace use kdebug_signpost().

 

So, don’t rush to upgrade to XCode 8.  

 

Cheers,

Jignesh 

Re: Outreach

[Jignesh Patel]

Thanks Harshad! Great idea to work backwards on the list of things that we need 
to do for a release. I think the current guidelines for a release are at: 
https://incubator.apache.org/guides/release.html . I can take a shot at working 
backwards from it. 

We need all the help we can to build the community, so if you feel like you 
want to help in that way, please announce it on this list. Just want to make 
sure the discussion on this thread doesn’t end with this email ☺ 

Cheers,
Jignesh 

On 10/25/16, 11:07 AM, "Harshad Deshmukh" <hars...@cs.wisc.edu> wrote:

Hi Jignesh,

I can certainly help with #1 and #3.

For #1, we can set up a release deadline and set up milestones in 
reverse chronological order so that we can meet the deadline. Apache has 
an elaborate documentation on the release procedure and hopefully that's 
a good starting point.

For #3, we can begin from participating in BigData Wisconsin meetups. 
 From what I know, there is a healthy interest in data management 
systems in the meetup, I can volunteer to attend and present the system 
over there.

For #4, I agree with you. Some of our JIRA reports are really extensive 
and describe the issues in detail. We probably need to bring some of the 
content from JIRA issues to the dev list. From here on, I can try to 
summarize in an email to the dev list, the features that I am currently 
working on (or about to begin work on) and its impact on the system.


On 10/25/2016 10:02 AM, Jignesh Patel wrote:
> I’m hoping to get some feedback from the general developers list on 
potential outreach activities for the project. To set the background for this 
discussion, Quickstep became an Apache project earlier this year. Nearly all 
the people on the project are relatively new to the Apache way of doing things 
(I certainly am, and I’m still learning various aspect of the Apache way).
>
>   
>
> Our mentors have been very helpful and rightly point out that we need to 
do more by way of outreach. This would include (but not limited to) doing 
things like:
>
>   
>
> #1: Making a release
>
> #2: Writing blogs about the project
>
> #3: Going to meetups and conferences like Apache Con to make a 
presentation about the project (we can find ways to fund these meetings).
>
> #4: Using the dev list more actively, even if it is to discuss 
interesting observations that we make – e.g. tried the new Xcode, and ran into 
the following issues.
>
>   
>
> Note on #4, I personally feel that we have a lot of active discussions. 
But, our primary mechanism is via Jiras and the discussion on the PRs. They are 
quite lively at times, and it is fantastic that people express their views in a 
respectful way but are not shy to point out any critical comments that they may 
have. We need to keep doing this. All those comments do go to the dev lists, 
but we should also talk about other things like what we think would be great to 
work on next, and/or just announce what topics you may be working on.
>
>   
>
> So, the main question in this email is: Are there folks on this list who 
want to help with building the Quickstep community in the ways described above? 
If you are interested, can you let this group know what you might want to help 
with. Also free free to pitch any ideas that you may have to help build the 
community. The main point is to get more people excited about the project in 
any role (including developers, users, …) and to share responsibilities for the 
core direction of the project.
>
>   
>
> One concrete proposal is to go make a release in about a month. I’m happy 
to help with that. Anyone else wants to help out? Now you may ask – what does 
it take to do a release? I honestly don’t know. But, we have to go read up on 
that, bug the mentors, and figure it out. All that is part of helping build an 
Apache community.
>
>   
>
> Cheers,
>
> Jignesh
>
>   
>
>   
>
>   
>
>   
>
>

-- 
Thanks,
Harshad

Outreach

[Jignesh Patel]

I’m hoping to get some feedback from the general developers list on potential 
outreach activities for the project. To set the background for this discussion, 
Quickstep became an Apache project earlier this year. Nearly all the people on 
the project are relatively new to the Apache way of doing things (I certainly 
am, and I’m still learning various aspect of the Apache way). 

 

Our mentors have been very helpful and rightly point out that we need to do 
more by way of outreach. This would include (but not limited to) doing things 
like: 

 

#1: Making a release

#2: Writing blogs about the project

#3: Going to meetups and conferences like Apache Con to make a presentation 
about the project (we can find ways to fund these meetings). 

#4: Using the dev list more actively, even if it is to discuss interesting 
observations that we make – e.g. tried the new Xcode, and ran into the 
following issues. 

 

Note on #4, I personally feel that we have a lot of active discussions. But, 
our primary mechanism is via Jiras and the discussion on the PRs. They are 
quite lively at times, and it is fantastic that people express their views in a 
respectful way but are not shy to point out any critical comments that they may 
have. We need to keep doing this. All those comments do go to the dev lists, 
but we should also talk about other things like what we think would be great to 
work on next, and/or just announce what topics you may be working on. 

 

So, the main question in this email is: Are there folks on this list who want 
to help with building the Quickstep community in the ways described above? If 
you are interested, can you let this group know what you might want to help 
with. Also free free to pitch any ideas that you may have to help build the 
community. The main point is to get more people excited about the project in 
any role (including developers, users, …) and to share responsibilities for the 
core direction of the project.

 

One concrete proposal is to go make a release in about a month. I’m happy to 
help with that. Anyone else wants to help out? Now you may ask – what does it 
take to do a release? I honestly don’t know. But, we have to go read up on 
that, bug the mentors, and figure it out. All that is part of helping build an 
Apache community. 

 

Cheers,

Jignesh 

 

 

 

 

Re: Podling Report Reminder - October 2016

[Jignesh Patel]

Dear Quickstep-pers: See my input for the podling report at 
https://wiki.apache.org/incubator/October2016. Comments welcome! 

Cheers,
Jignesh

On 9/29/16, 7:47 PM, "johndam...@apache.org"  wrote:

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 19 October 2016, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, October 05).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.

This should be appended to the Incubator Wiki page at:

http://wiki.apache.org/incubator/October2016

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: BlockNotFoundInMemory

[Jignesh Patel]

I have seen this before. I belive it is realated to the hash table allocation, 
which are very large (actually larger than they need to be due to estimation 
errors). Tcmalloc warns on such allocations. 

BTW: Jianqiao and Harshad, can we reduce the initial hash table allocation. I 
think starting with something small e.g, 8K entries and then doubling as needed 
(the code already does that) should work. We can try it.

Cheers,
Jignesh 


On 9/2/16, 9:48 PM, "Navneet Potti"  wrote:

As an aside, I also get this warning often when running some of the later 
queries.
tcmalloc: large alloc 1610612736 bytes == 0x99ed4000 @
tcmalloc: large alloc 1610612736 bytes == 0x89ec4000 @
tcmalloc: large alloc 1610612736 bytes == 0x89ec4000 @

Quickstep Copyright changes

[Jignesh Patel]

Quick update: The copyright changes are likely to happen today. I have a PR 
open, and Zuyu will review, and merge if it looks good. 

 

Sorry for the disruption that this will likely cause as it touches every file. 

 

Cheers,

Jignesh 

Question about using github as the main repo

[Jignesh Patel]

Currently we use the git-wip-us.apache.org as the main repo for Quickstep. This 
works, but has limitations compared to doing development on github. One key 
limitation is closing PRs on github is far easier.

 

Question: Is it possible for us to use github instead of ASF git server to host 
the main code base? I know we have a mirror on github, but is it possible to 
also have the main repo on github?

 

Thanks!

Jignesh

5 things

[Jignesh Patel]

Dear Quickstep-pers:

 

A bunch of comments/updates.

 

#1: The initial project website is up at http://quickstep.incubator.apache.org. 
It is really early and still needs a lot of work.

 

#2: There is now a quickstart guide in the main repo: 
https://github.com/apache/incubator-quickstep/blob/master/README.md Again lots 
of work to do, but it is a start. 

 

#3: We need a more pages/writeup to cover more of the basics, which includes at 
least a “Supported SQL surface” and additional examples. Will work on this as I 
can steal time. Volunteers are of course welcome! 

 

#4: We need to write a better developer guide; i.e. improve the intro to dev at 
https://github.com/apache/incubator-quickstep/blob/master/DEV_README.md. I know 
the code is well-commented, but we should be making it easier to welcome new 
developers. We can also provide a list of relatively simple projects that new 
developers could take on. Ideas here are welcome.

 

#5: We need a guide for the developer community governance. Below is a starting 
point. 

 

As usual comments welcome!

 

Cheers,

Jignesh 

 

Quickstep is a data platform that is written in C++ and uses advanced C++ 
techniques including template meta-programming and various abstractions to 
balance high-performance with extensibility. Thus, a good grasp over C++ 
concepts is essential for a Quickstep developer.

 

Quickstep has a set of core contributors who are collectively the stewards of 
the project. In addition, there is a set of general contributors who contribute 
individual changes. The initial list of core and general contributors is listed 
below.

 

Core contributors can close pull requests, except pull requests that they have 
created (which must be examined and closed by another core contributor). Anyone 
can open a pull request and once a pull request has been accepted that 
committer becomes part of the general contributors group. 

 

A general contributor can become a core contributor by getting support from at 
least two core contributors. It is expected that a general contributor will 
have demonstrated proficiency in understanding and working with the core engine 
to become part of the core contributors group.

 

To maintain membership in the core contributors group, the contributor must be 
active in the project in the preceding 6-month period. Membership of the core 
contributors is examined and determined bi-annually by the Apache Quickstep 
PPMC. 

 

Core Contributors (as of July 14, 2016):

·   Jignesh M. Patel

·   Harshad Deshmukh

·   Jianqiao Zhu

·   Zuyu Zhang

·   Marc Spehlmann

·   Saket Saurabh

·   Hakan Memisoglu

·   Rogers Jeffrey Leo John

·   Navneet Potti

 

Core Collaborators (as of June 18, 2016):

·   Adalbert Gerald Soosai Raj

·   Siddharth Suresh

·   Rathijit Sen

·   Craig Chasseur

·   Yinan Li

·   Qiang Zeng

·   Shoban Chandrabose

·   Roman Shaposhnik

·   Julian Hyde

·   Jesse Zhang

 

Re: LLVM Apt Repositories are back

[Jignesh Patel]

Go for it Nav! 


> On Jun 27, 2016, at 10:01 AM, Navneet Potti  wrote:
> 
> Do you think we should switch Travis back to using the Apt repositories?
> 
> http://lists.llvm.org/pipermail/llvm-dev/2016-June/101500.html 
> 
> 

Re: [DISCUSS] Building a community

[Jignesh Patel]

Great questions Julian and neat comments Greg. 

Website is being worked on, but need a bit more work before putting it up. 

Agreed — need to work on all this. The key question that we have to solve as a 
group is getting some funding stability in place to gather resources to work on 
things that you outline below, which is often hard to pull is as part of 
student thesis (as you may know most of the initial developer community is 
students). 

BTW — the goals were changes as one of the mentors objected to it :-) I think 
it was a valid objection.

I am actively developing guidelines to make it easier to allow developers 
outside the core group to join. You may have seen the wiki pages that went up 
recently. There is still a lot more to do there. Am also working on an quick 
start guide. 

If anyone on this list sees opportunities for early actual users to try us out, 
please point this group toward that. That would allow us to solve a lot of 
problems! 

Cheers,
Jignesh 

> On Jun 17, 2016, at 12:04 PM, Gregory Chase  wrote:
> 
> A few questions:
> 
> 1. Who should be in Quickstep's Community?
> 
> 2. Why  should they join?
> 
> 3. What do you want them to do?
> 
> I'd change your goals as follows:
> 
> 1. Create an ASF release
> 2. Acquire Early Adopters
> 3. Build a Community
> 
> It's hard to attract people to a community when there is little to offer.
> 
> Now, you can acquire some "early contributors" before the first ASF release
> if you provide a bread crumb trail for them to contribute:
> 1. Try out our daily snapshot
> 2. Test instructions to help provide feedback in the Jira
> 3. List of simple Jiras any first time contributor can solve (don't fix
> them yourself, make it easy for others to join)
> 
> I'd also recommend posting a more informative website so that people know
> what it is that Quickstep offers and why it might interest them as a
> product and a community.
> 
> -Greg
> 
> On Fri, Jun 17, 2016 at 9:55 AM, Julian Hyde  wrote:
> 
>> Hi Quickstep developers and community,
>> 
>> Let’s have a discussion about how to build a community around Quickstep.
>> 
>> In the last report, Quickstep’s goals were listed as
>> 
>>  1. Acquire early adopters
>>  2. Acquire early adopters
>>  3. Acquire early adopters
>> 
>> then changed to
>> 
>>  1. Acquire early adopters
>>  2. Build a community.
>>  3. Create an ASF release.
>> 
>> I’d like to see progress toward those goals. The main activity I see right
>> now is people checking in code; that’s important, but it isn’t very
>> effective at building community.
>> 
>> What concrete steps can we take to acquire early adopters and help build a
>> community?
>> 
>> Please don’t be shy. I’d like to hear from as many people as possible —
>> initial committers, mentors, and people who are on this list just because
>> they want to kick the tires. Tell us what you want from this project.
>> 
>> Julian
>> 
>> 
>> 
> 
> 
> -- 
> Greg Chase
> 
> Global Head, Big Data Communities
> http://www.pivotal.io/big-data
> 
> Pivotal Software
> http://www.pivotal.io/
> 
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/

Re: Do we need 3 different InsertDestination classes?

[Jignesh Patel]

A huge +1 from me to get rid of dead code!

+CC: Gerald who also worked on this a while back, in case he has some input. 

Thanks!
Jignesh 


> On Jun 14, 2016, at 11:36 PM, Navneet Potti  wrote:
> 
> Hi Harshad
> I’m just kicking off this discussion based on a conversation I had with 
> Jignesh this morning. We have 3 different implementations of 
> InsertDestination, and I think we only really need one, the 
> PartitionAwareBlockPoolInsertDestination. 
> The AlwaysCreateBlockInsertDestination seems to be entirely useless 
> practically. I’m guessing it’s a relic of early development. The normal 
> BlockPoolInsertDestination seems like a degenerate case of the PartitionAware 
> one, with a single partition. 
> 
> If my understanding of the design is right, then we should refactor this code 
> to only have one InsertDestination. There is a lot of duplication of code and 
> complex logic in there. Anything we can do to simplify and clean up the code 
> is probably a good move. 
> 
> Thoughts?
> 
> Cheers,
> Navneet
> 

Re: Guideline To Update Copyright Header

[Jignesh Patel]

Following up on Roman’s excellent comment, I took all the copyright notices 
under third_party and collected them into a new NOTICE file (see below). 

Notice that there are comments within [Square Braces]. This will make it easier 
for us to update the NOTICE file if we chose to upgrade some of these 
third-party packages in the future. 

Also, the copyright file in the third_party/benchmark does not have year, so I  
simply reproduced it as they state in their AUTHORS  file 
.

Comments? 

Cheers,
Jignesh 

Apache Quickstep (incubating)
Copyright 2016 The Apache Software Foundation.

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).

Portions Copyright (c) 2011-2015, Quickstep Technologies, LLC.
Portions Copyright (c) 2015-2016, Pivotal Software, Inc.

[Copyright for third_party/benchmark]
Portions Copyright (c) Arne Beer 
Portions Copyright (c) Christopher Seymour 
Portions Copyright (c) David Coeurjolly 
Portions Copyright (c) Dominic Hamon 
Portions Copyright (c) Eugene Zhuk 
Portions Copyright (c) Evgeny Safronov 
Portions Copyright (c) Felix Homann 
Portions Copyright (c) Google Inc.
Portions Copyright (c) JianXiong Zhou 
Portions Copyright (c) Lei Xu 
Portions Copyright (c) Matt Clarkson 
Portions Copyright (c) Oleksandr Sochka 
Portions Copyright (c) Paul Redmond 
Portions Copyright (c) Shuo Chen 
Portions Copyright (c) Yusuke Suzuki 

[Copyright for third_party/cpplint]
Portions Copyright (c) 2009 Google Inc 

[Copyright for third_party/farmhash]
Copyright (c) 2014 Google, Inc.

[Copyright for third_party/gflags]
Copyright (c) 2006, Google Inc.

[Copyright for third_party/glog]
Copyright (c) 2008, Google Inc.

[Copyright for third_party/gpertools]
Copyright (c) 2005, Google Inc.

[Copyright for third_party/linenoise]
Copyright (c) 2010-2014, Salvatore Sanfilippo 
Copyright (c) 2010-2013, Pieter Noordhuis 

Re: [jira] [Commented] (QUICKSTEP-20) Add parser support for SQL window aggregation function

[Jignesh Patel]

Great point Julian and something that I have been thinking about too. 

I’d love to kick off a discussion to see how we can find a way to make this 
work. I’d love to give a talk to the Calcite team sometime later on this summer 
(July?) on Quickstep and explore this very synergy. 

Some of the ORCA guys have also been thinking about this. But, in the end it 
boils down to two things: a) Synergy and b) Some commitment from the two 
projects to make this work.

For Quickstep, the goal is quite clear: we want to focus on the key aspects of 
our platform that relate to fast query execution and flexible scheduling. But, 
need to do this in a way that is trivially easy for users to use. 

Cheers,
Jignesh  

> Julian Hyde commented on QUICKSTEP-20:
> --
> 
> It sounds as if Quickstep is going down the route of building a full SQL 
> parser, validator, planner. This is fine, but it is a huge amount of work to 
> produce something that is high quality. Have you considered using Apache 
> Calcite? Calcite is written in Java but that shouldn't be too much of an 
> issue because Calcite can work as a pre-processor, producing a physical plan 
> that can be run without any Java in the runtime.
> 
>> Add parser support for SQL window aggregation function
>> --
>> 
>>Key: QUICKSTEP-20
>>URL: https://issues.apache.org/jira/browse/QUICKSTEP-20
>>Project: Apache Quickstep
>> Issue Type: New Feature
>> Components: Parser
>>   Reporter: Shixuan Fan
>> Labels: features, newbie
>> 
>> The first part of window aggregation function. There will be new grammar 
>> introduced to the parser so that the parser could understand a window 
>> aggregation query.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)

Re: Guideline To Update Copyright Header

[Jignesh Patel]

> +1 to keeping the NOTICE file as short as possible. Some projects get into 
> the habit of adding copyrights & notices merely out of “courtesy” but that 
> imposes a burden on downstream projects (who are obliged by the ASL to pass 
> on the NOTICE file intact).
> 
> Julian


Thanks Julian for the feedback about how it is important for downstream 
projects! I hadn’t thought of that — and makes perfect sense. In that spirit, 
we strictly only need the first two lines, so will make the NOTICE file even 
simpler, and just be:

Apache Quickstep (incubating) 
Copyright 2016 The Apache Software Foundation.

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/ 
).

Portions Copyright (c) 2011-2015, Quickstep Technologies, LLC.
Portions Copyright (c) 2015-2016, Pivotal Software, Inc.

Cheers,
Jignesh

Re: Guideline To Update Copyright Header

[Jignesh Patel]

Thanks Roman! 

To not disturb the ongoing work in existing PRs, I can take care of fixing the 
copyright in all existing files once we have closed the existing PRs (upto PR 
#28) . I’ll write a sed script to make the switch. Tentatively, lets plan on 
running this script this on Thursday 6/16 at noon CT. Soon after that, 
hopefully it will be merged into the master.

/** 
 * Licensed to the Apache Software Foundation (ASF) under one
 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 * 
 *   http://www.apache.org/licenses/LICENSE-2.0
 * 
 * Unless required by applicable law or agreed to in writing,
 * software distributed under the License is distributed on an
 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 **/ 

I’ll replace the existing NOTICE file in the root Quickstep directory that has 
the following contents tomorrow at June 14 at noon CT, so new files going in 
after that with the header above point to the right NOTICE file. For PRs being 
merged after the new NOTICE file is in the master, if you feel like you need to 
change the copyright notice (you don’t have to as I can take care of that when 
I run the sed script), please use the contents in the the copyright block above.

Apache Quickstep (incubating) 
Copyright 2016 The Apache Software Foundation.

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).

Portions Copyright (c) 2011-2015, Quickstep Technologies, LLC.
Portions Copyright (c) 2015-2016, Pivotal Software, Inc.
Portions Copyright (c) 2015-2016, Quickstep Research Group, University of 
Wisconsin-Madison. 

Please note it is my understanding that we don’t need to add our individual 
names or organization names to the NOTICE file, so don’t need to grow the list 
in the NOTICE file. 

Please let me know if you spot some errors in this approach. 

Cheers,
Jignesh 

> On Jun 12, 2016, at 5:38 PM, Roman Shaposhnik  wrote:
> 
> All of your copyright headers need to look exactly like this:
>http://www.apache.org/legal/src-headers.html#headers
> 
> In fact, this will be one of the requirements on which your first
> ASF release will be predicated. All the other Copyright statements
> need to be coalesced and moved into the NOTICE file similar to:
>https://github.com/apache/incubator-hawq/blob/master/NOTICE
> 
> Thanks,
> Roman.
> 
> On Mon, Jun 13, 2016 at 12:25 AM, Jignesh M. Patel  wrote:
>> Others can correct me if I have this wrong, but we should  it add any 
>> additional copyright anymore. It's implicit that contributions are to Apache.
>> 
>> This also means less work for committers and we can avoid requests during PR 
>> to update the copyright.
>> 
>> I suggest dropping the copyright line in this PR.
>> 
>> Thanks!
>> 
>> Sent from my iPhone
>> 
>>> On Jun 12, 2016, at 2:37 PM, Zuyu Zhang  wrote:
>>> 
>>> Hi,
>>> 
>>> I was wondering how to update copyright info in a file header to reflect
>>> outside contributors' change.
>>> 
>>> More specifically, is it appropriate to add "Copyright 2016 The Apache
>>> Quickstep Contributors."?
>>> 
>>> https://github.com/apache/incubator-quickstep/pull/27/files#diff-357f532831c389c757e7c87c7db1c4d3R4
>>> 
>>> Cheers,
>>> Zuyu

Code Style Guidelines and Code Review pages added to ASF wiki

[Jignesh Patel]

Folks: Added two pages to the ASF wiki under the How-to page. You can visit 
them by going here: 

 

https://cwiki.apache.org/confluence/display/QUICKSTEP/How-to+articles

 

Comments welcome! 

 

Cheers,

Jignesh  

Re: Travis Vector_Copy_Elision_Level

[Jignesh Patel]

Great idea Nav. I have no objections. 

Cheers,
Jignesh 

> On Jun 8, 2016, at 8:45 PM, Navneet Potti  wrote:
> 
> I noticed that we only run Travis with copy elision levels set to the two 
> non-default cases. The default case, which is also the only one that’s turned 
> out to be useful in the benchmarks, is not being tested at all. Does anyone 
> know why? Any objections to changing that?

Re: Logo?

[Jignesh Patel]

This is an interesting idea Julian. I tried to do something with the Basilisk 
lizard, but drawing that clipart is getting well beyond my clipart generating 
skills :-( Ok — so my art teacher was right :-) 

Cheers,
Jignesh 

> On Jun 4, 2016, at 9:51 PM, Julian Hyde <jh...@apache.org> wrote:
> 
> Word art + cute animal mascot has worked well for a lot of Apache projects.
> 
> This guy (a Basilisk lizard) seems appropriate:
> 
> https://i.ytimg.com/vi/PgSvN70lJ6w/hqdefault.jpg
> 
> The swoop of his tail could be incorporated into the flourish of the
> capital 'Q'.
> 
> On Sat, Jun 4, 2016 at 7:25 PM, Jignesh Patel <jipa...@pivotal.io> wrote:
>> Great to hear from our resident marketing guru. Awesome suggestion Greg!
>> 
>> Here is another design. It has the logo and the word art with the full 
>> system name in it. Comments Greg? I may have misunderstood what you were 
>> suggesting.
>> 
>> Powerpoint is also attached if someone is feeling adventurous. Note to see 
>> the whole image, you will have to zoom out in Powerpoint.
>> 
>> Cheers,
>> Jignesh
>> 
>>> On Jun 4, 2016, at 8:07 PM, Greg Chase <g...@gregchase.com> wrote:
>>> 
>>> Cool logos Jignesh!
>>> 
>>> Personally I'm a fan of word art that says what the brand is, so that 
>>> everyone will know without requiring much education.
>>> 
>>> So I would consider "Quickstep" in the logo.  You can also choose an icon 
>>> to be part, or not.
>>> 
>>> Having branded 3 Apache projects now, I will tell you that you don't need 
>>> to  put "Apache" in the name.
>>> 
>>> 0Greg

Logo?

[Jignesh Patel]

Hello Quickstep-pers: I think it would be good to have a logo for the project. 
I created three simple ones for us to consider. 

Ideally a logo is distinctive, renders well (so needs to be simple), and 
reflects the project theme. As many of you may recall, when we started this 
project, we had a simple theme (reflected in its name): making hardware and 
software dance to the same rhythm.

I never got the grade I wanted in my art class, so none of these may work. But 
would love to get input on these designs, or ideas for better designs.

Cheers,
Jignesh 

Re: Update on the Quickstep project

[Jignesh Patel]

Hi Roman,

I’m guessing that someone closing a PR should check if the committer has an 
ICLA. Or, is submitting a PR and implicit assignment by the code contributor 
that they are willing to donate the code to Apache? 

Cheers,
Jignesh 

> On May 31, 2016, at 12:21 PM, Roman Shaposhnik  wrote:
> 
>> 
>> Clearly this is important for anyone that is closing a PR.
> 
> Can you please elaborate?

Re: When do you think you can fully transition to ASF infrastructure?

[Jignesh Patel]

Zuyu is working with Roman on this. Thanks for the tip!

Cheers
Jignesh 

> On May 10, 2016, at 5:37 PM, Julian Hyde <jh...@apache.org> wrote:
> 
> OK, you should log an INFRA request to get Travis set up. It shouldn’t take 
> more than a day or two but definitely nothing will happen until you log an 
> INFRA request. Ask the Geode folks what they had to do to set up Travis.
> 
> Julian
> 
> 
>> On May 10, 2016, at 3:25 PM, Jignesh Patel <jipa...@pivotal.io> wrote:
>> 
>> Hi Julian: The current workflow is to have the PRs go through Travis to make 
>> the job of the reviewer far easier. This is what is missing and slows 
>> closing PRs. 
>> 
>> Cheers,
>> Jignesh 
>> 
>>> On May 10, 2016, at 5:23 PM, Julian Hyde <jh...@apache.org> wrote:
>>> 
>>> It’s a question of priority. Let’s not let the low priority stuff block the 
>>> important stuff. Moving source control is urgent. I haven’t yet heard a 
>>> reason why CI should delay moving source control.
>>> 
>>>> On May 10, 2016, at 3:15 PM, Jignesh Patel <jipa...@pivotal.io> wrote:
>>>> 
>>>> Dear Julian,
>>>> 
>>>> You do make a good point, but we have a very heavy reliance on the CI and 
>>>> it will certainly help the transition. 
>>>> 
>>>> Since other Apache projects do have a Travis CI, Zuyu has reached out to 
>>>> Roman to see if we can set this up. 
>>>> 
>>>> Agreed about the points that both you and Roman are making — we do need to 
>>>> move fully to ASF soon. Thanks for your patience. 
>>>> 
>>>> Cheers,
>>>> Jignesh 
>>>> 
>>>>> On May 9, 2016, at 1:27 AM, Julian Hyde <jh...@apache.org> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On May 8, 2016, at 8:39 PM, Zuyu Zhang <zzh...@pivotal.io> wrote:
>>>>>> 
>>>>>> Yes, we need fix QUICKSTEP-2 before transiting to ASF.
>>>>> 
>>>>> I disagree. It is much more important that you use ASF infrastructure for 
>>>>> source control than for CI, and the one does not block the other.
>>>>> 
>>>>> At Calcite it took a long time before we had CI running on ASF 
>>>>> infrastructure. We continued to use Travis-CI, which we’d used before ASF.
>>>>> 
>>>>> As Roman says, it is important for IP hygiene that commits are made 
>>>>> directly to ASF git, and the sooner you switch over the better. I think 
>>>>> you can do that before you transition CI.
>>>>> 
>>>>> Julian
>>>> 
>>> 
>> 
> 

Re: When do you think you can fully transition to ASF infrastructure?

[Jignesh Patel]

Dear Julian,

You do make a good point, but we have a very heavy reliance on the CI and it 
will certainly help the transition. 

Since other Apache projects do have a Travis CI, Zuyu has reached out to Roman 
to see if we can set this up. 

Agreed about the points that both you and Roman are making — we do need to move 
fully to ASF soon. Thanks for your patience. 

Cheers,
Jignesh 

> On May 9, 2016, at 1:27 AM, Julian Hyde  wrote:
> 
> 
> 
> 
>> On May 8, 2016, at 8:39 PM, Zuyu Zhang  wrote:
>> 
>> Yes, we need fix QUICKSTEP-2 before transiting to ASF.
> 
> I disagree. It is much more important that you use ASF infrastructure for 
> source control than for CI, and the one does not block the other.
> 
> At Calcite it took a long time before we had CI running on ASF 
> infrastructure. We continued to use Travis-CI, which we’d used before ASF.
> 
> As Roman says, it is important for IP hygiene that commits are made directly 
> to ASF git, and the sooner you switch over the better. I think you can do 
> that before you transition CI.
> 
> Julian

Re: When do you think you can fully transition to ASF infrastructure?

[Jignesh Patel]

Hi Julian,

I agree with the emails that moving faster is better. Working on it. 

Is there an easy way to see who has already signed the ICLA for Quickstep? 

Thanks! 
Jignesh 

> On May 9, 2016, at 1:36 AM, Julian Hyde  wrote:
> 
> Also, how is the transition to Apache email lists going? I see a couple of 
> commits per day going into git, and some discussion against pull requests, 
> but no discussion on the dev list. Where is this discussion happening?
> 
>> On May 8, 2016, at 11:27 PM, Julian Hyde  wrote:
>> 
>> 
>> 
>> 
>>> On May 8, 2016, at 8:39 PM, Zuyu Zhang  wrote:
>>> 
>>> Yes, we need fix QUICKSTEP-2 before transiting to ASF.
>> 
>> I disagree. It is much more important that you use ASF infrastructure for 
>> source control than for CI, and the one does not block the other.
>> 
>> At Calcite it took a long time before we had CI running on ASF 
>> infrastructure. We continued to use Travis-CI, which we’d used before ASF.
>> 
>> As Roman says, it is important for IP hygiene that commits are made directly 
>> to ASF git, and the sooner you switch over the better. I think you can do 
>> that before you transition CI.
>> 
>> Julian
> 

Re: Podling Report Reminder - May 2016

[Jignesh Patel]

I just entered info for Quickstep. Here it is for quick reference. Comments or 
corrections?  

Cheers,
Jignesh 
Quickstep

Quickstep is a high-performance data processing platform based on a core 
relational kernel.

Quickstep has been incubating since 2016-03-29.

Three most important issues to address in the move towards graduation:

  1. Expand the relational kernels to support a broader set of structured query 
processing, to cover at least TPC-H.
  2. Expand from the single-node version to a distributed version.
  3. Support concurrent multi-user/query settings with policies (e.g. 
fair-scheduling or highest-priority first).

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None.

How has the community developed since the last report?

This is the first report for this project.

How has the project developed since the last report?

This is the first report for this project.

Date of last release: N/A as the project was just incubated. 

When were the last committers or PMC members elected?

April 2016.


> On Apr 24, 2016, at 8:59 AM, johndam...@apache.org wrote:
> 
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 18 May 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, May 4th).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> 
> This should be appended to the Incubator Wiki page at:
> 
> http://wiki.apache.org/incubator/May2016
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC

Re: Twitter account?

[Jignesh Patel]

Great idea Julian! I’ll create one later on tonight. 

Cheers,
Jignesh 

> On Apr 18, 2016, at 3:33 PM, Julian Hyde  wrote:
> 
> Do you think it would be useful to have a project twitter account?
> 
> I tweeted about Quickstep a couple of days ago[1] and I would have referenced 
> @ApacheQuickstep if it existed.
> 
> Julian
> 
> [1] https://twitter.com/julianhyde/status/721194538241368064 
>