Likewise thanks Kengo !
> On Apr 19, 2020, at 1:54 AM, Konstantin Boudnik wrote:
>
> Great to have you on board!
>
>> On 2020-04-18 02:05, Olaf Flebbe wrote:
>> On behalf of the Apache Bigtop Project Management Committee, I am pleased
>> to announce that Kengo Seki has accepted our invitation
Likewise everyone .
Let’s get together soon.
Sent from my iPhone
> On Dec 31, 2019, at 2:48 PM, Konstantin Boudnik wrote:
>
> Happy New Year, yall! It is great to see this project coming to its 10th year
> being strong as ever and innovative as always!
>
> This group is great and it feels
, that's OK One day, we
>>>> can reduce serious rebase work to merge 'cnb' into master.
>>>>
>>>> At this point, we need a concrete architecture as a cloud native
>>>> distribution or product. feel free to let us know your thoughts.
>>>>
>>>&
n the domain so I believe you can shed lights on
> our journey!
>
> Thanks,
> Youngwoo
>
>> On Thu, Nov 7, 2019 at 6:01 AM Jay Vyas wrote:
>> Hi Eric long time no see :) anyways YoungWoo and Evans Ye, and I believe
>> others are hacking on it now. Are there
Hi Eric long time no see :) anyways YoungWoo and Evans Ye, and I believe
others are hacking on it now. Are there yaml artifacts available for Eric to
try out?
Eric in the meantime if you want to try looking at the motivation you can check
out my original proposal
projects.
Again these are just my thoughts - your driving it so - any k8s solution is
gonna be light years ahead of what we have now, so im very supportive
either way !
--
jay vyas
Hi folks! It’s more of a benchmark tool with barebones opinionated kafka
installation.
I think the benchmarks can be easily rewritten for bigtop - just use BpS.
Otherwise you’ll have a circular dependency .
>
> On Oct 14, 2019, at 10:02 AM, YoungWoo Kim (Jira) wrote:
>
>
> [
>
> and also created the branch 'cnb'
> https://gitbox.apache.org/repos/asf?p=bigtop.git;a=shortlog;h=refs/heads/cnb
>
> @Jay,
> Please push your work into 'cnb' branch and then, let's find out what we
> can improve.
>
> Thanks,
> Youngwoo
>
> On Fri, Sep 20, 2019 at 8:39 P
?
>>>>
>>>> As a distribution for big data and analytics, it would be nice to have
>>> such
>>>> components(already... there are nice projects in ASF :-)):
>>>> - Jupyter Notebook and jupyterhub
>>>> - More choices on str
gt;
>> I'm proposing a new branch for **incubating** cloud-native distribution
>> which is based on Jay's ground work!
>>
>> What do you think?
>>
>> Thanks,
>> Youngwoo
>>
>> 1. https://github.com/kubernetes-sigs/kubespray
>>
>>
> - and more...
>
> WDYT?
>
> Thanks,
> Youngwoo
>
> On Sun, Sep 15, 2019 at 2:07 AM jay vyas
> wrote:
>
>> Hi everyone !
>>
>> The contents for this that were finally presented are here...
>> https://github.com/jayunit100/apachecon-2019-b
Hi everyone !
The contents for this that were finally presented are here...
https://github.com/jayunit100/apachecon-2019-bigtop3x
and the video is here ! https://youtu.be/LUCE63qPMyM
Let us know what you think
On Thu, Sep 12, 2019 at 4:35 PM jay vyas
wrote:
> hi folks, am in the confere
ge :)
>
> --
> Cos
>
>
> On Wed, Sep 04, 2019 at 05:54AM, Jay Vyas wrote:
> > Hi folks. Couple of updateys in the next gen brainstorming we’ve been
> doing...
> >
> > Sid Mani from minio is going to copresent with me at our bigtop talk at
> > apac
Hi folks. Couple of updateys in the next gen brainstorming we’ve been doing...
Sid Mani from minio is going to copresent with me at our bigtop talk at
apachecon next week, around the internals of minio integrations etc.
Spoke with cos and sounds like we definetly have a quorum for hacking
th K8S stuff and the core components idea!
>>>>>
>>>>> I'm with Cos and Jun. Removing those stuffs can ease our CI resource
>>>>> utilization and yield more stable CI results. This is what I'm thinking
>>>> how
>>>>> to proceed based
gt;>
>>> 1. Spin up a vote to drop project XXX (if confident enough, put multiple
>>> components here)
>>> 2. If +3 binding votes with no -1 votes, it passes.
>>> 3. Put up the PR for code removing
>>> 4. Refine our CI settings (I can definitely h
First of all I’m all for dropping the old stuff.
1) My opinion - to further cos point - I think people running old stuff don’t
really need version updates, or if they do, they don’t constitute a large
audience , or should contribute them ok their own.
2) surprise surprise :):) here’s my k8s
Hey folks !
On my end if anyone wants to hack on something,
happy to collaborate around my talk as well. The goal is to define what a
cloud native bigtop would focus on.
Right now I’m looking at minio, and rook operator as storage level
implementations alongside presto, Kafka, spark as a
rms (ppc64le, aarch64
> and amd64). Local builders are deprecated since bigtop-1.2.
>
> Documented in confluence
> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+build+Bigtop-trunk
>
> What specifically are you missing?
>
> Olaf
>
>
>
>&g
Hi olaf- we do have containeirzed builders now, right? I might be wrong about
this, as I haven’t built full packages for bigtop in the last 12 months or so,
but I used to use docker... Am thinking we should update docs to reflect that
to build bigtop it’s easier to use our docker containers
Great work Evans .!.!.!
> On Jun 18, 2019, at 9:28 PM, Jun HE wrote:
>
> Great! Thanks Evans for your hard work.
>
> Evans Ye 于2019年6月19日周三 上午12:07写道:
>> On behalf of the Apache Bigtop team, I'd love to announce the general
>> availability of the Bigtop 1.4.0 release.
>>
>> The release is
Wow , yeah this is really sad to hear. Peter was a huge morale pillar in the
bigtop community and in others as well .
R.I.P and thanks to everyone. It would be nice if at some point we could send
something token to his family.
On that note I’ll be at the roadshow tomorrow, if anyone wants
+1
> On Feb 5, 2019, at 10:26 AM, Roman Shaposhnik wrote:
>
>> On Sun, Feb 3, 2019 at 12:05 PM Evans Ye wrote:
>>
>> Hi all,
>>
>> I'd like to propose a next minor release of Apache Bigtop, which is 1.3.1.
>>
>> Although Bigtop 1.3.0 was released back in Nov. 2018. It's a good sign for
>> a
others on this list, who want to be involved in open big data
related stuff, are interested in merging with another community.
On Tue, Jan 29, 2019 at 6:04 AM Evans Ye wrote:
> Hey Jay
> Just one more thing - can you explain what do you mean by the succesor of
> bigtop?
>
>
>
et me wrong. Kubeflow is a great direction. We just need to work on
> the details and see if there's a chance to establish a partnership.
>
> Evans
>
>
>
> Jay Vyas 於 2019年1月22日 週二 下午2:04寫道:
>
>> Hi folks !
>>
>> I’m going to propose another possible futur direc
Hi folks !
I’m going to propose another possible futur direction for bigtop - kubeflow
packaging and integration testing, and maybe even offering to bring it to the
asf.
As you know with hortonworks and cloudera merged, the outlook for innovation
supported by companies in the Hadoop
Hahah sorry. Meant to actually send this to Someone on the list :)... Gmail app
acting wonky.
> On Jan 4, 2019, at 8:52 AM, Jay Vyas wrote:
>
> Hey free to chat ?
>
>>> On Jul 22, 2014, at 12:04 PM, Konstantin Boudnik wrote:
>>>
>>> On July 22, 20
Hey free to chat ?
> On Jul 22, 2014, at 12:04 PM, Konstantin Boudnik wrote:
>
>> On July 22, 2014 6:08:11 AM PDT, jay vyas
>> wrote:
>> No prob cos.
>> Y
>> Now I'm getting curious : What is our take on passwordless SSH for
>> bigtop
>> hadoop
ps://lists.apache.org/thread.html/b3868092e86d3ffa3abec7f97dbc8272518c63e57232e5386c103f19@%3Cdev.bigtop.apache.org%3E
>
> Please vote by reply to this email until Sun., 6th of January 9pm CET
>
> +1: Let's move to gitbox early
> -1: Let's wait
> 0 : don't care
>
>
> Olaf Flebbe
>
>
>
--
jay vyas
ucing
> pkgs in helm what you proposed?
>
> Jay Vyas 於 2018年12月15日 週六 上午1:11寫道:
>
>> How about a Kubernetes native distribution :).
>>
>>> On Dec 14, 2018, at 11:53 AM, Evans Ye wrote:
>>>
>>> Hi all,
>>>
>>> We've just r
How about a Kubernetes native distribution :).
> On Dec 14, 2018, at 11:53 AM, Evans Ye wrote:
>
> Hi all,
>
> We've just released 1.3.0 back in Nov. 2018 with RM Jun He and the
> community's great help. Now it's time to look forward and setup a goal for
> the next stage. We've a doc
Congrats young woo!
Begin forwarded message:
> From: John Mertic
> Date: November 29, 2018 at 9:08:42 AM EST
> To: dev@bigtop.apache.org
> Subject: Re: [ANNOUNCE] YoungWoo Kim is now the chair of Apache Bigtop
> Reply-To: dev@bigtop.apache.org
>
> Congrats Youngwoo!
>
> I recall earlier in
Still not ready to go 100% containers ?:)
> On Nov 9, 2017, at 5:43 PM, Olaf Flebbe wrote:
>
> Hi Arnauld,
>
>> c via a -> use puppet repositories ? That way:
>
>> PRO: you're pretty sure to have _the_ version you want to support
>> PRO: available on every puppet supported
jay vyas created BIGTOP-2868:
Summary: Travis integration for Jar files.
Key: BIGTOP-2868
URL: https://issues.apache.org/jira/browse/BIGTOP-2868
Project: Bigtop
Issue Type: New Feature
If you guys finally decide to move to k8s then I can help get involved again.
I'm a k8s maintainer and my current company needs a Hadoop deployment that
supports containers
> On Jun 21, 2017, at 1:02 PM, Olaf Flebbe wrote:
>
> Hi Andrew,
>
> you surely are making jokes when
Yeah I'll help test to; thanks Guys, +1 new bucket
> On Mar 28, 2017, at 4:23 PM, Andrew Musselman
> wrote:
>
> We should have a mahout release tonight; what time tomorrow do you think
> you'll be making yours Roman?
>
>> On Tue, Mar 28, 2017 at 12:41 PM, Evans Ye
I can try and test this if we still have the dev tooling in place if the code
is finalized
> On Mar 19, 2017, at 6:29 AM, Olaf Flebbe wrote:
>
> Cos, thank you very much for your effort!
>
>> BIGTOP-2673
>
> I will work on this.
>
> Olaf
I think the more info the better, and making extra commits that are noisy is
ok. The priority is to keep big top and odp moving forward without making
extra work for ODPi for contributing :).
> On Mar 17, 2017, at 11:16 AM, Roman Shaposhnik wrote:
>
> Hi!
>
> as Evans
erized microsystem
environment.
--
jay vyas
Ditto !
> On Feb 28, 2017, at 11:33 PM, Roman Shaposhnik wrote:
>
> Many, many congratulations to Evans! And a big thank you to Olaf!
>
> Thanks,
> Roman.
>
>> On Tue, Feb 28, 2017 at 2:15 PM, 김영우 (YoungWoo Kim) wrote:
>> Congrats Evans & Thank you
t; HiBench code can be found at: https://github.com/intel-hadoop/HiBench
> >
> > Looking forward to your reply.
> >
> > Regards,
> > Hao
> >
> >
>
--
jay vyas
Why not CTR into a branch
And RTC in jira that promotes the branch to master?
That way process can continue and those interested can delay promotion to
master , without delaying other progress
> On Jan 17, 2017, at 12:08 PM, RJ Nowling wrote:
>
> I agree with Evans.
>
>
of Apache Bigtop
> with
> > > Juju. This enabled a whole set of
> > > >> improvements still waiting to be integrated.
> > > >>
> > > >> It's a pleasure to have him on board!
> > > >>
> > > >> Being a committer enables easier contribution to the project
> since
> > > there is no need
> > > >> to go via the patch submission process.A This should enable
> better
> > > productivity.
> > > >>
> > > >> Welcome and let the Source be with you!
> > > >>
> > > >> Olaf (on behalf of the ASF BigTop PMC)
> > >
>
--
jay vyas
Ditto!
> On Apr 20, 2016, at 10:49 PM, 김영우 (Youngwoo Kim) wrote:
>
> Congrats Olaf!
>
> Andrew,
> You did a great job. Thank you so much!
>
> Youngwoo
>
> 2016년 4월 21일 목요일, Andrew Purtell님이 작성한 메시지:
>> Please join me in congratulating Olaf Flebbe on
No route to host means I think that your TaskManager can't see Joanager.
Specifically 10.10.10.12 doesn't see 10.10.10.11.
... Next step confirm : Can you ping 10.10.10.11 from 10.10.10.12?
> On Apr 17, 2016, at 7:27 PM, Harshita Agrawal wrote:
>
> No route to host
>
Should be identical.
Where is your yum repo?
Can you ping the server hosting it from your open stack box ?
> On Apr 12, 2016, at 1:16 AM, Bhupendra Singh
> wrote:
>
> Hi,
>
> I am trying to deploy the bigtop with Flink component on an open-stack
> instance but it
t; process exited, code=exited status=3
> -- Subject: Unit flink-worker.service has failed
> -- Unit flink-worker.service has failed.
> Apr 12 01:21:30 bigtop1.vagrant systemd[1]: Unit flink-worker.service
> entered failed state.
> Apr 12 01:21:30 bigtop1.vagrant systemd[1]: f
akes sense to break this pull request into several
> > pull requests? For example, one for the packaging, one for the puppet
> > scripts, and another one for the smoke tests. That could make
> > reviewing of the changes easier and people could already try out
> > incremental changes. I'd be happy to help out with the packaging and
> > scripting.
> >
> > What do you think about that?
> >
> > Thanks,
> > Max
>
--
jay vyas
016, at 7:54 PM, Konstantin Boudnik <c...@apache.org> wrote:
>>>>
>>>> Olaf is complaining about GH-JIRA integration, which is crappy like
>> hell and I
>>>> whole-heartedly second this motion. Not a fun of GH however people are
>> using
>>>
Thanks again for this , don't apologize for the email.
We actually are excited about apex, thanks for this! We will get it reviewed
within the next couple of days I'm sure (I'll look some time after work if
nobody else gets to it first).
> On Feb 23, 2016, at 6:09 AM, Chinmay Kolhatkar
Cool;
Thanks guys for all the hard work.!.!.!.!.!.!.!.!.!.!.!.!.!.!
> On Feb 17, 2016, at 2:26 PM, Konstantin Boudnik wrote:
>
> Please help to spread the word
>
>https://twitter.com/ASFbigtop/status/72492617195520
>
> Thanks,
> Cos
>
>> On Wed, Feb 17, 2016 at
Yeah glad you guys joined the mailing list :). Looking forward to it!
> On Feb 10, 2016, at 3:44 PM, Konstantin Boudnik wrote:
>
> Great, thanks for your interest and contributions! Don't hesitate to
> communicate with the rest of the community either on the JIRA or here on the
Thanks Olaf !
> On Feb 9, 2016, at 5:15 PM, Olaf Flebbe wrote:
>
> Pfff this was tough
>
> https://ci.bigtop.apache.org is running now !!!
>
> I have to go to bed now. Short intro:
>
> Apache reverse proxy config for jenkins in /etc/httpd/conf.d/ssl.conf
> Certificates
Maven is building jar files...
Shouldn't those "just work" on powers JVM the way any jar would?
> On Jan 27, 2016, at 11:05 PM, MrAsanjar . wrote:
>
> Does the artifacts in maven "*local*" repository remain persistent between
> bigtop component builds (i.e. Hadoop, Spark,
Check how we do it in vagrant-deploy/vm.
The puppet commands are run by vagrant, you can see the exact commands in the
Vagrantfile, and in the vagrant logs
> On Jan 27, 2016, at 8:30 AM, YEONGEON wrote:
>
> Dear Bigtop devs.
>
> I have been interested in the project of
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
in 2 minutes. That's why if you're an admin for a
> production critical cluster you'll get paged immediately. Perhaps 3
> o'clock in
> the morning.
>
> I spent last three years working on the active-active software for mission
> critical systems, so I would love to share some arch
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,
>
Awesome! It's great to hear about another HDFS alternative :)
, We tried pretty hard to make bigtop more "HCFS" compliant, by adding the init
hcfs tooling and so on, but never completed making the puppet recipes add
support for other file systems.
Would be very interesting to see if the
Way to go Nate. Keep up the hard work of showing people our unique way of
running Hadoop!
> On Jan 25, 2016, at 4:00 PM, Andrew Purtell wrote:
>
> On behalf of the Apache Bigtop Project Management Committee, I am pleased
> to announce that Nate D'Amico has accepted our
Ah the vm smoke tests wrapper and maybe others expected that path to stay the
same .
I guess we will have to patch these on a case by case basis.
Thanks for noting cos.
> On Jan 14, 2016, at 11:24 PM, Konstantin Boudnik wrote:
>
> Hey guys.
>
> Looks like moving the
t; On Thu, Jan 7, 2016 at 1:13 PM, Konstantin Boudnik <c...@apache.org>
> wrote:
> >> Yeah, same here - Roman seems to be married to this thing (don't tell
> his
> >> wife!), so let him chime in. And then we can chope it off if noone
> signs up to
> >> mainta
NFO] Compiling 706 source files to
> /ws/build/giraph/rpm/BUILD/giraph-1.1.0/giraph-core/target/classes
> [INFO] Compiling 706 source files to
> /ws/build/giraph/rpm/BUILD/giraph-1.1.0/giraph-core/target/classes
> [INFO] Compiling 706 source files to
> /ws/build/giraph/rpm/BUILD/giraph-1.1.0/giraph-core/target/classes
>
>
>
>
> Olaf
>
>
>
--
jay vyas
1) Agree we can move to docker native solutions. Of course, this makes it
impossible to test the bare metal deployments that some folks still care about.
Otto also seems promising, it's ec2 native
Now, If we think docker is better for testing, then relying on OS specific VMs,
maybe that's
Makes sense. I think it's common to have to use these one off scripts when
dealing with Jenkins and daily build products and so on.
Another project I'm working on has a hack/ directory for stuff like this that
can be easily commited into, for sharing these sorts of one off tasks.
Maybe we
Deploy images? I thought we killed all the deploy images entirely since (1)
boxgrinder died off, and nobody had the packer expertise to redo everything and
(2) the vagrant deployer worked effectively for anyone wanting to do a quick
test.
> On Dec 26, 2015, at 7:21 PM, Konstantin Boudnik
ctually forked from branch-0.7 and
> > have added couple of hive tests. Now we wanted to contribute back to
> > bigtop.
> >
> > But in the latest master branch, i found that hive module itself is not
> > present so wanted to know
> > the placeholder to add the new hive tests in BIGTOP.
> >
> > Regards,
> > Srinivas.
> >
>
--
jay vyas
Ditto thanks Evans!
Like Andy said we will need to follow up w passwords for the PMC.
I don't know the "right" way to encrypt files, but I can hack a first pass
together for review, unless someone else wants to try?
> On Dec 13, 2015, at 12:25 PM, Konstantin Boudnik
t; unfortunately the docker daemon on docker-slave-06 is unresponsive , so I
> decided to disable bigtop-trunk-packages-nexus-start
>
> If someone with a root passwd please reboot the docker-slave-06 node and
> enable bigtop-trunk-packages-nexus-start ...
>
> Olaf
>
--
jay vyas
I love the talk thanks for submitting Evans
Very relevant to my current work.
> On Nov 25, 2015, at 1:06 PM, Evans Ye wrote:
>
> Hi all,
>
> I've submitted a talk to Hadoop Summit
> Apache Bigtop: Using Docker to Build, Test, and Run your Customized Big
> Data Platform
>
jay vyas created BIGTOP-2161:
Summary: [bigpetstore] transaction-queue Implment/Brainstorm ideas
for global data rate.
Key: BIGTOP-2161
URL: https://issues.apache.org/jira/browse/BIGTOP-2161
Project
+1
> On Nov 21, 2015, at 2:34 PM, Konstantin Boudnik wrote:
>
> Using CTR for the Bigtop project has been discussed, experimented for a few
> months, and discussed again on this long thread [1] for alomost a year now.
> The
> consensus seems to be reached, but because this is
other things this and next week, so I cannot contribute right now.
>
> -Olaf
>
>
--
jay vyas
I think we all put our public keys in the jira issue for sharing public keys,
right? Sorry I forgot the issue number and am in transit at the moment
> On Oct 29, 2015, at 3:21 AM, Evans Ye wrote:
>
> Hey, Cos
>
> Please send me your public key so that I can grant
Cool! Thanks evans. Keep us posted...
> On Oct 16, 2015, at 12:31 PM, RJ Nowling wrote:
>
> Thanks, Evans!
>
>> On Fri, Oct 16, 2015 at 11:17 AM, Evans Ye wrote:
>>
>> Hi all,
>>
>> I write this to avoid someone is not getting what's going on right
Ssounds awesome. Lot of good will I found around bigtop at strata this time,
especially emerging non-Hadoop projects wanting to package and deploy using our
machinery.
> On Oct 1, 2015, at 10:31 AM, Konstantin Boudnik wrote:
>
> It was super-great to finally meet you guys!
They had become obsolete and the hive stuff was changing , and the hive
community wasn't interested in maintaining them so we moved them to smoke tests.
Feel free to incrementally add them back if you'd like to use them!, or else,
add on to smoke-tests, which you can just run as groovy
I think we can delete cloudera instances. But not sure
Thank you guys for all the infra donations all these years!
Cos/Evans please confirm *
> On Sep 24, 2015, at 2:25 PM, Sean Mackrory wrote:
>
> All,
>
> I was just asked by some folks at Cloudera
jay vyas created BIGTOP-2067:
Summary: Dockerfile should build transaction-queue from zero
Key: BIGTOP-2067
URL: https://issues.apache.org/jira/browse/BIGTOP-2067
Project: Bigtop
Issue Type: Bug
Thanks Evans. I like your idea of separate Bigtop artifacts stored somewhere...
If Bigtop can publish its own jars to its own nexus (or else to upstream
apaches maven server) that is ideal I guess!
> On Sep 21, 2015, at 4:19 AM, Evans Ye wrote:
>
> Hi all !
>
> I spent
Welcom and thanks for all the data generation framework stuff and general
stewardship.
looking forward to more awesome ideas
> On Sep 16, 2015, at 2:56 PM, Konstantin Boudnik wrote:
>
> Welcome dude! Keep 'em coming! ;)
>
>> On Wed, Sep 16, 2015 at 11:35AM, Andrew Purtell
i think we moved this discussion here
https://issues.apache.org/jira/browse/BIGTOP-1249
The goal is definetely to get automated reviews.
we hacked around successfully with some prototypes but never productionized
them.
Sounds good to me: the roles are definitely the way to go.
1) I suggest keeping json , but won't turn down a patch that updates to yaml so
long as docs are fixed accordingly as well to. This might not be worth it
though.
2) Init-Hdfs.sh should overtime be deleted and replaced with pure hcfs
discretion. Try to wait long enough if a volunteer wants to show up and
>> do a
>>>> review. - We have an informal consensus practice where as long as the
>>>> change doesn't have major impact (again, committer discretion) then
>> after an
>>>> issue s
Yes thanks cos for getting this centos stuff figured out.!
> On Sep 3, 2015, at 12:35 PM, Andrew Purtell wrote:
>
> Thanks for sticking with it Cos. That's an annoying bug.
>
>
>> On Wed, Sep 2, 2015 at 9:31 PM, Konstantin Boudnik wrote:
>>
>> Ok, as I
jay vyas created BIGTOP-2006:
Summary: Migrate the dang web resources from SVN 100% to git.
Key: BIGTOP-2006
URL: https://issues.apache.org/jira/browse/BIGTOP-2006
Project: Bigtop
Issue Type
Yup and this file is commit without review so super easy to maintain :)
> On Sep 2, 2015, at 10:09 PM, RJ Nowling wrote:
>
> Hi all,
>
> When I created a patch to add Jay and myself as maintainers of BigPetStore
> and the data generators, I found a number of components
top/bigtop-data-gen --scheme weather --size 5GB --output
> > > data-dir --etc foo --etc bar --daemon
> > > 2015年8月31日 下午9:06於 "RJ Nowling" <rnowl...@gmail.com>寫道:
> > >
> > >> The BigPetStore, Bazaar, and weather data generators have
>
:
>
> Could picture at some point supporting something like this for non-jvm folk
> just looking for test/demo data:
>
> apt-get install bigtop-data-gen
> ~/ $ bigtop-data-gen --scheme weather --size 5GB --output data-dir --etc foo
> --etc bar
>
>
>
>
generators in Bigtop.
But please do not include it in bigtop_utils, since this package is
mandatory. Not everyone needs a data generator .
Yup. And let's move further design discussion to the JIRA!
Olaf
Am 26.08.2015 um 11:25 schrieb Jay Vyas jayunit100.apa...@gmail.com
:
Publishing
Publishing the jar to bigtops maven is probably a good first step ,Then apps
can just include it as needed...?.
I'm not against packaging if someone wants packages for this. Maybe even
include it in bigtop util ?
Let's move to jira,
On Aug 25, 2015, at 9:41 PM, Konstantin Boudnik
for booth preferences and potentially in BigPetStore for customer item
preferences
Most of these libraries came out of the BigPetStore data generator but the
other generators have been refactored to be based off the standard set of
libraries.
--
jay vyas
Hi srivinas.
Sounds great; If you're going to be long term investing in bigtop, then Maybe
before submitting the ten new patches for tests, you're folks can help us out
converging the two test frameworks as a first step?
https://issues.apache.org/jira/BIGTOP-1608
Then it will be easy to add
(Bigtop 1.0.0 RM)
--
jay vyas
, Konstantin Boudnik c...@apache.org wrote:
The vote has passed with 8 +1 (7 binding); and 0 -1's or 0's. Here's the
tally
Evans Ye+1
Sean Mackrory +1
Roman Shaposhnik+1
Youngwoo Kim+1 (non-binding)
Olaf Flebbe +1
jay vyas+1
Andrew Purtell +1
guys if we need the
manpower.
And of course Thanks everyone for the hard work so far on this release !
--
jay vyas
not have
any
licensing issues. When in doubt refer to
https://www.apache.org/licenses/
I think patch reviewers need to check the correctness of the license
headers
as a part of their review routine..
Regards,
Cos
--
jay vyas
+1 vagrant and bigpetstore parts, , looks good !
On Mon, Aug 10, 2015 at 5:39 AM, Olaf Flebbe o...@oflebbe.de wrote:
+1: Verified debian rebuild, git Tag
--
jay vyas
jay vyas created BIGTOP-1961:
Summary: update bps spark to use only datagenerators from bigtop.
Key: BIGTOP-1961
URL: https://issues.apache.org/jira/browse/BIGTOP-1961
Project: Bigtop
Issue Type
Thanks Sean.
Thankfully we don't release binaries under ASF but at the same time we do have
convenience artifacts, and I guess building hbase rpms and hosting em is
something we need to think about for this upcoming release.?
On Aug 4, 2015, at 8:39 PM, Sean Busbey bus...@cloudera.com wrote:
1 - 100 of 2109 matches
Mail list logo