Avro RPC stuff

[Tom Barber <to...@meteorite.bi>]

Hey Lewis/Radu

Where are we on this? Anything I can do to help drag it into the land of
the living?

Tom

Re: Avro RPC stuff

[Lewis John Mcgibbney <le...@gmail.com>]

We maintain a CI build over at https:// builds.apache.org. You can search
for OODT. This is also linked to from the website.


On Thursday, November 5, 2015, Radu Manole <ma...@gmail.com> wrote:

> Hello,
>
> I tried rebasing my changes on master, but, at least on my computer,
> building failed.
> Is that expected? Can point me to a stable commit to update?
>
> Thanks.
>
> On Wednesday, November 4, 2015, Lewis John Mcgibbney <
> lewis.mcgibbney@gmail.com <javascript:;>> wrote:
>
> > Yeah... Plus it's still a bunch of code to carry around.
> > Realistically we need to define remaining tasks first. The branch can I
> > exist easier now as merging is easier with Git than previously with SVN.
> > It's worth noting that we have a stable build for the Avro RPC stuff
> > meaning that is is as stable as trunk. Many tests have also been
> > implemented for the same.
> > When it comes to merging at some dark place a long way down the road, I
> > agree that this should be a new major release.
> > Having the functionality baked in as separate components is a refactoring
> > of around 7 or so OODT components. No trivial undertaking, but would mean
> > that we can cut loose all the XMLRPC code for good.
> > One con here is that we would need to be dilligent with Pom entries. As
> > noted on this list a few times recently Pom analysis has indicated a
> number
> > of areas where we really need to get OODT on a diet. Many declared but
> > unused dependencies lying around and several bloated artifacts which
> > makes my laptop sound like a Rolls Royce engine strapped to the side of
> my
> > desk.
> > Anyways, first thing first, I'll drag the branch up to date with master
> > (I'll try doing this maybe once every two weeks) then we need to scope
> out
> > what remains.
> > Ta
> >
> > On Wednesday, November 4, 2015, Chris Mattmann <chris.mattmann@gmail.com
> <javascript:;>
> > <javascript:;>>
> > wrote:
> >
> > > Yes, they are interfaced up. No it’s not a simple pick and
> > > choose everywhere since the parts for selecting the underlying
> > > transport are sometimes configurable, and other times hard coded
> > > last I looked.
> > >
> > > Also I think we can effectively split and simply not interface this
> > > and leave 1.x and 0.x as the XML-RPC lines, and eventually deprecate
> > > XML-RPC in 2.x (Avro) and just move to an Avro only thing. Maintaining
> > > both and having the communication layer interfaced up is a nightmare.
> > >
> > > My 2c.
> > >
> > > Cheers,
> > > Chris
> > >
> > > —
> > > Chris Mattmann
> > > chris.mattmann@gmail.com <javascript:;> <javascript:;> <javascript:;>
> > >
> > >
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Tom Barber <tom.barber@meteorite.bi <javascript:;>
> <javascript:;> <javascript:;>>
> > > Reply-To: <dev@oodt.apache.org <javascript:;> <javascript:;>
> <javascript:;>>
> > > Date: Wednesday, November 4, 2015 at 8:34 AM
> > > To: "dev@oodt.apache.org <javascript:;> <javascript:;>
> <javascript:;>" <
> > dev@oodt.apache.org <javascript:;> <javascript:;>
> > > <javascript:;>>
> > > Subject: Re: Avro RPC stuff
> > >
> > > >Booo!
> > > >
> > > >Aren't they just interfaced up and you pick either XMLRPC or Avro?
> > > >
> > > >
> > > >
> > > >On Wed, Nov 4, 2015 at 4:31 PM, Chris Mattmann <
> > chris.mattmann@gmail.com <javascript:;> <javascript:;>
> > > <javascript:;>>
> > > >wrote:
> > > >
> > > >> Hey Guys,
> > > >>
> > > >> IMO this is a post 1.0 Apache OODT release.
> > > >> I’d like to do a full triage of e.g., the OODT-491
> > > >> stuff, get as much of that committed as possible;
> > > >> also the typing stuff for File Manager, and a couple
> > > >> other bells and whistles.
> > > >>
> > > >> This will fundamentally change and is backwards non-compat
> > > >> if we move to Avro. For example an 0.x and/or 1.x OODT
> > > >> client or server won’t be able to talk to a 2.x OODT Avro
> > > >> client/server.
> > > >>
> > > >> Also this needs to be tested e.g, in an ImageCat, DRAT,
> > > >> and/or mission scenario to make sure it fully works as
> > > >> expected before a merge into master.
> > > >>
> > > >> Cheers,
> > > >> Chris
> > > >>
> > > >> —
> > > >> Chris Mattmann
> > > >> chris.mattmann@gmail.com <javascript:;> <javascript:;>
> <javascript:;>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> -----Original Message-----
> > > >> From: Lewis John Mcgibbney <lewis.mcgibbney@gmail.com
> <javascript:;> <javascript:;>
> > <javascript:;>>
> > > >> Reply-To: <dev@oodt.apache.org <javascript:;> <javascript:;>
> <javascript:;>>
> > > >> Date: Wednesday, November 4, 2015 at 8:25 AM
> > > >> To: "dev@oodt.apache.org <javascript:;> <javascript:;>
> <javascript:;>" <
> > dev@oodt.apache.org <javascript:;> <javascript:;>
> > > <javascript:;>>
> > > >> Subject: Re: Avro RPC stuff
> > > >>
> > > >> >The Pom.xml rearranging screwed me a few weeks back.
> > > >> >I've got a patch locally to sort this ot and will commit then drag
> > the
> > > >> >avro
> > > >> >RPC branch up to date with trunk.
> > > >> >What we need to do is properly scope out what needs to be done to
> > > >>finish
> > > >> >this task off.
> > > >> >Radu,
> > > >> >Are you able to write here what you think is required to finish the
> > > >>task
> > > >> >off please?
> > > >> >Thanks
> > > >> >
> > > >> >On Wednesday, November 4, 2015, Tom Barber <
> tom.barber@meteorite.bi <javascript:;>
> > <javascript:;>
> > > <javascript:;>>
> > > >> >wrote:
> > > >> >
> > > >> >> Hey Lewis/Radu
> > > >> >>
> > > >> >> Where are we on this? Anything I can do to help drag it into the
> > > >>land of
> > > >> >> the living?
> > > >> >>
> > > >> >> Tom
> > > >> >>
> > > >> >
> > > >> >
> > > >> >--
> > > >> >*Lewis*
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
> >
> > --
> > *Lewis*
> >
>


-- 
*Lewis*

Re: Avro RPC stuff

[Radu Manole <ma...@gmail.com>]

Hello,

I tried rebasing my changes on master, but, at least on my computer,
building failed.
Is that expected? Can point me to a stable commit to update?

Thanks.

On Wednesday, November 4, 2015, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:

> Yeah... Plus it's still a bunch of code to carry around.
> Realistically we need to define remaining tasks first. The branch can I
> exist easier now as merging is easier with Git than previously with SVN.
> It's worth noting that we have a stable build for the Avro RPC stuff
> meaning that is is as stable as trunk. Many tests have also been
> implemented for the same.
> When it comes to merging at some dark place a long way down the road, I
> agree that this should be a new major release.
> Having the functionality baked in as separate components is a refactoring
> of around 7 or so OODT components. No trivial undertaking, but would mean
> that we can cut loose all the XMLRPC code for good.
> One con here is that we would need to be dilligent with Pom entries. As
> noted on this list a few times recently Pom analysis has indicated a number
> of areas where we really need to get OODT on a diet. Many declared but
> unused dependencies lying around and several bloated artifacts which
> makes my laptop sound like a Rolls Royce engine strapped to the side of my
> desk.
> Anyways, first thing first, I'll drag the branch up to date with master
> (I'll try doing this maybe once every two weeks) then we need to scope out
> what remains.
> Ta
>
> On Wednesday, November 4, 2015, Chris Mattmann <chris.mattmann@gmail.com
> <javascript:;>>
> wrote:
>
> > Yes, they are interfaced up. No it’s not a simple pick and
> > choose everywhere since the parts for selecting the underlying
> > transport are sometimes configurable, and other times hard coded
> > last I looked.
> >
> > Also I think we can effectively split and simply not interface this
> > and leave 1.x and 0.x as the XML-RPC lines, and eventually deprecate
> > XML-RPC in 2.x (Avro) and just move to an Avro only thing. Maintaining
> > both and having the communication layer interfaced up is a nightmare.
> >
> > My 2c.
> >
> > Cheers,
> > Chris
> >
> > —
> > Chris Mattmann
> > chris.mattmann@gmail.com <javascript:;> <javascript:;>
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Tom Barber <tom.barber@meteorite.bi <javascript:;> <javascript:;>>
> > Reply-To: <dev@oodt.apache.org <javascript:;> <javascript:;>>
> > Date: Wednesday, November 4, 2015 at 8:34 AM
> > To: "dev@oodt.apache.org <javascript:;> <javascript:;>" <
> dev@oodt.apache.org <javascript:;>
> > <javascript:;>>
> > Subject: Re: Avro RPC stuff
> >
> > >Booo!
> > >
> > >Aren't they just interfaced up and you pick either XMLRPC or Avro?
> > >
> > >
> > >
> > >On Wed, Nov 4, 2015 at 4:31 PM, Chris Mattmann <
> chris.mattmann@gmail.com <javascript:;>
> > <javascript:;>>
> > >wrote:
> > >
> > >> Hey Guys,
> > >>
> > >> IMO this is a post 1.0 Apache OODT release.
> > >> I’d like to do a full triage of e.g., the OODT-491
> > >> stuff, get as much of that committed as possible;
> > >> also the typing stuff for File Manager, and a couple
> > >> other bells and whistles.
> > >>
> > >> This will fundamentally change and is backwards non-compat
> > >> if we move to Avro. For example an 0.x and/or 1.x OODT
> > >> client or server won’t be able to talk to a 2.x OODT Avro
> > >> client/server.
> > >>
> > >> Also this needs to be tested e.g, in an ImageCat, DRAT,
> > >> and/or mission scenario to make sure it fully works as
> > >> expected before a merge into master.
> > >>
> > >> Cheers,
> > >> Chris
> > >>
> > >> —
> > >> Chris Mattmann
> > >> chris.mattmann@gmail.com <javascript:;> <javascript:;>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Lewis John Mcgibbney <lewis.mcgibbney@gmail.com <javascript:;>
> <javascript:;>>
> > >> Reply-To: <dev@oodt.apache.org <javascript:;> <javascript:;>>
> > >> Date: Wednesday, November 4, 2015 at 8:25 AM
> > >> To: "dev@oodt.apache.org <javascript:;> <javascript:;>" <
> dev@oodt.apache.org <javascript:;>
> > <javascript:;>>
> > >> Subject: Re: Avro RPC stuff
> > >>
> > >> >The Pom.xml rearranging screwed me a few weeks back.
> > >> >I've got a patch locally to sort this ot and will commit then drag
> the
> > >> >avro
> > >> >RPC branch up to date with trunk.
> > >> >What we need to do is properly scope out what needs to be done to
> > >>finish
> > >> >this task off.
> > >> >Radu,
> > >> >Are you able to write here what you think is required to finish the
> > >>task
> > >> >off please?
> > >> >Thanks
> > >> >
> > >> >On Wednesday, November 4, 2015, Tom Barber <tom.barber@meteorite.bi
> <javascript:;>
> > <javascript:;>>
> > >> >wrote:
> > >> >
> > >> >> Hey Lewis/Radu
> > >> >>
> > >> >> Where are we on this? Anything I can do to help drag it into the
> > >>land of
> > >> >> the living?
> > >> >>
> > >> >> Tom
> > >> >>
> > >> >
> > >> >
> > >> >--
> > >> >*Lewis*
> > >>
> > >>
> > >>
> >
> >
> >
>
> --
> *Lewis*
>

Re: Avro RPC stuff

[Lewis John Mcgibbney <le...@gmail.com>]

Yeah... Plus it's still a bunch of code to carry around.
Realistically we need to define remaining tasks first. The branch can I
exist easier now as merging is easier with Git than previously with SVN.
It's worth noting that we have a stable build for the Avro RPC stuff
meaning that is is as stable as trunk. Many tests have also been
implemented for the same.
When it comes to merging at some dark place a long way down the road, I
agree that this should be a new major release.
Having the functionality baked in as separate components is a refactoring
of around 7 or so OODT components. No trivial undertaking, but would mean
that we can cut loose all the XMLRPC code for good.
One con here is that we would need to be dilligent with Pom entries. As
noted on this list a few times recently Pom analysis has indicated a number
of areas where we really need to get OODT on a diet. Many declared but
unused dependencies lying around and several bloated artifacts which
makes my laptop sound like a Rolls Royce engine strapped to the side of my
desk.
Anyways, first thing first, I'll drag the branch up to date with master
(I'll try doing this maybe once every two weeks) then we need to scope out
what remains.
Ta

On Wednesday, November 4, 2015, Chris Mattmann <ch...@gmail.com>
wrote:

> Yes, they are interfaced up. No it’s not a simple pick and
> choose everywhere since the parts for selecting the underlying
> transport are sometimes configurable, and other times hard coded
> last I looked.
>
> Also I think we can effectively split and simply not interface this
> and leave 1.x and 0.x as the XML-RPC lines, and eventually deprecate
> XML-RPC in 2.x (Avro) and just move to an Avro only thing. Maintaining
> both and having the communication layer interfaced up is a nightmare.
>
> My 2c.
>
> Cheers,
> Chris
>
> —
> Chris Mattmann
> chris.mattmann@gmail.com <javascript:;>
>
>
>
>
>
>
> -----Original Message-----
> From: Tom Barber <tom.barber@meteorite.bi <javascript:;>>
> Reply-To: <dev@oodt.apache.org <javascript:;>>
> Date: Wednesday, November 4, 2015 at 8:34 AM
> To: "dev@oodt.apache.org <javascript:;>" <dev@oodt.apache.org
> <javascript:;>>
> Subject: Re: Avro RPC stuff
>
> >Booo!
> >
> >Aren't they just interfaced up and you pick either XMLRPC or Avro?
> >
> >
> >
> >On Wed, Nov 4, 2015 at 4:31 PM, Chris Mattmann <chris.mattmann@gmail.com
> <javascript:;>>
> >wrote:
> >
> >> Hey Guys,
> >>
> >> IMO this is a post 1.0 Apache OODT release.
> >> I’d like to do a full triage of e.g., the OODT-491
> >> stuff, get as much of that committed as possible;
> >> also the typing stuff for File Manager, and a couple
> >> other bells and whistles.
> >>
> >> This will fundamentally change and is backwards non-compat
> >> if we move to Avro. For example an 0.x and/or 1.x OODT
> >> client or server won’t be able to talk to a 2.x OODT Avro
> >> client/server.
> >>
> >> Also this needs to be tested e.g, in an ImageCat, DRAT,
> >> and/or mission scenario to make sure it fully works as
> >> expected before a merge into master.
> >>
> >> Cheers,
> >> Chris
> >>
> >> —
> >> Chris Mattmann
> >> chris.mattmann@gmail.com <javascript:;>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Lewis John Mcgibbney <lewis.mcgibbney@gmail.com <javascript:;>>
> >> Reply-To: <dev@oodt.apache.org <javascript:;>>
> >> Date: Wednesday, November 4, 2015 at 8:25 AM
> >> To: "dev@oodt.apache.org <javascript:;>" <dev@oodt.apache.org
> <javascript:;>>
> >> Subject: Re: Avro RPC stuff
> >>
> >> >The Pom.xml rearranging screwed me a few weeks back.
> >> >I've got a patch locally to sort this ot and will commit then drag the
> >> >avro
> >> >RPC branch up to date with trunk.
> >> >What we need to do is properly scope out what needs to be done to
> >>finish
> >> >this task off.
> >> >Radu,
> >> >Are you able to write here what you think is required to finish the
> >>task
> >> >off please?
> >> >Thanks
> >> >
> >> >On Wednesday, November 4, 2015, Tom Barber <tom.barber@meteorite.bi
> <javascript:;>>
> >> >wrote:
> >> >
> >> >> Hey Lewis/Radu
> >> >>
> >> >> Where are we on this? Anything I can do to help drag it into the
> >>land of
> >> >> the living?
> >> >>
> >> >> Tom
> >> >>
> >> >
> >> >
> >> >--
> >> >*Lewis*
> >>
> >>
> >>
>
>
>

-- 
*Lewis*

Re: Avro RPC stuff

[Tom Barber <to...@meteorite.bi>]

Fair enough I'll leave it those who know!

(Still just continuing on my quest to dump XML-RPC and run for the hills!
;) )

I also don't want Radu's stuff just get forgotten about or so out of sync
its wasted, especially as you're talking about OODT 2 when we haven't even
got 1 shipped yet! ;)



On Wed, Nov 4, 2015 at 4:37 PM, Chris Mattmann <ch...@gmail.com>
wrote:

> Yes, they are interfaced up. No it’s not a simple pick and
> choose everywhere since the parts for selecting the underlying
> transport are sometimes configurable, and other times hard coded
> last I looked.
>
> Also I think we can effectively split and simply not interface this
> and leave 1.x and 0.x as the XML-RPC lines, and eventually deprecate
> XML-RPC in 2.x (Avro) and just move to an Avro only thing. Maintaining
> both and having the communication layer interfaced up is a nightmare.
>
> My 2c.
>
> Cheers,
> Chris
>
> —
> Chris Mattmann
> chris.mattmann@gmail.com
>
>
>
>
>
>
> -----Original Message-----
> From: Tom Barber <to...@meteorite.bi>
> Reply-To: <de...@oodt.apache.org>
> Date: Wednesday, November 4, 2015 at 8:34 AM
> To: "dev@oodt.apache.org" <de...@oodt.apache.org>
> Subject: Re: Avro RPC stuff
>
> >Booo!
> >
> >Aren't they just interfaced up and you pick either XMLRPC or Avro?
> >
> >
> >
> >On Wed, Nov 4, 2015 at 4:31 PM, Chris Mattmann <ch...@gmail.com>
> >wrote:
> >
> >> Hey Guys,
> >>
> >> IMO this is a post 1.0 Apache OODT release.
> >> I’d like to do a full triage of e.g., the OODT-491
> >> stuff, get as much of that committed as possible;
> >> also the typing stuff for File Manager, and a couple
> >> other bells and whistles.
> >>
> >> This will fundamentally change and is backwards non-compat
> >> if we move to Avro. For example an 0.x and/or 1.x OODT
> >> client or server won’t be able to talk to a 2.x OODT Avro
> >> client/server.
> >>
> >> Also this needs to be tested e.g, in an ImageCat, DRAT,
> >> and/or mission scenario to make sure it fully works as
> >> expected before a merge into master.
> >>
> >> Cheers,
> >> Chris
> >>
> >> —
> >> Chris Mattmann
> >> chris.mattmann@gmail.com
> >>
> >>
> >>
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Lewis John Mcgibbney <le...@gmail.com>
> >> Reply-To: <de...@oodt.apache.org>
> >> Date: Wednesday, November 4, 2015 at 8:25 AM
> >> To: "dev@oodt.apache.org" <de...@oodt.apache.org>
> >> Subject: Re: Avro RPC stuff
> >>
> >> >The Pom.xml rearranging screwed me a few weeks back.
> >> >I've got a patch locally to sort this ot and will commit then drag the
> >> >avro
> >> >RPC branch up to date with trunk.
> >> >What we need to do is properly scope out what needs to be done to
> >>finish
> >> >this task off.
> >> >Radu,
> >> >Are you able to write here what you think is required to finish the
> >>task
> >> >off please?
> >> >Thanks
> >> >
> >> >On Wednesday, November 4, 2015, Tom Barber <to...@meteorite.bi>
> >> >wrote:
> >> >
> >> >> Hey Lewis/Radu
> >> >>
> >> >> Where are we on this? Anything I can do to help drag it into the
> >>land of
> >> >> the living?
> >> >>
> >> >> Tom
> >> >>
> >> >
> >> >
> >> >--
> >> >*Lewis*
> >>
> >>
> >>
>
>
>

Re: Avro RPC stuff

[Chris Mattmann <ch...@gmail.com>]

Yes, they are interfaced up. No it’s not a simple pick and
choose everywhere since the parts for selecting the underlying
transport are sometimes configurable, and other times hard coded
last I looked.

Also I think we can effectively split and simply not interface this
and leave 1.x and 0.x as the XML-RPC lines, and eventually deprecate
XML-RPC in 2.x (Avro) and just move to an Avro only thing. Maintaining
both and having the communication layer interfaced up is a nightmare.

My 2c.

Cheers,
Chris

—
Chris Mattmann
chris.mattmann@gmail.com






-----Original Message-----
From: Tom Barber <to...@meteorite.bi>
Reply-To: <de...@oodt.apache.org>
Date: Wednesday, November 4, 2015 at 8:34 AM
To: "dev@oodt.apache.org" <de...@oodt.apache.org>
Subject: Re: Avro RPC stuff

>Booo!
>
>Aren't they just interfaced up and you pick either XMLRPC or Avro?
>
>
>
>On Wed, Nov 4, 2015 at 4:31 PM, Chris Mattmann <ch...@gmail.com>
>wrote:
>
>> Hey Guys,
>>
>> IMO this is a post 1.0 Apache OODT release.
>> I’d like to do a full triage of e.g., the OODT-491
>> stuff, get as much of that committed as possible;
>> also the typing stuff for File Manager, and a couple
>> other bells and whistles.
>>
>> This will fundamentally change and is backwards non-compat
>> if we move to Avro. For example an 0.x and/or 1.x OODT
>> client or server won’t be able to talk to a 2.x OODT Avro
>> client/server.
>>
>> Also this needs to be tested e.g, in an ImageCat, DRAT,
>> and/or mission scenario to make sure it fully works as
>> expected before a merge into master.
>>
>> Cheers,
>> Chris
>>
>> —
>> Chris Mattmann
>> chris.mattmann@gmail.com
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Lewis John Mcgibbney <le...@gmail.com>
>> Reply-To: <de...@oodt.apache.org>
>> Date: Wednesday, November 4, 2015 at 8:25 AM
>> To: "dev@oodt.apache.org" <de...@oodt.apache.org>
>> Subject: Re: Avro RPC stuff
>>
>> >The Pom.xml rearranging screwed me a few weeks back.
>> >I've got a patch locally to sort this ot and will commit then drag the
>> >avro
>> >RPC branch up to date with trunk.
>> >What we need to do is properly scope out what needs to be done to
>>finish
>> >this task off.
>> >Radu,
>> >Are you able to write here what you think is required to finish the
>>task
>> >off please?
>> >Thanks
>> >
>> >On Wednesday, November 4, 2015, Tom Barber <to...@meteorite.bi>
>> >wrote:
>> >
>> >> Hey Lewis/Radu
>> >>
>> >> Where are we on this? Anything I can do to help drag it into the
>>land of
>> >> the living?
>> >>
>> >> Tom
>> >>
>> >
>> >
>> >--
>> >*Lewis*
>>
>>
>>

Re: Avro RPC stuff

[Tom Barber <to...@meteorite.bi>]

Booo!

Aren't they just interfaced up and you pick either XMLRPC or Avro?



On Wed, Nov 4, 2015 at 4:31 PM, Chris Mattmann <ch...@gmail.com>
wrote:

> Hey Guys,
>
> IMO this is a post 1.0 Apache OODT release.
> I’d like to do a full triage of e.g., the OODT-491
> stuff, get as much of that committed as possible;
> also the typing stuff for File Manager, and a couple
> other bells and whistles.
>
> This will fundamentally change and is backwards non-compat
> if we move to Avro. For example an 0.x and/or 1.x OODT
> client or server won’t be able to talk to a 2.x OODT Avro
> client/server.
>
> Also this needs to be tested e.g, in an ImageCat, DRAT,
> and/or mission scenario to make sure it fully works as
> expected before a merge into master.
>
> Cheers,
> Chris
>
> —
> Chris Mattmann
> chris.mattmann@gmail.com
>
>
>
>
>
>
> -----Original Message-----
> From: Lewis John Mcgibbney <le...@gmail.com>
> Reply-To: <de...@oodt.apache.org>
> Date: Wednesday, November 4, 2015 at 8:25 AM
> To: "dev@oodt.apache.org" <de...@oodt.apache.org>
> Subject: Re: Avro RPC stuff
>
> >The Pom.xml rearranging screwed me a few weeks back.
> >I've got a patch locally to sort this ot and will commit then drag the
> >avro
> >RPC branch up to date with trunk.
> >What we need to do is properly scope out what needs to be done to finish
> >this task off.
> >Radu,
> >Are you able to write here what you think is required to finish the task
> >off please?
> >Thanks
> >
> >On Wednesday, November 4, 2015, Tom Barber <to...@meteorite.bi>
> >wrote:
> >
> >> Hey Lewis/Radu
> >>
> >> Where are we on this? Anything I can do to help drag it into the land of
> >> the living?
> >>
> >> Tom
> >>
> >
> >
> >--
> >*Lewis*
>
>
>

Re: Avro RPC stuff

[Chris Mattmann <ch...@gmail.com>]

Hey Guys,

IMO this is a post 1.0 Apache OODT release.
I’d like to do a full triage of e.g., the OODT-491
stuff, get as much of that committed as possible;
also the typing stuff for File Manager, and a couple
other bells and whistles.

This will fundamentally change and is backwards non-compat
if we move to Avro. For example an 0.x and/or 1.x OODT
client or server won’t be able to talk to a 2.x OODT Avro
client/server.

Also this needs to be tested e.g, in an ImageCat, DRAT,
and/or mission scenario to make sure it fully works as
expected before a merge into master.

Cheers,
Chris

—
Chris Mattmann
chris.mattmann@gmail.com






-----Original Message-----
From: Lewis John Mcgibbney <le...@gmail.com>
Reply-To: <de...@oodt.apache.org>
Date: Wednesday, November 4, 2015 at 8:25 AM
To: "dev@oodt.apache.org" <de...@oodt.apache.org>
Subject: Re: Avro RPC stuff

>The Pom.xml rearranging screwed me a few weeks back.
>I've got a patch locally to sort this ot and will commit then drag the
>avro
>RPC branch up to date with trunk.
>What we need to do is properly scope out what needs to be done to finish
>this task off.
>Radu,
>Are you able to write here what you think is required to finish the task
>off please?
>Thanks
>
>On Wednesday, November 4, 2015, Tom Barber <to...@meteorite.bi>
>wrote:
>
>> Hey Lewis/Radu
>>
>> Where are we on this? Anything I can do to help drag it into the land of
>> the living?
>>
>> Tom
>>
>
>
>-- 
>*Lewis*

Re: Avro RPC stuff

[Lewis John Mcgibbney <le...@gmail.com>]

The Pom.xml rearranging screwed me a few weeks back.
I've got a patch locally to sort this ot and will commit then drag the avro
RPC branch up to date with trunk.
What we need to do is properly scope out what needs to be done to finish
this task off.
Radu,
Are you able to write here what you think is required to finish the task
off please?
Thanks

On Wednesday, November 4, 2015, Tom Barber <to...@meteorite.bi> wrote:

> Hey Lewis/Radu
>
> Where are we on this? Anything I can do to help drag it into the land of
> the living?
>
> Tom
>


-- 
*Lewis*