Re: [ANNOUNCE] New PMC Chair of Apache Drill

[SorabhApache]

Congratulations Charles on your new role!. Thank you Arina for your
directions and contributions as PMC Chair over last year.

Thanks,
Sorabh

On Fri, Aug 23, 2019 at 7:35 AM Aman Sinha  wrote:

> Congratulations Charles !   And thank you Arina !
>
> -Aman
>
> On Thu, Aug 22, 2019 at 9:11 PM Divya Gehlot 
> wrote:
>
> > Congratulations Charles !
> > Looking forward for much better Drill and more addition in your book as
> > well :)
> >
> > Thanks ,
> > Divya
> >
> > On Fri, 23 Aug 2019 at 12:07 PM, Bhargava Vadlamani <
> > vadlamani1...@gmail.com>
> > wrote:
> >
> > > Congratulations Charles !!
> > >
> > > On Thu, Aug 22, 2019, 8:56 PM Abhishek Girish 
> > wrote:
> > >
> > > > Congratulations, Charles!! Looking forward to what's next.
> > > >
> > > > Thanks a lot Arina, for your leadership in the last year. I think we
> > may
> > > > have added more committers and PMC members in your tenure, than ever
> > > > before. The community is growing well, and I'm so glad to be a part
> of
> > > it.
> > > >
> > > > On Thu, Aug 22, 2019 at 8:30 PM Kunal Khatua 
> > > > wrote:
> > > >
> > > > > Congratulations, Charles!
> > > > >
> > > >
> > >
> >
>

Re: Apache Drill REST API returns numeric column value as String

[SorabhApache]

Hi Gayathri,
That is the expected behavior. There is already a JIRA[1] filed for this,
but no one got chance to work on it. The other option is to use JDBC/ODBC
drivers instead which will preserve the result data type.

[1]: https://issues.apache.org/jira/browse/DRILL-5072

Thanks,
Sorabh

On Mon, May 13, 2019 at 4:00 AM Gayathri Selvaraj <
gayathri.selvar...@gmail.com> wrote:

