Hi, I am passing along instructions on how to authorize an account (in my
case gmail) to send email as yourapachen...@apache.org
https://reference.apache.org/committer/email
Remember, you can manage your apache account at id.apache.org.
Cheers,
Marc
One of the steps that must take place before releasing a release tarball is
to have the release managers digitally sign the tarball.
Hakan, Jignesh, Harshad I think you all are the release managers. Please
follow this guide
http://quickstep.apache.org/release-signing/
to
1) create a key pair
2)
commit”.
>
> Julian
>
>
>
>
> > On Jan 31, 2017, at 3:35 PM, Marc Spehlmann
> wrote:
> >
> > One of the steps that must take place before releasing a release tarball
> is
> > to have the release managers digitally sign the tarball.
> >
>
t 6:20 PM, Jignesh Patel
> wrote:
> >
> > That would be nice if that were the case. We are nearly there then!
> >
> > Cheers,
> > Jignesh
> >
> > On 2/1/17, 7:47 PM, "Marc Spehlmann" wrote:
> >
> >It sounds like only one release manager needs to sign it then?
> >
> >
> >
> >
>
>
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 hea
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 Spehlman
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 in
et 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-quick
I'm looking through the impala guide to releases and they have an svm repo
where they store their release candidate tarballs, hashes plus an svn for
the final releases.
https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release
repo is
svn checkout https://dist.apache.org/repos/d
able to do this:
>
> svn co https://dist.apache.org/repos/dist/dev/incubator/quickstep
>
>
> Julian
>
>
> On Tue, Feb 14, 2017 at 2:12 PM, Marc Spehlmann wrote:
> > I'm looking through the impala guide to releases and they have an svm
> repo
> > where the
ponding
> https://dist.apache.org/repos/dist/release/incubator/quickstep
> directory and copy the KEYS file into it. (That's where releases will
> go, when you've passed all the votes. But the KEYS can go there
> already.)
>
> On Tue, Feb 14, 2017 at 2:25 PM, Marc Spehlma
Per the instructions of impala [1], I have been stepping through the
release process. Every time there is a release there can be multiple
release candidates. We vote on /dev as to whether we agree that we agree
this is worthy of a release.
So, if you please, try testing out the release candidate b
Per the instructions of impala [1], I have been stepping through the
release process. We voted once already for RC0, but it was turned down
because it did not include protobuf.
Try testing out the release candidate by pulling the SVN repo, and building
quickstep fresh, plus testing the hashes + si
Per the instructions of impala [1], I have been stepping through the
release process. There was an RC0/1 but they got turned down because they
did not include protobuf and were not signed correctly.
Try testing out the release candidate by pulling the SVN repo, and building
quickstep fresh, plus t
Release Candidate 3 should now include 3rd party protobuf correctly. I've
tested it on my mac and it works correctly. Here is a handy script [1] I
have been putting together to do the release. It's still in alpha, but
the test_rc() function will do everything you need it to.
***I did not make this
Jignesh and I spoke yesterday about how to specify what the minimum
requirements are for building quickstep. We decided to 'officially' support
ubuntu 14 LTS, 16 LTS.
Building on a mac will not be officially supported in the initial release.
Now there's the matter of what system packages will be
Hi everyone,
This past week I took a couple steps forward in the release process and
therefore made another release candidate.
- Created a Dockerfile with an ubuntu 16 version with all* the dependencies
quickstep should need to build. This should make verification of the
release candidate easy if
Jianqiao pointed out some issues yesterday. There was a gcc compile bug and
a hashtable issue which were both resolved in PRs.
I will cancel RC4 and take the latest changes as RC5 as we need to expedite
this process for the podling report.
--Marc
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
Hi Julian,
I agree that 'this week' is optimistic. Though, we have been going through
the voting process on @dev, it's likely that the current RC will not pass,
meaning that we'll need to restart the whole process, as you said.
Considering, 'this month' is probably a more realistic wording.
On T
otten more than 3 +1s
> so far. It appears that this release candidate (RC5) should be the final
> one, therefore I thought this week should be a realistic target for the
> release. Marc should have an idea about the next steps, so if I
> misunderstood something w.r.t the release
Vote Summary:
+ 1
Hakan
Jianqiao
Jignesh
Harshad
- 1
Myself - explained below
Discussion:
As Julian noted, a proper VOTE on a release candidate should include links
to the release artifacts. It follows that creating a vote email template is
good practice and makes releasing less painful.
link:
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 bett
mple http://www.apache.org/dist/calcite/KEYS <
> http://www.apache.org/dist/calcite/KEYS>) but import succeeded:
>
> $ gpg --import KEYS
> gpg: key A3C29E12: public key "Jignesh Patel "
> imported
> gpg: key 5A29899A: public key "Marc Spehlmann (apache) "
&
/incubator-quickstep/commit/1cfc1c40e2bcf7ff8671d5b899a8304c9e9fd455
On Tue, Mar 7, 2017 at 1:08 PM, Jignesh Patel
wrote:
> 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 wa
adding the volatile keyword does the trick!
On Tue, Mar 7, 2017 at 3:09 PM, Zuyu Zhang wrote:
> Btw, it seems that the compiler does not support or honor the flag
> '-Wno-unused-variable' set by the TMB.
>
> https://github.com/apache/incubator-quickstep/blob/
> master/third_party/src/tmb/CMakeLi
This vote is for approval of the Quickstep-0.1.0 RC6.
Voters should download, unpack, build, and test the package before voting.
+1 vote should be accompanied with what you did with the release.
-1 vote should be accompanied with a short reason.
Votes will remain open for 3 days.
___
Changes s
+1
Julian Hyde (binding)
Jignesh Patel (binding)
Harshad Deshmukh
Jianqiao
Hakan
-1
Thanks everyone for trying it out. As per the Apache policy, we will now
submit a vote to the general incubator discussion.
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.
Thank you to everyone who voted on the dev vote of RC7.
+1
Harshad
Josh
Jignesh
Julian (binding)
We will now submit the vote to the general incubator community.
Vote thread:
https://www.mail-archive.com/dev@quickstep.incubator.apache.org/msg02162.html
--Marc
Hello quickstep,
I am going to send an announce email to a few of the other apache lists
later today. Is there anything special about this release that we want to
mention (besides that it's our first release)?
If not, that's fine, I will send this email:
___
The Apache Quickstep (incubating) team
ow about the Apache protocol, so may be the mentors may have
> something to say about that.
>
> How about saying high performance, relational data processing engine
> developed in C++?
>
> The release is very exciting! I will start another thread regarding
> publicity of
processing engine
> developed in C++?
> >
> > The release is very exciting! I will start another thread regarding
> publicity of the release.
> >
> > Sent from Outlook for Android
> >
> >
> > From: Marc Spehlmann
> > Sent: Saturday, March 25, 9:57
Since this is the first release and there are a lot of features of
Quickstep which we have our specialities in, we might want to group edit
our release notes page. In the future this will be easier as it will be a
few months of changes rather than several years.
Here is the link
https://cwiki.apac
Hi dev,
I'm looking to make a simple TCP server interface to Quickstep so that we
can keep the db running while we communicate to it from a python program.
After investigating, I think the simplest way to do this is:
- create a Server executable which:
- opens a TCP socket
- forks a child with
cpp. The
> code might help and is available here:
>
> https://bitbucket.org/TianrunLi/tcpreader/src
>
> Best,
> Jianqiao
>
> 2017-03-30 10:10 GMT-05:00 Marc Spehlmann :
>
> > Hi dev,
> > I'm looking to make a simple TCP server interface to Quickstep so tha
Hi Zuyu,
Yes, that helps. I am making a prototype right now where I took the
QuickstepCli code and made another executable, QuickstepServer. The server
does all of the same initialization process. The main difference is that,
instead of communicating with a linereader, it must communicate with a
Ne
I think that in the initial version, it will not be aware of multiple
clients, but in the second version, this will not be hard to accommodate.
On Sat, Apr 1, 2017 at 4:48 PM, Zuyu Zhang wrote:
> Hi Marc,
>
> With the NetworkWrapper, does the QuickstepServer could serve queries from
> multiple c
Cool, thanks Harshad! Looks good.
One day we will come up with better css but sparse simplicity
trumps elaborate clutter so this is good.
On Thu, Apr 6, 2017 at 7:47 AM, Harshad Deshmukh
wrote:
> Hello,
>
> Thanks to Julian, Jignesh and Marc for your suggestions! The post is up
> now - http://
I have a PR out for a CLI which interfaces with the network over gRPC [1].
Julian recommended using a package called Avantica which wraps over a
standard JDBC+ODBC drivers and takes care the protocol.
The question I have for /dev is if we have a need right now for a standard
driver. I could see a
Hello Quicksteppers,
If you use vim, I recommend trying the plugin YouCompleteMe (
https://github.com/Valloric/YouCompleteMe). It offers code completion and
it works well out of the box with quickstep. I'll give a quick intro on how
to get it set up:
1 Requirements
- clang
- vim 7.3.8+
- ruby
Hey guys, has anyone experienced problems building on linux (Ubuntu 16) in
RelWithDebugInfo?
I have no trouble building in debug mode with clang-3.8, clang-3.7, and gcc
5.4 but the compiler hangs up and eats all the memory on my laptop (8gb)
then dies (bottom of message) when in Rel. This happens
hat machine has a lot more memory though,
> compared to your laptop.
>
> One possibility: If you are running a multi-threaded make, the compilation
> requires more memory which triggers the behavior that you saw. In which
> case, can you try a single threaded build?
>
>
>
>
I get annoying compiler warnings upgraded to errors when building with
clang 3.8, bison 3.0.4, flex 2.6.0:
[3/170] Building CXX object
parser/CMakeFiles/quickstep_parser_SqlLexer.dir/SqlLexer_gen.cpp.o
FAILED: parser/CMakeFiles/quickstep_parser_SqlLexer.dir/SqlLexer_gen.cpp.o
ccache /usr/bin/clang
Hey 2 questions about TPCH sf100.
(1)
On a cloud lab box, I am having trouble getting query 17 to finish. It
seems to be stuck in Hash table operations. Any ideas/experience?
(2)
Anyone got the link to the spreadsheet with benchmark results?
-Marc
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
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?
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
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:
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
+1 for the upgrade option
On Tue, Nov 29, 2016 at 11:45 AM, Saket Saurabh
wrote:
> Hi all,
> I would like to start a discussion around how to fix the failing build
> issue on OSX 10.12 due to deprecation of certain system APIs in the new OSX
> version.
> The Quickstep code does not rely on these
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
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 whic
Hi dev, I'm trying to create a gh-pages branch on our apache repo. I added
2 upstream branches:
https://github.com/apache/incubator-quickstep.git
git://git.apache.org/incubator-quickstep.git
However, I cannot push my new branch to either of them. On the github repo,
it's clear that people are abl
the address below?
>>
>> |https://git-wip-us.apache.org/repos/asf/incubator-quickstep-site <
>> https://git-wip-us.apache.org/repos/asf/incubator-quickstep>|
>>
>>
>> I guess that both Github and git.apache.org are read-only.
>>
>> On 12/11/2016 09:
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
http
oo difficult.
> >
> > Julian
> >
> > [1] https://github.com/apache/calcite/blob/master/site/README.md <
> https://github.com/apache/calcite/blob/master/site/README.md>
> >
> >> On Dec 11, 2016, at 12:36 PM, Hakan Memisoglu <
> hakanmemiso...@ap
://svn.apache.org/repos/asf/incubator-quickstep/site target
__
svn: E17: URL 'https://svn.apache.org/[...]' doesn't exist
On Mon, Dec 12, 2016 at 9:41 AM, Jignesh Patel
wrote:
> Nice. Thanks Marc!
>
> On 12/11/16, 11:54 AM, "Marc Spehlmann" wrote:
>
> Hey
ator.apache.org/guides/mentor.html#Set+Up+SVN+
> Repository> I think this means I need to create the repository and
> authorize committers. (Don’t worry, Quickstep will continue to use git for
> its source code, and for the source of the web site; SVN is just for the
> generat
Harshad pointed out the directory is
https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep-site.git
He found it by modifying the address found in
https://cwiki.apache.org/confluence/display/QUICKSTEP/Workflow+For+Committers
On Tue, Dec 13, 2016 at 10:02 AM, Marc Spehlmann
wrote
c 13, 2016 at 10:10 AM, Marc Spehlmann
wrote:
> Harshad pointed out the directory is
> https://git-wip-us.apache.org/repos/asf?p=incubator-quickstep-site.git
>
> He found it by modifying the address found in
> https://cwiki.apache.org/confluence/display/QUICKSTEP/
> Workflow+For+C
se, then maybe we will have to compile the jekyll files
> > locally and push them along with the markdown/config/scss/etc
> >
> > On Tue, Dec 13, 2016 at 10:10 AM, Marc Spehlmann >
> > wrote:
> >
> >> Harshad pointed out the directory is
> >>
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
s 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 req
good. You definitely cannot include
> binaries in a
> >>>> source release.
> >>>>
> >>>> The more you can remove from third_party, the better. It doesn’t have
> to
> >>>> be done this release, but the less IP there is to review,
Julian mentioned that it's unsafe to have submodules track from the head of
their respective repo because things can break unexpectedly.
I'm thinking a small change we can do is simply fix the submodules to a
release commit.
Google Test: release 1.8.0
https://github.com/google/googletest/releases
udu has a download script for dependencies in third_party folder.
> It seems to be a good example for our case.
>
> > On Jan 8, 2017, at 2:17 PM, Marc Spehlmann
> wrote:
> >
> > Regarding the IWYU script. It sounds safe then. If anything, maybe it
> > belongs
Also, IWYU script was written by Shoban
On Mon, Jan 9, 2017 at 3:39 PM, Marc Spehlmann
wrote:
> Thanks for finding these! Impala is more or less doing what we're doing,
> except it doesn't use submodules. One thing is that if you download their
> release (http://impala.apache
68 matches
Mail list logo
