Re: vim / Eclipse setups for new developers, on the C++ side

[Bikramjeet Vig]

I use eclipse for just about everything. For c++, in addition to the steps
mentioned in the wiki you need to manually add includes from the toolchain
dir for eclipse to identify everything, refer this file

to get an idea of which includes you need . Also you need to add support
for c++11 by following steps in this link
.
As far as debugging is concerned, eclipse is fairly painless when it comes
to c++, but if I want to do something more fancy that eclipse dosent
support, I fall back to using GDB.

On Fri, Sep 15, 2017 at 9:24 AM, Lars Volker  wrote:

> I use mosh + tmux + vim to develop on my desktop machine, and YouCompleteMe
> for completion and navigation (jump to definition only). Recently I found
> out that YCM also can jump to the declaration in Python. :)
>
> To debug the Frontend, I checkout the matching revision on my laptop and
> open it in Eclipse there. Then I forward the debug ports from my desktop
> machine. That gives me a better experience than running Eclipse in a remote
> X server.
>
> On Fri, Sep 15, 2017 at 7:36 AM, Shant Hovsepian 
> wrote:
>
> > Pretty happy with using clang_complete in vim for C++ code in impala.
> > Memory usage can get a bit high.
> >
> > clang_complete's quickfix feature is nice for showing errors, don't care
> > for the periodic mode instead prefer to bind it and run it as part of a
> :w
> >
> > -Shant
> >
> > On Wed, Sep 13, 2017 at 8:34 PM, 俊杰陈  wrote:
> >
> > > I use NetBeans to view the code, the "show call graph" is useful to me.
> > >
> > > 2017-09-14 5:44 GMT+08:00 Tim Armstrong :
> > >
> > > > For a long time I've just used GNU screen + VIM with syntax
> > highlighting.
> > > > Then "git grep" or search in VIM as needed to find things. Obviously
> > not
> > > > ideal for everyone.
> > > >
> > > > I've tried YouCompleteMe recently and it works fairly well but hasn't
> > > been
> > > > a game-changer for me. Jumping to definitions is handy sometimes but
> I
> > > > haven't found that it's changed my workflow that much.
> > > >
> > > > On Wed, Sep 13, 2017 at 2:18 PM, Philip Zeyliger <
> phi...@cloudera.com>
> > > > wrote:
> > > >
> > > > > Hi folks,
> > > > >
> > > > > I'm querying what folks use for working on the C++ side of the code
> > > base.
> > > > > I'm specifically interested in navigation tools for vim (better
> than
> > > > > ctags), error-highlighting tools for vim (showing syntax errors and
> > > such
> > > > > "live"), and Eclipse integration (yes, I've seen the wiki
> > > > >  > > > > Eclipse+Setup+for+Impala+Development>
> > > > > ).
> > > > >
> > > > > I'll be happy to collate and update
> > > > > https://cwiki.apache.org/confluence/display/IMPALA/
> > > > > Useful+Tips+for+New+Impala+Developers
> > > > > (or other appropriate pages) once I get some feedback!
> > > > >
> > > > > Thanks!
> > > > >
> > > > > -- Philip
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Thanks & Best Regards
> > >
> >
>

ZSH Users: Request for Review

[Lars Volker]

Hi All,

I've recently pushed a change to fix "enable_distcc" when using ZSH. Now
I'm looking for someone using ZSH who can have a look:
https://gerrit.cloudera.org/#/c/8049/

Thanks, Lars

Re: [ANNOUNCE] Apache Impala (incubating) 2.10.0 release

[Jim Apple]

-everyone but dev@

Thank you, Bharath!

On Thu, Sep 14, 2017 at 10:41 PM, Bharath Vissapragada 
wrote:

> The Apache Impala (incubating) team is pleased to announce the release of
> Impala 2.10.0.
>
> Impala is a high-performance C++ and Java SQL query engine for data stored
> in Apache Hadoop-based clusters.
>
> The release is available at: https://impala.incubator.
> apache.org/downloads.html
>
> Thanks,
>
> The Apache Impala (incubating) team
>
> =
>
> *Disclaimer*
>
> Apache Impala is an effort undergoing incubation at The Apache Software
> Foundation (ASF),
> sponsored by the name of Apache Incubator PMC. Incubation is required of
> all newly accepted
> projects until a further review indicates that the infrastructure,
> communications, and
> decision making process have stabilized in a manner consistent with other
> successful ASF
> projects. While incubation status is not necessarily a reflection of the
> completeness or
> stability of the code, it does indicate that the project has yet to be
> fully endorsed by
> the ASF.
>

