Welcome to my website. I am always posting links to photo albums, art, technology and other creations. Everything that you will see on my numerous personal sites is powered by the formVistaTM Website Management Engine.


  • Debugging MapReduce MRv2 Code in Eclipse
    03/24/2015 11:36PM

    Following is how to set-up your environment to be able to set breakpoints, step-through, and debug your MapReduce code in Eclipse.

    All of the this was done on a machine running Linux, but should work just fine for any *nix machine, and perhaps Windows running Cygwin (assuming that you can get Hadoop and its naitive libraries compiled under Windows).

    This also assumes that you are building your project with maven.

    Install a pseudo-distributed hadooop cluster on your development box.  (Yes, this calls for another article on exactly how to do that which I will do shortly and link to from here).

    Add the following environment variables to .bash_profile to ensure that they will be applied to any login shells (make sure to check the location of the directories for your installed hadoop distribution):

        export LD_LIBRARY_PATH=/usr/lib/hadoop/lib/native
        export HADOOP_HOME=/usr/lib/hadoop

    Make sure to include the following dependencies in your pom:


    After you import your maven project into Eclipse update the Build Path to include the correct path to the Native library shared objects:

    Right-click on your project and select 'Build Path -> Configure Build Path:

    Click on 'Libraries' tab:

    Click the drop-down arrow for the 'Maven Dependencies'

    Click on the drop-down arrow on the 'hadoop-common'.jar

    Select the 'Native library location' entry, and click 'Edit'

    Browse to the path of the native directory, in my case it was /usr/lib/hadoop/lib/native.

    Click 'OK'

    Click 'OK' to close the build path dialogue

    Create a run configuration for the Main class in your project:

    Make sure that you do not add the /etc/hadoop/conf* dir to the class path.

    Add any commandline arguments for input and output directories to the 'Program arguments' section of the run configuration, that points to your LOCAL file system and not HDFS.

    Afterwhich, you should be able to run your M/R code and debug it through Eclipse.

  • Configuring Eclipse to Replace Tabs with Spaces for Indentation
    01/23/2015 6:46PM

    Following are two basic settings (I believe that there are other language specific, C++ for instance, settings as well).

     For Java:

    Window->Preferences->Java->Code Style->Formatter->
    Click on 'New' to create a new profile and select the profile that you want to copy
    Then click 'Edit' and select 'Spaces Only' from the 'Tab Policy' dropdown.

    You can further set the indentation and tab size.

    For default text editor:

    Window->Preferences->General->Editors->Text Editors->Insert spaces for tabs

  • Eclipse Android Development Error executing aapt: Cannot run program "/path/to/aapt": error=2, No such file or directory: error=2, No such file or directory
    03/24/2014 2:44PM

    Even though the ADT bundle provides a 64 bit version, the system requirements indicate that "64-bit distributions must be capable of running 32-bit applications."  I failed to see that when installing it under Fedora Core 20 and was getting the following error from Eclipse:

    Error executing aapt: Cannot run program "/home/rchapin/sdks/adt-bundle-linux-x86_64-20131030/sdk/build-tools/android-4.4/aapt": error=2, No such file or directory: error=2, No such file or directory  android_sdk    line 1   Android ADT Problem

    I checked to see if the file was there.  Yep.  I checked to see if was executable.  Yep.

    It was only after finding a blog post about it and doing a $ file command on it that I noticed that it was a 32 bit executable:

    $ file adt-bundle-linux-x86_64-20131030/sdk/build-tools/android-4.4/aapt
    adt-bundle-linux-x86_64-20131030/sdk/build-tools/android-4.4/aapt: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped

    All I had to do was install the 32 bit libraries that the binaries are linked against:

    # yum install glibc.i686 zlib.i686 libstdc++.i686 ncurses-libs.i686 libgcc.i686

    Once installed, the error should disappear from Eclipse as it tries to invoke the binaries and do a regular build and/or restarting or cleaning the project should clear the errors.

  • Setting up Android in Eclipse, Unable to resolve target 'android-18'
    03/24/2014 2:22PM

    When setting up Eclipse for Android development, after you have installed the Develeper Tools and NDK Plugins and linked to the ADT-bundle and then imported your project (see othere posts related by searching for 'android') I got the following error:

    [2014-03-24 14:14:53 - android_sdk] Unable to resolve target 'android-18'

    I went and checked to make sure that the Platform.MinPlatformToolsRev property in the ~/path/to/adt-bundle-linux-x86_64-20131030/sdk/tools/source.properties matched that of my project.properties file.

    They were both 18.  Eh?  Why the error?

    So, in Eclipse, I went to the Window > Android SDK Manager and looked at the version of the Android SDK Platform that was installed.  It was:

    Android 4.4.2 (API 19) and the checkbox next to SDK Platform under that sub-heading was checked.

    So, I went back to my project.properties and updated the target property to:


    which eliminated that error.

  • "Invalid Project Description", project path "overlaps the location of another project" with the same name When Importing Existing Android Project in Eclipse
    03/24/2014 2:06PM

    I've got a new install of Eclipse and am setting up to do some Android development.

    After getting the Develeper Tools and NDK Plugins installed and linking to the ADT-bundle that I downloaded, I was getting an error when attempting to import the existing project by going to File > Import > Android > Existing Android Code Into Workspace.

    The error was:

    Invalid project description /some/path/to/project/dir_name overlaps the location of another project: dir_name

    After a few searches and a couple of tries, using the File > Import > General > Existing Projects into Workspace seemed to work just fine.

  • 1 2 3 4 >>
Advanced Search