Hello, I realized that the structure of Helium application has after https://github.com/apache/incubator-zeppelin/pull/836. I was able to run a sample Helium application based on the changed structure, will explore more of the changes in the code.
Thanks, Anish. On Wed, May 4, 2016 at 6:54 PM, moon soo Lee <m...@apache.org> wrote: > Hi Anish, > > SparkMon is an example that based on PoC implementation. While > https://github.com/apache/incubator-zeppelin/pull/836 is implementing > slightly different way, SparkMon has to be changed. > > Thanks, > moon > > On Tue, May 3, 2016 at 9:18 AM anish singh <anish18...@gmail.com> wrote: > > > Hello, > > > > As advised earlier, the Zeppelin project was successfully built after > > merging https://github.com/apache/incubator-zeppelin/pull/836 into the > > cloned repository. However, the code for Helium packages in > > ZEPPELIN_HOME/zeppelin-interpreter/target/classes/ directory does not > > contain the following classes: > > > > org.apache.zeppelin.helium.ApplicationArgument > > org.apache.zeppelin.helium.Signal > > org.apache.zeppelin.resource.ResourceKey > > > > which are needed by the SparkMon example Helium application in the run() > > and the signal() method. Please let me know where this is going wrong or > > the source code for the Helium packages has been modified so that the > > SparkMon application has to be changed to make it run. > > > > Thanks, > > Anish. > > > > On Mon, May 2, 2016 at 6:52 PM, anish singh <anish18...@gmail.com> > wrote: > > > > > Hello, > > > > > > In trying to import the zeppelin project into eclipse, using the 'mvn > > > eclipse:eclipse' command on the branch on which > > > https://github.com/apache/incubator-zeppelin/pull/836 was merged, the > > > following error log was generated : > > > > > > branch name : 'coding' > > > > > > incubator-zeppelin git:(coding) ✗ mvn -e > > > [INFO] Error stacktraces are turned on. > > > [INFO] Scanning for projects... > > > [WARNING] > > > [WARNING] Some problems were encountered while building the effective > > > model for > > org.apache.zeppelin:zeppelin-zengine:jar:0.6.0-incubating-SNAPSHOT > > > [WARNING] > 'dependencies.dependency.(groupId:artifactId:type:classifier)' > > > must be unique: junit:junit:jar -> duplicate declaration of version > (?) @ > > > line 204, column 17 > > > [WARNING] > > > [WARNING] Some problems were encountered while building the effective > > > model for > > org.apache.zeppelin:zeppelin-spark:jar:0.6.0-incubating-SNAPSHOT > > > [WARNING] 'build.plugins.plugin.version' for > > > org.scala-tools:maven-scala-plugin is missing. @ line 404, column 15 > > > [WARNING] > > > [WARNING] Some problems were encountered while building the effective > > > model for > > org.apache.zeppelin:zeppelin-flink:jar:0.6.0-incubating-SNAPSHOT > > > [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique > but > > > found duplicate declaration of plugin > > > org.apache.maven.plugins:maven-dependency-plugin @ line 349, column 15 > > > [WARNING] > > > [WARNING] Some problems were encountered while building the effective > > > model for > > > org.apache.zeppelin:zeppelin-cassandra:jar:0.6.0-incubating-SNAPSHOT > > > [WARNING] 'build.plugins.plugin.version' for > > > org.scala-tools:maven-scala-plugin is missing. @ line 173, column 21 > > > [WARNING] > > > [WARNING] It is highly recommended to fix these problems because they > > > threaten the stability of your build. > > > [WARNING] > > > [WARNING] For this reason, future Maven versions might no longer > support > > > building such malformed projects. > > > [WARNING] > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] Reactor Build Order: > > > [INFO] > > > [INFO] Zeppelin > > > [INFO] Zeppelin: Interpreter > > > [INFO] Zeppelin: Zengine > > > [INFO] Zeppelin: Display system apis > > > [INFO] Zeppelin: Spark dependencies > > > [INFO] Zeppelin: Spark > > > [INFO] Zeppelin: Markdown interpreter > > > [INFO] Zeppelin: Angular interpreter > > > [INFO] Zeppelin: Shell interpreter > > > [INFO] Zeppelin: Hive interpreter > > > [INFO] Zeppelin: HBase interpreter > > > [INFO] Zeppelin: Apache Phoenix Interpreter > > > [INFO] Zeppelin: PostgreSQL interpreter > > > [INFO] Zeppelin: JDBC interpreter > > > [INFO] Zeppelin: Tajo interpreter > > > [INFO] Zeppelin: File System Interpreters > > > [INFO] Zeppelin: Flink > > > [INFO] Zeppelin: Apache Ignite interpreter > > > [INFO] Zeppelin: Kylin interpreter > > > [INFO] Zeppelin: Lens interpreter > > > [INFO] Zeppelin: Cassandra > > > [INFO] Zeppelin: Elasticsearch interpreter > > > [INFO] Zeppelin: Alluxio interpreter > > > [INFO] Zeppelin: web Application > > > [INFO] Zeppelin: Server > > > [INFO] Zeppelin: Packaging distribution > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] Reactor Summary: > > > [INFO] > > > [INFO] Zeppelin ........................................... SKIPPED > > > [INFO] Zeppelin: Interpreter .............................. SKIPPED > > > [INFO] Zeppelin: Zengine .................................. SKIPPED > > > [INFO] Zeppelin: Display system apis ...................... SKIPPED > > > [INFO] Zeppelin: Spark dependencies ....................... SKIPPED > > > [INFO] Zeppelin: Spark .................................... SKIPPED > > > [INFO] Zeppelin: Markdown interpreter ..................... SKIPPED > > > [INFO] Zeppelin: Angular interpreter ...................... SKIPPED > > > [INFO] Zeppelin: Shell interpreter ........................ SKIPPED > > > [INFO] Zeppelin: Hive interpreter ......................... SKIPPED > > > [INFO] Zeppelin: HBase interpreter ........................ SKIPPED > > > [INFO] Zeppelin: Apache Phoenix Interpreter ............... SKIPPED > > > [INFO] Zeppelin: PostgreSQL interpreter ................... SKIPPED > > > [INFO] Zeppelin: JDBC interpreter ......................... SKIPPED > > > [INFO] Zeppelin: Tajo interpreter ......................... SKIPPED > > > [INFO] Zeppelin: File System Interpreters ................. SKIPPED > > > [INFO] Zeppelin: Flink .................................... SKIPPED > > > [INFO] Zeppelin: Apache Ignite interpreter ................ SKIPPED > > > [INFO] Zeppelin: Kylin interpreter ........................ SKIPPED > > > [INFO] Zeppelin: Lens interpreter ......................... SKIPPED > > > [INFO] Zeppelin: Cassandra ................................ SKIPPED > > > [INFO] Zeppelin: Elasticsearch interpreter ................ SKIPPED > > > [INFO] Zeppelin: Alluxio interpreter ...................... SKIPPED > > > [INFO] Zeppelin: web Application .......................... SKIPPED > > > [INFO] Zeppelin: Server ................................... SKIPPED > > > [INFO] Zeppelin: Packaging distribution ................... SKIPPED > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] BUILD FAILURE > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] Total time: 0.817 s > > > [INFO] Finished at: 2016-05-02T18:46:23+05:30 > > > [INFO] Final Memory: 11M/82M > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [ERROR] No goals have been specified for this build. You must specify a > > > valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or > > > <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. > > Available > > > lifecycle phases are: validate, initialize, generate-sources, > > > process-sources, generate-resources, process-resources, compile, > > > process-classes, generate-test-sources, process-test-sources, > > > generate-test-resources, process-test-resources, test-compile, > > > process-test-classes, test, prepare-package, package, > > pre-integration-test, > > > integration-test, post-integration-test, verify, install, deploy, > > > pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. > -> > > > [Help 1] > > > org.apache.maven.lifecycle.NoGoalSpecifiedException: No goals have been > > > specified for this build. You must specify a valid lifecycle phase or a > > > goal in the format <plugin-prefix>:<goal> or > > > <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. > > Available > > > lifecycle phases are: validate, initialize, generate-sources, > > > process-sources, generate-resources, process-resources, compile, > > > process-classes, generate-test-sources, process-test-sources, > > > generate-test-resources, process-test-resources, test-compile, > > > process-test-classes, test, prepare-package, package, > > pre-integration-test, > > > integration-test, post-integration-test, verify, install, deploy, > > > pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. > > > at > > > > > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:94) > > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) > > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) > > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > at > > > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > > > at > > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > > at java.lang.reflect.Method.invoke(Method.java:498) > > > at > > > > > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > > > at > > > > > > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > > > at > > > > > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > > > at > > > > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > > > [ERROR] > > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > > [ERROR] > > > [ERROR] For more information about the errors and possible solutions, > > > please read the following articles: > > > [ERROR] [Help 1] > > > > > > http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException > > > > > > Please provide help in how to solve this. > > > > > > Thanks, > > > Anish. > > > > > > > > > On Mon, May 2, 2016 at 4:53 PM, anish singh <anish18...@gmail.com> > > wrote: > > > > > >> Hello, > > >> > > >> I had earlier successfully built the zeppelin project after merging > > >> https://github.com/apache/incubator-zeppelin/pull/836 > > >> as told in an earlier mail. Then, I was trying to run the SparkMon > > Helium > > >> example from eclipse. In the 'configure Build path' option for the > > SparkMon > > >> application I added the 'external class folder' : > > >> > > >> ZEPPELIN_HOME/zeppelin-interpreter/target/classes/ > > >> > > >> which contains all the classes for the Helium application, however > some > > >> of the classes used in the SparkMon application such as the following > : > > >> > > >> org.apache.zeppelin.helium.ApplicationArgument > > >> org.apache.zeppelin.helium.Signal > > >> org.apache.zeppelin.resource.ResourceKey > > >> > > >> were not found in the classes directory or the src/ directory of the > > >> zeppelin-interpreter directory. I suppose these are important classes > as > > >> they are required by the run() method and the signal() method, without > > them > > >> the program may not run. > > >> Please let me know if I'm doing something wrong or the source code has > > >> been changed so that the SparkMon code has to be modified to make it > > run. > > >> > > >> I want to be able to run a Sample Helium application first, so that I > > may > > >> be able experiment with it and learn more about it. Please provide > help > > in > > >> where I'm going wrong. > > >> > > >> I would be doing the following things in the next few days : > > >> > > >> ->Try to run Helium Sample application and dive into the Helium code > > base > > >> to understand its working completely. > > >> ->Learn more of javascript( D3.js) for Helium applications. > > >> ->Create an introduction about Zeppelin and the pluggable Application > > >> framework on the blog. > > >> > > >> Additionally, I propose to choose the World bank datasets for a start > > for > > >> creating the notebooks. > > >> > > >> If mentors want any change in the workflow mentioned above, please let > > me > > >> know. Also please pardon me for any delays as I'm simultaneously > > working on > > >> the project and giving my university final exams(ending on 9th May). > > >> > > >> Thanks, > > >> Anish. > > >> > > >> > > >> <https://github.com/apache/incubator-zeppelin/pull/836> > > >> > > >> On Sat, Apr 30, 2016 at 10:44 PM, moon soo Lee <m...@apache.org> > wrote: > > >> > > >>> Hi Anish, > > >>> > > >>> I'm trying to add visualization example application, based on d3. Let > > me > > >>> ping you once it's been added. Hope i can add it in next week. > > >>> > > >>> I think it's okay to choose dataset that you think you're interested > > in. > > >>> > > >>> Thanks! > > >>> moon > > >>> > > >>> On Sat, Apr 30, 2016 at 10:10 AM anish singh <anish18...@gmail.com> > > >>> wrote: > > >>> > > >>> > Hello, > > >>> > > > >>> > Thanks for the help with building the project, the build was > > >>> successful, > > >>> > what I did was the following : > > >>> > > > >>> > -> forked from incubator-zeppelin > > >>> > -> created a branch from the master > > >>> > -> merged Zeppelin-732 in that branch. > > >>> > > > >>> > Since Helium involves the usage of JavaScript, please let me know > if > > >>> the > > >>> > usage of D3 libraries would be fine to create custom visualizations > > or > > >>> > Angular would be preferred instead, so that I may spend some > initial > > >>> days > > >>> > learning these libraries. > > >>> > > > >>> > Also, please let me know which dataset would mentors like me to > start > > >>> work > > >>> > on, so that I may begin exploring ways of analyzing the dataset and > > >>> begin > > >>> > with the work(creating the notebook) and have some initial reviews > > >>> about my > > >>> > work. > > >>> > > > >>> > I have created a blog post for my work(not posted anything yet) : > > >>> > zeppelinnotes.blogspot.in > > >>> > Here I would be posting updates and documentation about my work > > >>> regularly. > > >>> > > > >>> > Thanks, > > >>> > Anish. > > >>> > > > >>> > > >> > > >> > > > > > >
