Re: [VOTE] Release Apache Drill 1.18.0 - RC0

2020-09-01 Thread Volodymyr Vysotskyi
Verified checksums and signatures for binary and source tarballs and for
jars published to the maven repo.
Run all unit tests on Ubuntu with JDK 8 using tar with sources.
Run Drill in embedded mode on Ubuntu, submitted several queries, verified
that profiles displayed correctly.
Checked JDBC driver using SQuirreL SQL client and custom java client,
ensured that it works correctly with the custom authenticator.

+1 (binding)

Kind regards,
Volodymyr Vysotskyi


On Mon, Aug 31, 2020 at 1:37 PM Volodymyr Vysotskyi 
wrote:

> Hi all,
>
> I have looked into the DRILL-7785, and the problem is not in Drill, so it
> is not a blocker for the release.
> For more details please refer to my comment
> <https://issues.apache.org/jira/browse/DRILL-7785?focusedCommentId=17187629=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17187629>
> on this ticket.
>
> Kind regards,
> Volodymyr Vysotskyi
>
>
> On Mon, Aug 31, 2020 at 4:26 AM Abhishek Girish 
> wrote:
>
>> Yup we can certainly include it if RC0 fails. So far I’m inclined to not
>> consider it a blocker. I’ve requested Vova and Anton to take a look.
>>
>> So folks, please continue to test the candidate.
>>
>> On Sun, Aug 30, 2020 at 6:16 PM Charles Givre  wrote:
>>
>> > Ok.  Are you looking to include DRILL-7785?  I don't think it's a
>> blocker,
>> > but if we find anything with RC0... let's make sure we get it in.
>> >
>> > -- C
>> >
>> >
>> >
>> > > On Aug 30, 2020, at 9:14 PM, Abhishek Girish 
>> wrote:
>> >
>> > >
>> >
>> > > Hey Charles,
>> >
>> > >
>> >
>> > > I would have liked to. We did get one of the PRs merged after the
>> master
>> >
>> > > branch was closed as I hadn't made enough progress with the release
>> yet.
>> >
>> > > But that’s not the case now.
>> >
>> > >
>> >
>> > > Unless DRILL-7781 is a release blocker, we should probably skip it. So
>> > far,
>> >
>> > > a lot of effort has gone into getting RC0 ready. So I'm hoping to get
>> > this
>> >
>> > > closed asap.
>> >
>> > >
>> >
>> > > Regards,
>> >
>> > > Abhishek
>> >
>> > >
>> >
>> > > On Sun, Aug 30, 2020 at 6:07 PM Charles Givre 
>> wrote:
>> >
>> > >
>> >
>> > >> HI Abhishek,
>> >
>> > >>
>> >
>> > >> Can we merge DRILL-7781?  We really shouldn't ship something with a
>> > simple
>> >
>> > >> bug like this.
>> >
>> > >>
>> >
>> > >> -- C
>> >
>> > >>
>> >
>> > >>
>> >
>> > >>
>> >
>> > >>
>> >
>> > >>
>> >
>> > >>> On Aug 30, 2020, at 8:40 PM, Abhishek Girish 
>> > wrote:
>> >
>> > >>
>> >
>> > >>>
>> >
>> > >>
>> >
>> > >>> Advanced tests from [5] are also complete. All 7500+ tests passed,
>> > except
>> >
>> > >>
>> >
>> > >>> for a few relating to known resource issues (drillbit connectivity /
>> > OOM
>> >
>> > >>
>> >
>> > >>> /...). Plus a few with the same symptoms as DRILL-7785.
>> >
>> > >>
>> >
>> > >>>
>> >
>> > >>
>> >
>> > >>> On Sun, Aug 30, 2020 at 2:17 PM Abhishek Girish > >
>> >
>> > >> wrote:
>> >
>> > >>
>> >
>> > >>>
>> >
>> > >>
>> >
>> > >>>> Wanted to share an update on some of the testing I've done from my
>> > side:
>> >
>> > >>
>> >
>> > >>>>
>> >
>> > >>
>> >
>> > >>>> All Functional tests from [5] (plus private Customer tests) are
>> >
>> > >> complete.
>> >
>> > >>
>> >
>> > >>>> 10,000+ tests have passed. However, I did see an issue with Hive
>> ORC
>> >
>> > >> tables
>> >
>> > >>
>> >
>> > >>>> (DRILL-7785). N

Re: [VOTE] Release Apache Drill 1.18.0 - RC0

2020-08-31 Thread Volodymyr Vysotskyi
Hi all,

I have looked into the DRILL-7785, and the problem is not in Drill, so it
is not a blocker for the release.
For more details please refer to my comment
<https://issues.apache.org/jira/browse/DRILL-7785?focusedCommentId=17187629=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17187629>
on this ticket.

Kind regards,
Volodymyr Vysotskyi


On Mon, Aug 31, 2020 at 4:26 AM Abhishek Girish  wrote:

> Yup we can certainly include it if RC0 fails. So far I’m inclined to not
> consider it a blocker. I’ve requested Vova and Anton to take a look.
>
> So folks, please continue to test the candidate.
>
> On Sun, Aug 30, 2020 at 6:16 PM Charles Givre  wrote:
>
> > Ok.  Are you looking to include DRILL-7785?  I don't think it's a
> blocker,
> > but if we find anything with RC0... let's make sure we get it in.
> >
> > -- C
> >
> >
> >
> > > On Aug 30, 2020, at 9:14 PM, Abhishek Girish 
> wrote:
> >
> > >
> >
> > > Hey Charles,
> >
> > >
> >
> > > I would have liked to. We did get one of the PRs merged after the
> master
> >
> > > branch was closed as I hadn't made enough progress with the release
> yet.
> >
> > > But that’s not the case now.
> >
> > >
> >
> > > Unless DRILL-7781 is a release blocker, we should probably skip it. So
> > far,
> >
> > > a lot of effort has gone into getting RC0 ready. So I'm hoping to get
> > this
> >
> > > closed asap.
> >
> > >
> >
> > > Regards,
> >
> > > Abhishek
> >
> > >
> >
> > > On Sun, Aug 30, 2020 at 6:07 PM Charles Givre 
> wrote:
> >
> > >
> >
> > >> HI Abhishek,
> >
> > >>
> >
> > >> Can we merge DRILL-7781?  We really shouldn't ship something with a
> > simple
> >
> > >> bug like this.
> >
> > >>
> >
> > >> -- C
> >
> > >>
> >
> > >>
> >
> > >>
> >
> > >>
> >
> > >>
> >
> > >>> On Aug 30, 2020, at 8:40 PM, Abhishek Girish 
> > wrote:
> >
> > >>
> >
> > >>>
> >
> > >>
> >
> > >>> Advanced tests from [5] are also complete. All 7500+ tests passed,
> > except
> >
> > >>
> >
> > >>> for a few relating to known resource issues (drillbit connectivity /
> > OOM
> >
> > >>
> >
> > >>> /...). Plus a few with the same symptoms as DRILL-7785.
> >
> > >>
> >
> > >>>
> >
> > >>
> >
> > >>> On Sun, Aug 30, 2020 at 2:17 PM Abhishek Girish 
> >
> > >> wrote:
> >
> > >>
> >
> > >>>
> >
> > >>
> >
> > >>>> Wanted to share an update on some of the testing I've done from my
> > side:
> >
> > >>
> >
> > >>>>
> >
> > >>
> >
> > >>>> All Functional tests from [5] (plus private Customer tests) are
> >
> > >> complete.
> >
> > >>
> >
> > >>>> 10,000+ tests have passed. However, I did see an issue with Hive ORC
> >
> > >> tables
> >
> > >>
> >
> > >>>> (DRILL-7785). Need to investigate if it's a blocker for the release.
> >
> > >>
> >
> > >>>>
> >
> > >>
> >
> > >>>> Of course, all unit tests (part of the AD repo) - for both default
> and
> >
> > >>
> >
> > >>>> 'mapr' profiles are also successful.
> >
> > >>
> >
> > >>>>
> >
> > >>
> >
> > >>>>
> >
> > >>
> >
> > >>>>
> >
> > >>
> >
> > >>>> [5] https://github.com/mapr/drill-test-framework
> >
> > >>
> >
> > >>>>
> >
> > >>
> >
> > >>>> On Sun, Aug 30, 2020 at 10:14 AM Abhishek Girish <
> agir...@apache.org>
> >
> > >>
> >
> > >>>> wrote:
> >
> > >>
> >
> > >>>>
> >
> > >>
> >
> > >>>>> Hi all,
> >
> > >>
> >
> > >>>>>
> >
> 

Re: Problem running Drill in a Docker container in OpenShift

2020-01-29 Thread Volodymyr Vysotskyi
Hi all,

We have an image that includes the 1.17 release binaries:
apache/drill:1.17.0. It is a good point to try building a new image on top
of the existing one with the commands you need.

