Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/219#issuecomment-132387297
+1 on copy icon and interpreter bindings
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/222#issuecomment-132387939
is this default going to be stored with the interpreter binding?
perhaps some sort of template so one can create a python notebook, for
example
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/223#issuecomment-132389778
I didn't quite get, what was the root cause of the NPE?
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/220#issuecomment-132828943
cool it seems to work
---
If
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/220#issuecomment-132829280
hmm, but not this (this is without fix in this PR)
. At least I think it help use
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/222#issuecomment-133507012
@Leemoonsoo great point on copy notebook
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/239#issuecomment-133508427
looks great!
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/237#issuecomment-133508501
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/228#issuecomment-133934888
We could call `sc.stop()` or `SparkIMain.reset()`?
Though apparently SparkIMain reset() has some issue:
https://issues.apache.org/jira/browse/SPARK
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/244#issuecomment-134069646
looks good. this is a very important change, thanks for making it
---
If your project is set up for it, you can reply to this email and have your
reply
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/255#issuecomment-135201501
+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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/257#issuecomment-135201699
Do you have a screen cap of this with the textbox with unsaved text state
(text box left bar has a color)?
---
If your project is set up for it, you
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/263#issuecomment-135905228
looks good... what is the guideline on when to show this notification?
---
If your project is set up for it, you can reply to this email and have your
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/264#issuecomment-135905387
It should build this automatically when SPARK_HOME is defined right?
---
If your project is set up for it, you can reply to this email and have your
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/264#issuecomment-135931941
Hmm, should we use SparkConf instead then:
https://github.com/apache/spark/blob/69c9c177160e32a2fbc9b36ecc52156077fca6fc/yarn/src/main/scala/org
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/264#issuecomment-136522014
@Leemoonsoo good idea.
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/269#issuecomment-136526195
Instead of int/const, should we use enum for this? Instead we could say:
`hasDataFrame` or `hasSchemaRDD` etc?
---
If your project is set up
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/269#issuecomment-136550204
looks good! thanks for this, I'm going to pick this up with the "provided
spark" change
---
If your project is set up for it, you ca
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/269#issuecomment-136557244
awesome!
---
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 pull request:
https://github.com/apache/incubator-zeppelin/pull/265#issuecomment-136956164
+1 on 3.2.3 - I think that version is required to build Spark
---
If your project is set up for it, you can reply to this email and have your
reply
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/272#issuecomment-137476487
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/270#issuecomment-137903488
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/273#issuecomment-138098691
+1 @Leemoonsoo https://issues.apache.org/jira/browse/ZEPPELIN-214
I think we should be good with this PR and track the bigger work on
interpreter
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/278#issuecomment-138099373
Could you elaborate on what this does?
```
hbase.irb.load: (Testing only) Default is true. Whether to load irb in the
interpreter
GitHub user felixcheung opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/284
[ZEPPELIN-283] IllegalArgumentException when running provided Spark 1.5.0
snapshot build
This relax the Spark version check to allow for "1.5.0-SNAPSHOT"
@Leemoo
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/287#issuecomment-138359475
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/294#issuecomment-139389497
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
GitHub user felixcheung opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/297
Add documentation on how to add syntax highlighting in the ACE editor
For a new programming language
You can merge this pull request into a Git repository by running:
$ git
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/298#issuecomment-139690876
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/299#issuecomment-139692299
Could you please reference the JIRA ticket here?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/300#issuecomment-140147567
looks fine
---
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 pull request:
https://github.com/apache/incubator-zeppelin/pull/301#issuecomment-140149273
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/308#issuecomment-140585375
Thanks for looking into this. I myself have also bitten by this issue.
Is this the right user experience though, storing something that is
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/303#issuecomment-141516770
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/314#issuecomment-142160809
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/317#issuecomment-142453101
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/326#issuecomment-143904932
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
GitHub user felixcheung opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/328
[ZEPPELIN-328] Interpreter page should clarify the % magic syntax for
interpreter group.name
Currently the Interpreter page like the interpreters as
hive %hql
However, this
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/328#issuecomment-144201238
Any comment is welcome
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/328#issuecomment-144201203
Before
After
 not working.
Using `%hive` (hql is the default interpreter) or `%spark` (spark/scala is
the default
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/330#issuecomment-144493478
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/329#issuecomment-144493652
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/328#issuecomment-144815284
any more feedback on this?
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/328#issuecomment-145189910
I looked into this more.
The default interpreter for a given group is the first interpreter:
https://github.com/apache/incubator-zeppelin/blob
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/328#issuecomment-146723019
Updated to handle default group. My understanding is the default group is
the first interpreter group from config.
Here's what it looks
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/328#issuecomment-146730179
because when spark is the default group, you can run pyspark by simply
putting `%pyspark%` at the beginning of the paragraph. This is my understanding
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/328#issuecomment-147779901
any more thoughts on this?
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/340#issuecomment-147855008
Since the auto-save is timer based, I do agree it is confusing to see a new
paragraph appearing by itself.
I agree with @Leemoonsoo that the
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/340#issuecomment-147855146
And sometimes one does not want a new paragraph created automatically
---
If your project is set up for it, you can reply to this email and have your
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/342#issuecomment-148183257
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/344#issuecomment-148785887
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/346#issuecomment-148786244
looks good! thanks for fixing this
---
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 felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/348#issuecomment-148882452
Could you please include bug info in PR description?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/352#issuecomment-149300567
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/350#issuecomment-149300655
nice, 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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/361#issuecomment-150661569
@tzolov
---
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 pull request:
https://github.com/apache/incubator-zeppelin/pull/360#issuecomment-150853358
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/364#issuecomment-150986444
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/363#issuecomment-150986471
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/365#issuecomment-150986631
Spark does it by referring to copies under a license directory. Should that
be done here?
https://github.com/apache/spark/tree/master/licenses
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/359#issuecomment-150986734
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/361#issuecomment-150986836
There's another earlier attempt for this #211, #60
Other JDBC-like use cases perhaps you could also factor into your design?
#73, #110
-
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/366#issuecomment-150986877
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/367#issuecomment-150986921
Are you able to figure why the link to json files are broken on the doc
site?
---
If your project is set up for it, you can reply to this email and
GitHub user felixcheung opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/368
[ZEPPELIN-357] Add support for a configurable list of repo for dependencies
Make it configurable via `zeppelin.dep.additionalRemoteRepository`, with
spark-packages default. This
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/368#issuecomment-150989388
In action:
?
---
If your project is set up for it, you can
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-155594138
If I understand correctly this requires a special build of Flink?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/410#issuecomment-155596456
looks good, this covers most of this earlier bug: ZEPPELIN-368
I'd say we would need to add: complete list of properties supported by
interpr
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-155618776
I see, so this is referring to 0.10 Flink only?
"
http://trevorgrant.org/2015/11/03/apache-casserole-a-delicious-big-data-recipe-for-the-
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/412#issuecomment-155619296
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
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/411#issuecomment-155652264
looks good.
agreed multi-binding of the interpreter is confusing. also we might need to
support multiple working instances too.
---
If your project
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/410#issuecomment-155709616
Sure! Please feel free.
---
If your project is set up for it, you can reply to this email and have
Github user felixcheung commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-155912343
docs/assets/
like in: docs/assets/themes/zeppelin/img
---
If your project is set up for it, you can reply to this email and have your
reply
1 - 100 of 616 matches
Mail list logo