Re: vim / Eclipse setups for new developers, on the C++ side

[Lars Volker]

I use mosh + tmux + vim to develop on my desktop machine, and YouCompleteMe
for completion and navigation (jump to definition only). Recently I found
out that YCM also can jump to the declaration in Python. :)

To debug the Frontend, I checkout the matching revision on my laptop and
open it in Eclipse there. Then I forward the debug ports from my desktop
machine. That gives me a better experience than running Eclipse in a remote
X server.

On Fri, Sep 15, 2017 at 7:36 AM, Shant Hovsepian 
wrote:

> Pretty happy with using clang_complete in vim for C++ code in impala.
> Memory usage can get a bit high.
>
> clang_complete's quickfix feature is nice for showing errors, don't care
> for the periodic mode instead prefer to bind it and run it as part of a :w
>
> -Shant
>
> On Wed, Sep 13, 2017 at 8:34 PM, 俊杰陈  wrote:
>
> > I use NetBeans to view the code, the "show call graph" is useful to me.
> >
> > 2017-09-14 5:44 GMT+08:00 Tim Armstrong :
> >
> > > For a long time I've just used GNU screen + VIM with syntax
> highlighting.
> > > Then "git grep" or search in VIM as needed to find things. Obviously
> not
> > > ideal for everyone.
> > >
> > > I've tried YouCompleteMe recently and it works fairly well but hasn't
> > been
> > > a game-changer for me. Jumping to definitions is handy sometimes but I
> > > haven't found that it's changed my workflow that much.
> > >
> > > On Wed, Sep 13, 2017 at 2:18 PM, Philip Zeyliger 
> > > wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I'm querying what folks use for working on the C++ side of the code
> > base.
> > > > I'm specifically interested in navigation tools for vim (better than
> > > > ctags), error-highlighting tools for vim (showing syntax errors and
> > such
> > > > "live"), and Eclipse integration (yes, I've seen the wiki
> > > >  > > > Eclipse+Setup+for+Impala+Development>
> > > > ).
> > > >
> > > > I'll be happy to collate and update
> > > > https://cwiki.apache.org/confluence/display/IMPALA/
> > > > Useful+Tips+for+New+Impala+Developers
> > > > (or other appropriate pages) once I get some feedback!
> > > >
> > > > Thanks!
> > > >
> > > > -- Philip
> > > >
> > >
> >
> >
> >
> > --
> > Thanks & Best Regards
> >
>

Re: vim / Eclipse setups for new developers, on the C++ side

[Shant Hovsepian]

Pretty happy with using clang_complete in vim for C++ code in impala.
Memory usage can get a bit high.

clang_complete's quickfix feature is nice for showing errors, don't care
for the periodic mode instead prefer to bind it and run it as part of a :w

-Shant

On Wed, Sep 13, 2017 at 8:34 PM, 俊杰陈  wrote:

> I use NetBeans to view the code, the "show call graph" is useful to me.
>
> 2017-09-14 5:44 GMT+08:00 Tim Armstrong :
>
> > For a long time I've just used GNU screen + VIM with syntax highlighting.
> > Then "git grep" or search in VIM as needed to find things. Obviously not
> > ideal for everyone.
> >
> > I've tried YouCompleteMe recently and it works fairly well but hasn't
> been
> > a game-changer for me. Jumping to definitions is handy sometimes but I
> > haven't found that it's changed my workflow that much.
> >
> > On Wed, Sep 13, 2017 at 2:18 PM, Philip Zeyliger 
> > wrote:
> >
> > > Hi folks,
> > >
> > > I'm querying what folks use for working on the C++ side of the code
> base.
> > > I'm specifically interested in navigation tools for vim (better than
> > > ctags), error-highlighting tools for vim (showing syntax errors and
> such
> > > "live"), and Eclipse integration (yes, I've seen the wiki
> > >  > > Eclipse+Setup+for+Impala+Development>
> > > ).
> > >
> > > I'll be happy to collate and update
> > > https://cwiki.apache.org/confluence/display/IMPALA/
> > > Useful+Tips+for+New+Impala+Developers
> > > (or other appropriate pages) once I get some feedback!
> > >
> > > Thanks!
> > >
> > > -- Philip
> > >
> >
>
>
>
> --
> Thanks & Best Regards
>