m k created ZEPPELIN-2295:
-
Summary: Add option for BigQuery Standard SQL
Key: ZEPPELIN-2295
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2295
Project: Zeppelin
Issue Type: Improvement
Maven was not able to obtain the plexus-io-2.1.2.pom file. “Connection reset”
is the error I’m referring to.
Eventually the build of zeppelin-web component failed.
Initially I thought it’s a network problem that Maven is not able to retrieve
the artifact, but it’s happening consistently to me
Jeff Zhang created ZEPPELIN-2294:
Summary: Interpreter fail exception is not propagated to frontend
Key: ZEPPELIN-2294
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2294
Project: Zeppelin
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2174
@1ambda Will be really appreciated if you can help review 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 project
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/2174
[ZEPELIN-2209] Add pagination to Helium menu
### What is this PR for?
Like I did in #2126, added pagination to Helium menu in Zeppelin.
10 pkgs will be shown per 1 page.
###
Jeff Zhang created ZEPPELIN-2293:
Summary: Remove envName from interpreter-setting.json
Key: ZEPPELIN-2293
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2293
Project: Zeppelin
Issue
+1
-Original Message-
From: Ahyoung Ryu [mailto:ahyoung...@apache.org]
Sent: Wednesday, March 22, 2017 12:27 PM
To: dev@zeppelin.apache.org
Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC1)
+1
On Wed, Mar 22, 2017 at 12:19 PM, Jeff Zhang wrote:
>
> 0
>
> 1.
Hi Chaoran,
This is what I can see in your email.
[image: Inline image 1]
Can't see any error messages in this. Can you point me which part was the
problem with you exactly?
Thanks,
Ahyoung
On Wed, Mar 15, 2017 at 12:30 AM, Chaoran Yu
wrote:
> I’m trying to build the
+1
On Wed, Mar 22, 2017 at 12:19 PM, Jeff Zhang wrote:
>
> 0
>
> 1. Build it from source successfully
> 2. Run pig tutorial using tez successfully, and dynamic form works
> 3. Run livy interpreter via 2 users, 2 livy sessions are created, and
> restarting works in scoped per
0
1. Build it from source successfully
2. Run pig tutorial using tez successfully, and dynamic form works
3. Run livy interpreter via 2 users, 2 livy sessions are created, and
restarting works in scoped per user mode
4. If interpreter fails to start, the exception in interpreter is not
propagated
Github user sravan-s commented on the issue:
https://github.com/apache/zeppelin/pull/2168
@Leemoonsoo , the bug is limited only for 'stacked' version of bar chart.
Notice the radio button inside the chart
* This is the grouped version
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2172
---
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
I propose the following RC to be released for the Apache Zeppelin 0.7.1
release.
The commit id is 22b299b5c17c0c9ad8e54ee15bb7fde645472c65 which is
corresponds to the tag v0.7.1-rc1:
https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=refs/tags/v0.7.1-rc1
The release archives (tgz),
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2167
Thanks @Remilito for working on this issue.
Merge to master and branch-0.7 if no more comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user andreaTP commented on the issue:
https://github.com/apache/zeppelin/pull/2150
Please go on! Thanks!
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2168
Thanks for working on the issue.
I have tested problem
[ZEPPELIN-1889](https://issues.apache.org/jira/browse/ZEPPELIN-1889) in current
master. However i couldn't reproduce the
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2150
Thanks @andreaTP for the improvement!
LGTM and merge to master if no further discussions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2170
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2172
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2166
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2099
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2135
Looks like second test matrix succeeded after the manual restart.
In this case, you also need to trigger Jenkins again to check latest build
status.
Simply close and reopen this PR will
Hi,
I am a committer to the Apache Solr (search engine) project and
registered as a mentor for Google Summer of Code 2017 that just
started to get student proposals. I really like the concept of the
Zeppelin project and would love to see Solr backend integration for
it. Actually, we already
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2173
Looks like travis changed the name of option from "build pushes" to "Build
branch updates".
Amend your last commit with `git commit --amend` and do `git push
your-remote HEAD --force`
GitHub user Remilito reopened a pull request:
https://github.com/apache/zeppelin/pull/2151
[ZEPPELIN-465] Be able to run paragraph and the following ones
### What is this PR for?
Allow to run a paragraph **and** the ones following. This is useful for
instance if you are
Github user Remilito closed the pull request at:
https://github.com/apache/zeppelin/pull/2151
---
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 Remilito commented on the issue:
https://github.com/apache/zeppelin/pull/2151
@AhyoungRyu : updated (and now building and passing tests :sweat_smile: ).
@jongyoul : I am not sure to fully understand what you mean. If you are
talking "UI" IMO the need to run or not a
Github user elkangaroo commented on the issue:
https://github.com/apache/zeppelin/pull/2173
Hi, I have now swiched on 'zeppelin' repository at
https://travis-ci.org/profile.
But I don't see this option:
> And then make sure 'Build pushes' option is enabled in the settings
Shishir Choudhary created ZEPPELIN-2292:
---
Summary: Pyspark interpreter module not found even though --files
parameter provided
Key: ZEPPELIN-2292
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2292
And if i suggest simplest way for us to set quality expectation to user,
which will be labeling release in download page.
Currently releases are divided into 2 categories in download page. 'Latest
release' and 'Old releases'. I think we can treat 'Latest' as unstable and
add one more category
GitHub user elkangaroo opened a pull request:
https://github.com/apache/zeppelin/pull/2173
[ZEPPELIN-2291] Notebook commit dropdown cut-off
### What is this PR for?
When you have a notebook under GIT version control, the dropdown with your
commits will be cut-off with no
Yes, having longer RC period will help.
But if i recall 0.7.0 release, although 21 people participated verifying
through 4 RC for 15days, it wasn't enough to catch all critical problems
during the release process. After the release, we've got much more number
of bug reports, in next few days.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2163
All CI tests have passed now. Ready for review 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
I agree that it will help prolong RC period and use it actually. And also
we need code freeze for the new features and spend time to stabilize RC.
On Tue, Mar 21, 2017 at 1:25 PM, Felix Cheung
wrote:
> +1 on quality and stabilization.
>
> I'm not sure if releasing as
Github user anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/2161
Tested with some basic case, look 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
35 matches
Mail list logo