[GitHub] zeppelin issue #1743: add hadoop-2.7 to available hadoop version
Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/1743 Merge into master if there are no more comments :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/1663 @zjffdu +1 on the refactor part. I have written a [test](https://github.com/apache/zeppelin/pull/1663/files#diff-7d13c722724f9c346f38303f4b435548R326). Would this suffice? I can add more tests if required. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1663 BTW @karuppayya Do you have andy integration test for it ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1663 Personally, I think this feature is useful but I just feel that with adding more new features to zeppelin(especially related with interpreter). We couple many components closely much more than before. (e.g. We usually we add parameter to Constructor of class A to allow it access class B). This would add more complexities to the code base which would make it difficult to add new features and easy to break some function in future. I think maybe we should spend some time to do refactoring to make the component boundary more clean. It would not only make adding new feature easier but also make zeppelin robust and less error-prone. This comment is not related with PR but just share my thoughts of development of zeppelin. We could merge it first and do the refactoring later. \cc @Leemoonsoo --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1661: [ZEPPELIN-1605] zeppelin-interpreter: don't pub...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1661 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (ZEPPELIN-1785) Clarify where to pick up ZeppelinConfiguration
Jeff Zhang created ZEPPELIN-1785: Summary: Clarify where to pick up ZeppelinConfiguration Key: ZEPPELIN-1785 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1785 Project: Zeppelin Issue Type: Bug Affects Versions: 0.7.0 Reporter: Jeff Zhang Assignee: Jeff Zhang The current issue I found is that zeppelin.notebook.dir defined in zeppelin-site.xml doesn't take effect. Because we define it in https://github.com/apache/zeppelin/blob/master/bin/common.sh#L52 and ZeppelinConfiguration will pick up configugration through enviroment variable by first. I think some other conf like zeppelin.interpreter.dir are the same. There're 2 solutions for it. * Remove them in common.sh * Preferer property in zeppelin-site.xml over enviroment variable. Personally, I prefer the second solution. As I think property is easier to understand, and we should use zeppelin-site as central place for all the configurations. This is also the approach what spark use. \cc [~moon] [~luciano resende] [~anthonycorbacho] [~jongyoul] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] zeppelin issue #1743: add hadoop-2.7 to available hadoop version
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/1743 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1744: Better output of JDBC Interpreter.
GitHub user astroshim opened a pull request: https://github.com/apache/zeppelin/pull/1744 Better output of JDBC Interpreter. ### What is this PR for? Currently, the output format of the JDBC Interpreter is the table format with all the results except EXPLAIN statement, It is better for the user experience to output only the result of the SELECT statement in table format. This PR fixes the above issue and did some code refactoring. Tested on mysql and aws athena. ### What type of PR is it? Improvement ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-1784 ### How should this be tested? - before https://cloud.githubusercontent.com/assets/3348133/21074311/3bb25bd0-bf39-11e6-8cc2-c72af742c6fe.png;> https://cloud.githubusercontent.com/assets/3348133/21074320/61b2cdd8-bf39-11e6-8be2-b02eb48b32a7.png;> - after https://cloud.githubusercontent.com/assets/3348133/21074296/e349e3e6-bf38-11e6-96c2-fa7e92265e94.png;> https://cloud.githubusercontent.com/assets/3348133/21074297/e888130a-bf38-11e6-963e-d9fbe7eafb0f.png;> ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/astroshim/zeppelin ZEPPELIN-1784 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1744.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1744 commit 884113cfe9868bc2cd17fd1601cad0b67e155df8 Author: astroshimDate: 2016-12-10T15:09:15Z change output type of JDBC Interpreter. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (ZEPPELIN-1784) Why is the result of all JDBC commands printed as a table?
Shim HyungSung created ZEPPELIN-1784: Summary: Why is the result of all JDBC commands printed as a table? Key: ZEPPELIN-1784 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1784 Project: Zeppelin Issue Type: Improvement Reporter: Shim HyungSung Fix For: 0.7.0 Currently, the output format of the JDBC Interpreter is the table format with all the results except EXPLAIN statement, It is better for the user experience to output only the result of the SELECT statement in table format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Accessing Interpreter Context in Helium application ??
Hi All, In an attempt of building a small Helium app in zeppelin we are facing issues accessing *sparkContext/sparksession/sqlContext. * Any hints on taking this forward is highly appreciated. -- Thanks & Regards, Meenakshi.
[GitHub] zeppelin issue #1678: [ZEPPELIN-1706] Make spark Ui accesible in various int...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/1678 @Leemoonsoo @zjffdu can u please take a look.and let me know how it looks --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Adding Angular API to non-Spark interpreters
All interpreters can leverage the AngularObjectRegistry. The Cassandra interpreter does this here: https://github.com/apache/zeppelin/blob/master/cassandra/src/main/scala/org/apache/zeppelin/cassandra/InterpreterLogic.scala#L316-L356 On Fri, Dec 9, 2016 at 10:45 PM, Goodman, Alexander (398K) < alexander.good...@jpl.nasa.gov> wrote: > Hi Randy, > > The main thing you are probably looking for is the AngularObjectRegistry > class (https://github.com/apache/zeppelin/blob/master/zeppelin-int > erpreter/src/main/java/org/apache/zeppelin/display/AngularOb > jectRegistry.java). One of the fields of InterpreterContext is an instance > of this class, so you could in theory just place the interpreter result > into the registry here: > > https://github.com/apache/zeppelin/blob/master/zeppelin- > interpreter/src/main/java/org/apache/zeppelin/interpreter/remote/ > RemoteInterpreterServer.java#L474 > > While I agree that we should try to better expose the angular API to more > interpreters, there are a few problems with your approach. > > First, you may noticed that a recent change was made to interpreter results > (https://github.com/apache/zeppelin/pull/1658). This ultimately makes the > feature you are asking for considerably more complicated to implement > correctly since you have just one paragraphID but potentially multiple > results with different types, and you'll only want a certain part of the > result to get bound to the registry. > > Also, I am not sure if enforcing this automatically would be a good idea > considering that only certain types of results are useful to store as > AngularObjects. If this gets applied to every paragraph automatically I > could see this potentially leading to some churn within the system, but I > can't say for sure. Either way, I think this should be something like a per > paragraph feature which can be toggled via a UI option. > > I think this is a good discussion to have, since I do agree that leveraging > this feature to other interpreters would lead to great advances in > Zeppelin's visualization capabilities. Perhaps we should take some time to > discuss other ideas for making this happen? > > Thanks, > Alex > > On Fri, Dec 9, 2016 at 12:27 PM, Randy Gelhausen> wrote: > > > I created https://issues.apache.org/jira/browse/ZEPPELIN-1782 with > > additional detail for this feature request. > > > > I looked into the InterpreterContext classes, but am not sure how to > > implement this. Any suggestions from others? > > > > Thanks in advance, > > -Randy > > > > On 2016-11-24 18:31 (-0500), Randy Gelhausen wrote: > > > I often need to visualize data in other ways than supported by the out > > of> > > > the box charts. I can do this with Angular notes and custom JavaScript, > > but> > > > Spark is the only interpreter with capability to set Angular > variables.> > > > > > > Could it be possible to automatically expose all interpreter results > as> > > > Angular variables using the paragraph ID as the variable name?> > > > > > > This would greatly improve the custom viz capabilities for Zeppelin > > without> > > > requiring developers of each interpreter to integrate with Zeppelin's> > > > Angular API.> > > > > > > > > > -- > Alex Goodman > Data Scientist I > Science Data Modeling and Computing (398K) > Jet Propulsion Laboratory > California Institute of Technology > Tel: +1-818-354-6012 >