Page History

...

We use the Google Logging Library. See httphttps://google-gloggithub.googlecode.com/svngoogle/glog/trunkblob/docmaster/glogREADME.htmlrst 

The library defines logging levels of ERROR, INFO and WARNING. We also use verbose logging which can be turned on with with environment variables. e.g:

...

export GLOG_logtostderr=1

Call Trace

Sometimes you may want to know how the code path comes into a function. In the backend, you can add some logs for GetStackTrace():

VLOG_QUERY << "args: " << your_interested_var << std::endl << GetStackTrace();

Make sure "util/debug-util.h" is included in your file.

In the frontend, you can add some logs for a generated Exception:

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

public class YourInterestedClass {
  private final static Logger LOG = LoggerFactory.getLogger(YourInterestedClass.class);
  public void yourInterestedFunc() {
    ...
    LOG.info("some message", new Exception("call trace"));
    ...
  }

Existing Hadoop Installations

...

• vim
  • https://github.com/Valloric/YouCompleteMe. Smart completion, including understanding C++ code and highlighting errors.
    • Install Vundle by following instructions at https://github.com/VundleVim/Vundle.vim
    • Install the YouCompleteMe Vim plugin with the following steps.
      • Add plugin to .vimrc in the Vundle section: 

        Plugin 'Valloric/YouCompleteMe' 

         

        
        

      • Run
        

        vim +PluginInstall +qall  # from the command line

         

        
        

      • Finish compiling YCM with clang support:
        

        cd ~/.vim/bundle/YouCompleteMe
        ./install.sh --clang-completer

  • eclim. Eclipse integration
  • clang_complete (an alternative to YouCompleteMe)
• Eclipse
  • See Eclipse Setup for Impala Development
• NetBeans

...

Starting Minicluster with SSL

...

# Make sure you specify your Common Name as your host's FQDN
openssl req -newkey rsa:2048 -nodes -keyout key.pem -x509 -days 365 -out certificate.pem
 
# After building, you can start your Impala cluster with the same flags as documented in
# http://impala.apache.org/docs/build/html/topics/impala_ssl.html
# Note that we are setting the --catalog_service_host and --state_store_host to avoid them defaulting to localhost.
# SSL won't tolerate mismatch Common Name
 
$IMPALA_HOME/bin/start-impala-cluster.py --impalad_args='--backend_client_rpc_timeout_ms=10000 --catalog_service_host=$(hostname -f) --state_store_host=$(hostname -f) --ssl_server_certificate=$IMPALA_HOME/certificate.pem --ssl_private_key=$IMPALA_HOME/key.pem --ssl_client_ca_certificate=$IMPALA_HOME/certificate.pem' --catalogd_args='--catalog_service_host=$(hostname -f) --state_store_host=$(hostname -f) --ssl_server_certificate=$IMPALA_HOME/certificate.pem --ssl_private_key=$IMPALA_HOME/key.pem --ssl_client_ca_certificate=$IMPALA_HOME/certificate.pem' --state_store_args='--catalog_service_host=$(hostname -f) --state_store_host=$(hostname -f) --ssl_server_certificate=$IMPALA_HOME/certificate.pem --ssl_private_key=$IMPALA_HOME/key.pem --ssl_client_ca_certificate=$IMPALA_HOME/certificate.pem'

Running Automated Code Quality Checks Locally

When a patchset is published in Gerrit, automated code checks are ran.  To run these checks on local code before pushing, follow these steps.

Python

From the Impala home directory, run:

./bin/jenkins/critique-gerrit-review.py --dryrun 

C++

From the Impala home directory, run clang tidy (note: this runs a full build and thus takes a few minutes):

./bin/run_clang_tidy.sh