[GitHub] zeppelin issue #2237: ZEPPELIN-2377. Hive Support can not be enabled in spar...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2237 I don't prefer to call private method `hiveClassesArePresent` which is not guaranteed to be stable. The cause of hive support broken in spark master is due to we copied the implementation of `hiveClassesArePresent` of spark 2.0 in zeppelin, but `hiveClassesArePresent` is changed in spark master. So instead of checking difference classes for different versions, here I propose to checking class `InsertIntoHiveTable` which is public. --- 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 #2241: ZEPPELIN-2390. Improve returnType for z.checkbox
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2241 Before this PR It was not default to first item in checkbox, it is default to all items. The reason I change it to nothing is to make it consistent with scala implementation. Right, this would break the existing API, but I think it is worthwhile. I have several following PRs to improve `ZeppelinContext` and hope to stabilize it. IMO `ZeppelinContext` would play an important role for extending the rich functionality of zeppelin. --- 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 #2234: [ZEPPELIN-2374] sorting notes tree
Github user tinkoff-dwh closed the pull request at: https://github.com/apache/zeppelin/pull/2234 --- 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 #2237: ZEPPELIN-2377. Hive Support can not be enabled in spar...
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2237 For hiveClassesArePresent I mean either call hiveClassesArePresent (it's private yes) or do what it does? --- 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 #2228: [ZEPPELIN-2365] button to create note into folder
Github user soralee commented on the issue: https://github.com/apache/zeppelin/pull/2228 Thanks @tinkoff-dwh for quick resolving! Let me check again if CI become green. --- 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 #2244: [MINOR] fix typo from 'interpeter' to 'interpre...
GitHub user soralee opened a pull request: https://github.com/apache/zeppelin/pull/2244 [MINOR] fix typo from 'interpeter' to 'interpreter' ### What is this PR for? Fix typo from `interpeter` to `interpreter` ### What type of PR is it? [Improvement] ### What is the Jira issue? * No, it's minor issue ### How should this be tested? - N/A ### Screenshots (if appropriate) - N/A ### 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/soralee/zeppelin typo_interpreter Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2244.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 #2244 commit 863dc4fb09d35f0e503124b45990eb695649b527 Author: soraleeDate: 2017-04-11T00:43:03Z fix typo --- 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 #2241: ZEPPELIN-2390. Improve returnType for z.checkbox
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2241 A bit concerned with breaking API changes like this but I guess we have never defined the support or versioning plan on the API? Aren't we breaking the selected default item for checkbox by initializing defaultChecked to empty? It was default to first item in checkbox Now is default to nothing --- 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 #2228: [ZEPPELIN-2365] button to create note into folder
Github user soralee commented on the issue: https://github.com/apache/zeppelin/pull/2228 @tinkoff-dwh, Before testing, could you rebase for resolving conflicts, too? :slightly_smiling_face: --- 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 #2234: [ZEPPELIN-2374] sorting notes tree
Github user soralee commented on the issue: https://github.com/apache/zeppelin/pull/2234 @tinkoff-dwh, Could you rebase for resolving conflicts? --- 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 #2098: [ZEPPELIN-2217] AdvancedTransformation for Visualizati...
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2098 Removed `WIP` from PR title. --- 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 #2198: [ZEPPELIN-2318] Fix proxy configuration for http clien...
Github user khalidhuseynov commented on the issue: https://github.com/apache/zeppelin/pull/2198 merge into master and branch-0.7 if no further 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 pull request #2242: Improve the spark sql interpreter to run paragr...
Github user wary closed the pull request at: https://github.com/apache/zeppelin/pull/2242 --- 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 #2242: Improve the spark sql interpreter to run paragraph wit...
Github user wary commented on the issue: https://github.com/apache/zeppelin/pull/2242 @tinkoff-dwh oh, yes, you are right, I did not see that, thank you for reminding, I will close this pull request and reconsidered 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 #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...
Github user cloverhearts commented on the issue: https://github.com/apache/zeppelin/pull/2207 @zjffdu Yes, I will also reflect the namespace. Thank you for your advice :) . --- 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 #2241: ZEPPELIN-2390. Improve returnType for z.checkbox
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2241 Will merge to master if no more discussion. --- 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 #2243: [ZEPPELIN-2393] fix 403 error on http client ZeppelinH...
Github user khalidhuseynov commented on the issue: https://github.com/apache/zeppelin/pull/2243 Closing for now since can be solved by changing security policy without changing headers --- 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 #2243: [ZEPPELIN-2393] fix 403 error on http client Ze...
Github user khalidhuseynov closed the pull request at: https://github.com/apache/zeppelin/pull/2243 --- 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 #2241: ZEPPELIN-2390. Improve returnType for z.checkbox
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/2241 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. ---
Add User Api
Hello, I was wondering if you guys were working on a easier way to add users perhaps something that woulf let you add users to the shiro.ini page with out having to open the file because we do containerize our zeppelin image which we love by the way. Execing in to the container everytime though to add a new zeppelin user which we have alot of is a pain and not always the best. Do you think there will be some other way perhaps the same way we can make a credential rest request a user add rest request? Thanks
[jira] [Created] (ZEPPELIN-2394) Auto-save on input is broken
Ilia Fishbein created ZEPPELIN-2394: --- Summary: Auto-save on input is broken Key: ZEPPELIN-2394 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2394 Project: Zeppelin Issue Type: Bug Components: Core, front-end Affects Versions: 0.7.1, 0.7.0 Reporter: Ilia Fishbein Commit 42be839 changed ```$scope.startSaveTimer();``` to ``` $scope.$broadcast('startSaveTimer');``` in zeppelin-web/src/app/notebook/paragraph/paragraph.controller.js for seemingly no reason and did not include corresponding code that registers a "startSaveTimer" event. As a result, paragraphs are not auto-saved based on end-user input. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin issue #2242: Improve the spark sql interpreter to run paragraph wit...
Github user tinkoff-dwh commented on the issue: https://github.com/apache/zeppelin/pull/2242 why returns only last result? jdbc interpreter has method (splitSqlQueries) maybe do refactoring (general method to split + result for each request). And add test (jdbc interpreter has test) --- 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 #2229: [Zeppelin 2367] Hive JDBC proxy user option should be ...
Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/2229 @AhyoungRyu @felixcheung thank you for the review, have made the suggested changes. --- 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-2393) authentication with ZeppelinHubRealm throws 403 error
Khalid Huseynov created ZEPPELIN-2393: - Summary: authentication with ZeppelinHubRealm throws 403 error Key: ZEPPELIN-2393 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2393 Project: Zeppelin Issue Type: Bug Reporter: Khalid Huseynov In some cases, depending where authentication server is deployed and what services are used, it's possible that httpcomponents client request headers are not approved by the security rules. For example one of common problems can be 403 Forbidden response by cloudflare service with error-code 1010. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin pull request #2242: Improvement
GitHub user wary opened a pull request: https://github.com/apache/zeppelin/pull/2242 Improvement Improve the spark sql interpreter to run paragraph with multi sql statements split by semicolon ### What is this PR for? A few sentences describing the overall goals of the pull request's commits. First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html * Improve the spark sql interpreter to run paragraph with multi sql statements split by semicolon In current version of Zeppelin, we can only run one sql statement in one paragraph, that is very inconvenientï¼so I think we need to improve the spark sql interpreter to fix this problem ### What type of PR is it? [Improvement] ### Todos * [ ] - Task ### What is the Jira issue? * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/ * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. [ZEPPELIN-533] [ZEPPELIN-2392](https://issues.apache.org/jira/browse/ZEPPELIN-2392) ### How should this be tested? Outline the steps to test the PR here. ### Screenshots (if appropriate) https://cloud.githubusercontent.com/assets/869480/24916697/72d9cf24-1f0d-11e7-8a68-50ba9973fcb8.png;> ### Questions: * Does the licenses files need update? * Is there breaking changes for older versions? * Does this needs documentation? You can merge this pull request into a Git repository by running: $ git pull https://github.com/wary/zeppelin SparkSqlInterpreterEnhancement Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2242.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 #2242 commit 4b06a9e667c0ab3d32aa122766998ca2f6d938f7 Author: lei wangDate: 2017-04-11T15:18:14Z Improvement improve the spark sql interpreter to run paragraph with multi sql statements split by semicolon --- 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-2392) Improve the spark sql interpreter to run paragraph with multi sql statements split by semicolon
LeiWang created ZEPPELIN-2392: - Summary: Improve the spark sql interpreter to run paragraph with multi sql statements split by semicolon Key: ZEPPELIN-2392 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2392 Project: Zeppelin Issue Type: Improvement Reporter: LeiWang In current version of Zeppelin, we can only run one sql statement in one paragraph, that is very inconvenient,so I think we need to improve the spark sql interpreter to fix this problem -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin pull request #2098: [ZEPPELIN-2217][WIP] AdvancedTransformation for...
Github user 1ambda closed the pull request at: https://github.com/apache/zeppelin/pull/2098 --- 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 #2098: [ZEPPELIN-2217][WIP] AdvancedTransformation for...
GitHub user 1ambda reopened a pull request: https://github.com/apache/zeppelin/pull/2098 [ZEPPELIN-2217][WIP] AdvancedTransformation for Visualization ### What is this PR for? `AdvancedTransformation` has more detailed options while providing existing features of `PivotTransformation` and `ColumnselectorTransformation` which Zeppelin already has ![av_in_30sec](https://cloud.githubusercontent.com/assets/4968473/24037330/c9478e86-0b40-11e7-9886-1ffb85042a7a.gif) Here are some features which advanced-transformation can provide. 1. **(screenshot)** multiple sub charts 2. **(screenshot)** parameter widgets: `input`, `checkbox`, `option`, `textarea` 3. **(screenshot)** expand/fold axis and parameter panels 4. **(screenshot)** clear axis and parameter panels 5. **(screenshot)** remove duplicated columns in an axis 6. **(screenshot)** limit column count in an axis 7. configurable char axes: `valueType`, `axisType`, `description`, ... 8. configurable chart parameters 9. lazy transformation 10. parsing parameters automatically based on their type: `int`, `float`, `string`, `JSON` 11. multiple transformation methods 12. re-initialize whole configuration based on spec hash. 13. **(screenshot)** shared axis API Details: Spec `AdvancedTransformation` requires `spec` which includes axis and parameter details for charts. - Let's create 2 sub-charts called `simple-line` and `step-line`. - Each sub chart can have different `axis` and `parameter` depending on their requirements. ```js constructor(targetEl, config) { super(targetEl, config) const spec = { charts: { 'simple-line': { sharedAxis: true, /** set if you want to share axes between sub charts, default is `false` */ axis: { 'xAxis': { dimension: 'multiple', axisType: 'key', }, 'yAxis': { dimension: 'multiple', axisType: 'aggregator'}, 'category': { dimension: 'multiple', axisType: 'group', }, }, parameter: { 'xAxisUnit': { valueType: 'string', defaultValue: '', description: 'unit of xAxis', }, 'yAxisUnit': { valueType: 'string', defaultValue: '', description: 'unit of yAxis', }, 'dashLength': { valueType: 'int', defaultValue: 0, description: 'the length of dash', }, }, }, 'step-line': { axis: { 'xAxis': { dimension: 'single', axisType: 'unique', }, 'yAxis': { dimension: 'multiple', axisType: 'value', }, }, parameter: { 'xAxisUnit': { valueType: 'string', defaultValue: '', description: 'unit of xAxis', }, 'yAxisUnit': { valueType: 'string', defaultValue: '', description: 'unit of yAxis', }, 'noStepRisers': { valueType: 'boolean', defaultValue: false, description: 'no risers in step line', widget: 'checkbox', }, }, }, } this.transformation = new AdvancedTransformation(config, spec) } ``` API Details: Axis Spec | Field Name | Available Values (type) | Description | | --- | --- | --- | |`dimension` | `single` | Axis can contains only 1 column | |`dimension` | `multiple` | Axis can contains multiple columns | |`axisType` | `key` | Column(s) in this axis will be used as `key` like in `PivotTransformation`. These columns will be served in `column.key` | |`axisType` | `aggregator` | Column(s) in this axis will be used as `value` like in `PivotTransformation`. These columns will be served in `column.aggregator` | |`axisType` | `group` | Column(s) in this axis will be used as `group` like in `PivotTransformation`. These columns will be served in `column.group` | |`axisType` | (string) | Any string value can be used here. These columns will be served in `column.custom` | |`maxAxisCount` | (int) | The maximum column count that this axis can contains. (unlimited if `undefined`) | |`valueType` | (string) | Describe the value type just for annotation | Here is an example. ```js axis: { 'xAxis': { dimension: 'multiple', axisType: 'key', }, 'yAxis': { dimension: 'multiple', axisType: 'aggregator'}, 'category': { dimension: 'multiple', axisType: 'group', maxAxisCount: 2, valueType: 'string', }, }, ``` API Details: Parameter Spec | Field Name | Available Values (type) | Description | | --- | --- | --- | |`valueType` | `string` | Parameter which has string value | |`valueType` | `int` | Parameter which has int value | |`valueType` | `float` | Parameter which has float value | |`valueType` | `boolean` |
Re: Custom Interpreter group is not displayed on the GUI
Hi, Thanks for the quick reply. I followed that documentation. But after installing the interpreter using that given command, still my interpreter group is not listing when I try to create a interpreter from UI. In the interpreter-settings.json I have given "wso2" as my interpreter group[1]. Is there anymore configuration to be done to bind it with the zeppelin? [1] https://github.com/minudika/zeppelin/blob/WSO2_Siddhi_Interpreter/wso2_receiver/resources/interpreter-setting.json BR On Tue, Apr 11, 2017 at 7:18 PM, Jeff Zhangwrote: > Please check the document here. > https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/manual/ > interpreterinstallation.html > > > > Minudika Malshan 于2017年4月11日周二 下午9:40写道: > > > Hi, > > > > I am writing a custom interpreter for apache zeppelin. I added the > > interpreter class to the zeppelin-site.xml and also updated the > > interpreter-setting.json of my interpreter's module. > > But when build the project and start the zeppelin server, the interpreter > > group I given for my interpreter is not shown in the drop down. > > Could you please let me know how to resolve this? > > > > Please find my code here. [1] > > > > [1] > > > > https://github.com/minudika/zeppelin/tree/WSO2_Siddhi_ > Interpreter/wso2_receiver > > > > Also I have committed my current updated zeppelin-site.xml. > > > > Thank you! > > > > -- > > *Minudika Malshan* > > Undergraduate > > Department of Computer Science and Engineering > > University of Moratuwa > > Sri Lanka. > > > -- *Minudika Malshan* Undergraduate Department of Computer Science and Engineering University of Moratuwa Sri Lanka.
Re: Custom Interpreter group is not displayed on the GUI
Please check the document here. https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/manual/interpreterinstallation.html Minudika Malshan于2017年4月11日周二 下午9:40写道: > Hi, > > I am writing a custom interpreter for apache zeppelin. I added the > interpreter class to the zeppelin-site.xml and also updated the > interpreter-setting.json of my interpreter's module. > But when build the project and start the zeppelin server, the interpreter > group I given for my interpreter is not shown in the drop down. > Could you please let me know how to resolve this? > > Please find my code here. [1] > > [1] > > https://github.com/minudika/zeppelin/tree/WSO2_Siddhi_Interpreter/wso2_receiver > > Also I have committed my current updated zeppelin-site.xml. > > Thank you! > > -- > *Minudika Malshan* > Undergraduate > Department of Computer Science and Engineering > University of Moratuwa > Sri Lanka. >
Custom Interpreter group is not displayed on the GUI
Hi, I am writing a custom interpreter for apache zeppelin. I added the interpreter class to the zeppelin-site.xml and also updated the interpreter-setting.json of my interpreter's module. But when build the project and start the zeppelin server, the interpreter group I given for my interpreter is not shown in the drop down. Could you please let me know how to resolve this? Please find my code here. [1] [1] https://github.com/minudika/zeppelin/tree/WSO2_Siddhi_Interpreter/wso2_receiver Also I have committed my current updated zeppelin-site.xml. Thank you! -- *Minudika Malshan* Undergraduate Department of Computer Science and Engineering University of Moratuwa Sri Lanka.
[GitHub] zeppelin issue #2241: ZEPPELIN-2390. Improve returnType for z.checkbox
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2241 @Leemoonsoo @felixcheung Please help review. --- 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 #2241: ZEPPELIN-2390. Improve returnType for z.checkbo...
GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2241 ZEPPELIN-2390. Improve returnType for z.checkbox ### What is this PR for? Currently it is not convenient to access the individual item of the return value of z.checkbox, I would propose to return `Seq` for `SparkInterpreter` and `list` for `PySparkInterpreter`. This might cause some incompatibility, but I think it is acceptable considering the benefits. Besides that, before this PR, all the items of checkbox would be checked by default in `PySparkInterpreter` which is inconsistent with `SparkInterpreter`, so I change it to nothing is selected by default in this PR. ### What type of PR is it? [Improvement] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-2390 ### How should this be tested? Unit test is added ### 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/zjffdu/zeppelin ZEPPELIN-2390 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2241.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 #2241 commit 9bb616d95c6d4714d0574374cd314c2c87b3bfa0 Author: Jeff ZhangDate: 2017-04-11T10:09:35Z ZEPPELIN-2390. Improve returnType for z.checkbox --- 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-2391) Cannot initialize SparkContext on CDH5.7
Tony Liu created ZEPPELIN-2391: -- Summary: Cannot initialize SparkContext on CDH5.7 Key: ZEPPELIN-2391 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2391 Project: Zeppelin Issue Type: Bug Components: Interpreters Affects Versions: 0.7.1 Environment: OS: CentOS 6.8 Kernel: 2.6.32-642.el6.x86_64 CDH: CDH-5.10.0 (Hadoop version: 2.6.0-cdh5.10.0) Reporter: Tony Liu I built Zeppelin 0.7.1 from source with the following command: mvn clean package -Pspark-1.6 -Dspark.version=1.6.0 -Phadoop-2.6 -Dhadoop.version=2.6.0-cdh5.10.0 -Pvendor-repo -DskipTests -Pbuild-distr But when I create a new note with Spark interpreter and run sc.version, it gives this error: java.lang.NoSuchMethodError: org.apache.hadoop.io.retry.RetryPolicies.retryOtherThanRemoteException(Lorg/apache/hadoop/io/retry/RetryPolicy;Ljava/util/Map;)Lorg/apache/hadoop/io/retry/RetryPolicy; at org.apache.hadoop.yarn.client.RMProxy.createRetryPolicy(RMProxy.java:291) at org.apache.hadoop.yarn.client.RMProxy.createRetryPolicy(RMProxy.java:207) at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:91) at org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72) at org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceStart(YarnClientImpl.java:174) at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193) at org.apache.spark.deploy.yarn.Client.submitApplication(Client.scala:127) at org.apache.spark.scheduler.cluster.YarnClientSchedulerBackend.start(YarnClientSchedulerBackend.scala:57) at org.apache.spark.scheduler.TaskSchedulerImpl.start(TaskSchedulerImpl.scala:158) at org.apache.spark.SparkContext.(SparkContext.scala:538) at org.apache.zeppelin.spark.SparkInterpreter.createSparkContext_1(SparkInterpreter.java:484) at org.apache.zeppelin.spark.SparkInterpreter.createSparkContext(SparkInterpreter.java:382) at org.apache.zeppelin.spark.SparkInterpreter.getSparkContext(SparkInterpreter.java:146) at org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:828) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:70) at org.apache.zeppelin.spark.PySparkInterpreter.getSparkInterpreter(PySparkInterpreter.java:564) at org.apache.zeppelin.spark.PySparkInterpreter.createGatewayServerAndStartScript(PySparkInterpreter.java:208) at org.apache.zeppelin.spark.PySparkInterpreter.open(PySparkInterpreter.java:162) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:70) at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:483) at org.apache.zeppelin.scheduler.Job.run(Job.java:175) at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ZEPPELIN-2390) Improve returnType for z.checkbox
Jeff Zhang created ZEPPELIN-2390: Summary: Improve returnType for z.checkbox Key: ZEPPELIN-2390 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2390 Project: Zeppelin Issue Type: Improvement Affects Versions: 0.7.1 Reporter: Jeff Zhang Assignee: Jeff Zhang Currently it is not convenient to access the individual item of the return value of z.checkbox, I would propose to return Seq for SparkInterpreter and list for PySparkInterpreter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin pull request #2225: [ZEPPELIN-2357] fix: tooltip doesn't work in bt...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/2225 --- 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 #2133: [ZEPPELIN-1357,1892,1370][Umbrella] Text overla...
GitHub user soralee reopened a pull request: https://github.com/apache/zeppelin/pull/2133 [ZEPPELIN-1357,1892,1370][Umbrella] Text overlap in the MultiBarChart ### What is this PR for? If using the `multiChartBar`, it often occurs overlap in text. So, this PR is for preventing to overlap in text. >~~The below is the case what I updated.~~ ~~1. The xLabel generally show all of the text without rotation (less than 30).~~ ~~2. If the xLabel size is over than 30 and less than 80, the xLabel text are rotated as 90 degree and displayed.~~ ~~3. If the xLabel size is over than 80, the xLabel text are disappeared, but the tooltip is displayed.~~ >~~I have made improvements based on my thinking, so I would appreciate to give me your feedback.~~ ~~And if merged this PR, I'll update the feature so that user can use `min` and `max` variables by user on web.~~ **[Update]** To prevent overlap in xLabel text, in one way which is talked the below mentions, user who is using zeppelin could select to visualization type of xLabel such as `rotate 45 degree` or `hide`. ### What type of PR is it? [Bug Fix | Improvement ] ### What is the Jira issue? * [ZEPPELIN-1357; UI - label wrapping not done properly in charts](https://issues.apache.org/jira/browse/ZEPPELIN-1357) * [ZEPPELIN-1892; Display label vertically or horizontally smartly](https://issues.apache.org/jira/browse/ZEPPELIN-1892) * [ZEPPELIN-1370; Label overlaps - in default visualization example barchart](https://issues.apache.org/jira/browse/ZEPPELIN-1370) ### How should this be tested? 1. Run the paragraph for bank data in the `Basic Features (Spark)` notebook. 2. Execute the following query. ``` %sql select * from bank ``` 3. Use the pivot in the `Setting` toggle in the `MultiBarChart` such as the screenshots. ### Screenshots (if appropriate) **[Before]** ![z_zeppelin-1357_b](https://cloud.githubusercontent.com/assets/8110458/23898303/f80d7bbc-08f3-11e7-9b24-3248c492b8af.png) ![z_1357_b3_](https://cloud.githubusercontent.com/assets/8110458/23898435/75b3ae60-08f4-11e7-9d7c-31746f0d4edc.png) **[After]** ![update_overlap_in_text](https://cloud.githubusercontent.com/assets/8110458/24888251/f9acc8ce-1e9c-11e7-8a49-a5bcc00c4a29.gif) ### 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/soralee/zeppelin ZEPPELIN-1357_overlap_text Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2133.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 #2133 commit 67e739c0fc7f6ffbf36812c5c6970feb6e2f1c2f Author: soraleeDate: 2017-03-14T05:07:44Z prevent to overlap in text if using multiBarChart commit a47804bf2cd443e232ec11fc6cdd3727a83ed5ba Author: soralee Date: 2017-03-14T10:28:47Z prevent to overlap in text if using multiBarChart commit e5c7ac6d312913ba4b5b23ab7aafe40f7f6fb3e3 Author: soralee Date: 2017-03-17T04:35:51Z fix typo commit cd033ff336e0c2cd249ea30bdd36e5af8fade4c2 Author: soralee Date: 2017-03-17T06:32:52Z move to barchart commit 668702cec76bc920604066d7f6a3b14edada2daa Author: soralee Date: 2017-04-03T03:55:19Z remove initial defind xlabels commit 08411326289c89a9773402972faffd2031b72a84 Author: soralee Date: 2017-04-06T07:30:21Z update select visualization xLabel commit 7ec879c921e1f81c6fd6709c8c8cbeb342b0e8ad Author: soralee Date: 2017-04-06T07:35:42Z remove xLabel variable commit c3ececdc3c7c06d216fe55858a796c2afcd838f6 Author: soralee Date: 2017-04-11T00:51:59Z change remove to hide --- 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 #2133: [ZEPPELIN-1357,1892,1370][Umbrella] Text overla...
Github user soralee closed the pull request at: https://github.com/apache/zeppelin/pull/2133 --- 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-2389) Prettify Actionbar icons in Notebook
Hoon Park created ZEPPELIN-2389: --- Summary: Prettify Actionbar icons in Notebook Key: ZEPPELIN-2389 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2389 Project: Zeppelin Issue Type: Improvement Reporter: Hoon Park -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ZEPPELIN-2388) Prettify Keyboard Shortcut Dialog
Hoon Park created ZEPPELIN-2388: --- Summary: Prettify Keyboard Shortcut Dialog Key: ZEPPELIN-2388 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2388 Project: Zeppelin Issue Type: Improvement Components: front-end Reporter: Hoon Park -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (ZEPPELIN-2387) [Umbrella] Improve UX
Hoon Park created ZEPPELIN-2387: --- Summary: [Umbrella] Improve UX Key: ZEPPELIN-2387 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2387 Project: Zeppelin Issue Type: Improvement Components: front-end Reporter: Hoon Park This is umbrella issues collects issues regarding UX -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] zeppelin issue #2228: [ZEPPELIN-2365] button to create note into folder
Github user tae-jun commented on the issue: https://github.com/apache/zeppelin/pull/2228 Cool feature! 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 #2240: ZEPPELIN-2386. Add parameter for check running ...
GitHub user zjffdu opened a pull request: https://github.com/apache/zeppelin/pull/2240 ZEPPELIN-2386. Add parameter for check running current paragraph in ZeppelinContext ### What is this PR for? I can reproduce it via the test code in ZeppelinIT.testAngularDisplay. First run the 4 paragraphs to initiate the state. Then when I click paragraph 0 the first time, paragraph 2 will run correctly. But if I click paragraph 0 again, interpreter would raise the following exception. The cause is that ZeppelinContext's interpreterContext now point to paragraph 2, because paragraph 2 is the last paragraph that runs in this interpreter. So I propose to add parameter to ### What type of PR is it? [Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring] ### Todos * [ ] - Task ### What is the Jira issue? * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/ * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. [ZEPPELIN-533] ### How should this be tested? Outline the steps to test the PR here. ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? * Is there breaking changes for older versions? * Does this needs documentation? You can merge this pull request into a Git repository by running: $ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2386 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2240.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 #2240 commit 5cf771103fc38008b11910573eabd218f81ebd88 Author: Jeff ZhangDate: 2017-04-11T06:21:53Z ZEPPELIN-2386. Add parameter to check running current paragraph in ZeppelinContext --- 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-2386) Add parameter to check running current paragraph in ZeppelinContext
Jeff Zhang created ZEPPELIN-2386: Summary: Add parameter to check running current paragraph in ZeppelinContext Key: ZEPPELIN-2386 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2386 Project: Zeppelin Issue Type: Improvement Affects Versions: 0.7.1 Reporter: Jeff Zhang Assignee: Jeff Zhang -- This message was sent by Atlassian JIRA (v6.3.15#6346)