Kind regards,
Volodymyr Vysotskyi


On Wed, Jan 29, 2020 at 9:10 AM Paul Rogers 
wrote:

> Hi Ron,
>
> I don't think anyone on the Drill team has access to an OpenShift
> environment. Let's see if we can use your work to ensure that the Docker
> image supports OpenShift in the future.
>
> Please explain a bit more about the file permissions issue. Is the file
> owned by a user other than the one that runs Drill? If so, sounds like a
> bug, unless OpenShift uses a different user than plain Docker would.
>
>
> I believe our standard image is for building Drill. What you want is an
> image that uses an existing Drill build. The "SNAPSHOT" refers to the
> current master version of the code, which is probably not what you want.
> You want the released 1.17 binaries since you want to use, not develop,
> Drill.
>
> Question for the team: do we have a separate image for folks who want to
> run the latest 1.17 release?
>
> Short term, the best solution would be if you can build an image based on
> the existing Drill image rather than making a copy of the Dockerfile. If we
> understand the original file permission problem, perhaps we can find a way
> to fix that.
>
> Are you looking to run Drill in embedded mode (Sqlline in a container, you
> ssh into the container; config lost on Drill shutdown) or in server mode
> (config stored in ZK so it persists across container runs)?
>
>
> Thanks,
> - Paul
>
>
>
> On Tuesday, January 28, 2020, 9:41:28 PM PST, Ron Cecchini <
> roncecch...@comcast.net> wrote:
>
>
> Hi, all.  Drill and OpenShift newbie here.
>
> Has anyone successfully deployed a Drill Docker container to an OpenShift
> environment?
>
> While there is information about Drill Docker, there seems to be zero
> information about OpenShift in particular.
>
> Per the instructions at drill.apache.org/docs/running-drill-on-docker, I
> pulled the Drill Docker image from Docker Hub, and then pushed it to our
> OpenShift environment.  But when I tried to deploy it, I immediately ran
> into an error about /opt/drill/conf/drill-override.conf not being readable.
>
> I understand why the problem is happening (because of who OpenShift runs
> the container as), so I downloaded the source from GitHub and modified the
> Dockerfile to include:
>
> RUN chgrp -R 0 /opt/drill && chmod -R g=u /opt/drill
>
> so that all of /opt/drill would be available to everyone.  But then
> 'docker build' kept failing, giving the error:
>
> Non-resolvable parent POM for
> org.apache.drill:drill-root:1.18.0-SNAPSHOT:
> Could not transfer artifact org.apache:apache:pom:21
>
> I tried researching that error but couldn't figure out what was going on.
> So I finally decided to start trying to mount persistent volumes, creating
> one PV for /opt/drill/conf (and then copying the default
> drill-override.conf there) and one PV for /opt/drill/log.
>
> Now the container gets much further, but eventually fails on something
> Hadoop related.  I'm not trying to do anything with Hadoop, so I don't know
> what that's about, but it says I don't have HADOOP_HOME set.
>
> Hopefully I can figure out the remaining steps I need (an environment
> variable?  more configs?), but I was wondering if anyone else had already
> successfully figured out how to deploy to OpenShift, or might know why the
> 'docker build' fails with that error?
>
> For what it's worth, I copied over only that drill-override.conf and
> nothing else.  And I did not set any Drill environment variables in
> OpenShift.  I'm basically trying to run the "vanilla" Drill Docker as-is.
>
> Thanks for any help!
>
> Ron
>


Official Apache Drill Docker Images

2020-01-09 Thread Volodymyr Vysotskyi
Hi all,

Some time ago we have introduced Docker Images for Drill and published them
under custom repository.
But now we have Official Docker Repository for Apache Drill placed in
https://hub.docker.com/r/apache/drill.

All images from our previous repository were pushed there and also
DockerHub Automated Build was set up for the master branch which publishes
images with master tag after the master branch is updated.

Feel free to test it, and now even on the actual master branch!

For the instructions on how to run Drill on Docker, please refer to
https://drill.apache.org/docs/running-drill-on-docker/.

Kind regards,
Volodymyr Vysotskyi


Re: [VOTE] Release Apache Drill 1.17.0 - RC2

2019-12-28 Thread Volodymyr Vysotskyi
Hi all,

Since the release is finished, the master branch is opened for new commits.

Kind regards,
Volodymyr Vysotskyi


On Sat, Dec 28, 2019 at 10:56 AM Paul Rogers 
wrote:

> Hi Arina,
>
> Thanks much to everyone who helped with the release; it is quite a bit of
> work. Coordinating on doing the release builds sounds like a good plan. A
> huge THANK YOU to Vova for gathering the release instructions!
>
> Thanks,
> - Paul
>
>
>
> On Friday, December 27, 2019, 11:06:44 PM PST, Arina Yelchiyeva <
> arina.yelchiy...@gmail.com> wrote:
>
>  If release manager does not have access to the test cluster to run all
> tests, before starting the release he can ask, those who have, to run tests
> on the commit on which release candidate will be prepared. Other than that,
> all the remaining steps does not require any special environment setup.
> Vova is going to add release instruction and scripts to the Drill project
> soon.
>
> Kind regards,
> Arina
>
>


[ANNOUNCE] Apache Drill 1.17.0 Released

2019-12-26 Thread Volodymyr Vysotskyi
On behalf of the Apache Drill community, I am happy to announce the release
of Apache Drill 1.17.0.

Drill is an Apache open-source SQL query engine for Big Data exploration.
Drill is designed from the ground up to support high-performance analysis
on the semi-structured and rapidly evolving data coming from modern Big
Data applications, while still providing the familiarity and ecosystem of
ANSI SQL, the industry-standard query language. Drill provides
plug-and-play integration with existing Apache Hive and Apache HBase
deployments.

For information about Apache Drill, and to get involved, visit the project
website [1].

Total of 200 JIRA's are resolved in this release of Drill with following
new features and improvements [2]:

- Hive complex types support (DRILL-7251,
DRILL-7252, DRILL-7253, DRILL-7254)
- ESRI Shapefile (shp) (DRILL-4303) and Excel (DRILL-7177) format
plugins support
- Drill Metastore support (DRILL-7272, DRILL-7273, DRILL-7357)
- Upgrade to HADOOP-3.2 (DRILL-6540)
- Schema Provision using File / Table Function (DRILL-6835)
- Parquet runtime row group pruning (DRILL-7062)
- User-Agent UDFs (DRILL-7343)
- Canonical Map support (DRILL-7096)
- Kafka storage plugin improvements
(DRILL-6739, DRILL-6723, DRILL-7164, DRILL-7290, DRILL-7388)

For the full list please see release notes [3].

The binary and source artifacts are available here [4].

Thanks to everyone in the community who contributed to this release!

1. https://drill.apache.org/
2. https://drill.apache.org/blog/2019/12/26/drill-1.17-released/
3. https://drill.apache.org/docs/apache-drill-1-17-0-release-notes/
4. https://drill.apache.org/download/

Kind regards,
Volodymyr Vysotskyi


[RESULT] [VOTE] Release Apache Drill 1.17.0 - RC2

2019-12-25 Thread Volodymyr Vysotskyi
The vote passes. Thanks to everyone who has tested the release candidate
and given their comments and votes. Final tally:

3x +1 (binding): Arina, Charles, Vova

2x +1 (non-binding): Denys, Holger

No 0s or -1s.

I'll start process for pushing the release artifacts and send an
announcement once propagated.

Kind regards,
Volodymyr Vysotskyi


Fwd: [VOTE] Release Apache Drill 1.17.0 - RC2

2019-12-25 Thread Volodymyr Vysotskyi
Voting ends now. Thanks everybody who voted!
I'll post the results soon.

Kind regards,
Volodymyr Vysotskyi


On Wed, Dec 25, 2019 at 4:47 PM  wrote:

> + Installed from binary tar archive
> + RC files have been replaced with stabile versions
> + JDBC connect with custom authenticator
> + Basic queries (CSV, text manipulation, join, etc.)
> + Logged in to web UI, reviewed profiles & logs, submitted trivial queries
>
> LGTM
> +1 (non-binding)
>
> Thx & BR
> Holger
>


[VOTE] Release Apache Drill 1.17.0 - RC2

2019-12-22 Thread Volodymyr Vysotskyi
Hi all,

I'd like to propose the third release candidate (RC2) of Apache Drill,
version 1.17.0.

Changes since the previous release candidate: fixed show-stopper DRILL-7494
<https://issues.apache.org/jira/browse/DRILL-7494>.

The release candidate covers a total of 205 resolved JIRAs [1]. Thanks to
everyone who contributed to this release.

The tarball artifacts are hosted at [2] and the maven artifacts are hosted
at [3].

This release candidate is based on
commit 2eb6bbe0501cb6553106e63dc1f2810ff10ae375 located at [4].

Please download and try out the release.

