You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Lars Volker <lv...@cloudera.com> on 2017/03/29 12:52:18 UTC
Kudu version mismatch between impala-config.sh and toolchain
Hi All,
In impala-config.sh we consume Kudu version 16dd6e4.
bin/impala-config.sh:124:export IMPALA_KUDU_VERSION=16dd6e4
The toolchain does not build that version, but instead defaults to 2b0edbe.
This breaks using a custom toolchain for me. Even the historical versions
don't contain 16dd6e4.
KUDU_VERSIONS="0.8.0-RC1 0.9.0-RC1 0.10.0-RC1 1.0.0-RC1 f2aeba 60aa54e
a70c905006 e018a83 cd7b0dd"
Where does 16dd6e4 come from? How can we fix this?
Thanks, Lars
Re: Kudu version mismatch between impala-config.sh and toolchain
Posted by Matthew Jacobs <mj...@cloudera.com>.
https://gerrit.cloudera.org/#/c/6513/
On Wed, Mar 29, 2017 at 11:22 AM, Matthew Jacobs <mj...@cloudera.com> wrote:
> Will do.
>
> On Wed, Mar 29, 2017 at 10:49 AM, Lars Volker <lv...@cloudera.com> wrote:
>> Cool, thanks. My change has already been published to the S3 bucket, but I
>> hadn't updated the toolchain ID in the Impala repository. Could you push a
>> change to Impala once your publishing build is completed?
>>
>> On Wed, Mar 29, 2017 at 7:21 PM, Matthew Jacobs <mj...@cloudera.com> wrote:
>>
>>> Lars, I'm starting a new toolchain build now with that change as well
>>> as your latest change:
>>>
>>> * 5364e21 - (upstream/master, gerrit/master) IMPALA-4226, IMPALA-4227:
>>> bump max threads, handle dwz compressed symbols (2 days ago) <Lars
>>> Volker>
>>>
>>> On Wed, Mar 29, 2017 at 9:52 AM, Matthew Jacobs <mj...@cloudera.com> wrote:
>>> > I'll get that version in to the toolchain repo:
>>> > https://gerrit.cloudera.org/#/c/6509/
>>> >
>>> > On Wed, Mar 29, 2017 at 5:52 AM, Lars Volker <lv...@cloudera.com> wrote:
>>> >> Hi All,
>>> >>
>>> >> In impala-config.sh we consume Kudu version 16dd6e4.
>>> >>
>>> >> bin/impala-config.sh:124:export IMPALA_KUDU_VERSION=16dd6e4
>>> >>
>>> >> The toolchain does not build that version, but instead defaults to
>>> 2b0edbe.
>>> >> This breaks using a custom toolchain for me. Even the historical
>>> versions
>>> >> don't contain 16dd6e4.
>>> >>
>>> >> KUDU_VERSIONS="0.8.0-RC1 0.9.0-RC1 0.10.0-RC1 1.0.0-RC1 f2aeba 60aa54e
>>> >> a70c905006 e018a83 cd7b0dd"
>>> >>
>>> >> Where does 16dd6e4 come from? How can we fix this?
>>> >>
>>> >> Thanks, Lars
>>>
Re: Kudu version mismatch between impala-config.sh and toolchain
Posted by Matthew Jacobs <mj...@cloudera.com>.
Will do.
On Wed, Mar 29, 2017 at 10:49 AM, Lars Volker <lv...@cloudera.com> wrote:
> Cool, thanks. My change has already been published to the S3 bucket, but I
> hadn't updated the toolchain ID in the Impala repository. Could you push a
> change to Impala once your publishing build is completed?
>
> On Wed, Mar 29, 2017 at 7:21 PM, Matthew Jacobs <mj...@cloudera.com> wrote:
>
>> Lars, I'm starting a new toolchain build now with that change as well
>> as your latest change:
>>
>> * 5364e21 - (upstream/master, gerrit/master) IMPALA-4226, IMPALA-4227:
>> bump max threads, handle dwz compressed symbols (2 days ago) <Lars
>> Volker>
>>
>> On Wed, Mar 29, 2017 at 9:52 AM, Matthew Jacobs <mj...@cloudera.com> wrote:
>> > I'll get that version in to the toolchain repo:
>> > https://gerrit.cloudera.org/#/c/6509/
>> >
>> > On Wed, Mar 29, 2017 at 5:52 AM, Lars Volker <lv...@cloudera.com> wrote:
>> >> Hi All,
>> >>
>> >> In impala-config.sh we consume Kudu version 16dd6e4.
>> >>
>> >> bin/impala-config.sh:124:export IMPALA_KUDU_VERSION=16dd6e4
>> >>
>> >> The toolchain does not build that version, but instead defaults to
>> 2b0edbe.
>> >> This breaks using a custom toolchain for me. Even the historical
>> versions
>> >> don't contain 16dd6e4.
>> >>
>> >> KUDU_VERSIONS="0.8.0-RC1 0.9.0-RC1 0.10.0-RC1 1.0.0-RC1 f2aeba 60aa54e
>> >> a70c905006 e018a83 cd7b0dd"
>> >>
>> >> Where does 16dd6e4 come from? How can we fix this?
>> >>
>> >> Thanks, Lars
>>
Re: Kudu version mismatch between impala-config.sh and toolchain
Posted by Lars Volker <lv...@cloudera.com>.
Cool, thanks. My change has already been published to the S3 bucket, but I
hadn't updated the toolchain ID in the Impala repository. Could you push a
change to Impala once your publishing build is completed?
On Wed, Mar 29, 2017 at 7:21 PM, Matthew Jacobs <mj...@cloudera.com> wrote:
> Lars, I'm starting a new toolchain build now with that change as well
> as your latest change:
>
> * 5364e21 - (upstream/master, gerrit/master) IMPALA-4226, IMPALA-4227:
> bump max threads, handle dwz compressed symbols (2 days ago) <Lars
> Volker>
>
> On Wed, Mar 29, 2017 at 9:52 AM, Matthew Jacobs <mj...@cloudera.com> wrote:
> > I'll get that version in to the toolchain repo:
> > https://gerrit.cloudera.org/#/c/6509/
> >
> > On Wed, Mar 29, 2017 at 5:52 AM, Lars Volker <lv...@cloudera.com> wrote:
> >> Hi All,
> >>
> >> In impala-config.sh we consume Kudu version 16dd6e4.
> >>
> >> bin/impala-config.sh:124:export IMPALA_KUDU_VERSION=16dd6e4
> >>
> >> The toolchain does not build that version, but instead defaults to
> 2b0edbe.
> >> This breaks using a custom toolchain for me. Even the historical
> versions
> >> don't contain 16dd6e4.
> >>
> >> KUDU_VERSIONS="0.8.0-RC1 0.9.0-RC1 0.10.0-RC1 1.0.0-RC1 f2aeba 60aa54e
> >> a70c905006 e018a83 cd7b0dd"
> >>
> >> Where does 16dd6e4 come from? How can we fix this?
> >>
> >> Thanks, Lars
>
Re: Kudu version mismatch between impala-config.sh and toolchain
Posted by Matthew Jacobs <mj...@cloudera.com>.
Lars, I'm starting a new toolchain build now with that change as well
as your latest change:
* 5364e21 - (upstream/master, gerrit/master) IMPALA-4226, IMPALA-4227:
bump max threads, handle dwz compressed symbols (2 days ago) <Lars
Volker>
On Wed, Mar 29, 2017 at 9:52 AM, Matthew Jacobs <mj...@cloudera.com> wrote:
> I'll get that version in to the toolchain repo:
> https://gerrit.cloudera.org/#/c/6509/
>
> On Wed, Mar 29, 2017 at 5:52 AM, Lars Volker <lv...@cloudera.com> wrote:
>> Hi All,
>>
>> In impala-config.sh we consume Kudu version 16dd6e4.
>>
>> bin/impala-config.sh:124:export IMPALA_KUDU_VERSION=16dd6e4
>>
>> The toolchain does not build that version, but instead defaults to 2b0edbe.
>> This breaks using a custom toolchain for me. Even the historical versions
>> don't contain 16dd6e4.
>>
>> KUDU_VERSIONS="0.8.0-RC1 0.9.0-RC1 0.10.0-RC1 1.0.0-RC1 f2aeba 60aa54e
>> a70c905006 e018a83 cd7b0dd"
>>
>> Where does 16dd6e4 come from? How can we fix this?
>>
>> Thanks, Lars
Re: Kudu version mismatch between impala-config.sh and toolchain
Posted by Matthew Jacobs <mj...@cloudera.com>.
I'll get that version in to the toolchain repo:
https://gerrit.cloudera.org/#/c/6509/
On Wed, Mar 29, 2017 at 5:52 AM, Lars Volker <lv...@cloudera.com> wrote:
> Hi All,
>
> In impala-config.sh we consume Kudu version 16dd6e4.
>
> bin/impala-config.sh:124:export IMPALA_KUDU_VERSION=16dd6e4
>
> The toolchain does not build that version, but instead defaults to 2b0edbe.
> This breaks using a custom toolchain for me. Even the historical versions
> don't contain 16dd6e4.
>
> KUDU_VERSIONS="0.8.0-RC1 0.9.0-RC1 0.10.0-RC1 1.0.0-RC1 f2aeba 60aa54e
> a70c905006 e018a83 cd7b0dd"
>
> Where does 16dd6e4 come from? How can we fix this?
>
> Thanks, Lars