Hi young woo - if you want to make the JIRA and other aspects of how we will
formalize the messaging and transformation strategy, that will be awesome .
No prob cos, thanks for the support - ya let’s sync up about it in apachecon
> On Aug 30, 2019, at 2:54 AM, Konstantin Boudnik wrote:
>
+1 on both counts. Perhaps 'branch-1.x' would be informative.
Also, let's wait a couple of days to let others on the list to express their
opinion, perhaps different and/or complimentary.
And Jay - thanks for sharing your work: I owe you a look into this, but life
last month wasn't overly relaxed
Sounds great!
I like the idea that reshaping big data architecture at cloud native
deployments.
What about creating 'branch-1' from current status for existing users and
traditional architectures? So, we can make progress from master branch for
the future Bigtop releases.
Jay,
I feel like we
Here’s where I’m at .
https://github.com/jayunit100/apachecon-2019-bigtop3x/
It’s a lot easier then packaging all this stuff, but for most people will
accomplish a similar end goal ( a big Data cloud in a box) and mostly a
matter of curation of charts and images, and integration testing
Super +1 for Bigtop 2.0 with modern components and K8S support! I cannot
wait to see Bigtop running on K8S...
So can someone help to create a branch-2.0 now? :P
Konstantin Boudnik 于2019年8月30日周五 上午2:24写道：
> Aah, k8s - thanks Jay!
>
> BTW, I believe we can do this in a less formal stuff (ie no
Aah, k8s - thanks Jay!
BTW, I believe we can do this in a less formal stuff (ie no VOTE): we have a
discussion going on the version of Bigtop. How about we make it 2.0 and trim
the BOM into the needed shape and form? If there's enough drive in the
community to continue with 1.x line (1.4 and so
I'm super +1 with 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 on the previous feedback that a drop of supporting
component should be
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
I am not sure about Giraph, Tajo and some others, but Sqoop seems to be user
around by people. So, if it isn't much of the burden for us - and it seems
pretty stable at the moment - I'd leave it.
What I would think would makes sense to spend some of our efforts on is on
adding modern tooling like
Hi, folks,
I went through current components Bigtop is supporting, and I noticed that
these upstream projects haven't been released for quite a while:
Apache Tajo:
last release: release-0.11.3-rc0, May 11, 2016
Apache Apex:
last release: v3.7.0, Apr 27, 2018
Apache Giraph:
last
10 matches
Mail list logo
