Re: [ANNOUNCE] New Bigtop PMC member Nate D'Amico

Congrats Nate! Olaf > Am 25.01.2016 um 22:00 schrieb Andrew Purtell : > > On behalf of the Apache Bigtop Project Management Committee, I am pleased to > announce that Nate D'Amico has accepted our invitation to join the Bigtop PMC. > > Please join me in congratulating

[jira] [Created] (BIGTOP-2281) Add HIVE-12875 to Bigtop

Olaf Flebbe created BIGTOP-2281: --- Summary: Add HIVE-12875 to Bigtop Key: BIGTOP-2281 URL: https://issues.apache.org/jira/browse/BIGTOP-2281 Project: Bigtop Issue Type: Bug

Re: Maintainers list

Great idea! Thanks for staying on to of it - surely important considering how big the stack has become. Cos On Tue, Jan 26, 2016 at 09:06PM, RJ Nowling wrote: > Hi all, > > I sent follows up to the three groups who contacted us about contributing > new packages to bring up the importance of

Re: HiBench as part of Bigtop

On Tue, Jan 26, 2016 at 11:58PM, Jay Vyas wrote: > If hibench can run as a gradle task that would be far more useful to the > typical audience IMO and less technical debt to carry > > .I think the amount of boilerplate for a package only is justified if > it's a distributed component.

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user andrewmusselman commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175436927 Builds correctly locally via `$ sudo docker run --rm -v `pwd`:/ws --workdir /ws bigtop/slaves:trunk-centos-7 bash -l -c './gradlew --stacktrace mahout-clean

[GitHub] bigtop pull request: BIGTOP-2180: Add smoke-test scripts using gra...

Github user yeongeon closed the pull request at: https://github.com/apache/bigtop/pull/67 --- 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

RE: HiBench as part of Bigtop

Which way does the community prefer? Just for packaging or the put entire project into bigtop? -Original Message- From: RJ Nowling [mailto:rnowl...@gmail.com] Sent: Wednesday, January 27, 2016 11:24 AM To: dev@bigtop.apache.org Subject: Re: HiBench as part of Bigtop A few of us have

Re: HiBench as part of Bigtop

If HiBench itself were contributed to Bigtop, maybe we could work on joining forces with our efforts on the Bigtop Data Generators? Currently, the data generators are used in the BigPetStore examples but also for some Kubernetes examples. We could share in the maintenance (and vice versa), and I

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user c0s commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175423087 The reason for the error is in the commit 347c2f2ec61f6a83e06c00c19d069acaf3a938b7 README.txt has been renamed to README.md --- If your project is set up for it,

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user c0s commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175426108 Looks like bigtop CI is busy with nightly build, but I have kicked off mahout build here

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user andrewmusselman commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175426166 Alright, adding the .md version to the SPEC for now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user c0s commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175425691 The deb build is using logic encoded in install_mahout.sh - and that works. We can improve this separately (hint: open a JIRA for that ;) --- If your project is set up for

Re: HiBench as part of Bigtop

it depends in part of how you position HiBench. Ie, does it make sense to make it part of the deployable stack and be able to install it on a node to benchmark the whole cluster? Or there is a different deployment scenario you have in mind? Cos On Wed, Jan 27, 2016 at 03:45AM, Cheng, Hao wrote:

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user andrewmusselman commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175424061 Good catch; strange it's not a problem with the deb build though. I'll fix it. --- If your project is set up for it, you can reply to this email and have your

[GitHub] bigtop pull request: BIGTOP-2180: Add smoke-test scripts using gra...

GitHub user yeongeon opened a pull request: https://github.com/apache/bigtop/pull/76 BIGTOP-2180: Add smoke-test scripts using gradle for Apache Tajo. It's a new PR that is separated from BIGTOP-2179. You can merge this pull request into a Git repository by running: $ git pull

Re: HiBench as part of Bigtop

My personal view would be to start with adding packages. Then send an email to the dev@ list to open a separate discussion. On Tue, Jan 26, 2016 at 9:45 PM, Cheng, Hao wrote: > Which way does the community prefer? Just for packaging or the put entire > project into bigtop?

Re: HiBench as part of Bigtop

If hibench can run as a gradle task that would be far more useful to the typical audience IMO and less technical debt to carry .I think the amount of boilerplate for a package only is justified if it's a distributed component. > On Jan 26, 2016, at 11:03 PM, RJ Nowling

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user andrewmusselman commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175415108 I had a successful local build via: `$ sudo docker run --rm -v `pwd`:/ws --workdir /ws bigtop/slaves:trunk-centos-7 bash -l -c './gradlew --stacktrace

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user andrewmusselman commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175421593 I can reproduce the error with mahout 0.11.1 and do not get the error with 0.11.0 so this does look like a regression. --- If your project is set up for it, you

