Nope. Me and Chris were working on getting Avro stuff to work. And made
avro the default [1].
See the corresponding thread in dev list [2].

[1]
https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/filemgr.properties#L21
[2]
https://lists.apache.org/thread.html/162044a283b80ed00156e4cf9ba94d788623c713cf1aeaf3cfc07a7e@<dev.oodt.apache.org>

On Wed, 18 Sep 2019 at 14:34, Tom Barber <t...@spicule.co.uk> wrote:

> I thought Avro was the 2.0 default?
>
>
> On 18 September 2019 at 04:16:20, Imesha Sudasingha (ime...@apache.org)
> wrote:
>
> Hi Tom & Chris,
>
> I was thinking the same. Since we can get some support from the GSoC
> students as well, we will be able to get over the line.
>
> @Chris,
> If we can get this [1] PR merged to DRAT (there are some conflicts since
> it
> has been there fore over 1 year :-D), DRAT can be released with Avro
> support. Our intention was to make Avro the default in OODT 1.9 and make
> DRAT 1.0 work with OODT 1.9. I think we can still do that.
> What do you think?
>
> [1] https://github.com/apache/drat/pull/130
>
> On Wed, 18 Sep 2019 at 01:55, Chris Mattmann <mattm...@apache.org> wrote:
>
> > Perfect looking forward to reviewing it along with DRAT 1.0. Though on
> the
> > DRAT side
> >
> > CC’ing them BTW I think we should ship 1.x DRAT with OODT 1.9.x…and then
> > DRAT 2.x should
> > be with Avro and the new stuff.
> >
> >
> >
> > Cheers,
> >
> > Chris
> >
> >
> >
> >
> >
> >
> >
> > From: Tom Barber <t...@spicule.co.uk>
> > Reply-To: <dev@oodt.apache.org>
> > Date: Tuesday, September 17, 2019 at 12:46 PM
> > To: <dev@oodt.apache.org>
> > Subject: OODT 1.9 / 2.0
> >
> >
> >
> > Hey folks,
> >
> >
> >
> > I’ve finally cleared my decks of a bunch of stuff taking up too much of
> my
> >
> > time, with that done, I’d like to volunteer to be the RM for 1.9 and
> >
> > following that a 2.0 release.
> >
> >
> >
> > If no one objects I’ll start working to a 1.9 release next week so we
> can
> >
> > ship DRAT as well and get them both out the door.
> >
> >
> >
> > Tom
> >
> >
> >
> > --
> >
> >
> >
> >
> >
> > Spicule Limited is registered in England & Wales. Company Number:
> >
> > 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> >
> > Road, Brighton, England, BN1 6AF. VAT No. 251478891.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > All engagements
> >
> > are subject to Spicule Terms and Conditions of Business. This email and
> > its
> >
> > contents are intended solely for the individual to whom it is addressed
> > and
> >
> > may contain information that is confidential, privileged or otherwise
> >
> > protected from disclosure, distributing or copying. Any views or
> opinions
> >
> > presented in this email are solely those of the author and do not
> >
> > necessarily represent those of Spicule Limited. The company accepts no
> >
> > liability for any damage caused by any virus transmitted by this email.
> If
> >
> > you have received this message in error, please notify us immediately by
> >
> > reply email before deleting it from your system. Service of legal notice
> >
> > cannot be effected on Spicule Limited by email.
> >
> >
> >
> >
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
> All engagements are subject to Spicule Terms and Conditions of Business.
> This email and its contents are intended solely for the individual to whom
> it is addressed and may contain information that is confidential,
> privileged or otherwise protected from disclosure, distributing or copying.
> Any views or opinions presented in this email are solely those of the
> author and do not necessarily represent those of Spicule Limited. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email. If you have received this message in error, please notify us
> immediately by reply email before deleting it from your system. Service of
> legal notice cannot be effected on Spicule Limited by email.
>

Reply via email to