Re: [VOTE] incubator-quickstep-0.1.0RC5

[Jianqiao]

+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
>
>

Podling Report Reminder - March 2017

[johndament]

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, 15 March 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, March 01).

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/March2017

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: [VOTE] incubator-quickstep-0.1.0RC5

[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

[GitHub] incubator-quickstep issue #198: patch to fix gcc compile error gflags

[zuyu]

Github user zuyu commented on the issue:

https://github.com/apache/incubator-quickstep/pull/198
  
It is more about maintainability when we try to upgrade the third party 
while our patch may not work in a new release.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quickstep pull request #200: Style fixes in the distributed versio...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-quickstep/pull/200


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[VOTE] incubator-quickstep-0.1.0RC5

[Marc Spehlmann]

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

[GitHub] incubator-quickstep pull request #199: Init release scripts

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-quickstep/pull/199


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quickstep issue #199: Init release scripts

[jianqiao]

Github user jianqiao commented on the issue:

https://github.com/apache/incubator-quickstep/pull/199
  
LGTM! Merging.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quickstep issue #199: Init release scripts

[cramja]

Github user cramja commented on the issue:

https://github.com/apache/incubator-quickstep/pull/199
  
@jianqiao it's gtg


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quickstep issue #201: Fix a bug with SelectOperator

[hbdeshmukh]

Github user hbdeshmukh commented on the issue:

https://github.com/apache/incubator-quickstep/pull/201
  
LGTM, merging. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quickstep pull request #201: Fix a bug with SelectOperator

[jianqiao]

GitHub user jianqiao opened a pull request:

https://github.com/apache/incubator-quickstep/pull/201

Fix a bug with SelectOperator

This PR fixes a bug that `SELECT ... LIMIT n;` may output more than `n` 
rows.

The cause is that `SortMergeRunOperator` creates two relations, where one 
relation is the output relation to a `SelectOperator` and the other is a 
_temporary_ relation. However, the generated blocks of the temporary relation 
are also fed into the `SelectOperator` via a _DataPipelineMessage_ -- thus we 
need to check that the input block to a `SelectOperator` is actually from its 
input relation.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/incubator-quickstep fix-select

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-quickstep/pull/201.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #201


commit e896b61d1932d4593cb18033fe4da23a5e238f77
Author: jianqiao 
Date:   2017-03-01T19:16:47Z

Fix a bug with SelectOperator




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-quickstep issue #189: patches for missed linenoise changes

[cramja]

Github user cramja commented on the issue:

https://github.com/apache/incubator-quickstep/pull/189
  
@zuyu I cannot recreate the issue you are describing.

```
Starting Quickstep with 8 worker thread(s) and a 11.20 GB buffer pool.
--num_workers is 8, but only specified 0 CPU affinities with 
--worker_affinities. 8 workers will be unaffinitized.
quickstep> \d
quickstep> \dt
quickstep> \dt foo
ERROR:  Unrecognized relation foo (1 : 5)
\dt foo
^
quickstep> create table foo (id int);
Time: 0.205 ms
quickstep> \d
   List of relations

 Name   | Type  | Blocks
+---+---+-+
 foo| table | 0

quickstep> \dt foo
   List of relations

 Name   | Type  | Blocks
+---+---+-+
 foo| table | 0

quickstep> \d foo
 Table "foo"
 Column | Type
+---+---+
 id | Int
quickstep> \d foobar
ERROR:  Unrecognized relation foobar (1 : 4)
\d foobar
   ^
quickstep> \d
   List of relations

 Name   | Type  | Blocks
+---+---+-+
 foo| table | 0

quickstep> quit;
```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---