Github user prasadwagle commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
There were build failures with the java 1.8 change that seemed due to flaky
tests.
https://travis-ci.org/apache/incubator-zeppelin/builds/135174837
I think we should
Github user prasadwagle commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
@felixcheung yes, it should be. I have moved the classes to
org.apache.zeppelin.scalding but we need
[this](https://github.com/twitter/scalding/pull/1563) scalding change
Github user prasadwagle commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
All checks passed in the last build. Can someone please review? There is
interest in the cascading and scalding community for this interpreter.
---
If your project is set up
Github user prasadwagle commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
@Leemoonsoo I understand and have made the changes you recommended. I also
created https://issues.apache.org/jira/browse/ZEPPELIN-972.
---
If your project is set up for it, you can
Github user prasadwagle commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/917
@felixcheung @lresende I agree. I wanted to see the build errors before I
started a discussion on the dev list. In the previous build, one check didn't
complete, many failed
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/917
[ZEPPELIN-840] Scalding interpreter that works in hdfs mode
### What is this PR for?
Scalding interpreter that works in hdfs mode
### What type of PR
Github user prasadwagle closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/917
---
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
Github user prasadwagle closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/860
---
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
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/860
[ZEPPELIN-828] Use individual user credentials for data source
authentication
### What is this PR for?
The purpose of this pull request is to allow users to use their own
Github user prasadwagle commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/860#issuecomment-222004964
I just merged with the latest master and still got two build failures.
cc: @bzz @corneadoug @sagarkulkarni3592
https://travis-ci.org/apache
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/860
[ZEPPELIN-828] Use individual user credentials for data source
authentication
### What is this PR for?
The purpose of this pull request is to allow users to use their own
Github user prasadwagle closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/860
---
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
GitHub user prasadwagle opened a pull request:
https://github.com/apache/zeppelin/pull/1240
[ZEPPELIN-1246] In JDBCInterpreter.getScheduler, use
getMaxConcurrentConnection instead of hardcoding maxConcurrency to 10
### What is this PR for?
In JDBCInterpreter.getScheduler, use
Github user prasadwagle closed the pull request at:
https://github.com/apache/zeppelin/pull/1240
---
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
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/zeppelin/pull/1240
[ZEPPELIN-1246] In JDBCInterpreter.getScheduler, use
getMaxConcurrentConnection instead of hardcoding maxConcurrency to 10
### What is this PR for?
In JDBCInterpreter.getScheduler, use
Github user prasadwagle closed the pull request at:
https://github.com/apache/zeppelin/pull/1240
---
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
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1240
I rebased my branch of latest master and pushed it to origin, closed and
reopened pull request but the travis build hasn't started. What is the reason
for that?
```
tw-172-25-130
GitHub user prasadwagle opened a pull request:
https://github.com/apache/zeppelin/pull/1270
[ZEPPELIN-1273] Use Math.abs to determine if custom formatter should be
called for y axis values
### What is this PR for?
Use Math.abs to determine if custom formatter should be called
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/zeppelin/pull/1270
[ZEPPELIN-1273] Use Math.abs to determine if custom formatter should be
called for y axis values
### What is this PR for?
Use Math.abs to determine if custom formatter should be called
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1240
I got the latest master with #1261 Two checks in the last build failed. I
am going to close and reopen PR to restart build.
https://travis-ci.org/apache/zeppelin/jobs/149535134
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/zeppelin/pull/1240
[ZEPPELIN-1246] In JDBCInterpreter.getScheduler, use
getMaxConcurrentConnection instead of hardcoding maxConcurrency to 10
### What is this PR for?
In JDBCInterpreter.getScheduler, use
Github user prasadwagle closed the pull request at:
https://github.com/apache/zeppelin/pull/1240
---
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
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1270
> Or do you think we should also apply this to upcoming 0.6.1 as well?
I can do that. What branch should I use for 0.6.1?
I merged with latest master this morning. Two che
Github user prasadwagle closed the pull request at:
https://github.com/apache/zeppelin/pull/1270
---
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
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/zeppelin/pull/1240
[ZEPPELIN-1246] In JDBCInterpreter.getScheduler, use
getMaxConcurrentConnection instead of hardcoding maxConcurrency to 10
### What is this PR for?
In JDBCInterpreter.getScheduler, use
Github user prasadwagle closed the pull request at:
https://github.com/apache/zeppelin/pull/1240
---
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
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/zeppelin/pull/1240
[ZEPPELIN-1246] In JDBCInterpreter.getScheduler, use
getMaxConcurrentConnection instead of hardcoding maxConcurrency to 10
### What is this PR for?
In JDBCInterpreter.getScheduler, use
Github user prasadwagle closed the pull request at:
https://github.com/apache/zeppelin/pull/1240
---
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
GitHub user prasadwagle reopened a pull request:
https://github.com/apache/zeppelin/pull/1240
[ZEPPELIN-1246] In JDBCInterpreter.getScheduler, use
getMaxConcurrentConnection instead of hardcoding maxConcurrency to 10
### What is this PR for?
In JDBCInterpreter.getScheduler, use
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1351
Thanks @Peilin-Yang! This problem and the one in #1363 were reported by
Twitter users and I am glad we are fixing them.
The build failures are due to flaky tests, You may want to see
GitHub user prasadwagle opened a pull request:
https://github.com/apache/zeppelin/pull/1785
[ZEPPELIN-1833] Fix bug in ClientFactory.destroyObject that does not close
socket connections
### What is this PR for?
Fix bug in ClientFactory.destroyObject that does not close socket
31 matches
Mail list logo