Re: Introducing myself and adding QFS

Oh, if I made you uncomfortable, you know I didn't mean that :) I just want to know more about the design because I'm always interested in the architecture things, especially when I see something different. Even Spark just added HA in their master in recent release last year. So it's totally

Re: Introducing myself and adding QFS

On Wed, Jan 27, 2016 at 01:05AM, Evans Ye wrote: > Oh, if I made you uncomfortable, you know I didn't mean that :) Oh believe me - it takes a lot more than that to make me uncomfortable ;) Besides, you gave me an opportunity to speak up about the SPOFs in the Hadoop ecosystem. Which I can do for

Re: Introducing myself and adding QFS

Please add Your name to the MAINTAINERS.txt file in the PR for "QFS" ! On Tue, Jan 26, 2016 at 2:24 PM, Konstantin Boudnik wrote: > On Wed, Jan 27, 2016 at 01:05AM, Evans Ye wrote: > > Oh, if I made you uncomfortable, you know I didn't mean that :) > > Oh believe me - it takes

[jira] [Created] (BIGTOP-2282) Define Bigtop 1.next (1.1.1 or 1.2) release BOM

Konstantin Boudnik created BIGTOP-2282: -- Summary: Define Bigtop 1.next (1.1.1 or 1.2) release BOM Key: BIGTOP-2282 URL: https://issues.apache.org/jira/browse/BIGTOP-2282 Project: Bigtop

Re: Spark dependency issues (BIGTOP-2154)

On Sun, Jan 24, 2016 at 08:03PM, Evans Ye wrote: > Oh, yes. I confused myself,... Should be /usr/lib...sorry! > > For that hive thing, I mean, if we can't have a proper working spark env > w/o datanucleus, we can only accept it and put them together even though I > don't use hive. This should be

[jira] [Created] (BIGTOP-2283) QFS Integration

Faraaz Sareshwala created BIGTOP-2283: - Summary: QFS Integration Key: BIGTOP-2283 URL: https://issues.apache.org/jira/browse/BIGTOP-2283 Project: Bigtop Issue Type: New Feature

Re: Introducing myself and adding QFS

