You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Ryan Blue <rb...@netflix.com.INVALID> on 2018/11/05 18:03:43 UTC
[DISCUSS] Iceberg proposal for incubation
Hi everyone,
I'd like to start a discussion about moving Netflix's Iceberg project to
the incubator. Iceberg is a library and specification for tracking data
files that store table data in the big data ecosystem. Iceberg is designed
to guarantee snapshot isolation and improve on performance problems with
big data tables, especially when using S3 or another object store as the
source of truth.
We've written up an Iceberg proposal
<https://docs.google.com/document/d/1gRkXkIkEsupsBstv6h_6wwNixt3YhWKPSMuxkA-geV4/edit?usp=sharing>
in google docs. I can post it to the wiki as well if that's needed, but I
thought it may be easier to read and update after this discussion in docs.
The initial proposal is below. Thanks for taking a look!
*Iceberg ProposalAbstractIceberg is a new table format for storing large,
slow-moving tabular data. It is designed to improve on the de-facto
standard table layout built into Hive, Presto, and Spark.ProposalThe
purpose of Iceberg is to provide SQL-like tables that are backed by large
sets of data files. Iceberg is similar to the Hive table layout, the
de-facto standard structure used to track files in a table, but provides
additional guarantees and performance optimizations: - Atomicity - Each
change to the table is will be complete or will fail. “Do or do not. There
is no try.”- Snapshot isolation - Reads use one and only one snapshot of a
table at some time without holding a lock.- Safe schema evolution - A
table’s schema can change in well-defined ways, without breaking older data
files.- Column projection - An engine may request a subset of the available
columns, including nested fields.- Predicate pushdown - An engine can push
filters into read planning to improve performance using partition data and
file-level statistics.Iceberg does NOT define a new file format. All data
is stored in Avro, ORC, or Parquet files.Additionally, Iceberg is designed
to work well when data files are stored in cloud blob stores, even when
those systems provide weaker guarantees than a file system, including: -
Eventual consistency in the namespace- High latency for directory listings-
No renames of objects- No folder hierarchyRationaleInitial benchmarks show
dramatic improvements in query planning. For example, in Netflix’s Atlas
use case, which stores time-series metrics from Netflix runtime systems and
1 month is stored across 2.7 million files in 2,688 partitions: - Hive
table using Parquet:- 400k+ splits, not combined- Explain query: 9.6
minutes wall time (planning only)- Iceberg table with partition filtering:-
15,218 splits, combined- Planning: 10 seconds- Query wall time: 13 minutes-
Iceberg table with partition and min/max filtering:- 412 splits- Planning:
25 seconds- Query wall time: 42 secondsThese performance gains combined
with the cross-engine compatibility are a very compelling story.Initial
GoalsThe initial goal will be to move the existing codebase to Apache and
integrate with the Apache development process and infrastructure. A primary
goal of incubation will be to grow and diversify the Iceberg community. We
are well aware that the project community is largely comprised of
individuals from a single company. We aim to change that during
incubation.Current StatusAs previously mentioned, Iceberg is under active
development at Netflix, and is being used in processing large volumes of
data in Amazon EC2.MeritocracyWe value meritocracy and we understand that
it is the basis for an open community that encourages multiple companies
and individuals to contribute and be invested in the project’s future. We
will encourage and monitor participation and make sure to extend privileges
and responsibilities to all contributors.CommunityIceberg is currently
being used by developers at Netflix and a growing number of users are
actively using it in production environments. Iceberg has received
contributions from developers working at Hortonworks, WeWork, and Palantir.
By bringing Iceberg to Apache we aim to assure current and future
contributors that the Iceberg community is meritocratic and open, in order
to broaden and diversity the user and developer community.Core
DevelopersIceberg was initially developed at Netflix and is under active
development. We believe Netflix will be of interest to a broad range of
users and developers and that incubating the project at the ASF will help
us build a diverse, sustainable community.AlignmentIceberg utilizes other
Apache projects such as Avro, Hadoop, Hive, ORC, Parquet, Pig, and Spark.
We anticipate integration with additional Apache projects as the Iceberg
community and interest in the project grows.Known RisksOrphaned
ProductsNetflix is committed to the future development of Iceberg and
understands that graduation to a TLP, while preferable, is not the only
positive outcome of incubation.Should the Iceberg project be accepted by
the Incubator, the prospective PPMC would be willing to agree to a target
incubation period of 2 years or less, knowing that every Incubator project
incurs a certain cost in terms of ASF infrastructure and volunteer
time.Inexperience with Open SourceThree of the initial committers are
Apache members and Incubator PMC members. They will work with the other
community members to teach them the Apache Way.Homogenous DevelopersThe
majority of the committers work at Netflix, though we are committed to
recruiting and developing additional committers from a wide spectrum of
industries and backgrounds.Reliance on Salaried DevelopersIt is expected
that Iceberg development will occur on both salaried time and on volunteer
time, after hours. Most of the initial committers are paid by Netflix to
contribute to this project. However, they are all passionate about the
project, and we are both confident and hopeful that the project will
continue even if no salaried developers contribute to the
project.Relationships with Other Apache ProductsAs mentioned in the
Rationale section, Iceberg utilizes a number of existing Apache projects
(Avro, Hadoop, Hive, ORC, Parquet, Pig, & Spark), and we expect that list
to expand as the community grows and diversifies. Any Apache project in the
big data space that needs to store or process tabular data would be
potentially relevant.A Excessive Fascination with the Apache BrandWe are
applying to the Incubator process because we think it is the next logical
step for the Iceberg project after open-sourcing the code. This proposal is
not for the purpose of generating publicity. Rather, we want to make sure
to create a very inclusive and meritocratic community, outside the umbrella
of a single company. Netflix has a long history of contributing to Apache
projects and the Iceberg developers and contributors understand the
implication of making it an Apache project.Required ResourcesMailing lists
- dev@iceberg.incubator.apache.org <de...@iceberg.incubator.apache.org>-
commits@iceberg.incubator.apache.org
<co...@iceberg.incubator.apache.org>-
private@iceberg.incubator.apache.org
<pr...@iceberg.incubator.apache.org>The podling may also create a user
mailing list, if needed.Source Control and Issue TrackingThe Iceberg
podling would use Apache’s gitbox integration to sync between github and
Apache infrastructure. The podling would use github issues and pull
requests for community engagement.Current Resources - Initial source:
github.com/Netflix/iceberg <https://github.com/Netflix/iceberg>- Java
documentation
<https://netflix.github.io/iceberg/current/javadoc/index.html?com/netflix/iceberg/package-summary.html>-
Table specification
<https://docs.google.com/document/d/1Q-zL5lSCle6NEEdyfiYsXYzX_Q8Qf0ctMyGBKslOswA/edit>Source
and Intellectual Property Submission PlanThe Iceberg source code in Github
is currently licensed under Apache License v2.0 and the copyright is
assigned to Netflix. If Iceberg becomes an Incubator project at the ASF,
Netflix will transfer the source code and trademark ownership to the Apache
Software Foundation via a Software Grant Agreement.External
DependenciesExternal dependencies licensed under Apache License 2.0 - Guava
https://github.com/google/guava <https://github.com/google/guava>- Jackson
https://github.com/FasterXML/jackson-core
<https://github.com/FasterXML/jackson-core>- Joda-Time
http://www.joda.org/joda-time/ <http://www.joda.org/joda-time/>External
dependencies licensed under the MIT License - SLF4J https://www.slf4j.org/
<https://www.slf4j.org/>- Mockito https://github.com/mockito/mockito
<https://github.com/mockito/mockito>ASF Projects - Apache Avro- Apache
Hadoop- Apache Hive- Apache ORC- Apache Parquet- Apache Pig- Apache
SparkCryptographyNot applicable.Initial Committers - Ryan Blue
blue@apache.org <bl...@apache.org>- Parth Brahmbhatt parth@apache.org
<pa...@apache.org>- Julien Le Dem julien@apache.org <ju...@apache.org>-
Owen O’Malley omalley@apache.org <om...@apache.org>- Daniel Weeks
dweeks@netflix.com <dw...@netflix.com>Sponsors - Champion and mentor: Owen
O’Malley omalley@apache.org <om...@apache.org>- Mentor: Ryan Blue
blue@apache.org <bl...@apache.org>- Mentor: Julien Le Dem julien@apache.org
<ju...@apache.org>Sponsoring Entity - The Apache Incubator*
--
Ryan Blue
Software Engineer
Netflix
Re: Some early stage questions
Posted by Luciano Resende <lu...@gmail.com>.
On Tue, Nov 6, 2018 at 12:05 PM Jacques Basaldúa <ja...@dybot.com> wrote:
>
>
> I have been working really hard on the documentation in the last two months and I am almost done. The current public documentation is very incomplete. Please, allow me to share it with you when I merge the new version, as mentioned, in less than two weeks.
>
Note that at Apache we value community over code, so it might be
better to evangelize/recruit some folks to use/work on your project
instead of trying to make it "complete/done".
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: Some early stage questions
Posted by Jacques Basaldúa <ja...@dybot.com>.
Hi Dave, Nick and everyone,
Thank you very much for the quick answer.
The original project was built by a team and released under an Apache License. As originally designed, it has no activity now. For the moment, I am alone in the pivoting the code released into a new idea. I am an original author. The updated public website will be in github + github pages very soon. In two weeks I have the first presentation at an event in Spain were I try to explain why it matters to me and that, of course, we need a community to make it happen. I will promote it in similar events: C++, R and Python Meetups in Madrid. My concern here is: 1. do I meet the requirements or should I wait for, say, one year, 2. how to present it to the ASF. Of course, I consider reaching the Apache Incubator the number one place to make the project visible and maximize the chance of success.
From what I understand from your replies: It is not impossible to submit a proposal for an incomplete project and neither is it a requirement to have a sponsor. The way to present it is: just share what I have and, if an ASF member wants to champion the project, then I will get advice on how to formalize a proposal for voting.
Is that correct?
I have been working really hard on the documentation in the last two months and I am almost done. The current public documentation is very incomplete. Please, allow me to share it with you when I merge the new version, as mentioned, in less than two weeks.
Thanks again,
Jacques.
-----Mensaje original-----
De: Nick Kew [mailto:niq@apache.org]
Enviado el: Monday, November 05, 2018 9:31 PM
Para: general@incubator.apache.org
Asunto: Re: Some early stage questions
> On 5 Nov 2018, at 19:31, Jacques Basaldúa <ja...@dybot.com> wrote:
>
> Hi everyone,
>
> I would like to formulate a proposal to the ASF incubator. After spending some time browsing the website, I still have a few novice questions I wish to share with you.
>
> 1. https://incubator.apache.org/guides/proposal.html states: "Before starting on the formal proposal, recruit a Champion.", how can I do that?
Ideally you know someone from Apache who has taken an interest in your project.
Or if it relates to an existing Apache project(s), that could be somewhere to look.
Failing that, try and interest someone here.
> 2. I don't have a sponsor. I have been dedicating almost 2000 hours in 2018 (on top of my day job) to this project started end of 2016. At that time, the project was developed in a corporation that open sourced it under an Apache License in Dec 2017. As I understand it, the incubator is about building (or failing to build) a community around a project. Does that meet your expectations?
It may do: it depends on your potential for building a community. Is your project visible -
e.g. public repos and website? Can you show evidence of public interest in it?
Your level of committment there might risk burnout in a few years!
> 3. The project is under refactoring to an ambitious long term goal. I do not have an MVP, but it has good documentation and software engineering practices including: unit testing, static and dynamic analysis tools, building automation, etc. I expect the jury and candidates to be comfortable with unfinished projects and decide on the vision and the code. Does that make sense or is it too early?
That would be matters for your project community.
> I think my questions should be common. If you agree, I volunteer to contribute the answers to the website to help others boarding on the incubator.
That's a Very Good Way to earn goodwill around here, if you come out of the process
with a clear vision for better docs.
--
Nick Kew
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
-----Mensaje original-----
De: Dave Fisher [mailto:dave2wave@comcast.net]
Enviado el: Monday, November 05, 2018 8:59 PM
Para: general@incubator.apache.org
Asunto: Re: Some early stage questions
Hi Jacques,
Welcome to the Apache Incubator.
> On Nov 5, 2018, at 11:31 AM, Jacques Basaldúa <ja...@dybot.com> wrote:
>
> Hi everyone,
>
> I would like to formulate a proposal to the ASF incubator. After spending some time browsing the website, I still have a few novice questions I wish to share with you.
>
> 1. https://incubator.apache.org/guides/proposal.html states: "Before starting on the formal proposal, recruit a Champion.", how can I do that?
Asking on this email list is one way to do it. A Champion will be someone who is an Apache Member and understands how to create the Proposal.
>
> 2. I don't have a sponsor. I have been dedicating almost 2000 hours in 2018 (on top of my day job) to this project started end of 2016. At that time, the project was developed in a corporation that open sourced it under an Apache License in Dec 2017. As I understand it, the incubator is about building (or failing to build) a community around a project. Does that meet your expectations?
Do you have others already working with you on your open source project? Incubation works best when there is an existing community involved in the code base.
Tell us about your project and where the code may be found.
> 3. The project is under refactoring to an ambitious long term goal. I do not have an MVP, but it has good documentation and software engineering practices including: unit testing, static and dynamic analysis tools, building automation, etc. I expect the jury and candidates to be comfortable with unfinished projects and decide on the vision and the code. Does that make sense or is it too early?
That all depends. The ASF does not provide technical guidance. The Apache Way emphasizes developing a sustainable Community along with Permissively Licensed software that can always be used for the public good.
>
> I think my questions should be common. If you agree, I volunteer to contribute the answers to the website to help others boarding on the incubator.
While I can agree that the documentation for the Incubator can be improved, let’s focus on your proposal first.
Regards,
Dave
>
> Thanks.
>
> Jacques Basaldúa
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Some early stage questions
Posted by Nick Kew <ni...@apache.org>.
> On 5 Nov 2018, at 19:31, Jacques Basaldúa <ja...@dybot.com> wrote:
>
> Hi everyone,
>
> I would like to formulate a proposal to the ASF incubator. After spending some time browsing the website, I still have a few novice questions I wish to share with you.
>
> 1. https://incubator.apache.org/guides/proposal.html states: "Before starting on the formal proposal, recruit a Champion.", how can I do that?
Ideally you know someone from Apache who has taken an interest in your project.
Or if it relates to an existing Apache project(s), that could be somewhere to look.
Failing that, try and interest someone here.
> 2. I don't have a sponsor. I have been dedicating almost 2000 hours in 2018 (on top of my day job) to this project started end of 2016. At that time, the project was developed in a corporation that open sourced it under an Apache License in Dec 2017. As I understand it, the incubator is about building (or failing to build) a community around a project. Does that meet your expectations?
It may do: it depends on your potential for building a community. Is your project visible -
e.g. public repos and website? Can you show evidence of public interest in it?
Your level of committment there might risk burnout in a few years!
> 3. The project is under refactoring to an ambitious long term goal. I do not have an MVP, but it has good documentation and software engineering practices including: unit testing, static and dynamic analysis tools, building automation, etc. I expect the jury and candidates to be comfortable with unfinished projects and decide on the vision and the code. Does that make sense or is it too early?
That would be matters for your project community.
> I think my questions should be common. If you agree, I volunteer to contribute the answers to the website to help others boarding on the incubator.
That's a Very Good Way to earn goodwill around here, if you come out of the process
with a clear vision for better docs.
--
Nick Kew
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Some early stage questions
Posted by Dave Fisher <da...@comcast.net>.
Hi Jacques,
Welcome to the Apache Incubator.
> On Nov 5, 2018, at 11:31 AM, Jacques Basaldúa <ja...@dybot.com> wrote:
>
> Hi everyone,
>
> I would like to formulate a proposal to the ASF incubator. After spending some time browsing the website, I still have a few novice questions I wish to share with you.
>
> 1. https://incubator.apache.org/guides/proposal.html states: "Before starting on the formal proposal, recruit a Champion.", how can I do that?
Asking on this email list is one way to do it. A Champion will be someone who is an Apache Member and understands how to create the Proposal.
>
> 2. I don't have a sponsor. I have been dedicating almost 2000 hours in 2018 (on top of my day job) to this project started end of 2016. At that time, the project was developed in a corporation that open sourced it under an Apache License in Dec 2017. As I understand it, the incubator is about building (or failing to build) a community around a project. Does that meet your expectations?
Do you have others already working with you on your open source project? Incubation works best when there is an existing community involved in the code base.
Tell us about your project and where the code may be found.
> 3. The project is under refactoring to an ambitious long term goal. I do not have an MVP, but it has good documentation and software engineering practices including: unit testing, static and dynamic analysis tools, building automation, etc. I expect the jury and candidates to be comfortable with unfinished projects and decide on the vision and the code. Does that make sense or is it too early?
That all depends. The ASF does not provide technical guidance. The Apache Way emphasizes developing a sustainable Community along with Permissively Licensed software that can always be used for the public good.
>
> I think my questions should be common. If you agree, I volunteer to contribute the answers to the website to help others boarding on the incubator.
While I can agree that the documentation for the Incubator can be improved, let’s focus on your proposal first.
Regards,
Dave
>
> Thanks.
>
> Jacques Basaldúa
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Some early stage questions
Posted by Jacques Basaldúa <ja...@dybot.com>.
Hi everyone,
I would like to formulate a proposal to the ASF incubator. After spending some time browsing the website, I still have a few novice questions I wish to share with you.
1. https://incubator.apache.org/guides/proposal.html states: "Before starting on the formal proposal, recruit a Champion.", how can I do that?
2. I don't have a sponsor. I have been dedicating almost 2000 hours in 2018 (on top of my day job) to this project started end of 2016. At that time, the project was developed in a corporation that open sourced it under an Apache License in Dec 2017. As I understand it, the incubator is about building (or failing to build) a community around a project. Does that meet your expectations?
3. The project is under refactoring to an ambitious long term goal. I do not have an MVP, but it has good documentation and software engineering practices including: unit testing, static and dynamic analysis tools, building automation, etc. I expect the jury and candidates to be comfortable with unfinished projects and decide on the vision and the code. Does that make sense or is it too early?
I think my questions should be common. If you agree, I volunteer to contribute the answers to the website to help others boarding on the incubator.
Thanks.
Jacques Basaldúa
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Iceberg proposal for incubation
Posted by Ryan Blue <rb...@netflix.com.INVALID>.
It sounds like there is consensus, so I'll start a vote thread. Thanks,
everyone, for looking at the proposal!
rb
On Tue, Nov 13, 2018 at 1:27 AM Lars Francke <la...@gmail.com> wrote:
> I've been following the Iceberg project on and off for a while now and I
> think this is desperately needed. I don't claim to understand all of the
> details but I'm very happy to hear this being proposed for Apache. I think
> it'd be a great fit. Thank you Ryan and everyone else working on this so
> far.
>
> The proposal looks good to me.
>
> Cheers,
> Lars
>
> On Tue, Nov 13, 2018 at 4:01 AM Dave Fisher <da...@comcast.net> wrote:
>
>> Looks good to me. The challenge here is community development. With such
>> mentor/committer engagement I trust that the Apache Way is covered!
>>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>> > On Nov 12, 2018, at 6:46 PM, Kevin A. McGrail <km...@apache.org>
>> wrote:
>> >
>> >> On 11/12/2018 3:17 PM, Ryan Blue wrote:
>> >> Thanks for pointing that out, Dave. That section was accidentally not
>> >> updated after I copied the markup template. I'll fix it.
>> > Looks good to me. That's a lot of data to query!
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
--
Ryan Blue
Software Engineer
Netflix
Re: [DISCUSS] Iceberg proposal for incubation
Posted by Lars Francke <la...@gmail.com>.
I've been following the Iceberg project on and off for a while now and I
think this is desperately needed. I don't claim to understand all of the
details but I'm very happy to hear this being proposed for Apache. I think
it'd be a great fit. Thank you Ryan and everyone else working on this so
far.
The proposal looks good to me.
Cheers,
Lars
On Tue, Nov 13, 2018 at 4:01 AM Dave Fisher <da...@comcast.net> wrote:
> Looks good to me. The challenge here is community development. With such
> mentor/committer engagement I trust that the Apache Way is covered!
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Nov 12, 2018, at 6:46 PM, Kevin A. McGrail <km...@apache.org>
> wrote:
> >
> >> On 11/12/2018 3:17 PM, Ryan Blue wrote:
> >> Thanks for pointing that out, Dave. That section was accidentally not
> >> updated after I copied the markup template. I'll fix it.
> > Looks good to me. That's a lot of data to query!
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [DISCUSS] Iceberg proposal for incubation
Posted by Dave Fisher <da...@comcast.net>.
Looks good to me. The challenge here is community development. With such mentor/committer engagement I trust that the Apache Way is covered!
Regards,
Dave
Sent from my iPhone
> On Nov 12, 2018, at 6:46 PM, Kevin A. McGrail <km...@apache.org> wrote:
>
>> On 11/12/2018 3:17 PM, Ryan Blue wrote:
>> Thanks for pointing that out, Dave. That section was accidentally not
>> updated after I copied the markup template. I'll fix it.
> Looks good to me. That's a lot of data to query!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Iceberg proposal for incubation
Posted by "Kevin A. McGrail" <km...@apache.org>.
On 11/12/2018 3:17 PM, Ryan Blue wrote:
> Thanks for pointing that out, Dave. That section was accidentally not
> updated after I copied the markup template. I'll fix it.
Looks good to me. That's a lot of data to query!
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Iceberg proposal for incubation
Posted by Ryan Blue <rb...@netflix.com.INVALID>.
Thanks for pointing that out, Dave. That section was accidentally not
updated after I copied the markup template. I'll fix it.
On Mon, Nov 12, 2018 at 12:01 PM Dave Fisher <da...@comcast.net> wrote:
> Hi -
>
> Looks very interesting.
>
> I have questions about the discrepancy between the Initial Committer list
> of 5 people vs. the Affliations list with 16 people?
>
> Is it true that the podling plans to start with just 5 committers?
>
> Who from this group is affiliated with Netflix?
>
> Regards,
> Dave
>
> > On Nov 12, 2018, at 11:51 AM, Ryan Blue <bl...@apache.org> wrote:
> >
> > Since it has been a week without substantial comments or changes to this
> > proposal, I've posted it to the wiki as Bertrand suggested:
> > https://wiki.apache.org/incubator/IcebergProposal
> >
> > Any further comments or discussion? If not, I can start a vote thread
> > tomorrow.
> >
> > Thanks, everyone!
> >
> > rb
> >
> > On Tue, Nov 6, 2018 at 12:10 AM Bertrand Delacretaz <
> > bdelacretaz@codeconsult.ch> wrote:
> >
> >> Hi,
> >>
> >> On Mon, Nov 5, 2018 at 7:04 PM Ryan Blue <rb...@netflix.com.invalid>
> >> wrote:
> >>> ... I'd like to start a discussion about moving Netflix's Iceberg
> project
> >> to
> >>> the incubator...
> >>
> >> Looks like a very interesting project!
> >>
> >>> ...I can post it to the wiki as well if that's needed,...
> >>
> >> Yes please, it's good to have all proposals there - as soon as it's
> >> past the draft stage.
> >>
> >> -Bertrand
> >>
> >
> >
> > --
> > Ryan Blue
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Ryan Blue
Software Engineer
Netflix
Re: [DISCUSS] Iceberg proposal for incubation
Posted by Dave Fisher <da...@comcast.net>.
Hi -
Looks very interesting.
I have questions about the discrepancy between the Initial Committer list of 5 people vs. the Affliations list with 16 people?
Is it true that the podling plans to start with just 5 committers?
Who from this group is affiliated with Netflix?
Regards,
Dave
> On Nov 12, 2018, at 11:51 AM, Ryan Blue <bl...@apache.org> wrote:
>
> Since it has been a week without substantial comments or changes to this
> proposal, I've posted it to the wiki as Bertrand suggested:
> https://wiki.apache.org/incubator/IcebergProposal
>
> Any further comments or discussion? If not, I can start a vote thread
> tomorrow.
>
> Thanks, everyone!
>
> rb
>
> On Tue, Nov 6, 2018 at 12:10 AM Bertrand Delacretaz <
> bdelacretaz@codeconsult.ch> wrote:
>
>> Hi,
>>
>> On Mon, Nov 5, 2018 at 7:04 PM Ryan Blue <rb...@netflix.com.invalid>
>> wrote:
>>> ... I'd like to start a discussion about moving Netflix's Iceberg project
>> to
>>> the incubator...
>>
>> Looks like a very interesting project!
>>
>>> ...I can post it to the wiki as well if that's needed,...
>>
>> Yes please, it's good to have all proposals there - as soon as it's
>> past the draft stage.
>>
>> -Bertrand
>>
>
>
> --
> Ryan Blue
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [DISCUSS] Iceberg proposal for incubation
Posted by Ryan Blue <bl...@apache.org>.
Since it has been a week without substantial comments or changes to this
proposal, I've posted it to the wiki as Bertrand suggested:
https://wiki.apache.org/incubator/IcebergProposal
Any further comments or discussion? If not, I can start a vote thread
tomorrow.
Thanks, everyone!
rb
On Tue, Nov 6, 2018 at 12:10 AM Bertrand Delacretaz <
bdelacretaz@codeconsult.ch> wrote:
> Hi,
>
> On Mon, Nov 5, 2018 at 7:04 PM Ryan Blue <rb...@netflix.com.invalid>
> wrote:
> >... I'd like to start a discussion about moving Netflix's Iceberg project
> to
> > the incubator...
>
> Looks like a very interesting project!
>
> >...I can post it to the wiki as well if that's needed,...
>
> Yes please, it's good to have all proposals there - as soon as it's
> past the draft stage.
>
> -Bertrand
>
--
Ryan Blue
Re: [DISCUSS] Iceberg proposal for incubation
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Hi,
On Mon, Nov 5, 2018 at 7:04 PM Ryan Blue <rb...@netflix.com.invalid> wrote:
>... I'd like to start a discussion about moving Netflix's Iceberg project to
> the incubator...
Looks like a very interesting project!
>...I can post it to the wiki as well if that's needed,...
Yes please, it's good to have all proposals there - as soon as it's
past the draft stage.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org