Re: [VOTE] New development branch for ingestion component
Thanks Michael, The vote has passed with: 1 non-binding 8 binding we can certainly call it closed as enough time has elapsed. I can create the epic if needed. once we have the epic I'll create the branch. - Nathanael On Nov 28, 2017, at 12:16 PM, Michael Ridleywrote: Vartika, Since you coordinated the design doc development, can you create the JIRA Epic and related issues? Thanks! Michael On Tue, Nov 28, 2017 at 3:15 PM, Michael Ridley wrote: Hi team- Wanted to follow-up on this, it looks like the vote passed. Can we get the branch created on the ASF git repo? Thanks! Michael On Mon, Nov 27, 2017 at 2:51 PM, Michael Ridley wrote: Hope all in the US had a great Thanksgiving holiday! Wanted to follow-up on this as it looks like the vote passed? Michael On Wed, Nov 22, 2017 at 12:53 PM, Lujan Moreno, Gustavo < gustavo.lujan.mor...@intel.com> wrote: +1 On 11/21/17, 5:53 PM, "Mubashir Kazia" wrote: +1 On Nov 22, 2017 4:57 AM, "Nate Smith" wrote: +1 On Nov 21, 2017, at 12:41 PM, Vartika Singh wrote: +1 On Tue, Nov 21, 2017 at 12:21 PM, Cesar Berho wrote: +1 On Tue, Nov 21, 2017 at 12:26 PM, solrac...@apache.org < solrac...@apache.org wrote: +1 2017-11-21 5:12 GMT-06:00 Nate Smith : Hello, I’d like to call a vote in regards to the following: Creation of an Ingest redesign branch (name to be determined) and linkage of this branch to a Jira epic. These are the proposed requirements: 1. Extendible to any source. 2. NRT latency between ingestion and output to the HDFS/persistent store. 3. Maintain the integrity of the ODM module in order to facilitate seamless integration with applications. Please see the design spec for more details prior to voting: https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh 3f__ GyB1Msu2LUofIU4/edit# I will leave the vote open for 3 days, - Nathanael On Nov 17, 2017, at 2:28 PM, Mubashir Kazia < mka...@cloudera.com> wrote: +1 for breaking down into tasks. Let's resolve the comments in the doc and put it up for vote. Looks good to me otherwise. Thanks Vartika for working on this. On Wed, Nov 8, 2017 at 10:36 PM, Michael Ridley < mrid...@cloudera.com> wrote: I just realized that in my re-writing and editing of the last email I took out the part where I said that I thought it looks good. But I do think it looks good :-) Michael On Wed, Nov 8, 2017 at 10:35 PM, Michael Ridley < mrid...@cloudera.com> wrote: Hi Vartika- Thanks for the reminder about the ingestion design document. Suggest we open a JIRA (unless one has already been opened and I missed it) with the specific tasks broken down (create an Epic if necessary) and attach a PDF version of the architecture document. Would also be great to get this document into the Spot repo. Do we need a separate upstream branch? I don't think there has been much development process discussion here but I would expect the work to be in the main dev branch after the patches/PRs are accepted and the JIRAs are resolved. Michael On Tue, Oct 31, 2017 at 11:31 PM, Vartika Singh < vsi...@cloudera.com> wrote: Hello all, The following document has been out for discussion for a while: https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh 3f__ GyB1Msu2LUofIU4/edit#heading=h.ptz51qlqt0t I would like to start a new branch for ingestion component. A Again, the idea of ingestion component is the following: 1. Extendible to any source. 2. NRT latency between ingestion and output to the HDFS/persistent store. 3. Maintain the integrity of the ODM module in order to facilitate seamless integration with applications. Thoughts? Vartika Singh -- Michael Ridley office: (650) 352-1337 mobile: (571) 438-2420 Senior Solutions Architect Cloudera -- Michael Ridley office: (650) 352-1337 mobile: (571) 438-2420 Senior Solutions Architect Cloudera -- Vartika Singh Cloudera -- Michael Ridley office: (650) 352-1337 mobile: (571) 438-2420 Senior Solutions Architect Cloudera -- Michael Ridley office: (650) 352-1337 mobile: (571) 438-2420 Senior Solutions Architect Cloudera -- Michael Ridley office: (650) 352-1337 mobile: (571) 438-2420 Senior Solutions Architect Cloudera
Re: [VOTE] New development branch for ingestion component
+1 > On Nov 21, 2017, at 12:41 PM, Vartika Singhwrote: > > +1 > > On Tue, Nov 21, 2017 at 12:21 PM, Cesar Berho wrote: > >> +1 >> >> On Tue, Nov 21, 2017 at 12:26 PM, solrac...@apache.org < >> solrac...@apache.org >>> wrote: >> >>> +1 >>> >>> >>> 2017-11-21 5:12 GMT-06:00 Nate Smith : >>> Hello, I’d like to call a vote in regards to the following: Creation of an Ingest redesign branch (name to be determined) and >> linkage of this branch to a Jira epic. These are the proposed requirements: 1. Extendible to any source. 2. NRT latency between ingestion and output to the HDFS/persistent >>> store. 3. Maintain the integrity of the ODM module in order to facilitate seamless integration with applications. Please see the design spec for more details prior to voting: https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ GyB1Msu2LUofIU4/edit# I will leave the vote open for 3 days, - Nathanael On Nov 17, 2017, at 2:28 PM, Mubashir Kazia >> wrote: +1 for breaking down into tasks. Let's resolve the comments in the doc and put it up for vote. Looks >> good >>> to me otherwise. Thanks Vartika for working on this. On Wed, Nov 8, 2017 at 10:36 PM, Michael Ridley wrote: I just realized that in my re-writing and editing of the last email I >>> took out the part where I said that I thought it looks good. But I do think >>> it looks good :-) Michael On Wed, Nov 8, 2017 at 10:35 PM, Michael Ridley wrote: Hi Vartika- Thanks for the reminder about the ingestion design document. Suggest >> we open a JIRA (unless one has already been opened and I missed it) with >> the specific tasks broken down (create an Epic if necessary) and attach a >> PDF version of the architecture document. Would also be great to get this document into the Spot repo. Do we need a separate upstream branch? I don't think there has been >> much development process discussion here but I would expect the work to be >> in the main dev branch after the patches/PRs are accepted and the JIRAs >> are resolved. Michael On Tue, Oct 31, 2017 at 11:31 PM, Vartika Singh wrote: Hello all, The following document has been out for discussion for a while: https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ GyB1Msu2LUofIU4/edit#heading=h.ptz51qlqt0t I would like to start a new branch for ingestion component. A Again, the idea of ingestion component is the following: 1. Extendible to any source. 2. NRT latency between ingestion and output to the HDFS/persistent store. 3. Maintain the integrity of the ODM module in order to facilitate seamless integration with applications. Thoughts? Vartika Singh -- Michael Ridley office: (650) 352-1337 mobile: (571) 438-2420 Senior Solutions Architect Cloudera -- Michael Ridley office: (650) 352-1337 mobile: (571) 438-2420 Senior Solutions Architect Cloudera >>> >> > > > > -- > Vartika Singh > Cloudera
Re: [VOTE] New development branch for ingestion component
+1 On Tue, Nov 21, 2017 at 12:21 PM, Cesar Berhowrote: > +1 > > On Tue, Nov 21, 2017 at 12:26 PM, solrac...@apache.org < > solrac...@apache.org > > wrote: > > > +1 > > > > > > 2017-11-21 5:12 GMT-06:00 Nate Smith : > > > > > Hello, > > > > > > I’d like to call a vote in regards to the following: > > > > > > Creation of an Ingest redesign branch (name to be determined) and > linkage > > > of this branch to a Jira epic. > > > > > > These are the proposed requirements: > > > > > > 1. Extendible to any source. > > > 2. NRT latency between ingestion and output to the HDFS/persistent > > store. > > > 3. Maintain the integrity of the ODM module in order to facilitate > > > seamless integration with applications. > > > > > > Please see the design spec for more details prior to voting: > > > https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ > > > GyB1Msu2LUofIU4/edit# > > > > > > I will leave the vote open for 3 days, > > > > > > - Nathanael > > > > > > On Nov 17, 2017, at 2:28 PM, Mubashir Kazia > wrote: > > > > > > +1 for breaking down into tasks. > > > > > > Let's resolve the comments in the doc and put it up for vote. Looks > good > > to > > > me otherwise. > > > > > > Thanks Vartika for working on this. > > > > > > On Wed, Nov 8, 2017 at 10:36 PM, Michael Ridley > > > wrote: > > > > > > I just realized that in my re-writing and editing of the last email I > > took > > > out the part where I said that I thought it looks good. But I do think > > it > > > looks good :-) > > > > > > Michael > > > > > > On Wed, Nov 8, 2017 at 10:35 PM, Michael Ridley > > > wrote: > > > > > > Hi Vartika- > > > > > > Thanks for the reminder about the ingestion design document. Suggest > we > > > open a JIRA (unless one has already been opened and I missed it) with > the > > > specific tasks broken down (create an Epic if necessary) and attach a > PDF > > > version of the architecture document. Would also be great to get this > > > document into the Spot repo. > > > > > > Do we need a separate upstream branch? I don't think there has been > much > > > development process discussion here but I would expect the work to be > in > > > the main dev branch after the patches/PRs are accepted and the JIRAs > are > > > resolved. > > > > > > Michael > > > > > > On Tue, Oct 31, 2017 at 11:31 PM, Vartika Singh > > > wrote: > > > > > > Hello all, > > > > > > The following document has been out for discussion for a while: > > > > > > https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ > > > GyB1Msu2LUofIU4/edit#heading=h.ptz51qlqt0t > > > > > > I would like to start a new branch for ingestion component. A > > > > > > Again, the idea of ingestion component is the following: > > > > > > 1. Extendible to any source. > > > 2. NRT latency between ingestion and output to the HDFS/persistent > > > store. > > > 3. Maintain the integrity of the ODM module in order to facilitate > > > seamless integration with applications. > > > > > > > > > Thoughts? > > > > > > Vartika Singh > > > > > > > > > > > > > > > -- > > > Michael Ridley > > > office: (650) 352-1337 > > > mobile: (571) 438-2420 > > > Senior Solutions Architect > > > Cloudera > > > > > > > > > > > > > > > -- > > > Michael Ridley > > > office: (650) 352-1337 > > > mobile: (571) 438-2420 > > > Senior Solutions Architect > > > Cloudera > > > > > > -- Vartika Singh Cloudera
Re: [VOTE] New development branch for ingestion component
+1 *--* Best Regards! --- *Ray Panduro *http://spot.apache.org/ --- On Tue, Nov 21, 2017 at 10:51 AM, Michael Ridleywrote: > +1 (non-binding) > > Michael Ridley > Senior Solutions Architect > Cloudera > > Sent from my mobile. > Pardon any spelling errors. > > > On Nov 21, 2017, at 6:17 AM, Morris Hicks wrote: > > > > +1 > > > >> On Tue, Nov 21, 2017 at 6:12 AM, Nate Smith > wrote: > >> > >> Hello, > >> > >> I’d like to call a vote in regards to the following: > >> > >> Creation of an Ingest redesign branch (name to be determined) and > linkage > >> of this branch to a Jira epic. > >> > >> These are the proposed requirements: > >> > >> 1. Extendible to any source. > >> 2. NRT latency between ingestion and output to the HDFS/persistent > store. > >> 3. Maintain the integrity of the ODM module in order to facilitate > >> seamless integration with applications. > >> > >> Please see the design spec for more details prior to voting: > >> https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ > >> GyB1Msu2LUofIU4/edit# > >> > >> I will leave the vote open for 3 days, > >> > >> - Nathanael > >> > >> On Nov 17, 2017, at 2:28 PM, Mubashir Kazia > wrote: > >> > >> +1 for breaking down into tasks. > >> > >> Let's resolve the comments in the doc and put it up for vote. Looks > good to > >> me otherwise. > >> > >> Thanks Vartika for working on this. > >> > >> On Wed, Nov 8, 2017 at 10:36 PM, Michael Ridley > >> wrote: > >> > >> I just realized that in my re-writing and editing of the last email I > took > >> out the part where I said that I thought it looks good. But I do think > it > >> looks good :-) > >> > >> Michael > >> > >> On Wed, Nov 8, 2017 at 10:35 PM, Michael Ridley > >> wrote: > >> > >> Hi Vartika- > >> > >> Thanks for the reminder about the ingestion design document. Suggest we > >> open a JIRA (unless one has already been opened and I missed it) with > the > >> specific tasks broken down (create an Epic if necessary) and attach a > PDF > >> version of the architecture document. Would also be great to get this > >> document into the Spot repo. > >> > >> Do we need a separate upstream branch? I don't think there has been > much > >> development process discussion here but I would expect the work to be in > >> the main dev branch after the patches/PRs are accepted and the JIRAs are > >> resolved. > >> > >> Michael > >> > >> On Tue, Oct 31, 2017 at 11:31 PM, Vartika Singh > >> wrote: > >> > >> Hello all, > >> > >> The following document has been out for discussion for a while: > >> > >> https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ > >> GyB1Msu2LUofIU4/edit#heading=h.ptz51qlqt0t > >> > >> I would like to start a new branch for ingestion component. A > >> > >> Again, the idea of ingestion component is the following: > >> > >> 1. Extendible to any source. > >> 2. NRT latency between ingestion and output to the HDFS/persistent > >> store. > >> 3. Maintain the integrity of the ODM module in order to facilitate > >> seamless integration with applications. > >> > >> > >> Thoughts? > >> > >> Vartika Singh > >> > >> > >> > >> > >> -- > >> Michael Ridley > >> office: (650) 352-1337 > >> mobile: (571) 438-2420 > >> Senior Solutions Architect > >> Cloudera > >> > >> > >> > >> > >> -- > >> Michael Ridley > >> office: (650) 352-1337 > >> mobile: (571) 438-2420 > >> Senior Solutions Architect > >> Cloudera > >> > > > > > > > > -- > > Morris Hicks > > Strategic Enablement Expert, Cloudera > > mhi...@cloudera.com > > (703) 447-5883 >
Re: [VOTE] New development branch for ingestion component
+1 On Tue, Nov 21, 2017 at 6:12 AM, Nate Smithwrote: > Hello, > > I’d like to call a vote in regards to the following: > > Creation of an Ingest redesign branch (name to be determined) and linkage > of this branch to a Jira epic. > > These are the proposed requirements: > > 1. Extendible to any source. > 2. NRT latency between ingestion and output to the HDFS/persistent store. > 3. Maintain the integrity of the ODM module in order to facilitate > seamless integration with applications. > > Please see the design spec for more details prior to voting: > https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ > GyB1Msu2LUofIU4/edit# > > I will leave the vote open for 3 days, > > - Nathanael > > On Nov 17, 2017, at 2:28 PM, Mubashir Kazia wrote: > > +1 for breaking down into tasks. > > Let's resolve the comments in the doc and put it up for vote. Looks good to > me otherwise. > > Thanks Vartika for working on this. > > On Wed, Nov 8, 2017 at 10:36 PM, Michael Ridley > wrote: > > I just realized that in my re-writing and editing of the last email I took > out the part where I said that I thought it looks good. But I do think it > looks good :-) > > Michael > > On Wed, Nov 8, 2017 at 10:35 PM, Michael Ridley > wrote: > > Hi Vartika- > > Thanks for the reminder about the ingestion design document. Suggest we > open a JIRA (unless one has already been opened and I missed it) with the > specific tasks broken down (create an Epic if necessary) and attach a PDF > version of the architecture document. Would also be great to get this > document into the Spot repo. > > Do we need a separate upstream branch? I don't think there has been much > development process discussion here but I would expect the work to be in > the main dev branch after the patches/PRs are accepted and the JIRAs are > resolved. > > Michael > > On Tue, Oct 31, 2017 at 11:31 PM, Vartika Singh > wrote: > > Hello all, > > The following document has been out for discussion for a while: > > https://docs.google.com/document/d/1yYaD50gp2HN9RHYaUG8ASDfh3f__ > GyB1Msu2LUofIU4/edit#heading=h.ptz51qlqt0t > > I would like to start a new branch for ingestion component. A > > Again, the idea of ingestion component is the following: > > 1. Extendible to any source. > 2. NRT latency between ingestion and output to the HDFS/persistent > store. > 3. Maintain the integrity of the ODM module in order to facilitate > seamless integration with applications. > > > Thoughts? > > Vartika Singh > > > > > -- > Michael Ridley > office: (650) 352-1337 > mobile: (571) 438-2420 > Senior Solutions Architect > Cloudera > > > > > -- > Michael Ridley > office: (650) 352-1337 > mobile: (571) 438-2420 > Senior Solutions Architect > Cloudera > -- Morris Hicks Strategic Enablement Expert, Cloudera mhi...@cloudera.com (703) 447-5883