Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1902
@jaspinderdineout This was merged into master.
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1905
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2071
CI failed, but irrelevant.
- profile: https://travis-ci.org/1ambda/zeppelin/builds/205664772
- failed log1:
https://s3.amazonaws.com/archive.travis-ci.org/jobs/205664774/log.txt
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2037
I will review and comment soon. Great Feature!
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2077
CI failed, but irrelevant.
- build profile: https://travis-ci.org/1ambda/zeppelin/builds/206002571
- failed log1:
https://s3.amazonaws.com/archive.travis-ci.org/jobs/206002573/log.txt
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2074
Sure. I will test and give you feedback soon!
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1887
@AhyoungRyu Thanks for caring this!
- It would be easier to start from scratch i think. ð
- I will work on after #1982 is handed!
---
If your project is set up for it, you can
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2077
@AhyoungRyu Thanks for cool 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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2071
@AhyoungRyu It's because invalid `.babelrc`.
-
https://github.com/1ambda/zeppelin-advanced-transformation/blob/master/.babelrc
Thanks for detailed review!
---
If your project
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2054
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
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/2071
[ZEPPELIN-2166] HeliumBundleFactoty can't transfile imported es6+
### What is this PR for?
Currently, we don't use any preset. This cause error messages like
when a helium package
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1982
I'v just rebased to resolve conflict
## Newly added commits
- Remove `local` values in helium package jsons:
https://github.com/apache/zeppelin/pull/1982/commits
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/2077
[ZEPPELIN-2191] Helium package should be able to import css
### What is this PR for?
Helium package should be able to import css. For example,
- Someone want to create spell
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
@Leemoonsoo
I think **option 2** (Adding a property) is a better solution. because
1) Adding a new interpreter just for support another markdown parser might
be confusing
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
I'v restored markdown4j parser and add `markdown.parser.type` property to
`md` group. Pegdown parser will be used only if user specify `pegdown` property
value.
https
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
@AhyoungRyu Thanks for for your review and comments :)
I'v updated docs and added missing license declaration in some java files.
Now docs/markdown looks like
https
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1384
[ZEPPELIN-1387] Support table in markdown interpreter
### What is this PR for?
Support markdown syntax issued by
[ZEPPELIN-1387](https://issues.apache.org/jira/browse/ZEPPELIN-1387?jql
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
@Leemoonsoo I'v fixed license description. Also, now I understand when to
describe licenses to `licenses` or `bin_licenses`. Thanks. :)
@bzz I think it is better to use more specific
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
@AhyoungRyu
It was due to the `ANCHORLINK` option in pegdown. I removed it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
Now CI is failing on the third build job. :(
I checked out `zeppelin/master` and merged it on
`1ambda/fix-zeppelin-1387`.
Should I have use git `rebase` command instead? I thought
GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1384
[ZEPPELIN-1387] Support table syntax in markdown interpreter
### What is this PR for?
Support table markdown syntax issued by
[ZEPPELIN-1387](https://issues.apache.org/jira/browse
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1384
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
Close PR to re-trigger CI
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
Open PR to re-trigger CI
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1384
Finally, CI is 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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1594
@bzz Resolving CI failure will be next step. But i think it is not problem
of markdown processor. All tests are failed in scalding interpreter test
I will rebase and retrigger CI again
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1598
Blocked until 5.1 release due to too many undocumented breaking 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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1598
@bbonnin Thanks for the quick review :)
1. Duplicated code in `executeDeleteQuery` is due to incompatible API
between 2.x and 5.x
```
// 2.x
public boolean isFound
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1594
rebased
---
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
GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1594
[ZEPPELIN-1614] Remove markdown4j dep
### What is this PR for?
Remove unmanaged, old library markdown4j dep which exists just for
Websequence and YUML plugins.
(related to https
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1594
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1611
Hi ð @benoyantony!
I'v checked out your PR and tested, but zeppelin doesn't start rendering
503 page.
```
$ zeppelin-master git:(pr/1611) mvn clean package -DskipTests
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1594
@Leemoonsoo @felixcheung @bzz test is now 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
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1621
[ZEPPELIN-1650] Add mariadb, redshift configs and useful links to JDBC doc
### What is this PR for?
Add 2 JDBC configs and useful links to JDBC doc so that users can connect
those
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1621
I wanted to add drill settings in this PR but failed to test it. Could
anyone recently try drill (1.8)?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1598
Ref -
https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_50_java_api_changes.html
---
If your project is set up for it, you can reply to this email and have your
reply
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Additionally, It would be better to
- run zeppelin immediately (using `zeppelin.sh` because we can run docker
as daemon mode)
- allow user to modify config important config files
GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1621
[ZEPPELIN-1650] Add mariadb, redshift configs and useful links to JDBC doc
### What is this PR for?
Add 2 JDBC configs and useful links to JDBC doc so that users can connect
those
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1621
---
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
GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1629
[ZEPPELIN-1659] DON'T reset filter whenever each interpreter setting is
updated
### What is this PR for?
Filter is cleared whenever each interpreter setting is updated.
it's
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1629
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1629
After fixed:
---
If your project is set up for it, you
GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1621
[ZEPPELIN-1650] Add mariadb, redshift configs and useful links to JDBC doc
### What is this PR for?
Add 2 JDBC configs and useful links to JDBC doc so that users can connect
those
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1621
---
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
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1629
[ZEPPELIN-1569] DON'T reset filter whenever each interpreter setting is
updated
### What is this PR for?
Filter is cleared whenever each interpreter setting is updated.
it's
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1629
What if we keep filter after interpreter creation?
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1621
@AhyoungRyu Updated postgres image :) Thanks again.
CI is failing but it doens't related this PR i think.
---
If your project is set up for it, you can reply to this email and have your
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1594
@bzz Please let me know if you need anything to merge this PR :)
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1623
@benoyantony
Hi, I am trying to test this feature. May I ask 2 things about this PR?
- What is possible if this feature is merged in terms of usage? (e.g user
scenario
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1638
```
05:33:43,422 INFO alluxio.logger.type:202 - Connecting to local worker @
testing-docker-d2b67f49-f525-4c23-a9ab-36aafddcf032/172.17.0.12:42241
05:33:43,422 ERROR alluxio.logger.type
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1663
Let me review this PR and then give you some feedbacks. Thanks @karup1990
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1647
@Mleekko
Thanks for contribution.
A. CI failure is not related to this PR
```
// https://api.travis-ci.org/jobs/176444213/log.txt?deansi=true
17:44:25,594
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1663
@karup1990 sorry for misspelling It was **clear output**
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1668
@bzz Thanks for review! I didn't know about `change_scala_version.sh` but
it is very important if it's affected
There are many ways to compare, but i choose simple and reproduceable way
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1673
@bzz I think this is cool. This will reduce build time for profiles do not
test
If we worry about version, we could specify in `pretest` command like `npm
install karma-phantomjs-launcher
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1638
@bzz Removed styling commit. Let's see the CI result. Thanks!
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1662
@bzz I couldn't consider the reviewer's point of view. I will split this!
Thanks again :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1339
Let me also review this great PR and then give some feedbacks ð
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1668
@bzz
Failed due to not the related test. I will amend commit and trigger CI again
```
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 110.105 sec
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1638
Something is wrong. I will fix 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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1638
I will rebase to clean useless commits
---
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
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1668
[WIP] chore/centralize maven pom versions
I am trying to centralising versions of libraries, plugins in pom.xml. (I
need powerful CI to test this PR continuously)
You can merge this pull
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1659
---
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
GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/1659
[ZEPPELIN-1667] Fix maven options while updating node, npm packages
### What is this PR for?
Update maven plugin, node vesion, npm package and fix tests to make #1639
pass CI
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
retrigger CI due to failures of irrelevant tests
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1666
I think we can merge this first and then rebase #1659 easily :)
This PR looks good to me and is what we want :)
---
If your project is set up for it, you can reply to this email and have
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
rebased to resolve conflict with #1666
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1669
Test failed, but not irrelevant with this PR
```
// https://travis-ci.org/apache/zeppelin/jobs/177967999
// https://api.travis-ci.org/jobs/177967999/log.txt?deansi=true
14
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal
Hi :) ping
---
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
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1674
[ZEPPELIN-1695] Apply regular maven indent
### What is this PR for?
**First of all, this PR doesn't affect on runtime application behaivor and
existing build processes. Just styling all
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal @bzz
I think we should dockerize binary zeppelin images first because more users
use binary versions.
---
If your project is set up for it, you can reply to this email
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Now this issue is like more about building base image :) I will start
working on a new JIRA issue as @bzz mentioned about creating runnable zeppelin
images per version based on this. That would
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1168
@bzz
I created a JIRA issue for this:
https://issues.apache.org/jira/browse/ZEPPELIN-1709
We can resolve this in 1 PR or can split it into multiples. I think we can
resolve
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1680
[MINOR] Invalid constructor call in a test causes all CI failure
### What is this PR for?
A small minor fix for CI failure
### What type of PR is it?
[Bug Fix
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1674
@bzz We can rebase and merge smaller PRs first like
https://github.com/apache/zeppelin/pull/1668 and #1339 you mentioned.
I will rebase #1668 first.
---
If your project is set up
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1686
@soralee This is cool! ð
a small suggestions here :)
- usually, many tools use `CTRL + L` to clear output. Can we use this
familiar key instead?
---
If your project is set
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1668
rebased to keep sync with master (+ to see CI is green as well)
---
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
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1696
CI test for 1689
This is a comparison group for #1689
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1ambda/zeppelin ci-test-for-1689
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1690
I separated plugin link with setting guide @AhyoungRyu :)
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1339
Short summary and small thought about #1399
1. Using symlink like `local-spark/master` would be safe i think. It
enables user replace his local spark without renaming directories
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1696
@bzz That's because invalid `_tools/checkstyle.xml`. I'v just updated sorry
for distraction :)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1668
I will resolve conflict with
https://github.com/apache/zeppelin/commit/4ac577f711b2d62afb2016b95b6ccc3a85afd108
---
If your project is set up for it, you can reply to this email and have your
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1690
[ZEPPELIN-1709] docs: Describe how to use checkstyle plugins
### What is this PR for?
The sub issue of https://github.com/apache/zeppelin/pull/1689 (PRs are
splitted due
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1689
[ZEPPELIN-1709] Update checkstyle rule file, plugin
### What is this PR for?
We have
- outdated checkstyle.xml
- old maven checkstyle plugin
- no detailed style plugin
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1689
\cc @bzz for review thanks!
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1686
Ace users also issued about it. https://github.com/ajaxorg/ace/issues/210
- I think this is a good feature and will be used so many times by so many
people. Thus we should carefully
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1684
I am not sure but this might be due to OS
I tested this PR and works well as @marchpig described. (but i didn't
reproduce this issue like @AhyoungRyu)
---
If your project is set up
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1689
Failed due to log size limitation of travis CI
```
The log length has exceeded the limit of 4 MB (this usually means that the
test suite is raising the same exception over and over
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1693
[ZEPPELIN-1695] chore: Set xml plugin phase to verify (minor)
### What is this PR for?
Changed the phase of xml validation plugin from validate to verify so that
developers can use `mvn
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
@cloverhearts
Thanks for your comment. I have some questions.
- How we can check one of our dependencies doens't work on 6.x but works in
4.x even build passes?
- As I know
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
README is updated. You can preview
-
https://github.com/1ambda/zeppelin/blob/239c74a3100031bf615b879bf589719a78e9ba71/zeppelin-web/README.md
---
If your project is set up for it, you
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1659
README is updated.
- (preview)
https://github.com/1ambda/zeppelin/blob/ece898e982360aae05b899a02de9e8f8da095759/zeppelin-web/README.md
---
If your project is set up for it, you can
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1666
Hi, @asanjar
Actually, we are talking about upgrading node, npm and karma related
versions in https://github.com/apache/zeppelin/pull/1659
Could you check it?
---
If your project
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1640
I think this PR is cool :) @AhyoungRyu One more question,
What do you think if we can filter out interpreters using keywords like
`%dep` `%r`?
---
If your project is set up
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1649
CI failed but it doesn't related with this PR
- https://api.travis-ci.org/jobs/176613823/log.txt?deansi=true (NPE)
- https://api.travis-ci.org/jobs/176613828/log.txt?deansi=true
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1638
---
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
101 - 200 of 1201 matches
Mail list logo