The vote ends at 5 PM UTC (9 AM PDT, 7 PM EET, 10:30 PM IST), December 25,
2019

[ ] +1
[ ] +0
[ ] -1

Here's my vote: +1

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344870
[2] http://home.apache.org/~volodymyr/drill/releases/1.17.0/rc2/
[3] https://repository.apache.org/content/repositories/orgapachedrill-1077/
[4] https://github.com/vvysotskyi/drill/commits/drill-1.17.0

Kind regards,
Volodymyr Vysotskyi


[VOTE] Release Apache Drill 1.17.0 - RC1

2019-12-17 Thread Volodymyr Vysotskyi
Hi all,

I'd like to propose the second release candidate (RC1) of Apache Drill,
version 1.17.0.

Changes since the previous release candidate: fixed the following
show-stoppers: DRILL-7484 <https://issues.apache.org/jira/browse/DRILL-7484>
, DRILL-7485 <https://issues.apache.org/jira/browse/DRILL-7485>, DRILL-6332
<https://issues.apache.org/jira/browse/DRILL-6332>, DRILL-7472
<https://issues.apache.org/jira/browse/DRILL-7472>, DRILL-7474
<https://issues.apache.org/jira/browse/DRILL-7474>, DRILL-7476
<https://issues.apache.org/jira/browse/DRILL-7476>, DRILL-7481
<https://issues.apache.org/jira/browse/DRILL-7481>, DRILL-7482
<https://issues.apache.org/jira/browse/DRILL-7482>, DRILL-7473
<https://issues.apache.org/jira/browse/DRILL-7473>, DRILL-7479
<https://issues.apache.org/jira/browse/DRILL-7479>, DRILL-7483
<https://issues.apache.org/jira/browse/DRILL-7483>, DRILL-7486
<https://issues.apache.org/jira/browse/DRILL-7486>, and DRILL-7470
<https://issues.apache.org/jira/browse/DRILL-7470>.

The release candidate covers a total of 203 resolved JIRAs [1]. Thanks to
everyone who contributed to this release.

The tarball artifacts are hosted at [2] and the maven artifacts are hosted
at [3].

This release candidate is based on commit
d65d2b4cc2aa5ea7a59cd40d0ad57a1e4639ae12 located at [4].

Please download and try out the release.

The vote ends at 5 PM UTC (9 AM PDT, 7 PM EET, 10:30 PM IST), December 20,
2019

[ ] +1
[ ] +0
[ ] -1

Here's my vote: +1

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344870
[2] http://home.apache.org/~volodymyr/drill/releases/1.17.0/rc1/
[3] https://repository.apache.org/content/repositories/orgapachedrill-1076/
[4] https://github.com/vvysotskyi/drill/commits/drill-1.17.0

Kind regards,
Volodymyr Vysotskyi


[ANNOUNCE] New PMC member: Ihor Guzenko

2019-12-13 Thread Volodymyr Vysotskyi
I am pleased to announce that Drill PMC invited Ihor Guzenko to
the PMC and he has accepted the invitation.

Congratulations Ihor and welcome!

- Vova
(on behalf of Drill PMC)


Re: [VOTE] Release Apache Drill 1.17.0 - RC0

2019-12-11 Thread Volodymyr Vysotskyi
Thank you all for pointing out these issues.

The vote for Apache Drill 1.17.0 - RC0 is canceled due to DRILL-7473
<https://issues.apache.org/jira/browse/DRILL-7473> and DRILL-7476
<https://issues.apache.org/jira/browse/DRILL-7476>.

I'll create a new release candidate when these issues are fixed.

Kind regards,
Volodymyr Vysotskyi


On Tue, Dec 10, 2019 at 3:34 PM Arina Yelchiyeva 
wrote:

> And one more regression: https://issues.apache.org/jira/browse/DRILL-7476
> <https://issues.apache.org/jira/browse/DRILL-7476>
>
> Kind regards,
> Arina
>
> > On Dec 10, 2019, at 1:59 PM, Igor Guzenko 
> wrote:
> >
> > Hi all,
> >
> > I've found regression with repeated maps in parquet [1]. Also I
> personally
> > don't like that difference between previous and current tar.gz size is
> 124
> > Mb.
> >
> > My vote: -1.
> >
> > [1] https://issues.apache.org/jira/browse/DRILL-7473
> >
> > Thanks,
> > Igor
> >
> >
> > On Mon, Dec 9, 2019 at 2:47 PM Volodymyr Vysotskyi  >
> > wrote:
> >
> >> Hi all,
> >>
> >> I'd like to propose the first release candidate (RC0) of Apache Drill,
> >> version 1.17.0.
> >>
> >> The release candidate covers a total of 190 resolved JIRAs [1]. Thanks
> to
> >> everyone who contributed to this release.
> >>
> >> The tarball artifacts are hosted at [2] and the maven artifacts are
> hosted
> >> at [3].
> >>
> >> This release candidate is based on commit
> >> 4171eeac876249731ccf86d116455dd8d53c44e9 located at [4].
> >>
> >> The vote ends at 13:00 PM UTC (5:00 AM PST, 3:00 PM EET, 6:30 PM IST),
> >> December 12, 2019.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >>
> >> Here's my vote: +1
> >>
> >> [1]
> >>
> >>
> https://issues.apache.org/jira/secure/Releashttps://github.com/vvysotskyi/drill/commits/drill-1.17.0eNote.jspa?projectId=12313820=12344870
> >> <
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344870
> >>>
> >> [2] http://home.apache.org/~volodymyr/drill/releases/1.17.0/rc0/
> >> [3]
> >> https://repository.apache.org/content/repositories/orgapachedrill-1075/
> >> [4] https://github.com/vvysotskyi/drill/commits/drill-1.17.0
> >>
> >> Kind regards,
> >> Volodymyr Vysotskyi
> >>
>
>


[VOTE] Release Apache Drill 1.17.0 - RC0

2019-12-09 Thread Volodymyr Vysotskyi
Hi all,

I'd like to propose the first release candidate (RC0) of Apache Drill,
version 1.17.0.

The release candidate covers a total of 190 resolved JIRAs [1]. Thanks to
everyone who contributed to this release.

The tarball artifacts are hosted at [2] and the maven artifacts are hosted
at [3].

This release candidate is based on commit
4171eeac876249731ccf86d116455dd8d53c44e9 located at [4].

The vote ends at 13:00 PM UTC (5:00 AM PST, 3:00 PM EET, 6:30 PM IST),
December 12, 2019.

[ ] +1
[ ] +0
[ ] -1

Here's my vote: +1

[1]
https://issues.apache.org/jira/secure/Releashttps://github.com/vvysotskyi/drill/commits/drill-1.17.0eNote.jspa?projectId=12313820=12344870
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344870>
[2] http://home.apache.org/~volodymyr/drill/releases/1.17.0/rc0/
[3] https://repository.apache.org/content/repositories/orgapachedrill-1075/
[4] https://github.com/vvysotskyi/drill/commits/drill-1.17.0

Kind regards,
Volodymyr Vysotskyi


Re: [ANNOUNCE] New PMC Chair of Apache Drill

2019-08-22 Thread Volodymyr Vysotskyi
Congratulations, Charles!

And thanks Arina for your effort to grow the community and make the project
much better!
It will be hard to keep the bar so high, but for now, I know who tops my
chart of PMC chairs :)

Kind regards,
Volodymyr Vysotskyi


On Thu, Aug 22, 2019 at 10:39 AM Igor Guzenko 
wrote:

> Congratulations, Charles! Great job!
>
> On Thu, Aug 22, 2019 at 10:28 AM Arina Ielchiieva 
> wrote:
>
> > Hi all,
> >
> > It has been a honor to serve as Drill Chair during the past year but it's
> > high time for the new one...
> >
> > I am very pleased to announce that the Drill PMC has voted to elect
> Charles
> > Givre as the new PMC chair of Apache Drill. He has also been approved
> > unanimously by the Apache Board in last board meeting.
> >
> > Congratulations, Charles!
> >
> > Kind regards,
> > Arina
> >
>


[ANNOUNCE] New Committer: Anton Gozhyi

2019-07-29 Thread Volodymyr Vysotskyi
The Project Management Committee (PMC) for Apache Drill has invited Anton
Gozhyi to become a committer, and we are pleased to announce that he has
accepted.

Anton Gozhyi has been contributing to Drill for more than a year and a
half. He did significant contributions as a QA, including reporting
non-trivial issues and working on automation of Drill tests. All the issues
reported by Anton have a clear description of the problem, steps to
reproduce and expected behavior. Besides contributions as a QA, Anton made
high-quality fixes into Drill.

Welcome Anton, and thank you for your contributions!

- Volodymyr
(on behalf of Drill PMC)


Re: [DISCUSS]: Adding Issue Label Bot to Drill Github

2019-07-26 Thread Volodymyr Vysotskyi
Hi Charles,

