You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/23 23:58:00 UTC
[jira] [Commented] (BIGTOP-2282) Define Bigtop 1.2 release BOM
[ https://issues.apache.org/jira/browse/BIGTOP-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061661#comment-16061661 ]
ASF GitHub Bot commented on BIGTOP-2282:
----------------------------------------
GitHub user kwmonroe opened a pull request:
https://github.com/apache/bigtop/pull/239
BIGTOP-2282: spark charm: leverage puppet config, gpu enablement
- Document new install-cuda config option for installing cuda on
capable hardware.
- Leverage library and mem config options exposed in [BIGTOP-2821](https://issues.apache.org/jira/browse/BIGTOP-2821).
- Add CUDA handlers to add cuda lib paths to spark config.
- Drive by fixes:
- Simplify yarn detection in get_master_url.
- When installing spark standalone, use an empty string for the
namenode host so we don't use the default head_node value.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/juju-solutions/bigtop feature/BIGTOP-2822/spark-gpu-new-overrides
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/239.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #239
----
commit 40f091ecb6ea89ae083a7e521ca06f559ba8eb2e
Author: Kevin W Monroe <ke...@canonical.com>
Date: 2017-06-07T16:21:50Z
default cuda option true
commit 743afd0cf1b7120b101099593b81ddbbb52f116a
Author: Kevin W Monroe <ke...@canonical.com>
Date: 2017-06-23T23:48:13Z
BIGTOP-2822: spark charm: leverage puppet config, gpu enablement
- Document new install-cuda config option for installing cuda on
capable hardware.
- Leverage library and mem config options exposed in BIGTOP-2821.
- Add CUDA handlers to add cuda lib paths to spark config.
- Drive by fixes:
- Simplify yarn detection in get_master_url.
- When installing spark standalone, use an empty string for the
namenode host so we don't use the default head_node value.
----
> Define Bigtop 1.2 release BOM
> -----------------------------
>
> Key: BIGTOP-2282
> URL: https://issues.apache.org/jira/browse/BIGTOP-2282
> Project: Bigtop
> Issue Type: New Feature
> Components: general
> Affects Versions: 1.1.0
> Reporter: Konstantin Boudnik
> Assignee: Roman Shaposhnik
> Priority: Blocker
> Fix For: 1.2.0
>
>
> It is this time again to start thinking about what we'd like to put into the next release, once 1.1.0 is out of the doors.
> I know we have discussed this in the past, but I wonder if trying to make a quick consequent release with just some components updates would be make sense? Obvious candidates will be Hadoop 2.7.2, Hive 1.2.2 (might be ready soon), Spark 1.6.1
> Or the community would rather spend more time and deliver upgraded components along with the improvements to our own software as well?
> Here's the proposed list
> {code}
> alluxio 1.0.1 ==> 1.3.0
> ambari 2.5.0
> apex 3.4.0
> bigtop-groovy 2.4.4 ==> 2.4.10
> bigtop-jsvc 1.0.15
> bigtop-tomcat 6.0.45
> bigtop-utils 1.2.0-SNAPSHOT
> crunch 0.13.0 ==> 0.14.0
> datafu 1.0.0 ==> 1.3.0
> flink 1.0.3 ==> 1.1.3
> flume 1.7.0
> giraph 1.1.0
> gpdb 4.3.99.0 ==> 5.0.0-alpha.0
> hadoop 2.7.2 ==> we should move to 2.7.3
> hama 0.7.0
> hbase 1.1.3 ==> 1.2.4
> hive 1.2.1 ==> should we add Hive 2.1.x, as well? needs Tez 0.9.x??
> hue 3.9.0 ==> 3.11.0
> ignite-hadoop 1.5.0.final ==> 1.9.0
> kafka 0.9.0.1 ==> 0.10.1.1
> kite 1.1.0
> mahout 0.11.1 ==> 0.12.2
> oozie 4.2.0 ==> 4.3.0
> phoenix 4.9.0-HBase-1.1
> pig 0.15.0 ==> 0.16.0
> qfs 1.1.4
> solr 4.10.4 ==> 5.2.x
> spark 2.1.0
> spark1 1.6.2
> sqoop 1.4.6
> sqoop2 1.99.4
> tajo 0.11.1
> tez 0.6.2 ==> 0.7.x
> zeppelin 0.7.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)