Github user Karuppayya commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/156#issuecomment-123994032
Thanks @corneadoug
I have renamed the directive, since it is specific to visibility of the
modal.(Moreover it depends on bootstrap modal events).
Github user Madhuka commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/160#issuecomment-123987325
+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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/149
---
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 fea
I volunteer to write a doc for the zeppelin documentation site on step by
step for adding an "external interpreter" targeted for non developers who
wants to add someone's else external interpreter.
The challenge I see is from where to get the compiled interpreter from?
- my answer is to have a list
Congrats to thé team!
On Thursday, July 23, 2015, Henry Saputra wrote:
> Moon, as discussed in general@ list, we could move on with the release.
>
> Congrats Zeppelin community for your first release.
>
> PS:
>
> Just realize I forgot to send my VOTE when helping out at general@ list.
> Sincerel
Moon, as discussed in general@ list, we could move on with the release.
Congrats Zeppelin community for your first release.
PS:
Just realize I forgot to send my VOTE when helping out at general@ list.
Sincerely apologize. Will be more vigilant with next release.
On Wed, Jul 22, 2015 at 5:33 AM,
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/160#issuecomment-123940190
I guess this works as fix for now.
We never really worked on the mobile friendly version of zeppelin
+1 for merge
---
If your project is set
Thanks for the opinions and feedback.
My question was more like simply asking about merging code that does not
have test, but apparently went back to recurrent subject. :-)
Actually, plug'n'play interpreter is already possible by dropping all the
necessary jars under interpreter/[name] directory
Github user benbromhead commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/86#issuecomment-123879282
Ok makes sense, changed back to use the HiveContext by default
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/86#issuecomment-123868220
`zeppelin.spark.useHiveContext` was originally 'false' but changed to
'true'. The reason was to give the same experience with spark-shell, which uses
HiveC
Renxia Wang created ZEPPELIN-182:
Summary: Broadcast the Note's Info to a client Is Not Working when
Creating a New Note
Key: ZEPPELIN-182
URL: https://issues.apache.org/jira/browse/ZEPPELIN-182
Proje
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/163#issuecomment-123860819
Thanks a lot for contributing the code!
---
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 vasilievip opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/163
As an author of code https://groups.google.com/forum/#!msg/selenium-dâ¦
â¦evelopers/PTR_j4xLVRM/k2yVq01Fa7oJ
Based on discussion:
http://markmail.org/thread/inhp3syk244
Github user Madhuka commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/160#issuecomment-123821210
Here is changes and new look of zeppelin in mobile device.
@corneadoug: Both changes are done.
![fix-nav-bar](https://cloud.githubusercontent.co
Renxia Wang created ZEPPELIN-181:
Summary: Provide more Feedback on UI when Clicking the Cancel/Stop
Button of a Pending/Running Paragraph
Key: ZEPPELIN-181
URL: https://issues.apache.org/jira/browse/ZEPPELIN-181
Github user benbromhead commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/86#issuecomment-123802962
@Leemoonsoo yeah I struggled to come up with a good answer for this. On the
one hand I think the default behaviour should be to use the standard SQLSpark
+1
I agree with tog ... the core interpreters should be those that can
complete all the tests and provide the functionality as well. Spark local
being the best example. The Apache Drill interpreter I wrote would need a
single node Drill installation in order to provide the same testing
capability.
Sure,
let's see if we can resolve that in timely manner, its always better
to have a contribution, otherwise yes, we might need to exclude.
https://issues.apache.org/jira/browse/ZEPPELIN-180 was created to
track the progress.
As for the vote - I was under impression we already have 4 +1s in the
t
Alexander Bezzubov created ZEPPELIN-180:
---
Summary: Clarify contribution of the ScreenCaptureHtmlUnitDriver
Key: ZEPPELIN-180
URL: https://issues.apache.org/jira/browse/ZEPPELIN-180
Project: Zeppe
I think that we can have the interpreters add in the build system using
compilation parameters (e.g. same as the list in the zeppelin-env.xml that
way the basic build builds only the core interpreters and the user can
easily interperters to the build process.
With regard to a release, this can be j
If we want to make the intepreters system modular to decouple souce code,
the process of activating an interpreter should be flexible and easy to use.
Asking end-users to make a custom build is not a viable strategy. Recently
I've seen some people trying to make a custom build of Zeppelin and faci
+1 what tog says
From: tog
Sent: Wednesday, July 22, 12:22 AM
Subject: Interpreter with no test.
To: dev@zeppelin.incubator.apache.org
+1
This seems to be a recurrent topic ;-)
It has to be decided what are the core interpreters the Zeppelin want to
support - then I would believe y
DOAN DuyHai created ZEPPELIN-179:
Summary: Add Cassandra Interpreter
Key: ZEPPELIN-179
URL: https://issues.apache.org/jira/browse/ZEPPELIN-179
Project: Zeppelin
Issue Type: Improvement
To run test classes for only a specify module, go into this module and do a
"mvn test"
On Wed, Jul 22, 2015 at 11:37 AM, IT CTO wrote:
> Hi,
> I added a new test class to one of the modules and I would like to run it.
> 1) can I run build and test for a single module e.g. zeppelin-interpreter?
GitHub user doanduyhai opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/162
Cassandra Interpreter
This is a Cassandra interpreter for Zeppelin.
I tried to make the code as clean & modular as possible. The code coverage
is quite high with 75 tests (un
Eran W created ZEPPELIN-178:
---
Summary: Improve magic display system
Key: ZEPPELIN-178
URL: https://issues.apache.org/jira/browse/ZEPPELIN-178
Project: Zeppelin
Issue Type: Improvement
Com
Hi,
I added a new test class to one of the modules and I would like to run it.
1) can I run build and test for a single module e.g. zeppelin-interpreter?
2) Should I add the new test class somewhere in order for it to be run?
Thanks
Eran
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/161
ZEPPELIN-174 Fix sha checksum in release package
https://issues.apache.org/jira/browse/ZEPPELIN-174
* [x] change suffix to sha512
* [x] change to sha512sum command verifia
Having multiple block to display all magic blocks sounds good too.
But having this:
myVar: org.apache.spark.rdd.RDD[Int] = ...
Printed in the middle would look bad
On Wed, Jul 22, 2015 at 4:08 PM, DuyHai Doan wrote:
> Your alternative sounds interesting.
>
> I had something in mind lately, e.g.
+1
This seems to be a recurrent topic ;-)
It has to be decided what are the core interpreters the Zeppelin want to
support - then I would believe you can have a wiki/webpage dedicated to
listing all interpreters that are known to be working with Zeppelin. You
may even consider having recommended p
Your alternative sounds interesting.
I had something in mind lately, e.g. enclosing block of magic
val myVar = ...
println("%table %endTable")
val anotherVar = ...
println("%table % endTable")
The output would be:
myVar: org.apache.spark.rdd.RDD[Int] = ...
%table
...
%endTable
anot
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/160#issuecomment-123584604
Could you also remove those 2 black lines?
And add margin on the left of connected
---
If your project is set up for it, you can reply to this email a
32 matches
Mail list logo