Superset uses GitHub issues for tracking bugs, features, improvements, etc.
So using an issue label bot is justified since it helps to highlight
different kinds of the issues.

But Drill uses Jira for these purposes, so I'm not sure that we should add
this to the Drill.

Kind regards,
Volodymyr Vysotskyi


On Sat, Jul 27, 2019 at 12:23 AM Charles Givre  wrote:

> All,
> I've been following the Apache Superset project and they use an issue
> label bot (https://github.com/marketplace/issue-label-bot <
> https://github.com/marketplace/issue-label-bot>) which, as the name
> implies, adds issue labels such as "Question", "Size" etc. automatically.
> What does the community think about adding this to Drill?
> Thanks,
> -- C


Re: [ANNOUNCE] New Committer: Bohdan Kazydub

2019-07-23 Thread Volodymyr Vysotskyi
Congratulations, Bohdan! Thanks for your contributions!

Kind regards,
Volodymyr Vysotskyi


On Thu, Jul 18, 2019 at 4:55 PM Kunal Khatua  wrote:

> Congratulations, Bohdan!
> On 7/16/2019 2:21:14 PM, Robert Hou  wrote:
> Congratulations, Bohdan. Thanks for contributing to Drill!
>
> --Robert
>
> On Tue, Jul 16, 2019 at 11:50 AM hanu mapr wrote:
>
> > Congratulations Bohdan!
> >
> > On Tue, Jul 16, 2019 at 9:30 AM Gautam Parai wrote:
> >
> > > Congratulations Bohdan!
> > >
> > > Gautam
> > >
> > > On Mon, Jul 15, 2019 at 11:53 PM Bohdan Kazydub
> > bohdan.kazy...@gmail.com>
> > > wrote:
> > >
> > > > Thank you all for your support!
> > > >
> > > > On Tue, Jul 16, 2019 at 4:16 AM weijie tong
> > > > wrote:
> > > >
> > > > > Congrats Bohdan!
> > > > >
> > > > > On Tue, Jul 16, 2019 at 12:54 AM Vitalii Diravka
> > >
> > > > > wrote:
> > > > >
> > > > > > Congrats Bohdan! Well deserved!
> > > > > >
> > > > > > Kind regards
> > > > > > Vitalii
> > > > > >
> > > > > >
> > > > > > On Mon, Jul 15, 2019 at 6:48 PM Paul Rogers
> > >
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Congrats Bohdan!
> > > > > > > - Paul
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Monday, July 15, 2019, 01:08:04 AM PDT, Arina Ielchiieva
> > > > > > > ar...@apache.org> wrote:
> > > > > > >
> > > > > > > The Project Management Committee (PMC) for Apache Drill has
> > > invited
> > > > > > Bohdan
> > > > > > > Kazydub to become a committer, and we are pleased to announce
> > that
> > > he
> > > > > has
> > > > > > > accepted.
> > > > > > >
> > > > > > > Bohdan has been contributing into Drill for more than a year.
> His
> > > > > > > contributions include
> > > > > > > logging and various functions handling improvements, planning
> > > > > > optimizations
> > > > > > > and S3 improvements / fixes. His recent work includes Calcite
> > 1.19
> > > /
> > > > > 1.20
> > > > > > > [DRILL-7200] and implementation of canonical Map
> > [DRILL-7096].
> > > > > > >
> > > > > > > Welcome Bohdan, and thank you for your contributions!
> > > > > > >
> > > > > > > - Arina
> > > > > > > (on behalf of the Apache Drill PMC)
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: [ANNOUNCE] New Committer: Igor Guzenko

2019-07-23 Thread Volodymyr Vysotskyi
Congratulations, Ihor! Thanks for your contributions!

Kind regards,
Volodymyr Vysotskyi


On Mon, Jul 22, 2019 at 5:02 PM Arina Ielchiieva  wrote:

> The Project Management Committee (PMC) for Apache Drill has invited Igor
> Guzenko to become a committer, and we are pleased to announce that he has
> accepted.
>
> Igor has been contributing into Drill for 9 months and made a number of
> significant contributions, including cross join syntax support, Hive views
> support, as well as improving performance for Hive show schema and unit
> tests. Currently he is working on supporting Hive complex types
> [DRILL-3290]. He already added support for list type and working on struct
> and canonical map.
>
> Welcome Igor, and thank you for your contributions!
>
> - Arina
> (on behalf of the Apache Drill PMC)
>


Apache Drill Hangout - May 28, 2019

2019-05-27 Thread Volodymyr Vysotskyi
Hi Drillers,

We will have our bi-weekly hangout tomorrow May 28th, at 10 AM PST
(link: https://meet.google.com/yki-iqdf-tai ).

If there are any topics you would like to discuss during the hangout please
respond to this email.

Kind regards,
Volodymyr Vysotskyi


Re: May Apache Drill board report

2019-05-03 Thread Volodymyr Vysotskyi
Looks good, +1


Пт, 3 трав. 2019 23:32 користувач Arina Ielchiieva  пише:

> Hi all,
>
> please take a look at the draft board report for the last quarter and let
> me know if you have any comments.
>
> Thanks,
> Arina
>
> =
>
> ## Description:
> - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud
>   Storage.
>
> ## Issues:
>  - There are no issues requiring board attention at this time.
>
> ## Activity:
> - Since the last board report, Drill has released version 1.16.0, including
>   the following enhancements:
>   - CREATE OR REPLACE SCHEMA command to define a schema for text files
>   - REFRESH TABLE METADATA command can generate metadata cache files for
>   specific columns
>   - ANALYZE TABLE statement to computes statistics on Parquet data
>   - SYSLOG (RFC-5424) Format Plugin
>   - NEAREST DATE function to facilitate time series analysis
>   - Format plugin for LTSV files
>   - Ability to query Hive views
>   - Upgrade to SQLLine 1.7
>   - Apache Calcite upgrade to 1.18.0
>   - Several Drill Web UI improvements, including:
>  - Storage plugin management improvements
>  - Query progress indicators and warnings
>  - Ability to limit the result size for better UI response
>  - Ability to sort the list of profiles in the Drill Web UI
>  - Display query state in query result page
>  - Button to reset the options filter
>
> - Drill User Meetup will be held on May 22, 2019. Two talks are planned:
>   - Alibaba's Usage of Apache Drill for querying a Time Series Database
>   - What’s new with Apache Drill 1.16 & a demo of Schema Provisioning
>
> ## Health report:
> - The project is healthy. Development activity as reflected in the pull
>   requests and JIRAs is good.
> - Activity on the dev and user mailing lists are stable.
> - One PMC member was added in the last period.
>
> ## PMC changes:
>
> - Currently 24 PMC members.
> - Sorabh Hamirwasia was added to the PMC on Fri Apr 05 2019
>
> ## Committer base changes:
>
> - Currently 51 committers.
> - No new committers added in the last 3 months
> - Last committer addition was Salim Achouche at Mon Dec 17 2018
>
> ## Releases:
>
> - 1.16.0 was released on Thu May 02 2019
>
> ## Mailing list activity:
>
> - d...@drill.apache.org:
>- 406 subscribers (down -10 in the last 3 months):
>- 2299 emails sent to list (1903 in previous quarter)
>
> - iss...@drill.apache.org:
>- 17 subscribers (down -1 in the last 3 months):
>- 2373 emails sent to list (2233 in previous quarter)
>
> - user@drill.apache.org:
>- 582 subscribers (down -15 in the last 3 months):
>- 235 emails sent to list (227 in previous quarter)
>
> ## JIRA activity:
>
> - 214 JIRA tickets created in the last 3 months
> - 212 JIRA tickets closed/resolved in the last 3 months
>


Re: [VOTE] Apache Drill Release 1.16.0 - RC2

2019-05-01 Thread Volodymyr Vysotskyi
Downloaded binary and source tarballs, verified signatures and checksums.
Run unit tests on ubuntu with JDK 8 using tar with sources (31:52 min),
built on Windows using sources tarball without any issues.
Run Drill in embedded and distributed modes on Ubuntu and in embedded mode
on Windows, submitted several TPC-DS queries, verified that profiles
displayed correctly.
Checked JDBC driver using SQuirreL SQL client and custom java client.
Verified that jars from prebuilt tar do not contain excessive files I
mentioned before.

+1 (binding)

Kind regards,
Volodymyr Vysotskyi


On Wed, May 1, 2019 at 5:50 AM Boaz Ben-Zvi  wrote:

> Downloaded both the binary and src tarballs, and verified the SHA
> signatures and the PGP.
>
> Built and ran the full unit tests on both Linux and Mac.
>
> Successfully ran some old favorite queries, and several manual tests of
> REFRESH METADATA with COLUMNS, and verified the metadata files and
> summaries.
>
>+1 from me for RC2 .
>
> -- Boaz
>
> On 4/30/19 11:26 AM, Kunal Khatua wrote:
> > Ran manual tests with random queries, trying out the UI and running
> joins on small tables.
> >
> > HOCON export of storage plugins does not actually export in HOCON
> format, but that is not a blocker.
> >
> > +1 (binding)
> >
> > ~ Kunal
> >
> > On 4/30/2019 4:53:48 AM, Arina Yelchiyeva 
> wrote:
> > Downloaded binary tarball and ran Drill in embedded mode.
> > Verified schema provisioning for text files, dynamic UDFs.
> > Ran random queries, including long-running, queried system tables,
> created tables with different formats.
> > Checked Web UI (queries, profiles, storage plugins, logs pages).
> >
> > +1 (binding)
> >
> > Kind regards,
> > Arina
> >
> >> On Apr 30, 2019, at 8:33 AM, Aman Sinha wrote:
> >>
> >> Downloaded binary tarball on my Mac and ran in embedded mode.
> >> Verified Sorabh's release signature and the tar file's checksum
> >> Did a quick glance through maven artifacts
> >> Did some manual tests with TPC-DS Web_Sales table and ran REFRESH
> METADATA
> >> command against the same table
> >> Checked runtime query profiles of above queries and verified COUNT(*),
> >> COUNT(column) optimization is getting applied.
> >> Also did a build from source on my linux VM.
> >>
> >> RC2 looks good ! +1
> >>
> >> On Fri, Apr 26, 2019 at 8:28 AM SorabhApache wrote:
> >>
> >>> Hi Drillers,
> >>> I'd like to propose the third release candidate (RC2) for the Apache
> Drill,
> >>> version 1.16.0.
> >>>
> >>> Changes since the previous release candidate:
> >>> DRILL-7201: Strange symbols in error window (Windows)
> >>> DRILL-7202: Failed query shows warning that fragments has made no
> progress
> >>> DRILL-7207: Update the copyright year in NOTICE.txt file
> >>> DRILL-7212: Add gpg key with apache.org email for sorabh
> >>> DRILL-7213: drill-format-mapr.jar contains stale git.properties file
> >>>
> >>> The RC2 includes total of 220 resolved JIRAs [1].
> >>> Thanks to everyone for their hard work to contribute to this release.
> >>>
> >>> The tarball artifacts are hosted at [2] and the maven artifacts are
> hosted
> >>> at [3].
> >>>
> >>> This release candidate is based on commit
> >>> 751e87736c2ddbc184b52cfa56f4e29c68417cfe located at [4].
> >>>
> >>> Please download and try out the release candidate.
> >>>
> >>> The vote ends at 04:00 PM UTC (09:00 AM PDT, 07:00 PM EET, 09:30 PM
> IST),
> >>> May 1st, 2019
> >>>
> >>> [ ] +1
> >>> [ ] +0
> >>> [ ] -1
> >>>
> >>> Here is my vote: +1
> >>> [1]
> >>>
> >>>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344284
> >>> [2] http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/
> >>> [3]
> >>>
> https://repository.apache.org/content/repositories/orgapachedrill-1073/
> >>> [4] https://github.com/sohami/drill/commits/drill-1.16.0
> >>>
> >>> Thanks,
> >>> Sorabh
> >>>
> >
>


Re: [VOTE] Apache Drill Release 1.16.0 - RC1

2019-04-25 Thread Volodymyr Vysotskyi
Hi Sorabh,

I have noticed that jars in prebuild tar contain some strange files, for
example, *drill-jdbc-all-1.16.0.jar* contains the following files:
*javac.sh*
*org.codehaus.plexus.compiler.javac.JavacCompiler1256088670033285178arguments*
*org.codehaus.plexus.compiler.javac.JavacCompiler1458111453480208588arguments*
*org.codehaus.plexus.compiler.javac.JavacCompiler2392560589194600493arguments*
*org.codehaus.plexus.compiler.javac.JavacCompiler4475905192586529595arguments*
*org.codehaus.plexus.compiler.javac.JavacCompiler4524532450095901144arguments*
*org.codehaus.plexus.compiler.javac.JavacCompiler4670895443631397937arguments*
*org.codehaus.plexus.compiler.javac.JavacCompiler5215058338087807885arguments*
*org.codehaus.plexus.compiler.javac.JavacCompiler7526103232425779297arguments*

which contain some info about your machine (username, etc.)

Jars from the previous release didn't contain these files. Also, I have
built master on my machine and these files are absent for me.

Could you please take a look? This problem is observed for both RCs.

Kind regards,
Volodymyr Vysotskyi


On Thu, Apr 25, 2019 at 8:20 AM SorabhApache  wrote:

> Update:
> 1) DRILL-7208 is there in 1.15 release as well, so it's not a blocker for
> 1.16
> 2) DRILL-7213: drill-format-mapr.jar contains stale git.properties file
>
>- Still investigating on the above issue.
>
> 3) DRILL-7201: Strange symbols in error window (Windows)
>
>- Issue is not reproducible on Kunal's machine. He is having discussion
>on JIRA to see if it's treated as a blocker or not.
>
> To investigate for DRILL-7213 I have to drop the RC1 candidate since again
> performing the release required to push it to my remote repo and publish to
> maven repo as well. So I don't have RC1 binaries if we consider all the
> issues as non-blocking.
>
> I will re-share the RC candidate once either fix for DRILL-7213/DRILL-7201
> are available or it's considered as non-blockers. Any thoughts?
>
> Thanks,
> Sorabh
>
> On Wed, Apr 24, 2019 at 9:17 PM Boaz Ben-Zvi  wrote:
>
> > Downloaded both the binary and src tarballs, and verified the SHA
> > signatures and the PGP.
> >
> > Built and ran the full unit tests on both Linux and Mac (took 3:05 hours
> > on my Mac).
> >
> > Successfully ran some old favorite queries with Sort/Hash-Join/Hash-Agg
> > spilling.
> >
> > Ran several manual tests of REFRESH METADATA with COLUMNS, and verified
> > the metadata files and summaries.
> >
> > Noticed that when specifying a COLUMN which a sub-field in a complex
> > type (e.g., a key in a map), the whole column (i.e. all the other keys
> > as well) was marked as "interesting"; but this may be "by design", as
> > the refresh granularity is the whole column.
> >
> > Also noticed the sys.version issue (DRILL-7208
> > <https://issues.apache.org/jira/browse/DRILL-7208>) - should be minor as
> > only affecting users of the SRC tarball, likely developers who
> > build/modify the code anyway.
> >
> > Hence my vote is  +1 .
> >
> >-- Boaz
> >
> > On 4/24/19 10:57 AM, Kunal Khatua wrote:
> > > Downloaded the tarball and tried it in embedded mode.
> > >
> > > Ran simple join queries and interacted with the WebUI.
> > >
> > > Issues confirmed were DRILL-7192 and DRILL-7203.
> > > I'm unable to repro DRILL-7201 and DRILL-7202, though I have a fix for
> > the latter. Will work with Arina to identify repro steps.
> > >
> > > None of these are blockers IMO, so I'll vote +1.
> > >
> > > ~ Kunal
> > >
> > >
> > > On 4/24/2019 10:38:31 AM, Khurram Faraaz  wrote:
> > > i see the correct version and commit, I deployed the binaries to test.
> > >
> > > Apache Drill 1.16.0
> > > "Start your SQL engine."
> > > apache drill> select * from sys.version;
> > >
> >
> +-+--+-+---+---+---+
> > > | version | commit_id |
> > > commit_message | commit_time |
> > > build_email | build_time |
> > >
> >
> +-+--+-+---+---+---+
> > > | 1.16.0 | cf5b758e0a4c22b75bfb02ac2653ff09415ddf53 |
> > > [maven-release-plugin] prepare release drill-1.16.0 | 22.04.2019 @
> > 09:08:36
> > > PDT | sor...@apache.org | 22.04.2019 @ 09:53:25 PDT |
> > 

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

2019-04-24 Thread Volodymyr Vysotskyi
Hi Aman,

There are two different issues connected with *git.properties* file.
Regarding the problem I have mentioned, prebuilt tar
(apache-drill-1.16.0.tar.gz) contains *drill-format-mapr-1.16.0.jar* jar
which contains a *git.properties* file with the incorrect version.
When *select * from sys.version* query is submitted, class loader finds the
first file named as *git.properties* from the classpath (each drill jar
contains its own *git.properties* file) and for my case file from
*drill-format-mapr-1.16.0.jar *is picked up, so the incorrect result is
returned. But it may not be reproducible for other machines since it
depends on the order of files for the class loader.

Regarding the problem Anton has mentioned, Drill should be built from the
sources (apache-drill-1.16.0-src.tar.gz), and for that version, *select *
from sys.version* returns the result without information about commit.

Kind regards,
Volodymyr Vysotskyi


On Wed, Apr 24, 2019 at 6:33 PM Aman Sinha  wrote:

> This works fine for me with the binary tarball that I installed on my Mac.
> ..it shows the correct commit message.
>
> Apache Drill 1.16.0
>
> "This isn't your grandfather's SQL."
>
> apache drill> *select* * *from* sys.version;
>
>  
> +-+--+-+---+---+---+
> | version |commit_id |
>  commit_message|commit_time|
> build_email|build_time |
>
> +-+--+-+---+---+---+
> | 1.16.0  | cf5b758e0a4c22b75bfb02ac2653ff09415ddf53 |
> [maven-release-plugin] prepare release drill-1.16.0 | 22.04.2019 @ 09:08:36
> PDT | sor...@apache.org | 22.04.2019 @ 09:54:09 PDT |
>
> +-+--+-+---+---+---+
>
> I don't see any extraneous git.properties anywhere in the source
> distribution that I downloaded:
>
> [root@aman1 apache-drill-1.16.0-src]# find . -name "git.properties"
>
>
> ./distribution/target/apache-drill-1.16.0/apache-drill-1.16.0/git.properties
>
> ./git.properties
>
>
>
> On Wed, Apr 24, 2019 at 4:51 AM Arina Ielchiieva  wrote:
>
> > Taking into account previous emails, looks like we'll need to have new
> RC.
> > I also suggest to include
> https://issues.apache.org/jira/browse/DRILL-7201
> > into
> > new RC.
> >
> > Kind regards,
> > Arina
> >
> > On Wed, Apr 24, 2019 at 2:44 PM Volodymyr Vysotskyi <
> volody...@apache.org>
> > wrote:
> >
> > > Also, I have noticed that for the prebuilt tar, the following query on
> my
> > > machine returns the wrong results:
> > >
> > > apache drill> select * from sys.version;
> > >
> > >
> >
> +-+--++---+---+---+
> > > | version |commit_id |
> > >commit_message |commit_time|
> > > build_email|build_time |
> > >
> > >
> >
> +-+--++---+---+---+
> > > | 1.16.0  | b3db1ff4b0d29210593c4485125578cca7a64b42 | DRILL-7188:
> Revert
> > > DRILL-6642: Update protocol-buffers version | 21.04.2019 @ 15:35:28
> PDT |
> > > sor...@apache.org | 22.04.2019 @ 09:07:35 PDT |
> > >
> > >
> >
> +-+--++---+-------+---+
> > > 1 row selected (1.318 seconds)
> > >
> > > The root cause for this problem is that drill-format-mapr-1.16.0.jar
> jar
> > > contains git.properties file with incorrect version, and this file was
> > the
> > > first one which was found by the class loader.
> > >
> > > I think this is a blocker for the release.
> > >
> > > Kind regards,
> > > Volodymyr Vysotskyi
> > >
> > >
> > > On Wed, Apr 24, 2019 at 2:31 PM Anton Gozhiy 

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

2019-04-24 Thread Volodymyr Vysotskyi
Also, I have noticed that for the prebuilt tar, the following query on my
machine returns the wrong results:

apache drill> select * from sys.version;
+-+--++---+---+---+
| version |commit_id |
   commit_message |commit_time|
build_email|build_time |
+-+--++---+---+---+
| 1.16.0  | b3db1ff4b0d29210593c4485125578cca7a64b42 | DRILL-7188: Revert
DRILL-6642: Update protocol-buffers version | 21.04.2019 @ 15:35:28 PDT |
sor...@apache.org | 22.04.2019 @ 09:07:35 PDT |
+-+--++---+---+---+
1 row selected (1.318 seconds)

The root cause for this problem is that drill-format-mapr-1.16.0.jar jar
contains git.properties file with incorrect version, and this file was the
first one which was found by the class loader.

I think this is a blocker for the release.

Kind regards,
Volodymyr Vysotskyi


On Wed, Apr 24, 2019 at 2:31 PM Anton Gozhiy  wrote:

> Clarification to my last message:
> I downloaded Drill from here:
>
> http://home.apache.org/~sorabh/drill/releases/1.16.0/rc1/apache-drill-1.16.0-src.tar.gz
> and built it by command:
> mvn clean install -DskipTests
>
> On Wed, Apr 24, 2019 at 1:53 PM Anton Gozhiy  wrote:
>
> > Hi All,
> >
> > I found an issue with Drill version, used the provided rc1 source:
> > apache drill> select * from sys.version;
> >
> >
> +-+---++-+-++
> > | version | commit_id | commit_message | commit_time | build_email |
> > build_time |
> >
> >
> +-+---++-+-++
> > | 1.16.0  | Unknown   || | Unknown |
> >   |
> >
> >
> +-+---++-+-++
> >
> > Although there is a valid git.properties file in the Drill root
> directory:
> > #Generated by Git-Commit-Id-Plugin
> > #Mon Apr 22 09:52:07 PDT 2019
> > git.branch=cf5b758e0a4c22b75bfb02ac2653ff09415ddf53
> > git.build.host=SHamirw-E755.local
> > git.build.time=22.04.2019 @ 09\:52\:07 PDT
> > git.build.user.email=sor...@apache.org
> > git.build.user.name=Sorabh Hamirwasia
> > git.build.version=1.16.0
> > git.closest.tag.commit.count=0
> > git.closest.tag.name=drill-1.16.0
> > git.commit.id=cf5b758e0a4c22b75bfb02ac2653ff09415ddf53
> > git.commit.id.abbrev=cf5b758
> > git.commit.id.describe=drill-1.16.0-0-gcf5b758
> > git.commit.id.describe-short=drill-1.16.0-0
> > git.commit.message.full=[maven-release-plugin] prepare release
> drill-1.16.0
> > git.commit.message.short=[maven-release-plugin] prepare release
> > drill-1.16.0
> > git.commit.time=22.04.2019 @ 09\:08\:36 PDT
> > git.commit.user.email=sor...@apache.org
> > git.commit.user.name=Sorabh Hamirwasia
> > git.dirty=false
> > git.remote.origin.url=https\://github.com/apache/drill.git
> > git.tags=drill-1.16.0
> > git.total.commit.count=3568
> >
> > But looks like it doesn't get into the classpath.
> > Could someone take a look into this?
> >
> > Thanks!
> >
> > On Wed, Apr 24, 2019 at 11:50 AM Volodymyr Vysotskyi <
> volody...@apache.org>
> > wrote:
> >
> >> Hi Sorabh,
> >>
> >> Sorry for being picky, but looks like the key you have published was
> >> generated for non-apache email: sohami.apa...@gmail.com. According to
> the
> >> [1], it is highly recommended to use Apache email address as the primary
> >> User-ID.
> >>
> >> [1] https://www.apache.org/dev/release-signing#user-id
> >>
> >> Kind regards,
> >> Volodymyr Vysotskyi
> >>
> >>
> >> On Wed, Apr 24, 2019 at 10:10 AM Jyothsna Reddy  >
> >> wrote:
> >>
> >> > Built it from cloning the git branch and unit tests on my Linux VM
> (time
> >> > taken - 43 min).
> >> > Tested new features of metadata caching by creating v4 cache files
> using
> >> > new Refresh Metadata commands and manually verified the cache files.
> >> Tried
> >> >

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

2019-04-23 Thread Volodymyr Vysotskyi
Sorabh, could you please add your key to the
https://dist.apache.org/repos/dist/release/drill/KEYS file?

Not sure that it is a blocker, but the year in NOTICE is 2018.

Do we have any guides for basic checks for release? If no, it would be good
to introduce such a list of things to check for the release manager.

Kind regards,
Volodymyr Vysotskyi


On Tue, Apr 23, 2019 at 11:09 PM Aman Sinha  wrote:

> Downloaded source tarball on my Linux VM and built and ran unit tests
> successfully (elapsed time 46 mins).
> Downloaded binary tarball on my Mac  and ran in embedded mode.
> Verified Sorabh's release signature using  gpg --verify
> Checked the maven artifacts are published
> Checked Ran a few queries against TPC-DS SF1 and examined query profiles in
> the Web UI.  Looked good.
> Did a few manual tests with REFRESH METADATA by creating the new V4
> metadata cache and checked EXPLAIN plans and query results.
> Found an issue with control-c handling and filed DRILL-7198  and noted in
> the JIRA that I don't think it is a blocker.
>
> Overall, release looks good !  +1
>
> Aman
>
>
> On Tue, Apr 23, 2019 at 10:01 AM SorabhApache  wrote:
>
> > Thanks Aman and Volodymyr for discussing on this issue. Just to clarify
> on
> > the thread that RC1 still stands as valid, since the issue is not blocker
> > anymore.
> >
> > On Tue, Apr 23, 2019 at 9:18 AM Volodymyr Vysotskyi <
> volody...@apache.org>
> > wrote:
> >
> > > Discussed with Aman and concluded that this issue is not a blocker for
> > the
> > > release.
> > >
> > > Kind regards,
> > > Volodymyr Vysotskyi
> > >
> > >
> > > On Tue, Apr 23, 2019 at 6:39 PM Aman Sinha 
> wrote:
> > >
> > > > Hi Vova,
> > > > I added some thoughts in the DRILL-7195 JIRA.
> > > >
> > > > Aman
> > > >
> > > > On Tue, Apr 23, 2019 at 6:06 AM Volodymyr Vysotskyi <
> > > volody...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I did some checks and found the following issues:
> > > > > - DRILL-7195 <https://issues.apache.org/jira/browse/DRILL-7195>
> > > > > - DRILL-7194 <https://issues.apache.org/jira/browse/DRILL-7194>
> > > > > - DRILL-7192 <https://issues.apache.org/jira/browse/DRILL-7192>
> > > > >
> > > > > One of them (DRILL-7194) is also reproduced on the previous
> version,
> > > > > another is connected with the new feature (DRILL-7192), so I don't
> > > think
> > > > > that we should treat them as blockers.
> > > > > The third one (DRILL-7195) is a regression and in some cases may
> > cause
> > > > the
> > > > > wrong results, so I think that it should be fixed before the
> release.
> > > > > Any thoughts?
> > > > >
> > > > > Kind regards,
> > > > > Volodymyr Vysotskyi
> > > > >
> > > > >
> > > > > On Mon, Apr 22, 2019 at 8:58 PM SorabhApache 
> > > wrote:
> > > > >
> > > > > > *< Please disregard previous email, one of the link is not
> correct
> > in
> > > > it.
> > > > > > Use the information in this email instead >*
> > > > > >
> > > > > > Hi Drillers,
> > > > > > I'd like to propose the second release candidate (RC1) for the
> > Apache
> > > > > > Drill,
> > > > > > version 1.16.0.
> > > > > >
> > > > > > Changes since the previous release candidate:
> > > > > > DRILL-7185: Drill Fails to Read Large Packets
> > > > > > DRILL-7186: Missing storage.json REST endpoint
> > > > > > DRILL-7190: Missing backward compatibility for REST API with
> > > DRILL-6562
> > > > > >
> > > > > > Also below 2 JIRA's were created to separately track revert of
> > > protbuf
> > > > > > changes in 1.16.0:
> > > > > > DRILL-7188: Revert DRILL-6642: Update protocol-buffers version
> > > > > > DRILL-7189: Revert DRILL-7105 Error while building the Drill
> native
> > > > > client
> > > > > >
> > > > > > The RC1 includes total of 215 resolved JIRAs [1].
> > > > > > Thanks to everyone for their hard work to contribute to this
> > release.
> > > > > >
> > > > > > The tarball artifacts are hosted at [2] and the maven artifacts
> are
> > > > > hosted
> > > > > > at [3].
> > > > > >
> > > > > > This release candidate is based on commit
> > > > > > cf5b758e0a4c22b75bfb02ac2653ff09415ddf53 located at [4].
> > > > > >
> > > > > > Please download and try out the release candidate.
> > > > > >
> > > > > > The vote ends at 06:00 PM UTC (11:00 AM PDT, 09:00 PM EET, 11:30
> PM
> > > > IST),
> > > > > > Apr 25th, 2019
> > > > > >
> > > > > > [ ] +1
> > > > > > [ ] +0
> > > > > > [ ] -1
> > > > > >
> > > > > > Here is my vote: +1
> > > > > >   [1]
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344284
> > > > > >   [2] http://home.apache.org/~sorabh/drill/releases/1.16.0/rc1/
> > > > > >   [3]
> > > > > >
> > > >
> > https://repository.apache.org/content/repositories/orgapachedrill-1067/
> > > > > >   [4] https://github.com/sohami/drill/commits/drill-1.16.0
> > > > > >
> > > > > > Thanks,
> > > > > > Sorabh
> > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: [VOTE] Apache Drill Release 1.16.0 - RC1

2019-04-23 Thread Volodymyr Vysotskyi
Discussed with Aman and concluded that this issue is not a blocker for the
release.

Kind regards,
Volodymyr Vysotskyi


On Tue, Apr 23, 2019 at 6:39 PM Aman Sinha  wrote:

> Hi Vova,
> I added some thoughts in the DRILL-7195 JIRA.
>
> Aman
>
> On Tue, Apr 23, 2019 at 6:06 AM Volodymyr Vysotskyi 
> wrote:
>
> > Hi all,
> >
> > I did some checks and found the following issues:
> > - DRILL-7195 <https://issues.apache.org/jira/browse/DRILL-7195>
> > - DRILL-7194 <https://issues.apache.org/jira/browse/DRILL-7194>
> > - DRILL-7192 <https://issues.apache.org/jira/browse/DRILL-7192>
> >
> > One of them (DRILL-7194) is also reproduced on the previous version,
> > another is connected with the new feature (DRILL-7192), so I don't think
> > that we should treat them as blockers.
> > The third one (DRILL-7195) is a regression and in some cases may cause
> the
> > wrong results, so I think that it should be fixed before the release.
> > Any thoughts?
> >
> > Kind regards,
> > Volodymyr Vysotskyi
> >
> >
> > On Mon, Apr 22, 2019 at 8:58 PM SorabhApache  wrote:
> >
> > > *< Please disregard previous email, one of the link is not correct in
> it.
> > > Use the information in this email instead >*
> > >
> > > Hi Drillers,
> > > I'd like to propose the second release candidate (RC1) for the Apache
> > > Drill,
> > > version 1.16.0.
> > >
> > > Changes since the previous release candidate:
> > > DRILL-7185: Drill Fails to Read Large Packets
> > > DRILL-7186: Missing storage.json REST endpoint
> > > DRILL-7190: Missing backward compatibility for REST API with DRILL-6562
> > >
> > > Also below 2 JIRA's were created to separately track revert of protbuf
> > > changes in 1.16.0:
> > > DRILL-7188: Revert DRILL-6642: Update protocol-buffers version
> > > DRILL-7189: Revert DRILL-7105 Error while building the Drill native
> > client
> > >
> > > The RC1 includes total of 215 resolved JIRAs [1].
> > > Thanks to everyone for their hard work to contribute to this release.
> > >
> > > The tarball artifacts are hosted at [2] and the maven artifacts are
> > hosted
> > > at [3].
> > >
> > > This release candidate is based on commit
> > > cf5b758e0a4c22b75bfb02ac2653ff09415ddf53 located at [4].
> > >
> > > Please download and try out the release candidate.
> > >
> > > The vote ends at 06:00 PM UTC (11:00 AM PDT, 09:00 PM EET, 11:30 PM
> IST),
> > > Apr 25th, 2019
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> > > Here is my vote: +1
> > >   [1]
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344284
> > >   [2] http://home.apache.org/~sorabh/drill/releases/1.16.0/rc1/
> > >   [3]
> > >
> https://repository.apache.org/content/repositories/orgapachedrill-1067/
> > >   [4] https://github.com/sohami/drill/commits/drill-1.16.0
> > >
> > > Thanks,
> > > Sorabh
> > >
> > > >
> > >
> >
>


Re: [VOTE] Apache Drill Release 1.16.0 - RC1

2019-04-23 Thread Volodymyr Vysotskyi
Hi all,

I did some checks and found the following issues:
- DRILL-7195 <https://issues.apache.org/jira/browse/DRILL-7195>
- DRILL-7194 <https://issues.apache.org/jira/browse/DRILL-7194>
- DRILL-7192 <https://issues.apache.org/jira/browse/DRILL-7192>

One of them (DRILL-7194) is also reproduced on the previous version,
another is connected with the new feature (DRILL-7192), so I don't think
that we should treat them as blockers.
The third one (DRILL-7195) is a regression and in some cases may cause the
wrong results, so I think that it should be fixed before the release.
Any thoughts?

Kind regards,
Volodymyr Vysotskyi


On Mon, Apr 22, 2019 at 8:58 PM SorabhApache  wrote:

> *< Please disregard previous email, one of the link is not correct in it.
> Use the information in this email instead >*
>
> Hi Drillers,
> I'd like to propose the second release candidate (RC1) for the Apache
> Drill,
> version 1.16.0.
>
> Changes since the previous release candidate:
> DRILL-7185: Drill Fails to Read Large Packets
> DRILL-7186: Missing storage.json REST endpoint
> DRILL-7190: Missing backward compatibility for REST API with DRILL-6562
>
> Also below 2 JIRA's were created to separately track revert of protbuf
> changes in 1.16.0:
> DRILL-7188: Revert DRILL-6642: Update protocol-buffers version
> DRILL-7189: Revert DRILL-7105 Error while building the Drill native client
>
> The RC1 includes total of 215 resolved JIRAs [1].
> Thanks to everyone for their hard work to contribute to this release.
>
> The tarball artifacts are hosted at [2] and the maven artifacts are hosted
> at [3].
>
> This release candidate is based on commit
> cf5b758e0a4c22b75bfb02ac2653ff09415ddf53 located at [4].
>
> Please download and try out the release candidate.
>
> The vote ends at 06:00 PM UTC (11:00 AM PDT, 09:00 PM EET, 11:30 PM IST),
> Apr 25th, 2019
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Here is my vote: +1
>   [1]
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820=12344284
>   [2] http://home.apache.org/~sorabh/drill/releases/1.16.0/rc1/
>   [3]
> https://repository.apache.org/content/repositories/orgapachedrill-1067/
>   [4] https://github.com/sohami/drill/commits/drill-1.16.0
>
> Thanks,
> Sorabh
>
> >
>


Re: January Apache Drill board report

2019-01-31 Thread Volodymyr Vysotskyi
Looks good, +1

Kind regards,
Volodymyr Vysotskyi


On Thu, Jan 31, 2019 at 5:58 PM Arina Ielchiieva  wrote:

> Hi all,
>
> please take a look at the draft board report for the last quarter and let
> me know if you have any comments.
>
> Thanks,
> Arina
>
> =
>
> ## Description:
>  - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud
> Storage.
>
> ## Issues:
>  - There are no issues requiring board attention at this time.
>
> ## Activity:
>  - Since the last board report, Drill has released version 1.15.0,
>including the following enhancements:
>- Add capability to do index based planning and execution
>- CROSS join support
>- INFORMATION_SCHEMA FILES and FUNCTIONS were added
>- Support for TIMESTAMPADD and TIMESTAMPDIFF functions
>- Ability to secure znodes with custom ACLs
>- Upgrade to SQLLine 1.6
>- Parquet filter pushdown for VARCHAR and DECIMAL data types
>- Support JPPD (Join Predicate Push Down)
>- Lateral join functionality was enabled by default
>- Multiple Web UI improvements to simplify the use of options and submit
> queries
>- Query performance with the semi-join functionality was improved
>- Support for aliases in the GROUP BY clause
>- Options to return null for empty string and prevents Drill from
> returning
>  a result set for DDL statements
>- Storage plugin names became case-insensitive
>
> - Drill developer meet up was held on November 14, 2018.
>
> ## Health report:
>  - The project is healthy. Development activity
>as reflected in the pull requests and JIRAs is good.
>  - Activity on the dev and user mailing lists are stable.
>  - Three committers were added in the last period.
>
> ## PMC changes:
>
>  - Currently 23 PMC members.
>  - No new PMC members added in the last 3 months
>  - Last PMC addition was Charles Givre on Mon Sep 03 2018
>
> ## Committer base changes:
>
>  - Currently 51 committers.
>  - New commmitters:
> - Hanumath Rao Maduri was added as a committer on Thu Nov 01 2018
> - Karthikeyan Manivannan was added as a committer on Fri Dec 07 2018
> - Salim Achouche was added as a committer on Mon Dec 17 2018
>
> ## Releases:
>
>  - 1.15.0 was released on Mon Dec 31 2018
>
> ## Mailing list activity:
>
>  - d...@drill.apache.org:
> - 415 subscribers (down -12 in the last 3 months):
> - 2066 emails sent to list (2653 in previous quarter)
>
>  - iss...@drill.apache.org:
> - 18 subscribers (up 0 in the last 3 months):
> - 2480 emails sent to list (3228 in previous quarter)
>
>  - user@drill.apache.org:
> - 592 subscribers (down -5 in the last 3 months):
> - 249 emails sent to list (310 in previous quarter)
>
>
> ## JIRA activity:
>
>  - 196 JIRA tickets created in the last 3 months
>  - 171 JIRA tickets closed/resolved in the last 3 months
>


Re: November Apache Drill board report

2018-11-07 Thread Volodymyr Vysotskyi
+1, sorry for the delay.

Kind regards,
Volodymyr Vysotskyi


On Wed, Nov 7, 2018 at 3:56 PM Arina Ielchiieva  wrote:

> Hi Padma,
>
> I can include mention about batch sizing but I am not sure what I should
> mention, quick search over release notes shows a couple of changes related
> to batch sizing:
> https://drill.apache.org/docs/apache-drill-1-14-0-release-notes/
> Could you please propose what I should include?
>
> @PMCs and committers
> Only one PMC member has given +1 for the report. Could more folks please
> review the report?
>
> Kind regards,
> Arina
>
> On Fri, Nov 2, 2018 at 8:33 PM Padma Penumarthy <
> penumarthy.pa...@gmail.com>
> wrote:
>
> > Hi Arina,
> >
> > Can you add batch sizing (for bunch of operators and parquet reader)
> also ?
> >
> > Thanks
> > Padma
> >
> >
> > On Fri, Nov 2, 2018 at 2:55 AM Arina Ielchiieva 
> wrote:
> >
> > > Sure, let's mention.
> > > Updated the report.
> > >
> > > =
> > >
> > >  ## Description:
> > >  - Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud
> > > Storage.
> > >
> > > ## Issues:
> > >  - There are no issues requiring board attention at this time.
> > >
> > > ## Activity:
> > >  - Since the last board report, Drill has released version 1.14.0,
> > >including the following enhancements:
> > > - Drill in a Docker container
> > > - Image metadata format plugin
> > > - Upgrade to Calcite 1.16.0
> > > - Kafka plugin push down support
> > > - Phonetic and String functions
> > > - Enhanced decimal data support
> > > - Spill to disk for the Hash Join support
> > > - CGROUPs resource management support
> > > - Lateral / Unnest support (disabled by default)
> > >  - There were active discussions about schema provision in Drill.
> > >Based on these discussions two projects are currently evolving:
> > >Drill metastore and schema provision in the file and in a query.
> > >  - Apache Drill book has been written by two PMC members (Charles and
> > > Paul).
> > >  - Drill developer meet up will be held on November 14, 2018.
> > >
> > >The following areas are going to be discussed:
> > > - Storage plugins
> > > - Schema discovery & Evolution
> > > - Metadata Management
> > > - Resource management
> > > - Integration with Apache Arrow
> > >
> > > ## Health report:
> > >  - The project is healthy. Development activity
> > >as reflected in the pull requests and JIRAs is good.
> > >  - Activity on the dev and user mailing lists are stable.
> > >  - Three committers and three new PMC member were added in the last
> > period.
> > >
> > > ## PMC changes:
> > >
> > >  - Currently 23 PMC members.
> > >  - New PMC members:
> > > - Boaz Ben-Zvi was added to the PMC on Fri Aug 17 2018
> > > - Charles Givre was added to the PMC on Mon Sep 03 2018
> > > - Vova Vysotskyi was added to the PMC on Fri Aug 24 2018
> > >
> > > ## Committer base changes:
> > >
> > >  - Currently 48 committers.
> > >  - New commmitters:
> > > - Chunhui Shi was added as a committer on Thu Sep 27 2018
> > > - Gautam Parai was added as a committer on Mon Oct 22 2018
> > > - Weijie Tong was added as a committer on Fri Aug 31 2018
> > >
> > > ## Releases:
> > >
> > >  - 1.14.0 was released on Sat Aug 04 2018
> > >
> > > ## Mailing list activity:
> > >
> > >  - d...@drill.apache.org:
> > > - 427 subscribers (down -6 in the last 3 months):
> > > - 2827 emails sent to list (2126 in previous quarter)
> > >
> > >  - iss...@drill.apache.org:
> > > - 18 subscribers (down -1 in the last 3 months):
> > > - 3487 emails sent to list (4769 in previous quarter)
> > >
> > >  - user@drill.apache.org:
> > > - 597 subscribers (down -6 in the last 3 months):
> > > - 332 emails sent to list (346 in previous quarter)
> > >
> > >
> > > ## JIRA activity:
> > >
> > >  - 164 JIRA tickets created in the last 3 months
> > >  - 128 JIRA tickets closed/resolved in the last 3 months
> > >
> > >
> > >
> > > On Fri, Nov 2, 2018 at 12:25 AM Sorabh Hamirwasia <
> shamirwa...@mapr.com>
> > > wrote:
> > >
> > &

Re: Drill Hangout tomorrow 08/21

2018-08-20 Thread Volodymyr Vysotskyi
Hi all,

I and Vitalii Diravka want to give the presentation with our ideas
connected with Drill Metadata management project (DRILL-6552
<https://issues.apache.org/jira/browse/DRILL-6552>).

We will be happy to discuss it and choose the right way for further
development.

Kind regards,
Volodymyr Vysotskyi


On Mon, Aug 20, 2018 at 10:35 PM Hanumath Rao Maduri 
wrote:

> The Apache Drill Hangout will be held tomorrow at 10:00am PST; please let
> us know should you have a topic for tomorrow's hangout. We will also ask
> for topics at the beginning of the hangout.
>
> Hangout Link -
> https://hangouts.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc
>
> Regards,
> Hanu
>