hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-726) Hama on Mesos
Date Tue, 01 Jul 2014 05:48:26 GMT

    [ https://issues.apache.org/jira/browse/HAMA-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048544#comment-14048544

Edward J. Yoon commented on HAMA-726:

Hi [~jfenc91], I wonder why did you use double quotation again?

@@ -202,14 +210,15 @@ if $cygwin; then
-HAMA_OPTS="$HAMA_OPTS -Dhama.home.dir=$HAMA_HOME"
-HAMA_OPTS="$HAMA_OPTS -Dhama.root.logger=${HAMA_ROOT_LOGGER:-INFO,console}"
+HAMA_OPTS=""$HAMA_OPTS" -Dhama.home.dir=\"$HAMA_HOME\""
+HAMA_OPTS=""$HAMA_OPTS" -Dhama.root.logger=${HAMA_ROOT_LOGGER:-INFO,console}"
 if [ "x$JAVA_LIBRARY_PATH" != "x" ]; then
-  HAMA_OPTS="$HAMA_OPTS -Djava.library.path=$JAVA_LIBRARY_PATH"
+  HAMA_OPTS=""$HAMA_OPTS" -Djava.library.path=$JAVA_LIBRARY_PATH"
 # run it
-exec "$JAVA" $JAVA_HEAP_MAX $HAMA_OPTS -classpath "$CLASSPATH" $CLASS "$@"
+exec "$JAVA" "$JAVA_HEAP_MAX" "$HAMA_OPTS" -classpath "$CLASSPATH" $CLASS "$@"

When I run Hama as a classic-mode, system creates odd directories and can't find the proper

edward@edward-VirtualBox:~/workspace/hama-trunk$ ls
"    c++          commons  contrib  dist  examples  lib          logs   ml          pom.xml
    src     yarn
bin  CHANGES.txt  conf     core     docs  graph     LICENSE.txt  mesos  NOTICE.txt  README.txt
edward@edward-VirtualBox:~/workspace/hama-trunk$ ls '"'
edward@edward-VirtualBox:~/workspace/hama-trunk$ ls '"/home/'

> Hama on Mesos
> -------------
>                 Key: HAMA-726
>                 URL: https://issues.apache.org/jira/browse/HAMA-726
>             Project: Hama
>          Issue Type: New Feature
>          Components: bsp core
>            Reporter: Suraj Menon
>            Assignee: Jeff Fenchel
>             Fix For: 0.7.0
>         Attachments: HAMA-726-v2.patch, HAMA-726.patch
> Since we are going to refactor our code to work on YARN, it would be nice to keep our
abstraction levels to make it feasible to work on Mesos. 
> Documentation: http://incubator.apache.org/mesos/documentation.html
> Framework development guide:
> https://github.com/mesos/mesos/wiki/App-Framework-development-guide

This message was sent by Atlassian JIRA

View raw message