Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1970
change is good but I'm not completely sure of the behavior change, which is
completely opposite to before?
or more precisely, I'm not sure why it was not passing `spark.*` before?
---
If
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1969
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1967
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1957
Right - please develop against master and open a new 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 no
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1957
and please add interpreter documentation .md file and update license
information as suggested in the PR template `Does the licenses files need
update?` should be yes.
---
If your project is
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1970
@felixcheung I think this is a bug, but didn't cause potential issues yet
for now. In the previous version it would pass all the properties with
non-empty value to SparkConf which means it won't mi
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1929
---
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 e
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1944
@DrIgor You're right. I've misunderstood something. the failure looks
unrelated. Will merge it if there's no more discussion.
---
If your project is set up for it, you can reply to this email an
Github user beriaanirudh commented on the issue:
https://github.com/apache/zeppelin/pull/1971
I checked the CI failure, it does not look relevant to this change.
---
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 pro
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1935
---
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 e
Mina Lee created ZEPPELIN-2054:
--
Summary: Add document for personalize mode
Key: ZEPPELIN-2054
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2054
Project: Zeppelin
Issue Type: Task
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1968
LGTM. merging if there's 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 feat
+1 (binding)
On Sat, Feb 4, 2017 at 12:41 PM, moon soo Lee wrote:
> Verified
> - checksum and signature for release artifacts
> - build from source
> - LICENSE source/binary release
> - source release does not have unexpected binary
> - binary package functioning
>
> +1 (binding)
>
> On Fri
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1946
@DrIgor The last failures looks related to this PR. Can you check it?
- https://api.travis-ci.org/jobs/197657609/log.txt?deansi=true
---
If your project is set up for it, you can reply to th
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1970
That's intended behavior because Zeppelin wants to pass some other
properties not starting "spark.". I didn't remembers exactly, but some
properties should be passed with different prefix "spark.
GitHub user minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1972
[WIP][DOC] 0.7.0 release note
### What is this PR for?
Add 0.7.0 release note
### What type of PR is it?
Documentation
### Todos
* [ ] Confirm release date and updat
Ahyoung Ryu created ZEPPELIN-2055:
-
Summary: Make main page contents enrich in Zeppelin official
website
Key: ZEPPELIN-2055
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2055
Project: Zeppelin
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1973
[gh-pages][ZEPPELIN-2055] Add "What's new in 0.7" and Twitter feed to
website main page
### What is this PR for?
There are lots of improvement in upcoming release 0.7(as mentioned in #1972
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1970
This doesn't conform with spark. Spark don't allow property that doesn't
start with `spark.` [1]
If user want to use any properties in driver side, they should use
properties of Interpreter rat
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1970
I didn't find a history for it but your code snippet tells us no spark
properties doesn't affect anymore in current spark. LGTM
---
If your project is set up for it, you can reply to this email
Jongyoul Lee created ZEPPELIN-2056:
--
Summary: Restructuring InterpreterFactory
Key: ZEPPELIN-2056
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2056
Project: Zeppelin
Issue Type: Impro
Jongyoul Lee created ZEPPELIN-2057:
--
Summary: Extract InterpreterSetting functions from
InterpreterFactory
Key: ZEPPELIN-2057
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2057
Project: Zeppeli
Github user keithchambers commented on the issue:
https://github.com/apache/zeppelin/pull/1600
Is this ready to be merged?
---
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 wesm commented on the issue:
https://github.com/apache/zeppelin/pull/1574
In trying to investigate why the Apache Travis CI build queue is extremely
backlogged, I found many build requests from this particular PR in
https://travis-ci.org/apache/zeppelin/pull_requests
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1972
Looks good 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 this feature
enabled and wishes s
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1973
Looks great!
What do you think add things about improvements on Python/pyspark in what's
new section?
Matplotlib integration in python/pyspark and conda support in python are
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1970
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1574
thanks @wesm for investigating this and following up. it's odd since this
PR is 3 months old? though I'll add we should streamline the test matrix a bit
(as we have from time to time)
---
I
Felix Cheung created ZEPPELIN-2058:
--
Summary: Reduce test matrix on Travis
Key: ZEPPELIN-2058
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2058
Project: Zeppelin
Issue Type: Bug
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1873
I guess the question is by excluding this would it break something down the
line?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1973
^^ that should be a per release what's new page, I think?
---
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 n
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1973
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 and wishes so, or
Github user wesm commented on the issue:
https://github.com/apache/zeppelin/pull/1574
@felixcheung it looks like these builds were triggered by a merge on a
different branch. see for example
https://github.com/apache/zeppelin/commit/e259feacf78770b5dc412c0642216acdce17008f
in
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1971
Great fix, interesting approach.
Looks good 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
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1574
Thanks @wesm , I updated this PR yesterday, but didn't use `git merge`. I
use `git rebase` and `git commit --amend`, does these also the issue as well ?
---
If your project is set up for it, you c
Github user wesm commented on the issue:
https://github.com/apache/zeppelin/pull/1574
Whatever you did generated a merge commit. The proof is right there -- a
rebate or amend would not have two parents
---
If your project is set up for it, you can reply to this email and have your
r
It's very strange - tested with netinst and as previous RC, in the tutorial,
the Martial status drop down box doesn't trigger rerun of the query, works when
manually clicking run.
I double checked to make sure. Could someone else check?
_
From: Jongyoul Lee mailto:j
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1973
@Leemoonsoo @felixcheung Thanks for your review! As @Leemoonsoo mentioned I
added "Improvement in Python" section like below. How about this?
https://cloud.githubusercontent.com/assets/10060
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1973
cool!
---
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 th
Yes, Felix you are right, even I see it.
On 5 February 2017 at 09:43, Felix Cheung wrote:
> It's very strange - tested with netinst and as previous RC, in the
> tutorial, the Martial status drop down box doesn't trigger rerun of the
> query, works when manually clicking run.
>
> I double checked
GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/zeppelin/pull/1974
[ZEPPELIN-2000][HOTFIX] Run paragraph on ng-change when select value
changed.
### What is this PR for?
Run paragraph on ng-change when select value changed.
### What type
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1974
@minahlee, @jongyoul, @felixcheung Please help review 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 proje
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1663
---
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 e
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1969
---
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 e
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1974
looks good. I guess the difference between this and PR #1932 is
> Change selected value from married to single in 5th paragraph ~~and hit
enter.~~
?
---
If your project is s
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1974
fyi, this behavior change is introduced in #1647.
---
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 felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1974
hmm.. interesting, so it's by design 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 fe
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1974
I think Zeppelin has been back and forth couple of times with this
behavior.
I agree current behavior (require user run paragraph after dynamic form
change) can confuse user because
48 matches
Mail list logo