> Hi team,
>
> I am working on a project that make use of Apache Drill REST API to run
> queries on JSON data. The response which I get from Drill is having rows
> with all values as string irrespective of numeric or boolean.
>
> Below is the sample:
>
> *test.json:*
>
> [{"a":"uxv","b":1,"c":2.0},{"a":"uxv","b":2,"c":3.15}]
>
> *Request:* {"queryType" : "SQL","query" : "select * from
> dfs.`\files\test.json`"};
>
> *Response:* { "queryId": " ",
> "columns": ["a","b","c"],
> "rows": [
> { "b": "1", "c": " 2.0", "a": "uxv"}
>
> , { "b": "2", "c": "3.15", "a": "uxv"} ] }
>
> *Expected: *Numeric values without double quotes in response.
>
>
> One of our requirement is failing because of this. Can anyone please give
> some inputs or any configuration needs to be done to make it work as
> expected.
>
> Highly appreciating your response in advance.
>
>
> Thanks,
> Gayathri
>

Apache Drill Hangout - May 13, 2019

[SorabhApache]

Hi Drillers,
We have our bi-weekly hangout scheduled for tomorrow (05/13). If there are
any topics you would like to discuss during the hangout please respond to
this email. We will start at 10AM PST and you can use this link to join: (
http://meet.google.com/yki-iqdf-tai).

Thanks,
Sorabh

Apache master branch

[SorabhApache]

Hi All,
Apache master branch is open for merging PR's now since we have already
released 1.16.0. I was waiting to merge most of Ready-To-Commit JIRA's
which took some time because of backlog which was created. Most of the PR's
are merged and only 3 PR's are pending now either because of some test
issues or there is a discussion thread going on.

Thanks,
Sorabh

Re: May Apache Drill board report

[SorabhApache]

+1

On Fri, May 3, 2019 at 4:22 PM Boaz Ben-Zvi  wrote:

> No comments; looks fine; +1
>
> On 5/3/19 3:10 PM, Aman Sinha wrote:
> > +1
> >
> > On Fri, May 3, 2019 at 1:40 PM Volodymyr Vysotskyi  >
> > wrote:
> >
> >> 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:
> >>>
> >>> - dev@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)
> >>>
> >>> - u...@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
> >>>
>

[ANNOUNCE] Apache Drill 1.16.0 Release

[SorabhApache]

On behalf of the Apache Drill community, I am happy to announce the release
of Apache Drill 1.16.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 220 JIRA's are resolved in this release of Drill with following
new features and improvements [2]:

   - CREATE OR REPLACE SCHEMA command to define a schema for text files
   (DRILL-6964)
   - REFRESH TABLE METADATA command can generate metadata cache files for
   specific columns (DRILL-7058)
   - ANALYZE TABLE statement to computes statistics on Parquet data
   (DRILL-1328)
   - SYSLOG (RFC-5424) Format Plugin (DRILL-6582)
   - NEAREST DATE function to facilitate time series analysis (DRILL-7077)
   - Format plugin for LTSV files (DRILL-7014)
   - Ability to query Hive views, like querying Hive tables in a hive
   schema, for example SELECT * FROM hive.hive_view`; (DRILL-540)
   - Upgrade to SQLLine 1.7 (DRILL-6989)
   - Calcite updated to version 1.18.0 (DRILL-6862)
   - Several Drill Web UI improvements, including:
  - Storage plugin management improvements (DRILL-6562)
  - Query progress indicators and warnings (DRILL-6879)
  - Ability to limit the result size for better UI response (DRILL-6050)
  - Ability to sort the list of profiles in the Drill Web UI
  (DRILL-6942)
  - Display query state in query result page (DRILL-6939)
  - Button to reset the options filter (DRILL-6921)

For the full list please see release notes [3].
The binary and source artifacts are available here [4].

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

1. https://drill.apache.org/
2. https://drill.apache.org/blog/2019/05/02/drill-1.16-released/
3. https://drill.apache.org/docs/apache-drill-1-16-0-release-notes/
4. https://drill.apache.org/download/

Thanks,
Sorabh

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

[SorabhApache]

Hi All,
RC2 candidate for 1.16.0 passes the voting criteria. Thanks to everyone who
has tested and voted for release candidate. The summary of voting is:

Total Votes: 8
5x +1 (binding): Aman, Arina, Boaz, Sorabh, Vova
3x +1 (non-binding): Anton, Denys, Kunal
No 0s or -1s.

I'll start the process of publishing the release artifacts and send an
announcement once it's propagated.

Thanks,
Sorabh

Re: [VOTE] Apache Drill Release 1.16.0 - RC2

[SorabhApache]

Thanks everyone who voted on RC2 candidate. Voting ends now and I will
share the result soon.

Thanks,
Sorabh

On Wed, May 1, 2019 at 6:31 AM Anton Gozhiy  wrote:

> Downloaded the binary tarball, verified it by simple queries.
> Successfully built the source tarball on Ubuntu 16.04 and Windows 10.
> Checked both embedded and distributed mode.
> Verified Drill with impersonation and with plain authentication, all is
> working fine.
> Ran tests for Web-UI and REST API, everything is ok.
> Connected to Hive and executed some queries to external and managed tables.
> Tried to submit physical and logical plans through the Web-UI.
> No issues found.
>
> +1
>
> On Wed, May 1, 2019 at 1:57 PM Volodymyr Vysotskyi 
> wrote:
>
> > 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 <
> arina.yelchiy...@gmail.com>
> > > 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
> > > >>>
> >

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

[SorabhApache]

Sure. I will do it.

Thanks,
Sorabh

On Fri, Apr 26, 2019 at 8:35 AM Arina Yelchiyeva 
wrote:

> Sure, we can discuss it during Hangout.
> Sorabh, since you are latest release manager, I am wondering if you would
> volunteer to add scripts into Drill project? :)
> At least something to start with.
>
> Kind regards,
> Arina
>
> > On Apr 26, 2019, at 6:32 PM, SorabhApache  wrote:
> >
> > +1 for including release scripts. I would also recommend adding a
> README.md
> > in the same location, which can include link to a wiki for the release
> > process or all the instructions in it. Also it would be great if we can
> > formulate some guidelines as to what kind of issues may not be considered
> > as blocker for a release going forward. May be we can discuss in the next
> > hangout as well.
> >
> > Thanks,
> > Sorabh
> >
> > On Fri, Apr 26, 2019 at 8:03 AM Aman Sinha  wrote:
> >
> >> +1 on including the release preparation script into the code base.
> Location
> >> TBD.  Perhaps under a separate 'release' subdirectory either in contrib
> or
> >> docs ?
> >>
> >> On Fri, Apr 26, 2019 at 12:46 AM Arina Yelchiyeva <
> >> arina.yelchiy...@gmail.com> wrote:
> >>
> >>> Maybe we should include these scripts directly into Drill project (of
> >>> course if Parth does not mind), maybe in doc module?
> >>> This way we will be able to modify them if needed using regular PR
> >> process
> >>> and everybody will know where to find them.
> >>>
> >>> Any thoughts?
> >>>
> >>> Kind regards,
> >>> Arina
> >>>
> >>>> On Apr 26, 2019, at 1:56 AM, SorabhApache  wrote:
> >>>>
> >>>> Update:
> >>>> DRILL-7201 / DRILL-7202: Kunal has fixes for both and are
> >>> ready-to-commit.
> >>>> DRILL-7213: drill-format-mapr.jar contains stale git.properties file
> >>>>
> >>>>  - The main issue here was that in 1.14 and 1.15 drill-format-mapr.jar
> >>>>  was included with release tarballs where it shouldn't be. So Vova
> >>> helped to
> >>>>  make a change in 1.16 to fix that and now format-mapr will not be
> >>> included
> >>>>  in release tarballs, not any mapr specific jars. The PR is approved
> >> and
> >>>>  ready-to-commit.
> >>>>
> >>>> DRILL-7212: Add gpg key with apache.org email for sorabh
> >>>>
> >>>>  - PR is opened for it. I have added both my emails to the gpg key and
> >>> is
> >>>>  signed by boaz.
> >>>>
> >>>> DRILL-7207: Update the copyright year in NOTICE.txt file
> >>>>
> >>>>  - PR is opened for this as well.
> >>>>
> >>>> Last issue which Vova reported about files like
> >>>>
> >>>
> >>
> *org.codehaus.plexus.compiler.javac.JavacCompiler1256088670033285178arguments*
> >>>> being included in jar. This was present in 1.14 as well but not in
> >> 1.15.
> >>>> The reason is it looks like different processes are followed for
> >> release.
> >>>> Every release done using the script (drill-release.sh)[1] will have
> >> above
> >>>> file. The reason is because the *mvn release:prepare* phase is done
> >> with
> >>> -X
> >>>> flag which creates debug files and those are not excluded from
> >> maven-jar
> >>>> plugin configuration. After removing the -X option I am not seeing
> >> above
> >>>> files anymore and speed of prepare phase is increased significantly as
> >>>> well. Will submit a separate PR for this change in script post
> release.
> >>>>
> >>>> Once all the changes are merged into master, I will re-prepare the RC
> >>>> candidate and share with the community.
> >>>>
> >>>> [1]: https://github.com/parthchandra/stuff/tree/master/scripts
> >>>>
> >>>> Thanks,
> >>>> Sorabh
> >>>>
> >>>> On Thu, Apr 25, 2019 at 3:02 PM Kunal Khatua 
> wrote:
> >>>>
> >>>>> UPDATE:
> >>>>>
> >>>>>
> >>>>> Both, DRILL-7201 and DRILL-7202 has been fixed and verified by Sorabh
> >>>>> and Arina, so we can have it as part of "RC2".
> >>>>>
>

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

[SorabhApache]

+1 for including release scripts. I would also recommend adding a README.md
in the same location, which can include link to a wiki for the release
process or all the instructions in it. Also it would be great if we can
formulate some guidelines as to what kind of issues may not be considered
as blocker for a release going forward. May be we can discuss in the next
hangout as well.

Thanks,
Sorabh

On Fri, Apr 26, 2019 at 8:03 AM Aman Sinha  wrote:

> +1 on including the release preparation script into the code base. Location
> TBD.  Perhaps under a separate 'release' subdirectory either in contrib or
> docs ?
>
> On Fri, Apr 26, 2019 at 12:46 AM Arina Yelchiyeva <
> arina.yelchiy...@gmail.com> wrote:
>
> > Maybe we should include these scripts directly into Drill project (of
> > course if Parth does not mind), maybe in doc module?
> > This way we will be able to modify them if needed using regular PR
> process
> > and everybody will know where to find them.
> >
> > Any thoughts?
> >
> > Kind regards,
> > Arina
> >
> > > On Apr 26, 2019, at 1:56 AM, SorabhApache  wrote:
> > >
> > > Update:
> > > DRILL-7201 / DRILL-7202: Kunal has fixes for both and are
> > ready-to-commit.
> > > DRILL-7213: drill-format-mapr.jar contains stale git.properties file
> > >
> > >   - The main issue here was that in 1.14 and 1.15 drill-format-mapr.jar
> > >   was included with release tarballs where it shouldn't be. So Vova
> > helped to
> > >   make a change in 1.16 to fix that and now format-mapr will not be
> > included
> > >   in release tarballs, not any mapr specific jars. The PR is approved
> and
> > >   ready-to-commit.
> > >
> > > DRILL-7212: Add gpg key with apache.org email for sorabh
> > >
> > >   - PR is opened for it. I have added both my emails to the gpg key and
> > is
> > >   signed by boaz.
> > >
> > > DRILL-7207: Update the copyright year in NOTICE.txt file
> > >
> > >   - PR is opened for this as well.
> > >
> > > Last issue which Vova reported about files like
> > >
> >
> *org.codehaus.plexus.compiler.javac.JavacCompiler1256088670033285178arguments*
> > > being included in jar. This was present in 1.14 as well but not in
> 1.15.
> > > The reason is it looks like different processes are followed for
> release.
> > > Every release done using the script (drill-release.sh)[1] will have
> above
> > > file. The reason is because the *mvn release:prepare* phase is done
> with
> > -X
> > > flag which creates debug files and those are not excluded from
> maven-jar
> > > plugin configuration. After removing the -X option I am not seeing
> above
> > > files anymore and speed of prepare phase is increased significantly as
> > > well. Will submit a separate PR for this change in script post release.
> > >
> > > Once all the changes are merged into master, I will re-prepare the RC
> > > candidate and share with the community.
> > >
> > > [1]: https://github.com/parthchandra/stuff/tree/master/scripts
> > >
> > > Thanks,
> > > Sorabh
> > >
> > > On Thu, Apr 25, 2019 at 3:02 PM Kunal Khatua  wrote:
> > >
> > >> UPDATE:
> > >>
> > >>
> > >> Both, DRILL-7201 and DRILL-7202 has been fixed and verified by Sorabh
> > >> and Arina, so we can have it as part of "RC2".
> > >>
> > >> (Thanks for catching the issues, Arina ! )
> > >>
> > >> ~ kunal
> > >>
> > >> On 4/25/2019 4:12:16 AM, Volodymyr Vysotskyi 
> > wrote:
> > >> 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*
> > >>
> > >>

[VOTE] Apache Drill Release 1.16.0 - RC2

[SorabhApache]

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

[SorabhApache]

Update:
DRILL-7201 / DRILL-7202: Kunal has fixes for both and are ready-to-commit.
DRILL-7213: drill-format-mapr.jar contains stale git.properties file

   - The main issue here was that in 1.14 and 1.15 drill-format-mapr.jar
   was included with release tarballs where it shouldn't be. So Vova helped to
   make a change in 1.16 to fix that and now format-mapr will not be included
   in release tarballs, not any mapr specific jars. The PR is approved and
   ready-to-commit.

DRILL-7212: Add gpg key with apache.org email for sorabh

   - PR is opened for it. I have added both my emails to the gpg key and is
   signed by boaz.

DRILL-7207: Update the copyright year in NOTICE.txt file

   - PR is opened for this as well.

Last issue which Vova reported about files like
*org.codehaus.plexus.compiler.javac.JavacCompiler1256088670033285178arguments*
being included in jar. This was present in 1.14 as well but not in 1.15.
The reason is it looks like different processes are followed for release.
Every release done using the script (drill-release.sh)[1] will have above
file. The reason is because the *mvn release:prepare* phase is done with -X
flag which creates debug files and those are not excluded from maven-jar
plugin configuration. After removing the -X option I am not seeing above
files anymore and speed of prepare phase is increased significantly as
well. Will submit a separate PR for this change in script post release.

Once all the changes are merged into master, I will re-prepare the RC
candidate and share with the community.

[1]: https://github.com/parthchandra/stuff/tree/master/scripts

Thanks,
Sorabh

On Thu, Apr 25, 2019 at 3:02 PM Kunal Khatua  wrote:

> UPDATE:
>
>
> Both, DRILL-7201 and DRILL-7202 has been fixed and verified by Sorabh
> and Arina, so we can have it as part of "RC2".
>
> (Thanks for catching the issues, Arina ! )
>
> ~ kunal
>
> On 4/25/2019 4:12:16 AM, Volodymyr Vysotskyi  wrote:
> 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

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

[SorabhApache]

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 |
> >
> +-+--+-+---+---+---+
> > 1 row selected (0.274 seconds)
> > apache drill>
> >
> > Thanks,
> > Khurram
> >
> > On Wed, Apr 24, 2019 at 9:52 AM SorabhApache wrote:
> >
> >> Hi Volodymyr/Anton,
> >> I can verify that I am seeing both the below issues as reported by Anton
> >> and Volodymyr. I will investigate further why we are seeing these
> issues.
> >> Thanks for catching this. Can you please open JIRA's for these issues ?
> >>
> >> 1) Wrong result for sys.version query when built from source tarball.
> >> 2) git.properties file in drill-format-mapr-1.16.0.jar has wrong commit
> id
> >> but as Volodymyr mentioned because of order in which jars are picked up
> >> it's not showing the issue when tried from prebuilt tarball.
> >>
> >> @Volodymyr Vysotskyi
> >> Regarding the GPG key I am not sure if we mandate it to use apache.org,
> >> there other keys in the file which are using gmail address as well. As
> far
> >> as the signing person is authenticating the key and details associated
> with
> >> it, I think it should be fine. But since it's recommended I will use
> >> apache.org email address instead.
> >>
> >> Thanks,
> >> Sorabh
> >>
> &g

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

[SorabhApache]

 > > > 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 <
> > > > jyothsna@gmail.com
> > > > > >
> > > > > >> 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
> > > > > >> > a few queries that use metadata cache and verified results.
> > > > > >> >
> > > > > >> > The release looks good to me +1.
> > > > > >> >
> > > > > >> > Thank you,
> > > > > >> > Jyothsna
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > [image: Mailtrack]
> > > > > >> > <
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality5;
> > > > > >> > >
> > > > > >> > Sender
> > > > > >> > notified by
> > > > > >> > Mailtrack
> > > > > >> > <
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> https://mailtrack.io?utm_source=gmail_medium=signature_campaign=signaturevirality5;
> > > > > >> > >
> > > > > >> > 04/24/19,
> > > > > >> > 12:09:52 AM
> > > > > >> >
> > > > > >> > On Wed, Apr 24, 2019 at 12:09 AM Jyothsna Reddy <
> > > > > jyothsna@gmail.com
> > > > > >> >
> > > > > >> > 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
> > > > > >> > > a few queries that use metadata cache and verified results.
> > > > > >> > > Did a few manual tests with REFRESH METADATA by creating the
> > new
> > > > V4
> > > > > >> > >
> > > > > >> > > The release looks good to me +1.
> > > > > >> > >
&g

Re: [VOTE] Apache Drill Release 1.16.0 - RC1

[SorabhApache]

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

[SorabhApache]

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

>

[VOTE] Apache Drill Release 1.16.0 - RC1

[SorabhApache]

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

[SorabhApache]

Hi Anton/Arina,
Thanks for finding the issue and fixing it. I have some follow-up questions
for the original change which I have posted in DRILL-7186
<https://issues.apache.org/jira/browse/DRILL-7186>, would be great to
clarify on those as well.

Thanks,
Sorabh

On Fri, Apr 19, 2019 at 9:54 AM Arina Yelchiyeva 
wrote:

> Fix is ready: https://github.com/apache/drill/pull/1757
>
> > On Apr 19, 2019, at 2:36 PM, Anton Gozhiy  wrote:
> >
> > Reported a regression:
> > https://issues.apache.org/jira/browse/DRILL-7186
> >
> > On Fri, Apr 19, 2019 at 2:10 AM Bob Rudis  wrote:
> >
> >> Thx Sorabh!
> >>
> >> On Thu, Apr 18, 2019 at 16:23 SorabhApache  wrote:
> >>
> >>> Hi Bob,
> >>> With protobuf change both JDBC and ODBC will need to be updated but for
> >>> 1.16 release this change was reverted since it will take some time to
> >>> prepare for drivers with latest protobuf versions. In the original JIRA
> >>> there is a comment stating that the commit is reverted on 1.16 branch
> and
> >>> will add the commit id once the release branch is finalized.
> >>>
> >>> JIRA: https://issues.apache.org/jira/browse/DRILL-6642
> >>> Commit that revert's the change [1]:
> >>> 6eedd93dadf6d7d4f745f99d30aee329976c2191
> >>>
> >>> [1]: https://github.com/sohami/drill/commits/drill-1.16.0
> >>>
> >>> Thanks,
> >>> Sorabh
> >>>
> >>> On Thu, Apr 18, 2019 at 1:12 PM Bob Rudis  wrote:
> >>>
> >>>> Q abt the RC (and eventual full release): Does
> >>>> https://issues.apache.org/jira/browse/DRILL-5509 mean that the ODBC
> >>>> drivers will need to be updated to avoid warning messages (and
> >>>> potential result set errors) as the was the case with a previous
> >>>> release or is this purely (as I read the ticket) a "make maven less
> >>>> unhappy" and no underlying formats are changing? If it does mean the
> >>>> ODBC drivers need changing, any chance there's a way to ensure the
> >>>> provider of those syncs it closer to release than the last time?
> >>>>
> >>>> On Thu, Apr 18, 2019 at 3:06 PM SorabhApache 
> >> wrote:
> >>>>>
> >>>>> Hi Drillers,
> >>>>> I'd like to propose the first release candidate (RC0) for the Apache
> >>>> Drill,
> >>>>> version 1.16.0.
> >>>>>
> >>>>> The RC0 includes total of 211 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
> >>>>> 61cd2b779d85ff1e06947327fca2e076994796b5 located at [4].
> >>>>>
> >>>>> Please download and try out the release.
> >>>>>
> >>>>> The vote ends at 07:00 PM UTC (12:00 PM PDT, 10:00 PM EET, 12:30 AM
> >>>>> IST(next day)), Apr 23rd, 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/rc0/
> >>>>>  [3]
> >>>>>
> >>>
> https://repository.apache.org/content/repositories/orgapachedrill-1066/
> >>>>>  [4] https://github.com/sohami/drill/commits/drill-1.16.0
> >>>>>
> >>>>> Thanks,
> >>>>> Sorabh
> >>>>
> >>>
> >>
> >
> >
> > --
> > Sincerely, Anton Gozhiy
> > anton5...@gmail.com
>
>

Re: [VOTE] Apache Drill Release 1.16.0 - RC0

[SorabhApache]

Hi Bob,
With protobuf change both JDBC and ODBC will need to be updated but for
1.16 release this change was reverted since it will take some time to
prepare for drivers with latest protobuf versions. In the original JIRA
there is a comment stating that the commit is reverted on 1.16 branch and
will add the commit id once the release branch is finalized.

JIRA: https://issues.apache.org/jira/browse/DRILL-6642
Commit that revert's the change [1]:
6eedd93dadf6d7d4f745f99d30aee329976c2191

[1]: https://github.com/sohami/drill/commits/drill-1.16.0

Thanks,
Sorabh

On Thu, Apr 18, 2019 at 1:12 PM Bob Rudis  wrote:

> Q abt the RC (and eventual full release): Does
> https://issues.apache.org/jira/browse/DRILL-5509 mean that the ODBC
> drivers will need to be updated to avoid warning messages (and
> potential result set errors) as the was the case with a previous
> release or is this purely (as I read the ticket) a "make maven less
> unhappy" and no underlying formats are changing? If it does mean the
> ODBC drivers need changing, any chance there's a way to ensure the
> provider of those syncs it closer to release than the last time?
>
> On Thu, Apr 18, 2019 at 3:06 PM SorabhApache  wrote:
> >
> > Hi Drillers,
> > I'd like to propose the first release candidate (RC0) for the Apache
> Drill,
> > version 1.16.0.
> >
> > The RC0 includes total of 211 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
> > 61cd2b779d85ff1e06947327fca2e076994796b5 located at [4].
> >
> > Please download and try out the release.
> >
> > The vote ends at 07:00 PM UTC (12:00 PM PDT, 10:00 PM EET, 12:30 AM
> > IST(next day)), Apr 23rd, 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/rc0/
> >   [3]
> > https://repository.apache.org/content/repositories/orgapachedrill-1066/
> >   [4] https://github.com/sohami/drill/commits/drill-1.16.0
> >
> > Thanks,
> > Sorabh
>

[VOTE] Apache Drill Release 1.16.0 - RC0

[SorabhApache]

Hi Drillers,
I'd like to propose the first release candidate (RC0) for the Apache Drill,
version 1.16.0.

The RC0 includes total of 211 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
61cd2b779d85ff1e06947327fca2e076994796b5 located at [4].

Please download and try out the release.

The vote ends at 07:00 PM UTC (12:00 PM PDT, 10:00 PM EET, 12:30 AM
IST(next day)), Apr 23rd, 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/rc0/
  [3]
https://repository.apache.org/content/repositories/orgapachedrill-1066/
  [4] https://github.com/sohami/drill/commits/drill-1.16.0

Thanks,
Sorabh

Re: [DISCUSS] 1.16.0 release

[SorabhApache]

Hi Charles,
I don't think DRILL-7185 is a blocker bug since it's there from 1.11.0
onwards. I will prefer for this fix to go in master branch instead of
release branch to avoid having to prepare for RC candidate again from
scratch (which will take another ~3 hours). In case if RC0 doesn't succeed
then we can take this fix in next candidate. For now I am removing the
blocker tag from it and marking it for 1.17.

Thanks,
Sorabh

On Thu, Apr 18, 2019 at 11:25 AM Charles Givre  wrote:

> I put is as a blocker (and maybe that is overkill and if so I apologize)
> because I wasn’t able to actually use Drill to query my data.  Drill kept
> crashing when I was trying to query these collection of PCAP files, which
> it really should have been able to read.
>
> It literally was something as simple as adding a ‘=‘.
> — C
>
> > On Apr 18, 2019, at 2:23 PM, SorabhApache  wrote:
> >
> > Hi Charles,
> > I was about to share the RC0 candidate and just saw that you have
> created a
> > blocker issue for 1.16. The JIRA doesn't have much detail as to why it is
> > treated as blocker bug. Can you please provide more details on it ?
> > https://issues.apache.org/jira/browse/DRILL-7185
> >
> > Thanks,
> > Sorabh
> >
> > On Tue, Apr 16, 2019 at 11:21 AM Sorabh Hamirwasia <
> sohami.apa...@gmail.com>
> > wrote:
> >
> >> *Update:*
> >> There is a blocker bug [1] found for 1.16 with TPCDS performance runs
> and
> >> Gautam is working on it currently. Once that is fixed and there are no
> >> other blocker bugs I will prepare RC0. Since the branch is already
> created
> >> for 1.16.0 on apache side [2], it will be helpful if everyone can do
> some
> >> initial testing. This will help to find any potential issues before RC
> >> candidate is created and avoid delays with release.
> >>
> >> [1]: https://issues.apache.org/jira/browse/DRILL-7182
> >> [2]: https://github.com/apache/drill/commits/1.16.0
> >>
> >> Thanks,
> >> Sorabh
> >>
> >> On Mon, Apr 15, 2019 at 7:42 PM Ted Dunning 
> wrote:
> >>
> >>>
> >>>
> >>> On Mon, Apr 15, 2019 at 12:35 PM Sorabh Hamirwasia <
> >>> sohami.apa...@gmail.com> wrote:
> >>>
> >>>> ...
> >>>>
> >>>> @Ted Dunning  - I am not sure if I understood
> >>>> correctly but I think the reason master is locked and two active
> branches
> >>>> are not chosen is to reduce the overhead of cherry-picking commits
> from
> >>>> master to release branch. And also if master is not locked then the
> >>>> scenario which Arina mentioned can still happen if a required commit
> for
> >>>> 1.16 is between 2 commits intended for 1.17 only.
> >>>>
> >>>> For now *** Please treat master branch as locked and don't merge any
> >>>> commit until further notice ***
> >>>>
> >>>
> >>>
> >>> Yes. I get it. I understand the lock motivation. That means that master
> >>> is effectively a 1.16-RC branch. Somebody who needs to commit changes
> to
> >>> 1.17 will (should) create a 1.17 branch from which they will eventually
> >>> cherry-pick commits back to master. At the very least, they will have a
> >>> private copy of master that is effectively a separate branch that they
> will
> >>> have to rebase as changes go on to master to get the release in shape.
> >>>
> >>> This means that there *will* be at least two branches. Probably more
> than
> >>> two since there is no formal place to put the 1.17 changes that are
> pending.
> >>>
> >>> As such, I would suggest that making this situation explicit and public
> >>> would be easier for people. It would help people to either create a
> 1.16
> >>> branch, committing fixes there for RC problems and cherry-picking to or
> >>> from master as needed OR create a 1.17 branch and use master as the
> 1.16
> >>> branch (which is a bit confusing because it changes peoples normal
> >>> procedures). Neither strategy requires that master be locked. The
> former
> >>> leaves master as the place all new stuff goes. The latter follows the
> "all
> >>> development on a branch" orthodoxy.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
>
>

Re: [DISCUSS] 1.16.0 release

[SorabhApache]

Hi Charles,
I was about to share the RC0 candidate and just saw that you have created a
blocker issue for 1.16. The JIRA doesn't have much detail as to why it is
treated as blocker bug. Can you please provide more details on it ?
https://issues.apache.org/jira/browse/DRILL-7185

Thanks,
Sorabh

On Tue, Apr 16, 2019 at 11:21 AM Sorabh Hamirwasia 
wrote:

> *Update:*
> There is a blocker bug [1] found for 1.16 with TPCDS performance runs and
> Gautam is working on it currently. Once that is fixed and there are no
> other blocker bugs I will prepare RC0. Since the branch is already created
> for 1.16.0 on apache side [2], it will be helpful if everyone can do some
> initial testing. This will help to find any potential issues before RC
> candidate is created and avoid delays with release.
>
> [1]: https://issues.apache.org/jira/browse/DRILL-7182
> [2]: https://github.com/apache/drill/commits/1.16.0
>
> Thanks,
> Sorabh
>
> On Mon, Apr 15, 2019 at 7:42 PM Ted Dunning  wrote:
>
>>
>>
>> On Mon, Apr 15, 2019 at 12:35 PM Sorabh Hamirwasia <
>> sohami.apa...@gmail.com> wrote:
>>
>>> ...
>>>
>>> @Ted Dunning  - I am not sure if I understood
>>> correctly but I think the reason master is locked and two active branches
>>> are not chosen is to reduce the overhead of cherry-picking commits from
>>> master to release branch. And also if master is not locked then the
>>> scenario which Arina mentioned can still happen if a required commit for
>>> 1.16 is between 2 commits intended for 1.17 only.
>>>
>>> For now *** Please treat master branch as locked and don't merge any
>>> commit until further notice ***
>>>
>>
>>
>> Yes. I get it. I understand the lock motivation. That means that master
>> is effectively a 1.16-RC branch. Somebody who needs to commit changes to
>> 1.17 will (should) create a 1.17 branch from which they will eventually
>> cherry-pick commits back to master. At the very least, they will have a
>> private copy of master that is effectively a separate branch that they will
>> have to rebase as changes go on to master to get the release in shape.
>>
>> This means that there *will* be at least two branches. Probably more than
>> two since there is no formal place to put the 1.17 changes that are pending.
>>
>> As such, I would suggest that making this situation explicit and public
>> would be easier for people. It would help people to either create a 1.16
>> branch, committing fixes there for RC problems and cherry-picking to or
>> from master as needed OR create a 1.17 branch and use master as the 1.16
>> branch (which is a bit confusing because it changes peoples normal
>> procedures). Neither strategy requires that master be locked. The former
>> leaves master as the place all new stuff goes. The latter follows the "all
>> development on a branch" orthodoxy.
>>
>>
>>
>>
>>
>>