[jira] [Created] (BIGTOP-3327) Fix Zeppelin build issue after upgrading Spark-2.4.5
Yuqi Gu created BIGTOP-3327:
---
Summary: Fix Zeppelin build issue after upgrading Spark-2.4.5
Key: BIGTOP-3327
URL: https://issues.apache.org/jira/browse/BIGTOP-3327
Project: Bigtop
Issue Type: Bug
Reporter: Yuqi Gu
Assignee: Yuqi Gu
Fix Zeppelin build issue after upgrading Spark-2.4.5:
{code:java}
[ERROR] Failed to execute goal
com.googlecode.maven-download-plugin:download-maven-plugin:1.3.0:wget
(download-pyspark-files) on project zeppelin-spark-dependencies_2.11: IO Error:
Could not get content -> [Help 1]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [bigtop] JunHe77 commented on issue #613: BIGTOP-3286: Bump Ignite to 2.7.6
JunHe77 commented on issue #613: BIGTOP-3286: Bump Ignite to 2.7.6 URL: https://github.com/apache/bigtop/pull/613#issuecomment-599860927 This pr passed build/smoke tests on both x86 and arm64: https://ci.bigtop.apache.org/view/Test/job/Build-Deploy-Smoke-Test-Pull-Request-All-Distros/50/ Thanks for the contribution and review, @guyuqi @evans-ye This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [bigtop] JunHe77 merged pull request #613: BIGTOP-3286: Bump Ignite to 2.7.6
JunHe77 merged pull request #613: BIGTOP-3286: Bump Ignite to 2.7.6 URL: https://github.com/apache/bigtop/pull/613 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: [DISCUSS] Drop Apache Tajo, Apache Hama, and Apache Apex
I'm +1 to remove these inactive projects. I remember that there was a discussion to leave those projects to another branch, and related dev work depends on volunteered maintainer/contributor. So maybe we can start this after v1.5 is released. Masatake Iwasaki 于2020年3月17日周二 上午7:56写道： > I'm +1 on removing (effectively) retired products. > > While deprecating in the next release and > removing in after the next might be usual way, > I think it would be ok to remove them in 1.5.0. > Each product in Bigtop has dedicated subdirectories. > Removing (and reverting the removal) should be easy > unless it is depended by other products. > > Thanks, > Masatake Iwasaki > > > On 3/16/20 15:13, Konstantin Boudnik wrote: > > Thanks for bringing this up, Evans! > > > > I think this trimming makes total sense and we were through similar > > discussions before. In fact there's a consensus that we simply can't > > support all the projects that seem to be nice, especially those that > > weren't been active in 3+ years. > > > > I am in favor of trimming the stack down. Unless, there's a maintainer > > in the community who wants to step up and help. > > > > -- > > Regards, > > Cos > > > > On 3/16/20 1:05 PM, Evans Ye wrote: > >> Hi folks, > >> > >> I'd like to raise the discussion about the cleanup of supported > >> component > >> matrix. > >> > >> From [1] the latest release of Tajo is 0.11.3 which was out on > >> 2016-05-18. > >> Since then there're no further release. Similarly on Hama side the > >> latest > >> release is on Jan 28, 2016 [2]. Apex is on Attic so there's no chance to > >> get new release further [3]. > >> > >> Though we'd like to support as many projects as possible, there's simply > >> not enough effort and resource to do it. Dropping them can also let > >> us more > >> focus on what's valuable to the users. What do you think? > >> > >> Kengo Seki > >> As 1.5 RM what do you think? I think if the discussion is positive this > >> will be in 1.5 release. > >> > >> [1] https://tajo.apache.org/ > >> [2] https://hama.apache.org/ > >> [3] https://apex.apache.org/ > >> > >> Evans > >> > >
Re: [DISCUSS] Drop Apache Tajo, Apache Hama, and Apache Apex
I'm +1 on removing (effectively) retired products. While deprecating in the next release and removing in after the next might be usual way, I think it would be ok to remove them in 1.5.0. Each product in Bigtop has dedicated subdirectories. Removing (and reverting the removal) should be easy unless it is depended by other products. Thanks, Masatake Iwasaki On 3/16/20 15:13, Konstantin Boudnik wrote: Thanks for bringing this up, Evans! I think this trimming makes total sense and we were through similar discussions before. In fact there's a consensus that we simply can't support all the projects that seem to be nice, especially those that weren't been active in 3+ years. I am in favor of trimming the stack down. Unless, there's a maintainer in the community who wants to step up and help. -- Regards, Cos On 3/16/20 1:05 PM, Evans Ye wrote: Hi folks, I'd like to raise the discussion about the cleanup of supported component matrix. From [1] the latest release of Tajo is 0.11.3 which was out on 2016-05-18. Since then there're no further release. Similarly on Hama side the latest release is on Jan 28, 2016 [2]. Apex is on Attic so there's no chance to get new release further [3]. Though we'd like to support as many projects as possible, there's simply not enough effort and resource to do it. Dropping them can also let us more focus on what's valuable to the users. What do you think? Kengo Seki As 1.5 RM what do you think? I think if the discussion is positive this will be in 1.5 release. [1] https://tajo.apache.org/ [2] https://hama.apache.org/ [3] https://apex.apache.org/ Evans
[GitHub] [bigtop] guyuqi commented on issue #555: BIGTOP-3264: Add a new Bigtop Mpack definition for Ambari
guyuqi commented on issue #555: BIGTOP-3264: Add a new Bigtop Mpack definition for Ambari URL: https://github.com/apache/bigtop/pull/555#issuecomment-599397759 > @guyuqi Thanks for the video and instructions. Those are very informative. So it seems that the the url need to be updated and II need to rebuild the amber packages w/ the patch, correct? > > When building, I'm running into another error, which wasn't there previously. Probably another 3rd party dependency issue. > https://ci.bigtop.apache.org/view/Test/job/Build-Deploy-Smoke-Test-Pull-Request-Single-Distro/14/console > Let me try to get around this. > > In the meantime, I've looked into the PR again. I've concern on how ODPi's mpack work. It seems the JAR/binary is contained in the patch file, making the patch 20MB large. > Can we get ride of this? Why the jars need to be included instead of fetched and packaged? @evans-ye really sry for the late response. For ODPi Mpack has been included in Ambari trunk, it just added some build and deploying srcripts in bigtop to make itself work. But the ODPi Mpack doesn't work now and no guys would maintain it. For the BGTP Mpack in this PR, it has not been merged in Ambari. So the [PR #3073](https://github.com/apache/ambari/pull/3073) was proposed and `patch3-AMBARI-MPACK.diff` is used as the mirror-file for [PR #3073](https://github.com/apache/ambari/pull/3073) . `patch3-AMBARI-MPACK.diff` composed of 158 files including Json, py and other scripts. Firstly we retain this mirror-file to make BGTP mpack work in Bigtop and we will remove this mirror-file when [PR #3073](https://github.com/apache/ambari/pull/3073) is merged. WDYT? Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
