Hi Alex, Thanks for the suggestion! It worked and I am able to run the tests now :)
I was trying to run a test in SparkInterpreter class - emptyConfigurationVariablesOnlyForNonSparkProperties - just to see how the logging is done since that seems be to what needs to be handled in JIRA 722 : ZEPPELIN-722 <https://issues.apache.org/jira/browse/ZEPPELIN-722?jql=project%20%3D%20ZEPPELIN%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Trivial%20ORDER%20BY%20key%20DESC> Even though the test uses a logger to log the property key-value pairs as shown on line 189 here <https://github.com/PratikRJoshi/incubator-zeppelin/blob/master/spark/src/test/java/org/apache/zeppelin/spark/SparkInterpreterTest.java> , I couldn't find where the statements are printed to (it was not on the console). I have tried setting a file in the log4j properties as - >> Contents of incubator-zeppelin/conf/log4j.properties - > *log4j.rootLogger = DEBUG, dailyfilelog4j.appender.stdout = > org.apache.log4j.ConsoleAppender* > log4j.appender.stdout.layout = org.apache.log4j.PatternLayout > log4j.appender.stdout.layout.ConversionPattern=%5p [%d] ({%t} %F[%M]:%L) - > %m%n > log4j.appender.dailyfile.DatePattern=.yyyy-MM-dd > *log4j.appender.dailyfile.Threshold = DEBUG* > log4j.appender.dailyfile = org.apache.log4j.DailyRollingFileAppender > *log4j.appender.dailyfile.File = ${zeppelin.log.file}/myOutput* > log4j.appender.dailyfile.layout = org.apache.log4j.PatternLayout > log4j.appender.dailyfile.layout.ConversionPattern=%5p [%d] ({%t} > %F[%M]:%L) - %m%n As can be seen, I have tried setting a file (dailyfile) to write the logger output to and have given the path to the file too (${zeppelin.log.file}/myOutput) but still neither the file gets generated nor is the logger output shown on the console. Previously, the log4j.appender.dailyfile.File was set to ${zeppelin.log.file} which also didn't help (I found that zeppelin/logs/file is a directory instead of a file, and so I gave a file name as I mentioned above). Please let me know what mistakes I might be committing here and how can I go about rectifying them so as to be able to proceed with the JIRA resolution. Thanks! :) On Thu, Mar 31, 2016 at 5:30 PM, Alexander Bezzubov <b...@apache.org> wrote: > Hi, > > if you are running test directly from one of the maven sub-modules, in > order to get all it's dependencies resolved you first have to make `mvn > install` from the root of the repo, to deploy all artifacts to your local > .m2 repository. > > -- > Alex > > > On Fri, Apr 1, 2016 at 4:07 AM, Pratik Joshi <pratiktuto...@gmail.com> > wrote: > > > Hi, > > > > I am trying to run one test (it could be any test) from JDBC module of > > Zeppelin. But I get a build failure complaining about unresolved > > dependencies > > for org.apache.zeppelin:zeppelin-jdbc:jar:0.6.0-incubating-SNAPSHOT as > > below - > > > > mvn test -Dtest=JDBCInterpreterTest#testForParsePropertyKey > > > > [INFO] Scanning for projects... > > [INFO] > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Building Zeppelin: JDBC interpreter 0.6.0-incubating-SNAPSHOT > > [INFO] > > ------------------------------------------------------------------------ > > [WARNING] The POM for > > org.apache.zeppelin:zeppelin-interpreter:jar:0.6.0-incubating-SNAPSHOT is > > missing, no dependency information available > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 0.973 s > > [INFO] Finished at: 2016-03-30T17:29:34-07:00 > > [INFO] Final Memory: 9M/309M > > [INFO] > > ------------------------------------------------------------------------ > > [ERROR] Failed to execute goal on project zeppelin-jdbc: Could not > resolve > > dependencies for project > > org.apache.zeppelin:zeppelin-jdbc:jar:0.6.0-incubating-SNAPSHOT: Failure > to > > find > org.apache.zeppelin:zeppelin-interpreter:jar:0.6.0-incubating-SNAPSHOT > > in http://repository.apache.org/snapshots was cached in the local > > repository, resolution will not be reattempted until the update interval > of > > apache.snapshots has elapsed or updates are forced -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e > > switch. > > [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/DependencyResolutionException > > > > > > I get the same error even if I try to run other test in some other module > > (I tried running a spark module test). > > > > I browsed through Jira and came across similar problem someone else > faced, > > tried the solution suggested but didn't help - > > https://issues.apache.org/jira/browse/ZEPPELIN-637. > > They mention checking out the v0.5.6 tag instead of the branch-0.5.6. But > > the issue on doing that is that the jdbc module doesn't contain a POM. > > > > Just as a side note, the build is successful when I build from the parent > > POM - > > incubator-zeppelin ✓ sudo mvn clean package -DskipTests -T 4C > -Pvendor-repo > > [INFO] Scanning for projects... > > ... > > ... > > [INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ > > zeppelin-cassandra --- > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Reactor Summary: > > [INFO] > > [INFO] Zeppelin ........................................... SUCCESS [ > > 19.705 s] > > [INFO] Zeppelin: Interpreter .............................. SUCCESS [ > > 32.895 s] > > [INFO] Zeppelin: Zengine .................................. SUCCESS [ > > 22.590 s] > > [INFO] Zeppelin: Display system apis ...................... SUCCESS > [01:09 > > min] > > [INFO] Zeppelin: Spark dependencies ....................... SUCCESS > [02:06 > > min] > > [INFO] Zeppelin: Spark .................................... SUCCESS [ > > 50.619 s] > > [INFO] Zeppelin: Markdown interpreter ..................... SUCCESS [ > > 5.647 s] > > [INFO] Zeppelin: Angular interpreter ...................... SUCCESS [ > > 5.028 s] > > [INFO] Zeppelin: Shell interpreter ........................ SUCCESS [ > > 5.026 s] > > [INFO] Zeppelin: Hive interpreter ......................... SUCCESS [ > > 28.098 s] > > [INFO] Zeppelin: HBase interpreter ........................ SUCCESS [ > > 38.951 s] > > [INFO] Zeppelin: Apache Phoenix Interpreter ............... SUCCESS [ > > 40.600 s] > > [INFO] Zeppelin: PostgreSQL interpreter ................... SUCCESS [ > > 8.332 s] > > [INFO] Zeppelin: JDBC interpreter ......................... SUCCESS [ > > 7.482 s] > > [INFO] Zeppelin: Tajo interpreter ......................... SUCCESS [ > > 18.663 s] > > [INFO] Zeppelin File System Interpreters .................. SUCCESS [ > > 18.197 s] > > [INFO] Zeppelin: Flink .................................... SUCCESS [ > > 49.581 s] > > [INFO] Zeppelin: Apache Ignite interpreter ................ SUCCESS [ > > 19.202 s] > > [INFO] Zeppelin: Kylin interpreter ........................ SUCCESS [ > > 12.808 s] > > [INFO] Zeppelin: Lens interpreter ......................... SUCCESS [ > > 25.224 s] > > [INFO] Zeppelin: Cassandra ................................ SUCCESS > [02:41 > > min] > > [INFO] Zeppelin: Elasticsearch interpreter ................ SUCCESS [ > > 29.086 s] > > [INFO] Zeppelin: Alluxio interpreter ...................... SUCCESS [ > > 33.549 s] > > [INFO] Zeppelin: web Application .......................... SUCCESS > [02:01 > > min] > > [INFO] Zeppelin: Server ................................... SUCCESS [ > > 55.602 s] > > [INFO] Zeppelin: Packaging distribution ................... SUCCESS [ > > 4.417 s] > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD SUCCESS > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 03:40 min (Wall Clock) > > [INFO] Finished at: 2016-03-30T17:04:23-07:00 > > [INFO] Final Memory: 170M/1769M > > [INFO] > > ------------------------------------------------------------------------ > > > > > > Please let me know how do I resolve this issue so that I can run tests in > > Zeppelin. > > > > Thanks! > > -- > > Sincerely, > > Pratik Joshi > > M. S. Computer Science > > University of Southern California, > > Los Angeles, CA 90089-0471 > > +1(213)400-0946 > > > -- Sincerely, Pratik Joshi M. S. Computer Science University of Southern California, Los Angeles, CA 90089-0471 +1(213)400-0946
