Re: Podling Report Reminder - December 2017

2017-12-06 Thread Harshad Deshmukh 
Hi Jignesh,


Robert Claus is the latest committer. I have added that in the report.


Thanks,

Harshad


From: J. M. Patel 
Sent: Wednesday, December 6, 2017 2:05:07 PM
To: dev@quickstep.incubator.apache.org
Subject: Re: Podling Report Reminder - December 2017

Hi everyone: I've added an initial report (see below). Feedback?


Quickstep is a high-performance database engine.

Quickstep has been incubating since 2016-03-29.

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

  1. Work on adoption of the Quickstep technology.
  2. Continue building a developer community.
  3. Work towards a second release.

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?

There are a number of active developers working with the code base, who may 
become committers in the near future.


How has the project developed since the last report?

A number of bug reports have been filed and features added to move the 
single-node version of the system forward.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-25

When were the last committers or PPMC members elected?

  2017-05-12 Tianrun Lee (committer)


On 12/6/17, 12:32 PM, "Julian Hyde"  wrote:

Hi Quicksteppers,

The report is due TODAY. Can someone write it please?

Julian


> On Nov 26, 2017, at 7:48 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, 20 December 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, December 06).
>
> 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/December2017
>
> 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 - December 2017

2017-12-06 Thread J. M. Patel 
Hi everyone: I've added an initial report (see below). Feedback? 


Quickstep is a high-performance database engine.

Quickstep has been incubating since 2016-03-29.

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

  1. Work on adoption of the Quickstep technology.
  2. Continue building a developer community.
  3. Work towards a second release.

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?

There are a number of active developers working with the code base, who may 
become committers in the near future.


How has the project developed since the last report?

A number of bug reports have been filed and features added to move the 
single-node version of the system forward.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-25

When were the last committers or PPMC members elected?

  2017-05-12 Tianrun Lee (committer)


On 12/6/17, 12:32 PM, "Julian Hyde"  wrote:

Hi Quicksteppers,

The report is due TODAY. Can someone write it please?

Julian


> On Nov 26, 2017, at 7:48 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, 20 December 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, December 06).
> 
> 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/December2017
> 
> 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 - December 2017

2017-12-06 Thread Julian Hyde 
Hi Quicksteppers,

The report is due TODAY. Can someone write it please?

Julian


> On Nov 26, 2017, at 7:48 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, 20 December 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, December 06).
> 
> 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/December2017
> 
> 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: Query Rows Returned Printing Disable

2017-12-06 Thread Harshad Deshmukh 
Hi Robert,


Please feel free to create a PR to merge the changes regarding 
quickstep::FLAGS_display_relation_size.


Thanks,

Harshad


From: Robert Claus 
Sent: Wednesday, December 6, 2017 10:24:12 AM
To: dev@quickstep.incubator.apache.org
Subject: Re: Query Rows Returned Printing Disable

I'm pretty sure it's in QuickstepCLI.cpp calling
PrintToScreen::PrintOutputSize.  In the branch I created for supporting csv
output
I
also added a flag to turn this off: quickstep::FLAGS_display_relation_size.

In QuickstepCLI.cpp:

if (query_result_relation) {

PrintToScreen::PrintRelation(*query_result_relation,
_manager, io_handle->out());

PrintToScreen::PrintOutputSize(*query_result_relation,
_manager, io_handle->err());


DropRelation::Drop(*query_result_relation, query_processor->
getDefaultDatabase(), _manager);

  }

On Wed, Dec 6, 2017 at 1:18 AM, Dylan Bacon  wrote:

> Hello,
>
> Where in the code while printing a query is the (x rows) part printed? I
> am not seeing a flag for that like I am for time and I think that including
> a flag to disable that would help end user applications not have to parse
> that message away. I'm seeing the code that determines the tuples in a
> relation, but not the printing part of the code that actually outputs that
> result.
>
> --
> Regards,
>
> Dylan Bacon
> University of Wisconsin - Madison
> Department of Computer Sciences
> dba...@wisc.edu
>
>

Re: Query Rows Returned Printing Disable

2017-12-06 Thread Robert Claus 
I'm pretty sure it's in QuickstepCLI.cpp calling
PrintToScreen::PrintOutputSize.  In the branch I created for supporting csv
output
I
also added a flag to turn this off: quickstep::FLAGS_display_relation_size.

In QuickstepCLI.cpp:

if (query_result_relation) {

PrintToScreen::PrintRelation(*query_result_relation,
_manager, io_handle->out());

PrintToScreen::PrintOutputSize(*query_result_relation,
_manager, io_handle->err());


DropRelation::Drop(*query_result_relation, query_processor->
getDefaultDatabase(), _manager);

  }

On Wed, Dec 6, 2017 at 1:18 AM, Dylan Bacon  wrote:

> Hello,
>
> Where in the code while printing a query is the (x rows) part printed? I
> am not seeing a flag for that like I am for time and I think that including
> a flag to disable that would help end user applications not have to parse
> that message away. I'm seeing the code that determines the tuples in a
> relation, but not the printing part of the code that actually outputs that
> result.
>
> --
> Regards,
>
> Dylan Bacon
> University of Wisconsin - Madison
> Department of Computer Sciences
> dba...@wisc.edu
>
>