You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Matthew Jacobs <mj...@cloudera.com> on 2016/12/07 05:48:15 UTC
Important: new shell & bootstrap required after rebasing
The Kudu version was updated to the latest master. After fetching the
latest Impala commits (including commit 5188f87) and rebasing, you'll
need to:
1) start a new shell OR make sure to
export IMPALA_TOOLCHAIN_BUILD_ID=301-05e1fe2b3b
2) Run buildall.sh, that will:
a) download the new Kudu bits in the toolchain by calling
bootstrap_toolchain.py (or you can do so yourself)
b) restart the minicluster with the new kudu
We will have to update Kudu a few more times before the release, so
thank you for your patience. Hopefully this makes it as painless as
possible.
Re: Important: new shell & bootstrap required after rebasing
Posted by Lars Volker <lv...@cloudera.com>.
If you don't want to mess with your pane layout in tmux you can run
tmux respawn-pane -k
to kill and replace the current pane with an entirely fresh shell.
I bind this to a shortcut in my tmux config like so:
bind K respawn-pane -k
Cheers, Lars
On Wed, Dec 7, 2016 at 2:49 PM, Matthew Jacobs <mj...@cloudera.com> wrote:
> Sorry, that was a different build I referenced for a newer toolchain.
>
>
> Starting a new shell should work.
>
> Otherwise use:
> export IMPALA_TOOLCHAIN_BUILD_ID=289-f12b0dd2e9
>
> On Wed, Dec 7, 2016 at 2:44 PM, Jim Apple <jb...@cloudera.com> wrote:
> > I followed these instructions and saw a HTTP 403 error on:
> >
> > https://native-toolchain.s3.amazonaws.com/build/301-
> 05e1fe2b3b/kudu/60aa54e-gcc-4.9.2/kudu-60aa54e-gcc-4.9.2-
> ec2-package-ubuntu-14-04.tar.gz
> >
> > On Tue, Dec 6, 2016 at 9:48 PM, Matthew Jacobs <mj...@cloudera.com> wrote:
> >> The Kudu version was updated to the latest master. After fetching the
> >> latest Impala commits (including commit 5188f87) and rebasing, you'll
> >> need to:
> >>
> >> 1) start a new shell OR make sure to
> >> export IMPALA_TOOLCHAIN_BUILD_ID=301-05e1fe2b3b
> >>
> >>
> >> 2) Run buildall.sh, that will:
> >> a) download the new Kudu bits in the toolchain by calling
> >> bootstrap_toolchain.py (or you can do so yourself)
> >> b) restart the minicluster with the new kudu
> >>
> >>
> >> We will have to update Kudu a few more times before the release, so
> >> thank you for your patience. Hopefully this makes it as painless as
> >> possible.
>
Re: Important: new shell & bootstrap required after rebasing
Posted by Matthew Jacobs <mj...@cloudera.com>.
Sorry, that was a different build I referenced for a newer toolchain.
Starting a new shell should work.
Otherwise use:
export IMPALA_TOOLCHAIN_BUILD_ID=289-f12b0dd2e9
On Wed, Dec 7, 2016 at 2:44 PM, Jim Apple <jb...@cloudera.com> wrote:
> I followed these instructions and saw a HTTP 403 error on:
>
> https://native-toolchain.s3.amazonaws.com/build/301-05e1fe2b3b/kudu/60aa54e-gcc-4.9.2/kudu-60aa54e-gcc-4.9.2-ec2-package-ubuntu-14-04.tar.gz
>
> On Tue, Dec 6, 2016 at 9:48 PM, Matthew Jacobs <mj...@cloudera.com> wrote:
>> The Kudu version was updated to the latest master. After fetching the
>> latest Impala commits (including commit 5188f87) and rebasing, you'll
>> need to:
>>
>> 1) start a new shell OR make sure to
>> export IMPALA_TOOLCHAIN_BUILD_ID=301-05e1fe2b3b
>>
>>
>> 2) Run buildall.sh, that will:
>> a) download the new Kudu bits in the toolchain by calling
>> bootstrap_toolchain.py (or you can do so yourself)
>> b) restart the minicluster with the new kudu
>>
>>
>> We will have to update Kudu a few more times before the release, so
>> thank you for your patience. Hopefully this makes it as painless as
>> possible.
Re: Important: new shell & bootstrap required after rebasing
Posted by Jim Apple <jb...@cloudera.com>.
I followed these instructions and saw a HTTP 403 error on:
https://native-toolchain.s3.amazonaws.com/build/301-05e1fe2b3b/kudu/60aa54e-gcc-4.9.2/kudu-60aa54e-gcc-4.9.2-ec2-package-ubuntu-14-04.tar.gz
On Tue, Dec 6, 2016 at 9:48 PM, Matthew Jacobs <mj...@cloudera.com> wrote:
> The Kudu version was updated to the latest master. After fetching the
> latest Impala commits (including commit 5188f87) and rebasing, you'll
> need to:
>
> 1) start a new shell OR make sure to
> export IMPALA_TOOLCHAIN_BUILD_ID=301-05e1fe2b3b
>
>
> 2) Run buildall.sh, that will:
> a) download the new Kudu bits in the toolchain by calling
> bootstrap_toolchain.py (or you can do so yourself)
> b) restart the minicluster with the new kudu
>
>
> We will have to update Kudu a few more times before the release, so
> thank you for your patience. Hopefully this makes it as painless as
> possible.