orc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Gates <alanfga...@gmail.com>
Subject Re: [DISCUSS] ORC 2.0
Date Fri, 04 Aug 2017 22:54:58 GMT
It seems ok to change them in a source and binary compatible way.  +1 to
making upgrades as easy as switching out the jars at runtime.

Alan.

On Fri, Aug 4, 2017 at 3:00 PM, Dain Sundstrom <dain@iq80.com> wrote:

>
> > On Aug 4, 2017, at 2:51 PM, Owen O'Malley <owen.omalley@gmail.com>
> wrote:
> >
> > On Fri, Aug 4, 2017 at 12:15 PM, Alan Gates <alanfgates@gmail.com>
> wrote:
> >
> >> Let me make sure I have the backwards compatibility straight.  If a user
> >> switches to ORC 2.0, he could choose to continue writing in older
> formats
> >> so that his old tools could read it.  Then once all his tools are
> upgraded
> >> he could throw a config switch and new data would be written in the new
> >> format.  Once that switch was thrown, any pre-ORC 2.0 tools would be
> >> unusable.  Before throwing that switch, he would get none of the
> benefits
> >> of ORC 2.0.  Is this summary correct?
> >>
> >
> > Yes, exactly.
>
> I think the important part is not to change the APIs so tools can be
> updated by just upgrading the dep.
>
> -dain

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message