GitHub user lresende opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/925
[ZEPPELIN-896] Remove individual developer tags from pom
### What is this PR for?
This PR removes individual developer tags from project pom.
### What type of PR is it
GitHub user lresende opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/926
[ZEPPELIN-897] Remove incubator disclaimer
### What is this PR for?
Remove obsolete incubator disclaimer file
### What type of PR is it?
[Bug Fix]
### What is
GitHub user lresende opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/927
[ZEPPELIN-898] Update resources to use Zeppelin TLP links
### What is this PR for?
Update resources to use Zeppelin TLP links
### What type of PR is it?
[Bug Fix
Github user lresende commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/941
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
Github user lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/747
@Leemoonsoo @felixcheung Any ideas what might be causing these build issues
in
[TravisCI](https://s3.amazonaws.com/archive.travis-ci.org/jobs/133750597/log.txt)
?
[INFO
Github user lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
This seems to be moving the whole build to JDK8 and moving some components
to only support scala 2.11 ? Is that really the plan ?
---
If your project is set up for it, you can reply
Github user lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
Agreed @felixcheung , at least we should have a discussion on the dev list
if we plan to have some changes like this.
---
If your project is set up for it, you can reply to this email
GitHub user lresende opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/967
[ZEPPELIN-956] Download old spark versions direct from archive
### What is this PR for?
Older Apache Spark releases seems to have been removed from mirrors, and
thus the build
Github user lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/967
@bzz pushed some updates to fix style issues.
---
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 lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/968
As we have some scala code, do we also want to update with scala style
guide (http://docs.scala-lang.org/style/) ?
---
If your project is set up for it, you can reply to this email and
Github user lresende commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/962
Nice, 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
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
Thank you @Leemoonsoo, let me look at this tonight/tomorrow morning. And
provide any findings on the reported issues.
---
If your project is set up for it, you can reply to this email and have
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo this is now merged and rebased, will still do some test and
investigate the issues reported. Others are welcome to help testing as well.
---
If your project is set up for it, you can
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@prasadwagle Looks like a merge conflict, waiting for local build before
pushing a fix for this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
Ok, things are looking better now, the branch is rebased and I have started
more testing based on Zeppelin and Spark 1.6.1 both compiled with Scala 2.11. I
can run parts of the Zeppelin tutorial
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1039
[ZEPPELIN-1032] Update Apache Flink to 1.0.3 release
### What is this PR for?
Update Flink interpreter to use most recent Apache Flink 1.0.3 release
### What type of PR is it
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1040
[ZEPPELIN-1031] Update Elasticsearch to release 2.3.3
### What is this PR for?
Update ElasticSearch interpreter to use ElasticSearch 2.3.3
### What type of PR is it
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
Ok, looks like the hanging I was seeing was mostly a local issue in my
Spark conf and is now fixed.
I have Zeppelin and Spark built with Scala 2.11, and the tutorial notebook
works well
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo What should be our next step here ?
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo great, let me investigate the issue
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo Thanks for your help, this is now rebased and most of the test
jobs are passing, except with one issue that I am seeing in Travis, but seems
to work ok locally:
...
[INFO
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
We finally got a green build with Scala 2.11 thanks for @Leemoonsoo help on
resolving the couple remaining issues... I now also rebased to latest master
and this PR should be ready to final
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo All green again.
---
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
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@bzz and @Leemoonsoo
I have updated the readme to match the ci, and also refactored the
reflection utility methods to a separate class.
---
If your project is set up for it, you can
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo all back to 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 lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1186
[ZEPPELIN-1179] Append scala version to maven artifacts
### What is this PR for?
Now that we have support for both Scala 2.10 and 2.11 we need to append
Scala version to the maven artifact
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1186
This assumes that #747 is 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
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1194
[ZEPPELIN-1193] Update Node JS related dependencies to avoid RegExp DoS
### What is this PR for?
Update Node JS related dependencies to avoid intermittent build issues that
suggest updates
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1186
@minahlee Good catch, let me fix that.
---
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 lresende commented on the pull request:
https://github.com/apache/zeppelin/commit/bd714c2b96d28b9b6e1b2c71431ace99e5e963ec#commitcomment-18310691
In spark/src/main/java/org/apache/zeppelin/spark/DepInterpreter.java:
In spark/src/main/java/org/apache/zeppelin/spark
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1186
@minahlee I have included the missing modules, and also updated the build
to change the artifact version to _2.11 when performing the build based on
Scala 2.11.
The build is still
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1219
[ZEPPELIN-1180] Update release scripts to publish scala 2.10 and 2.11
artifacts
### What is this PR for?
[ZEPPELIN-1180] Update release scripts to publish Scala 2.10 and 2.11
artifacts
Github user lresende closed the pull request at:
https://github.com/apache/zeppelin/pull/1219
---
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 lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1220
[MINOR] Make scala version definition consistent in Travis.CI configuration
### What is this PR for?
Minor cleanup to make scala version definition consistent in the Travis.CI
configuration
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1209
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1221
If the URLs are all the same, and we set on the parent pom, wouldn't they
be inherited ? In this case, we can actually remove all the child ones, and
make future maintenance easier.
-
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1194
I am with limited internet access for the next week, so if anyone want to
give it a try on continuing this I am fine, otherwise I can continue when I am
back.
---
If your project is set up
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1370
[FLINK-1379] Flink interpreter is missing scala libraries
### What is this PR for?
On Flink interpreter, remove provided scope from scala libraries to enable
copying them to interpreter
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1370
After the fix, performed a full build and compared scala libraries from
flink and ignite
$ cd flink/
$ ls scala*
-rw-r--r-- 1 lresende staff14M Aug 26 12:39 scala-compiler
GitHub user lresende reopened a pull request:
https://github.com/apache/zeppelin/pull/1370
[ZEPPELIN-1379] Flink interpreter is missing scala libraries
### What is this PR for?
On Flink interpreter, remove provided scope from scala libraries to enable
copying them to
Github user lresende closed the pull request at:
https://github.com/apache/zeppelin/pull/1370
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1368
I am not sure what's wrong here. I would say that the proper way to build
for 2.10 and 2.11 is to use the dev/change_scala_version.sh and then change to
use the 2.11 profile.
Is
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1368
This is also how it's documented on the readme.md
https://github.com/apache/zeppelin#building-for-scala-211
---
If your project is set up for it, you can reply to this email and have
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1368
Currently build, by default, is configured to support Scala 2.10, thus just
executing the build works.
In order to build with Scala 2.11, you need to execute:
```
./dev
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1373
[ZEPPELIN-1385] Avoid NPE when create SparkSession
### What is this PR for?
Avoid NPE when create SparkSession is outputDir has not been set yet
### What type of PR is it
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1373
After this fix is applied, have verified that can connect and execute a job
on a remote Spark cluster.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1374
[MINOR] Add new line before logging paragraph content
### What is this PR for?
Add new line before logging paragraph content
### What type of PR is it?
[Improvement]
You can
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1373
@Leemoonsoo No worries, didn't see that...
---
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 lresende closed the pull request at:
https://github.com/apache/zeppelin/pull/1373
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1347
LGTM, Do we need to wait on anything else to get this 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
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1375
[ZEPPELIN-1171] Only retrieve resources if client is set
### What is this PR for?
Fix NullPointerException when trying to retrieve resources and the client
is not set
### What type
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1376
[ZEPPELIN-449] Enhance log messages when interpreter is initializing
### What is this PR for?
Enhance log messages when interpreter is initializing to avoid user
confusion
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1368
@krystiannowak In the referenced commit, you can see that artifacts are
called _2.10 and dependencies are based on _${scala.binary.version}, which
makes things flexible based on the version of
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1387
[ZEPPELIN-1398] Use relative path for search_data.json
### What is this PR for?
Use relative path for search_data.json
### What type of PR is it?
[Bug Fix
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1387
Thanks for checking @Leemoonsoo , I have followed your steps and provided
an updated fix.
Here are the results on my local env.
https://cloud.githubusercontent.com/assets/382917
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1374
@Leemoonsoo any other comments here ?
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1370
@bzz Anything else needed here ?
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1376
@bzz Based on the jira, the exception is causing some confusion with users,
so I would merge, but it's up to the community, I am fine if there are
objections with this change.
An
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1376
Now the issues seems to be related to build timeout ?
No output has been received in the last 10 minutes, this potentially
indicates a stalled build or something wrong with the build itself
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1400
[ZEPPELIN-1407] Fix Scala 2.11 build
### What is this PR for?
Avoid activating the Scala 2.10 profile when building for Scala 2.11
### What type of PR is it?
[Bug Fix
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@bzz @Leemoonsoo Please review, this is more like a hotfix for the 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
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
This should go for both master and 0.6x release.
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@bzz Sorry, I had put the profiles activation as if scala 2.11 was the
default, have fixed it now.
three builds still failing with timeout, I will try to force new builds
---
If your
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1401
[SPARK-17392] Refactor RAT build on Travis.CI configuration
### What is this PR for?
Create a specific build for checking license compliance with RAT
and avoid running these checks on
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1401
One of the builds failed with the following, which seems not related
- should provide onclick method *** FAILED ***
The code passed to eventually never returned normally. Attempted
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1401
@bzz @Leemoonsoo Please 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
enabled
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@bzz the build errors are related to RAT issues
>>>
No output has been received in the last 10 minutes, this potentially
indicates a stalled build or something wrong with the bui
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1402
[MINOR] Remove duplicated dependency declaration
### What is this PR for?
Remove duplicated declaration of maven dependency
### What type of PR is it?
[Bug Fix]
You can merge
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1401
@bzz this has now been updated to follow the same pattern used for maven
tests, enable RAT to run by default, but support disabling it with -DskipRat.
Travis CI will run RAT once, on the RAT
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1401
@corneadoug This is exactly what is implemented 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. If your project does
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@felixcheung @Leemoonsoo @bzz Any more comments here ? Should we merge this
to 0.6 branch and master, as it's kind blocking to 2.11
---
If your project is set up for it, you can reply to
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
@Leemoonsoo The issue wasn't about -P versus -D, but that the Scala 2.10
was with activation true by default, so even when you did only -Pscala2.11 the
Scala 2.10 profile was being acti
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
BTW, the properties on the profile activation, only enables the "default"
to be activated by default, so mvn clean install will not have properties
defined, so will start Scala 2.10..
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
But unfortunately this wasn't what maven was enforcing, and Scala 2.11
build was failing when -PScala2.11 was being used, and when invoking
dependency:tree with -Pscala2.11 there wer
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1400
I have verified that with that by reverting my changes
-PScala2.10/Scala2.11 have the proper behavior and my original issue was that
indeed my build alias had -D for the profile activation
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1376
@bzz Are we merging this ? Or should i 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 does not have
Github user lresende closed the pull request at:
https://github.com/apache/zeppelin/pull/1194
---
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 lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1713
[ZEPPELIN-1530] Update common scripts for Linux and Windows platforms
### What is this PR for?
Avoid forcing set the DEBUG environment variable and also review the two
common scripts for
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1747
Could you please update the title and the PR description with high level
description of your changes even if we still mar it as [MINOR].
---
If your project is set up for it, you can reply to
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1747
Overall, the code changes LGTM.
As for the PR, I would recommend :
1. Add [MINOR] to the title, as this is going to be the commit title
2. Respond the "What is this p
GitHub user lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1757
[ZEPPELIN-1074] Enhance SSL Support
### What is this PR for?
- Run SLL on the defined SSL port
- If Client Authentication is not enabled does not use it's prope
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1762
Please check the build failure, but it might be a flaky test.
Otherwise, LGTM. Tested on master with these changes on top of #1757 and
all looks good with relative path trust store
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1757
@vinayshukla I have extended the README.md to detail how to obfuscate the
passwords using the Jetty password tool
---
If your project is set up for it, you can reply to this email and have your
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1757
@Leemoonsoo Could you please take a quick look at this. Thank you.
---
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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1762
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 lresende opened a pull request:
https://github.com/apache/zeppelin/pull/1779
[ZEPPELIN-1835] Upgrade ElasticSearch to version 2.4.3
### What is this PR for?
Upgrade ElasticSearch to version 2.4.3
### What type of PR is it?
[Improvement]
### What
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1757
No worries @AhyoungRyu I will make the suggested changes and add
ZEPPELIN-1811 to this pr as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1757
@AhyoungRyu @felixcheung Please take a look and let me know if I should
update any other pieces.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/1757
@felixcheung and @AhyoungRyu Sorry for the delay, as I was a little offline
in the last few days. I have implemented the suggestion and this should be
ready to merge.
---
If your project is
Github user lresende closed the pull request at:
https://github.com/apache/zeppelin/pull/1375
---
90 matches
Mail list logo
