GitHub user rajarajan-g opened a pull request:
https://github.com/apache/zeppelin/pull/1464
[Zeppelin 796] [WIP] Duplicated notebook names should not be allowed
### What is this PR for?
When a notebook is created/cloned/imported the title/name of the new
notebook should not be
Github user nevillelyh commented on the issue:
https://github.com/apache/zeppelin/pull/132
Sorry haven't worked on this in a while and probably won't have time to.
Closing it for now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/133
@corneadoug Yes we need it, it's a very convenient helper class to display
html/img ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user benbromhead commented on the issue:
https://github.com/apache/zeppelin/pull/86
I'll look to address the remarks. I've also noticed the project now has a
formal tracker via Jira. I'll also look to complete the requirements listed in
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/264
I'm not sure if we do but the py4j version changes for the last few Spark
releases, so if we do, we would need a way to set the right version as per
spark version
---
If your project is set
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1461
@felixcheung AFAIK since this `Patua One` is from
[here](https://github.com/apache/zeppelin/blob/848dbd0302a4e6d4917a70c1cbc2220a7a814488/zeppelin-web/Gruntfile.js#L82),
if some
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1465
@felixcheung Thank you for quick review.
It's because we should get result message even if `pythonScriptInitialized`
is `true` and I thought `pythonScriptInitialized` on the `completion()`
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1408
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1461
Hmmm I don't think anyone has reported this being an issue so I think we
are good.
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user meenakshisekar commented on the issue:
https://github.com/apache/zeppelin/pull/1445
@corneadoug
Based on your comments i shall proceed further.
Thanks,
Meenakshi
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1436
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1465
do we have tests for completion?
---
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 meenakshisekar closed the pull request at:
https://github.com/apache/zeppelin/pull/1445
---
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
GitHub user meenakshisekar reopened a pull request:
https://github.com/apache/zeppelin/pull/1445
[Zeppelin-1001] Take care of comma/tab escape in csv/tsv download
### What is this PR for?
When the data is downloaded as CSV/TSV, the comma/tab in the actual data
has to be
Github user meenakshisekar commented on the issue:
https://github.com/apache/zeppelin/pull/1445
Re opening the pull request to run CI build.
---
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 vensant commented on the issue:
https://github.com/apache/zeppelin/pull/1430
Reopening the pull request as the build failed
---
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
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1441
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 and wishes so, or if
GitHub user vensant reopened a pull request:
https://github.com/apache/zeppelin/pull/1430
[ZEPPELIN-868] Notebook import fails when notebook is large
### What is this PR for?
A bug fix: Added validation in the note import dialog box to check for the
uploaded json file size and
Github user vensant closed the pull request at:
https://github.com/apache/zeppelin/pull/1430
---
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
GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1441
[ ZEPPELIN-967 ] Implement search bar in job manager
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1441
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1449
---
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
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1462
I am afraid this is the only workaround for now. Because these jars are not
available in maven repository.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1463
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1465
why is `pythonScriptInitialized` check removed?
---
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
Robert Marshall created ZEPPELIN-1501:
-
Summary: Cassandra Interpreter SSL support
Key: ZEPPELIN-1501
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1501
Project: Zeppelin
Issue
GitHub user robertdkmarshall opened a pull request:
https://github.com/apache/zeppelin/pull/1466
Add SSL Cassandra support
### What is this PR for?
The Cassandra Interpreter does not support talking to clusters that use
SSL/client to node encryption. It does not have the
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1461
would `Patua One` font be not available on some platforms?
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/133
@doanduyhai Then can you create a Jira issue for it and maybe update the PR
description?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/530
@fanlu As @felixcheung mentioned, you can report issue to
dev@zeppelin.apache.org.
and Could you test https://github.com/apache/zeppelin/pull/1465 for solving
your problem?
---
If your
GitHub user astroshim opened a pull request:
https://github.com/apache/zeppelin/pull/1465
[ZEPPELIN-1500] pyspark completion doesn't work.
### What is this PR for?
@fanlu reported bug on https://github.com/apache/zeppelin/pull/530.
This PR fixes bug of checking condition in
Github user kennknowles commented on the issue:
https://github.com/apache/zeppelin/pull/1334
:+1:!
---
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
Shim HyungSung created ZEPPELIN-1500:
Summary: pyspark completion doesn't work.
Key: ZEPPELIN-1500
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1500
Project: Zeppelin
Issue Type:
GitHub user corneadoug opened a pull request:
https://github.com/apache/zeppelin/pull/1463
[ZEPPELIN-1495] Add Good Practice #4
### What is this PR for?
This Good Practice Guide promotes the usage of `ng-bind` instead of the
classic `{{}}` syntax, to have a performance boost.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1458
Hi @spektom. Thanks for your contribution :)
As you said
>Yes. Documenting zeppelin.livy.spark.sql.truncateResult option.
But it seems there is no docs file change. The
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1463
@corneadoug Looks good ð
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1463
:) Merging it then
---
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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1463
I can't see the code block!
---
If your
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/72
If there is no more discussions, I will close 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 does not
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/132
@nevillelyh
I'm going around old PRs, is there any news on this issue?
Or do you want to close it?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user vensant commented on the issue:
https://github.com/apache/zeppelin/pull/1430
@corneadoug instead of validating the error in server side, I have just
changed the code in the client side, that compares the input file size with the
maximum limit of file size that is already
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1449
Merging if there is 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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1463
@AhyoungRyu Nice catch, I also escaped those in Good Practice #3
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1463
@corneadoug Yeah tested again and now the code blocks are shown well. 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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/125
@Leemoonsoo Do we want to keep this PR, or should we close 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
Github user craigching commented on the issue:
https://github.com/apache/zeppelin/pull/409
It's not. Someone else added this exact feature are part of another PR, so
this has been implemented.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/86
@benbromhead some remarks before rebasing
1) maybe upgrade C* version and Spark/Cassandra connector version
2) maybe use Achilles-embedded (look Cassandra interpreter unit tests)
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/318
@corneadoug it can still be rebased, however more than two repos
concurrently still not supported, so basically it wouldn't change anything. so
it can be closed safely as well in case no
Dmitry Zhukov created ZEPPELIN-1497:
---
Summary: %spark and %python interpreters are able to read
credentials.json file
Key: ZEPPELIN-1497
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1497
Jeff Zhang created ZEPPELIN-1498:
Summary: Flaky test:
http://stackoverflow.com/questions/6121403/how-do-i-get-the-scala-version-from-within-scala-itself
Key: ZEPPELIN-1498
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/61
---
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
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1436
Merge if there is 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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/152
@Madhuka Let's close this one since you opened another one
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/139
@doanduyhai
I'm going around old PRs,
What should we do about that one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/193
@tzolov
I'm going around old PRs,
What is the status of this one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user iemejia commented on the issue:
https://github.com/apache/zeppelin/pull/1334
@mfelgamal or @bzz you must announce this milestone in the beam mailing
list too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/197
We don't usually add to old branch if there is no more releases.
It seems the PR branch doesn't exist anymore.
Closing this PR is there is no more discussions
---
If your project is set
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/246
@Leemoonsoo Any plan on finishing this one?
---
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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/234
@guptarajat Hi, any plan on finishing 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 does not have this
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/273
@tzolov Should we close this one?
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/291
@tzolov @bzz
Do we want to rebase and try 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 guptarajat closed the pull request at:
https://github.com/apache/zeppelin/pull/234
---
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 guptarajat commented on the issue:
https://github.com/apache/zeppelin/pull/234
Noyou can close this PR. As I remember many of the issues I tried to
address in this PR were fixed later on by other guys. Thanks for pinging me on
this one.
---
If your project is set up
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/318
@khalidhuseynov Is this still an issue with our current implementation?
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/389
@babokim
Going around old PRs,
Is it still needed considering the efforts for user authentication, and
notebook acl restrictions?
---
If your project is set up for it, you can reply
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/409
@craigching Is this PR still needed?
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/418
@rawkintrevo Lets remove the `incubator` from URLs, rebase, then merge 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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/560
@Stefan9149 Any plan on trying to finish this PR? Or should we just close
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
CORNEAU Damien created ZEPPELIN-1496:
Summary: Apply Zeppelin-Web Good Practice guide #1 to the code
Key: ZEPPELIN-1496
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1496
Project: Zeppelin
Github user spektom commented on the issue:
https://github.com/apache/zeppelin/pull/1458
@AhyoungRyu Added, thanks for pointing it out to me.
---
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 zjffdu reopened a pull request:
https://github.com/apache/zeppelin/pull/1462
ZEPPELIN-1477. Add Integration Test for LivyInterpreter
### What is this PR for?
This PR fix several issues of LivyInterpeter test.
* Livy interpreter's test code is not in the right
Github user zjffdu closed the pull request at:
https://github.com/apache/zeppelin/pull/1462
---
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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/133
@doanduyhai Do we have the still the need of that 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 does not
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/86
@bbromhead @jongyoul @Leemoonsoo any more feedback on changes needed on
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.
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/228
@akhiluanandh
I'm going around old PRs.
Any plan on continuing that one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/252
@azeloo Any plan on finishing 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 does not have this feature
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/264
@riverajo @felixcheung @Leemoonsoo
Any changes to be done here?
Is this documentation change still needed?
---
If your project is set up for it, you can reply to this email and have
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/299
@leonardofoderaro
I'm going around old PRs,
Any plan on finishing this one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/320
@rolmovel If this PRs is still needed, can we try to rebase 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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/336
Going around old PRs.
As stated before, we had issues with version 1.8.1, and have no plan on
upgrading.
In case newer versions don't have issues we can create a Jira issue to
upgrade.
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/338
@abajwa-hw
I'm going around old PRs, any plan on finishing this one?
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/884
@wind0727 Any plan on taking care of this PR?
I think it would need a new one, based on a special branch instead of your
master.
---
If your project is set up for it, you can reply to this
Nerea created ZEPPELIN-1499:
---
Summary: Create checkbox to choose how to show empty points in
line charts
Key: ZEPPELIN-1499
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1499
Project: Zeppelin
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1462
@Leemoonsoo @prabhjyotsingh @felixcheung Please help review, the failed
test is irrelevant, I have created
[ZEPPELIN-1498](https://issues.apache.org/jira/browse/ZEPPELIN-1498) for it.
---
If
84 matches
Mail list logo
