drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vova Vysotskyi <vvo...@gmail.com>
Subject Re: 1.17.0 updated protobuf but mapr ODBC drivers have not been updated
Date Mon, 13 Jan 2020 18:40:19 GMT
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 <bob@rud.is> 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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message