Installation Problem?

[Katelyn Mulgrew]

Impala experts,

I am trying to run the impala shell (what I really want is to see if I 
installed impala properly).  I am on Ubuntu and have done all the necessary 
apt-gets.  However, when I write "impala-shell" and hit return, I get a number 
of errors, as described here https://issues.apache.org/jira/browse/IMPALA-2863. 
 Can you help me?

Sincerely,

Katelyn Mulgrew
The information included in this email and any attachments transmitted with it 
may contain information that is confidential. This email and any attachments 
are for the exclusive and confidential use of the intended recipient. If you 
are not the intended recipient, please do not read, copy, disclose, distribute 
or take action in reliance upon this email. If you have received this email in 
error, please notify the sender immediately by return email and promptly delete 
this message and its attachments from your computer system. In the absence of a 
signed writing to the contrary, BJSS' relevant standard terms and conditions 
will apply to instructions or descriptions in this email regarding any work to 
be undertaken. BJSS shall have no liability for any damages to your system or 
data caused by any virus transmitted by this email or any attachments. Please 
carry out virus or such other checks as you consider appropriate. BJSS, Inc. 14 
Wall Street, 20th Fl, Suite #2069, New York, NY 10005

Upcoming changes to distcc scripts

[Tim Armstrong]

I'm about to start a merge for a patch that solves some of the issues with
distcc - switching between ASAN and non-ASAN builds and with ccache:
https://gerrit.cloudera.org/#/c/6493/ . Unfortunately it won't be
completely transparent. When you pull down the patch, you'll need to:

   - Open a new terminal or run "unset IMPALA_CXX_COMPILER" in your current
   terminal
   - Source bin/distcc/distcc_env.sh
   - Rebuild with buildall.sh

If you run into any problems, you can try cleaning out your cmake-generated
files.

   - ./bin/clean.sh && ./bin/create-test-configuration.sh


Cheers,
Tim

Re: Best practice when closing issues?

[Tim Armstrong]

I've always used "Resolve Issue".

I think there's only a distinction for more complex workflows. According to
JIRA, "Resolving an issue indicates that the developers are satisfied the
issue is finished" and "Closing an issue indicates that there is no more
work to be done on it, and that it has been verified as complete".


On Mon, Apr 3, 2017 at 2:32 AM, Lars Volker  wrote:

> Do we have a best practice for the Status of finished work? Currently we
> seem to use "Resolved" mostly, but sometime also "Closed". When should I
> use which one?
>
> Thanks, Lars
>
> StatusIssuesPercentage
> Open
>  jspa?reset=true=project+%3D+IMPALA+AND+status+
> %3D+Open+ORDER+BY+priority+DESC=hide>
> 1491
>
>29%
> Reopened
>  jspa?reset=true=project+%3D+IMPALA+AND+status+
> %3D+Reopened+ORDER+BY+priority+DESC=hide>
> 44
>
>1%
> Resolved
>  jspa?reset=true=project+%3D+IMPALA+AND+status+
> %3D+Resolved+ORDER+BY+priority+DESC=hide>
> 3550
>
>69%
> Closed
>  jspa?reset=true=project+%3D+IMPALA+AND+status+
> %3D+Closed+ORDER+BY+priority+DESC=hide>
> 45
>
>1%
>

Best practice when closing issues?

[Lars Volker]

Do we have a best practice for the Status of finished work? Currently we
seem to use "Resolved" mostly, but sometime also "Closed". When should I
use which one?

Thanks, Lars

StatusIssuesPercentage
Open

1491

   29%
Reopened

44

   1%
Resolved

3550

   69%
Closed

45

   1%