Hi Val, I'm working on this at the link below and will post an update here once complete https://cwiki.apache.org/confluence/display/OODT/OODT+XMLRPC+--%3E+AvroRPC+Upgrade Thanks
On Thu, Oct 6, 2016 at 8:02 AM, lewis john mcgibbney <lewi...@apache.org> wrote: > Hi Val, > Yes when Radu and I worked on this code a year or two ago now we were very > much aware of the upgrade issue. > I am preparing myself to put a wiki page together which will fully > document 1) why we have put time and effort into the XMLRP --> AvroRPC > shift, 2) Which services are affected, and 3) How you can upgrade. > On another note, I am also going to put together a wiki page for the > various configuration files and what configuration options you need to use. > It would be less than wise for us to leave people like yourself (and a > significant amount of others I would imagine) in the dark about all of this > so be rest assured that we will not be mandating an upgrade without the > relevant support for your existing pipelines and the path to upgrade. > Actually, in an ideal world we would probably get a blog post together for > this at some stage and post to the foundation blog. > Lewis > > > On Thu, Oct 6, 2016 at 7:19 AM, Mallder, Valerie < > valerie.mall...@jhuapl.edu> wrote: > >> Hi Guys, >> >> So what happens now for the folks like me who are using each of the >> following: >> >> XmlRpcFileManager >> XmlRpcFileManagerClient >> XmlRpcResourceManager >> XmlRpcResourceManagerClient >> XmlRpcBatchStub >> XmlRpcWorkflowManager >> XmlRpcWorkflowManagerClient >> >> I have two science data pipelines, and working on a third, that use these >> objects. Does this mean that all of my pipelines will have to be frozen to >> the current version? Is there an easy way to change over to the Avro-RPC? >> Will someone document all the steps you need to take to change over to >> using it? >> >> Thanks, >> Val >> >> >> >> >> -----Original Message----- >> From: Chris Mattmann [mailto:chris.mattm...@gmail.com] >> Sent: Wednesday, October 05, 2016 5:35 PM >> To: dev@oodt.apache.org >> Subject: Re: Merge Avro RPC >> >> +1 to removing XML-RPC period, and just defaulting to Avro-RPC. >> >> >> >> — >> Chris Mattmann >> chris.mattm...@gmail.com >> >> On 10/5/16, 2:22 PM, "Radu Manole" <manole.v.r...@gmail.com> wrote: >> >> Hello, I I revisited every module where avrorpc was implemented and >> where >> xmlrpc is, >> and marked every class where avro rpc is not implemented. What kind of >> transition to avro-rpc should be implemented? The easiest way is to >> remove >> xml-rpc and give up on compatibility with old version. Or make the >> client >> compatible to connect to both xml-rpc or avro-rpc servers, for the >> transition. >> >> 2016-09-09 19:23 GMT+03:00 lewis john mcgibbney <lewi...@apache.org>: >> >> > So what's the plan then? Where is work going into? Did we define a >> roadmap? >> > Maybe we are best working off of 2.x branch then. >> > >> > On Wednesday, September 7, 2016, Tom Barber < >> tom.bar...@meteorite.bi> >> > wrote: >> > >> > > Be warned folks, don't forget we've merged into mainline and >> have a >> > > development branch for 2.0! >> > > >> > > On Wed, Sep 7, 2016 at 7:38 PM, lewis john mcgibbney < >> lewi...@apache.org >> > > <javascript:;>> >> > > wrote: >> > > >> > > > Hi Radu, >> > > > Yes this is great. >> > > > I would suggest that you submit a patch to '@Deprecate' all of >> the >> > XMLRPC >> > > > code for this current development drive. >> > > > I also suggest that we make the AvroRPC material default from >> now on >> > and >> > > > get more people using it. >> > > > We can also make upgrades to Avro 1.8.X >> > > > Would be great if others can chime in here to discuss the path >> for a >> > > > complete replacement of the XMLRPC logic with AvroRPC for the >> next >> > > release >> > > > or two. >> > > > Thanks >> > > > Lewis >> > > > >> > > > P.S. @Radu, in the meantime please log an issue for >> @Deprecat'ing all >> > of >> > > > the XMLRPC stuff. This should be clearly stated and present >> within >> > > > generated Javadoc such that people know to use the AvroRPC >> > > implementation. >> > > > Thanks >> > > > >> > > > On Mon, Sep 5, 2016 at 6:17 AM, Radu Manole < >> manole.v.r...@gmail.com >> > > <javascript:;>> >> > > > wrote: >> > > > >> > > > > Hello, great to hear that avro rpc support is still wanted, >> if there >> > is >> > > > > anything else to be done, I have a lot of free time now. >> > > > > >> > > > > 2016-07-06 17:09 GMT+03:00 Mattmann, Chris A (3980) < >> > > > > chris.a.mattm...@jpl.nasa.gov <javascript:;>>: >> > > > > >> > > > > > +1 awesome >> > > > > > >> > > > > > ++++++++++++++++++++++++++++++ >> ++++++++++++++++++++++++++++++++++++ >> > > > > > Chris Mattmann, Ph.D. >> > > > > > Chief Architect >> > > > > > Instrument Software and Science Data Systems Section (398) >> > > > > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> > > > > > Office: 168-519, Mailstop: 168-527 >> > > > > > Email: chris.a.mattm...@nasa.gov <javascript:;> >> > > > > > WWW: http://sunset.usc.edu/~mattmann/ >> > > > > > ++++++++++++++++++++++++++++++ >> ++++++++++++++++++++++++++++++++++++ >> > > > > > Director, Information Retrieval and Data Science Group >> (IRDS) >> > > > > > Adjunct Associate Professor, Computer Science Department >> > > > > > University of Southern California, Los Angeles, CA 90089 USA >> > > > > > WWW: http://irds.usc.edu/ >> > > > > > ++++++++++++++++++++++++++++++ >> ++++++++++++++++++++++++++++++++++++ >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > On 7/6/16, 7:07 AM, "Tom Barber" <tom.bar...@meteorite.bi >> > > <javascript:;>> wrote: >> > > > > > >> > > > > > >Absolutely, all we've done is merge master into 2.x, the >> plan was >> > to >> > > > > keep >> > > > > > >that in sync, rename it or whatever and let people who >> care play >> > > > around. >> > > > > > We >> > > > > > >also then planned to merge it into master but leave >> XML-RPC as the >> > > > > default >> > > > > > >for a release or two marked depreciated, as extra security >> in case >> > > it >> > > > > > >affects anything else. Then at some point just switch the >> defaults >> > > in >> > > > > the >> > > > > > >configs and remove the XML-RPC crud. >> > > > > > > >> > > > > > >On Wed, Jul 6, 2016 at 3:04 PM, Mattmann, Chris A (3980) < >> > > > > > >chris.a.mattm...@jpl.nasa.gov <javascript:;>> wrote: >> > > > > > > >> > > > > > >> Great work. >> > > > > > >> >> > > > > > >> Can we agree to create a 2.x branch and work forward >> from that >> > > > > > >> with Avro-RPC? 1.x can remain XML-RPC for a few versions >> while >> > > > > > >> I fix all lingering crap I found on the BigTranslate end? >> > > > > > >> >> > > > > > >> Cheers, >> > > > > > >> Chris >> > > > > > >> >> > > > > > >> ++++++++++++++++++++++++++++++ >> ++++++++++++++++++++++++++++++ >> > > ++++++ >> > > > > > >> Chris Mattmann, Ph.D. >> > > > > > >> Chief Architect >> > > > > > >> Instrument Software and Science Data Systems Section >> (398) >> > > > > > >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> > > > > > >> Office: 168-519, Mailstop: 168-527 >> > > > > > >> Email: chris.a.mattm...@nasa.gov <javascript:;> >> > > > > > >> WWW: http://sunset.usc.edu/~mattmann/ >> > > > > > >> ++++++++++++++++++++++++++++++ >> ++++++++++++++++++++++++++++++ >> > > ++++++ >> > > > > > >> Director, Information Retrieval and Data Science Group >> (IRDS) >> > > > > > >> Adjunct Associate Professor, Computer Science Department >> > > > > > >> University of Southern California, Los Angeles, CA 90089 >> USA >> > > > > > >> WWW: http://irds.usc.edu/ >> > > > > > >> ++++++++++++++++++++++++++++++ >> ++++++++++++++++++++++++++++++ >> > > ++++++ >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> >> > > > > > >> On 7/6/16, 7:01 AM, "Tom Barber" < >> tom.bar...@meteorite.bi >> > > <javascript:;>> wrote: >> > > > > > >> >> > > > > > >> >I'm making progress here, I updated a few libs which >> fixed a >> > > couple >> > > > > of >> > > > > > the >> > > > > > >> >test failures I was seeing locally. Timezones are once >> again >> > > > kicking >> > > > > me >> > > > > > >> >whilst I'm down, for some reason OODT fails badly with >> people >> > in >> > > > > > >> >GMT/BST.... I'll figure it out though. >> > > > > > >> > >> > > > > > >> >On Fri, Jul 1, 2016 at 12:36 AM, Lewis John Mcgibbney < >> > > > > > >> >lewis.mcgibb...@gmail.com <javascript:;>> wrote: >> > > > > > >> > >> > > > > > >> >> Sound ttyl >> > > > > > >> >> On Jun 30, 2016 4:32 PM, "Tom Barber" < >> > tom.bar...@meteorite.bi >> > > <javascript:;>> >> > > > > > wrote: >> > > > > > >> >> >> > > > > > >> >> > Not really, tomoz? >> > > > > > >> >> > >> > > > > > >> >> > On Fri, Jul 1, 2016 at 12:24 AM, Lewis John >> Mcgibbney < >> > > > > > >> >> > lewis.mcgibb...@gmail.com <javascript:;>> wrote: >> > > > > > >> >> > >> > > > > > >> >> > > Want to do a hangout right now? >> > > > > > >> >> > > >> > > > > > >> >> > > On Thu, Jun 30, 2016 at 4:17 PM, Tom Barber < >> > > > > > >> tom.bar...@meteorite.bi <javascript:;>> >> > > > > > >> >> > > wrote: >> > > > > > >> >> > > >> > > > > > >> >> > > > Hey Lewis >> > > > > > >> >> > > > >> > > > > > >> >> > > > I have no idea which branch is current, I >> merged master >> > > > into >> > > > > > >> avrorpc >> > > > > > >> >> > and >> > > > > > >> >> > > it >> > > > > > >> >> > > > merged okay and built so I pushed it back. >> > > > > > >> >> > > > >> > > > > > >> >> > > > Is that the correct branch to be looking at for >> Avro >> > > > Support? >> > > > > > Lets >> > > > > > >> >> > figure >> > > > > > >> >> > > > it all out and get it merged into Master. >> > > > > > >> >> > > > >> > > > > > >> >> > > > Tom >> > > > > > >> >> > > > >> > > > > > >> >> > > >> > > > > > >> >> > > >> > > > > > >> >> > > >> > > > > > >> >> > > -- >> > > > > > >> >> > > *Lewis* >> > > > > > >> >> > > >> > > > > > >> >> > >> > > > > > >> >> >> > > > > > >> >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> > > > -- >> > > > http://home.apache.org/~lewismc/ >> > > > @hectorMcSpector >> > > > http://www.linkedin.com/in/lmcgibbney >> > > > >> > > >> > >> > >> > -- >> > http://home.apache.org/~lewismc/ >> > @hectorMcSpector >> > http://www.linkedin.com/in/lmcgibbney >> > >> >> >> >> > > > -- > http://home.apache.org/~lewismc/ > @hectorMcSpector > http://www.linkedin.com/in/lmcgibbney > -- http://home.apache.org/~lewismc/ @hectorMcSpector http://www.linkedin.com/in/lmcgibbney
