Re: 1.17.0 updated protobuf but mapr ODBC drivers have not been updated

[Veera Naranammalpuram]

Hi Rob,

We are aware of an upgrade (protobuf) in Apache Drill 1.17 that's throwing
some errors in the ODBC drivers regression tests. We are working on this
with Simba who develops the ODBC driver and looking to have this resolved.
If you are a MapR/HPe customer,  could you please open a support case
through the support portal?

Could you please let us know if any queries are failing? When you encounter
the error message above, is there anything that used to work but doesn't
work anymore?

Thanks for letting us know.

Veera Naranammalpuram
Principal Product Manager - MapR
Mobile: (1) 917 683 8116 (US/Eastern Time)| 
vee...@hpe.com


On Mon, Jan 13, 2020 at 1:40 PM Vova Vysotskyi  wrote:

> Hi Bob,
>
> Could you please create Jira and share more details on how to reproduce
> this issue, so QA will be able to verify that it was fixed on a newer
> version of the Driver.
>
> Kind regards,
> Volodymyr Vysotskyi
>
>
> On Mon, Jan 13, 2020 at 8:16 PM Bob Rudis  wrote:
>
> > HNY folks,
> >
> > This is more of an FYI vs anything else.
> >
> > I realize the intrepid/awesome Drill team has little control over MapR's
> > speed of catching up to the latest releases but just in case others
> haven't
> > upgraded to 1.17.0 (I just did today) and use ODBC, you'll see something
> > like this in logs:
> >
> > [libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse
> > message of type "exec.user.GetServerMetaResp" because it is missing
> > required fields: server_meta.convert_support[506].to,
> > server_meta.convert_support[545].from,
> server_meta.convert_support[545].to
> >
> > until MapR updates their side of this (this happened with previous
> > releases and is 100% on MapR to publish new ODBC drivers).
> >
> > It seems to only impact Drill instance metadata retrieval (all my usual
> > queries are working fine).
> >
> > REST API & JDBC (which I use via the {sergeant} & {sergeant.caffeinated}
> R
> > pkgs) are fine (as expected).
> >
> > -Bob
>

Apache Drill documentation updates

[Bevens, Bridget]

Hi,



I wanted to let everyone know that I won’t be working regularly on the Apache 
Drill documentation, but I’ll be available to update the website for the 
releases, which includes:

  *   Generating the release notes, blog, What’s New pages
  *   Updating files with the new release version/pointing files to the correct 
mirrors site
  *   Publishing the Apache Drill website for the release


If you have documentation updates or feature documentation that you want to add 
to the Apache Drill project, please submit your updates through a pull request. 
I am planning to review and publish content at the end of each month and before 
each release.

For information about how to update the documentation, refer to the 
Documentation Guidelines in the README.md file in the Apache Drill gh-pages 
branch.

Thanks,

Bridget

Re: 1.17.0 updated protobuf but mapr ODBC drivers have not been updated

[Vova Vysotskyi]

Hi Bob,

Could you please create Jira and share more details on how to reproduce
this issue, so QA will be able to verify that it was fixed on a newer
version of the Driver.

Kind regards,
Volodymyr Vysotskyi


On Mon, Jan 13, 2020 at 8:16 PM Bob Rudis  wrote:

> HNY folks,
>
> This is more of an FYI vs anything else.
>
> I realize the intrepid/awesome Drill team has little control over MapR's
> speed of catching up to the latest releases but just in case others haven't
> upgraded to 1.17.0 (I just did today) and use ODBC, you'll see something
> like this in logs:
>
> [libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse
> message of type "exec.user.GetServerMetaResp" because it is missing
> required fields: server_meta.convert_support[506].to,
> server_meta.convert_support[545].from, server_meta.convert_support[545].to
>
> until MapR updates their side of this (this happened with previous
> releases and is 100% on MapR to publish new ODBC drivers).
>
> It seems to only impact Drill instance metadata retrieval (all my usual
> queries are working fine).
>
> REST API & JDBC (which I use via the {sergeant} & {sergeant.caffeinated} R
> pkgs) are fine (as expected).
>
> -Bob

1.17.0 updated protobuf but mapr ODBC drivers have not been updated

[Bob Rudis]

HNY folks,

This is more of an FYI vs anything else.

I realize the intrepid/awesome Drill team has little control over MapR's speed 
of catching up to the latest releases but just in case others haven't upgraded 
to 1.17.0 (I just did today) and use ODBC, you'll see something like this in 
logs:

[libprotobuf ERROR google/protobuf/message_lite.cc:123] Can't parse message of 
type "exec.user.GetServerMetaResp" because it is missing required fields: 
server_meta.convert_support[506].to, server_meta.convert_support[545].from, 
server_meta.convert_support[545].to

until MapR updates their side of this (this happened with previous releases and 
is 100% on MapR to publish new ODBC drivers).

It seems to only impact Drill instance metadata retrieval (all my usual queries 
are working fine).

REST API & JDBC (which I use via the {sergeant} & {sergeant.caffeinated} R 
pkgs) are fine (as expected).

-Bob

Re: Drill Hangout

[Igor Guzenko]

Hello Drillers,

I'm fine with recovery of hangouts with one good suggestion. I think it
will be fine to have a bi-weekly call like it was earlier, but also I'd
like to suggest skip calls if one day before no one introduced good topic
for discussion.
>From previous experience, we had a few times when nobody wanted to say
anything just because there was no interesting topic selected.

Thanks,
Igor

On Mon, Jan 13, 2020 at 4:37 PM Vova Vysotskyi  wrote:

> Hi Charles,
>
> I wouldn't be able to join Drill Hangouts during this week.
>
> Kind regards,
> Volodymyr Vysotskyi
>
>
> On Mon, Jan 13, 2020 at 4:26 PM Charles Givre  wrote:
>
> > Hello Drill Community,
> > I'd like to propose a reinstitution of Drill Hangouts, perhaps every
> other
> > week.  Given that the bulk of the development at the moment has shifted
> > from the US to Europe, I'd like to propose 0930 ET / 1630EET / 0630 PT
> for
> > the first one.  Depending on interest, we can rotate times.  Date TBD.
> >
> > Topics could include:
> > - Drill - Arrow integration
> > - Future work
> > - Anything else of interest
> >
> > Thoughts?
> > -- C
>

Re: Drill Hangout

[Charles Givre]

This week is a little busy for me as well.  I was thinking next week.  I'd like 
to get as many of us as possible.  

@Paul are you an early riser?

-- C


> On Jan 13, 2020, at 9:37 AM, Vova Vysotskyi  wrote:
> 
> Hi Charles,
> 
> I wouldn't be able to join Drill Hangouts during this week.
> 
> Kind regards,
> Volodymyr Vysotskyi
> 
> 
> On Mon, Jan 13, 2020 at 4:26 PM Charles Givre  wrote:
> 
>> Hello Drill Community,
>> I'd like to propose a reinstitution of Drill Hangouts, perhaps every other
>> week.  Given that the bulk of the development at the moment has shifted
>> from the US to Europe, I'd like to propose 0930 ET / 1630EET / 0630 PT for
>> the first one.  Depending on interest, we can rotate times.  Date TBD.
>> 
>> Topics could include:
>> - Drill - Arrow integration
>> - Future work
>> - Anything else of interest
>> 
>> Thoughts?
>> -- C

Re: Drill Hangout

[Vova Vysotskyi]

Hi Charles,

I wouldn't be able to join Drill Hangouts during this week.

Kind regards,
Volodymyr Vysotskyi


On Mon, Jan 13, 2020 at 4:26 PM Charles Givre  wrote:

> Hello Drill Community,
> I'd like to propose a reinstitution of Drill Hangouts, perhaps every other
> week.  Given that the bulk of the development at the moment has shifted
> from the US to Europe, I'd like to propose 0930 ET / 1630EET / 0630 PT for
> the first one.  Depending on interest, we can rotate times.  Date TBD.
>
> Topics could include:
> - Drill - Arrow integration
> - Future work
> - Anything else of interest
>
> Thoughts?
> -- C

Drill Hangout

[Charles Givre]

Hello Drill Community, 
I'd like to propose a reinstitution of Drill Hangouts, perhaps every other 
week.  Given that the bulk of the development at the moment has shifted from 
the US to Europe, I'd like to propose 0930 ET / 1630EET / 0630 PT for the first 
one.  Depending on interest, we can rotate times.  Date TBD.

Topics could include:
- Drill - Arrow integration
- Future work
- Anything else of interest

Thoughts?
-- C