Thanks for the warm welcome guys :). I agree that smaller patches will be easier to parse and review. Right now, I have Debian and RPM packaging complete. I have created a JIRA ticket (https://issues.apache.org/jira/browse/BIGTOP-2283) which I will use to track the integration. I’ll start

[jira] [Created] (BIGTOP-2284) Update getting started docs for adding new components

Nate DAmico created BIGTOP-2284: --- Summary: Update getting started docs for adding new components Key: BIGTOP-2284 URL: https://issues.apache.org/jira/browse/BIGTOP-2284 Project: Bigtop Issue

docs, getting started, ux of bigtop contribs

Hey Bigtoppers, With a little flurry of new activity to kick off 2016, think we can use this as push to gather notes and new docs on the process to look towards continual improvement of the process of new folks adding their perspective component. I will try to keep pulse of the latest

[jira] [Created] (BIGTOP-2285) Add QFS packages

Faraaz Sareshwala created BIGTOP-2285: - Summary: Add QFS packages Key: BIGTOP-2285 URL: https://issues.apache.org/jira/browse/BIGTOP-2285 Project: Bigtop Issue Type: Sub-task

RE: [ANNOUNCE] New Bigtop PMC member Nate D'Amico

Thanks for the invite and warm welcome. Looking forward to 2016 and helping out the community wherever I can From: Andrew Purtell [mailto:apurt...@apache.org] Sent: Monday, January 25, 2016 1:01 PM To: dev@bigtop.apache.org; u...@bigtop.apache.org Subject: [ANNOUNCE] New Bigtop PMC

[jira] [Created] (BIGTOP-2286) Fedora22-ppc64le: Hadoop build fails

Amir Sanjar created BIGTOP-2286: --- Summary: Fedora22-ppc64le: Hadoop build fails Key: BIGTOP-2286 URL: https://issues.apache.org/jira/browse/BIGTOP-2286 Project: Bigtop Issue Type: Bug

Re: docs, getting started, ux of bigtop contribs

Having a wiki page or something to explain the process would be mostly helpful. Somehow we haven't ever put an effort into doing such a thing, although over the years we had people asking about it all the time. Even if there's a simple seed page outlining just an overall requirements, we can

Re: docs, getting started, ux of bigtop contribs

I say: How bout a contributing.md file in the top of the repo? > On Jan 26, 2016, at 4:57 PM, Konstantin Boudnik wrote: > > Having a wiki page or something to explain the process would be mostly > helpful. Somehow we haven't ever put an effort into doing such a thing, >

Re: docs, getting started, ux of bigtop contribs

Ah, that's way better idea! On Tue, Jan 26, 2016 at 07:17PM, Jay Vyas wrote: > I say: How bout a contributing.md file in the top of the repo? > > > On Jan 26, 2016, at 4:57 PM, Konstantin Boudnik wrote: > > > > Having a wiki page or something to explain the process would be

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

GitHub user andrewmusselman opened a pull request: https://github.com/apache/bigtop/pull/75 BIGTOP-2119: Bump Mahout version to 0.11.1 Updated mahout version in bigtop.bom, built mahout-pkg, installed .deb, and ran a recommender job as well as checked the spark-shell works. You

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user c0s commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175329074 Hey Andrew, thanks! What about some of the missing files in the package you've mentioned on the dev@ or JIRA? Is this issue gone away somehow? --- If your project is set up

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user andrewmusselman commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175330146 All cleared up, those were just not in 0.11.0. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user andrewmusselman commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175330871 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 does not have this

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user c0s commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175330720 Ah, makes sense. The patch looks good to me. +1 and I will run the build as well before pushing this into the master. Thanks! --- If your project is set up for it, you

[GitHub] bigtop pull request: BIGTOP-2119: Bump Mahout version to 0.11.1

Github user c0s commented on the pull request: https://github.com/apache/bigtop/pull/75#issuecomment-175334984 Unfortunately, the rpm build failed

Re: Introducing myself and adding QFS

Hi Faraaz, Is there someone who would be willing to take responsibility for maintaining the Apache Apex packages in Bigtop? We generally like to find a maintainer for each package and add them to our maintainers list. This way we know who to contact if a build fails and blocks a release. If

Re: HiBench as part of Bigtop

Hi Hao, Are you interested in just packaging HiBench in Bigtop or contributing the entire project to Bigtop? Is there someone who would be willing to take responsibility for maintenance? We generally like to find a maintainer for each package and add them to our maintainers list. This way we

Re: Introducing myself and adding QFS

Oops... meant QFS, not Apache Apex. Sorry! But the question about having a maintainer still stands. :) On Tue, Jan 26, 2016 at 9:02 PM, RJ Nowling wrote: > Hi Faraaz, > > Is there someone who would be willing to take responsibility for > maintaining the Apache Apex

Maintainers list

Hi all, I sent follows up to the three groups who contacted us about contributing new packages to bring up the importance of finding a maintainer for components. I suggest that we keep the maintainers file maintained so that we know who to turn to when the release is blocked. :) RJ

RE: HiBench as part of Bigtop

Hi RJ, Currently, we are targeting packaging the HiBench in Bigtop; but is there any other subproject entirely be part of BigTop? Thanks, Hao -Original Message- From: RJ Nowling [mailto:rnowl...@gmail.com] Sent: Wednesday, January 27, 2016 11:04 AM To: dev@bigtop.apache.org Subject:

Re: Apache Apex as part of Bigtop

Hi RJ, Yes, we are going to nominate a maintainer and will ensure Apex related build issues will be resolved. Thanks, Thomas On Tue, Jan 26, 2016 at 7:00 PM, RJ Nowling wrote: > Hi Thomas, > > Is there someone who would be willing to take responsibility for > maintaining

Re: HiBench as part of Bigtop

A few of us have been working on BigPetStore, a family of example applications (blueprints). We've also been working on data generators to create relatively complex fake data for those demo apps. On Tue, Jan 26, 2016 at 9:10 PM, Cheng, Hao wrote: > Hi RJ, > > Currently, we

Re: Apache Apex as part of Bigtop

Great, thanks! When you create the patches, please add that person to our MAINTAINERS file as part of the patch. On Tue, Jan 26, 2016 at 9:21 PM, Thomas Weise wrote: > Hi RJ, > > Yes, we are going to nominate a maintainer and will ensure Apex related > build issues will be