Hola!!. I have a question regarding arrow upgrade to 0.13.1

# arrow

[Alvaro Blazquez checa]

Hola!!. I have a question regarding arrow upgrade to 0.13.1

[Alvaro Blazquez checa]

So far my team have being using arrow 2 years long, more than 10 apps using it. We have also developed 3 libraries used by the other projets.

[Alvaro Blazquez checa]

So question is: if an upgrade is done just to library clients 2 versions of arrow will live along in rumtime. Could this incur into runtime issues?

[Alvaro Blazquez checa]

As a quick guess i have seen that some fully qualified names of packages have changed so no conflicts Will arise. But i am not sure about the full library

[Alvaro Blazquez checa]

All our codebase is dependant on arrow 0.9

[raulraja]

hi @Alvaro Blazquez checa, Having 0.9 and a newer version of Arrow both in the classpath can be problematic because since 0.13 there are binary breaking changes. We are planning on releasing 1.0 at the end of July or in August if all goes well. I recommend you migrate to the latest version or 1.0 when available, that will be a long maintenance release that guarantees no breaking changes.

[thanh]

I recently did Arrow upgrade for some projects and libraries from 0.10.5 to 0.13.2 . The experient was quite pleasant. But I expect more difficulty if you want to update from 0.9 to 0.13.2.

[stojan]

I would add that 0.12 might be a good temporary step, it's basically 0.13 + a bunch of deprecated methods (removed in 0.13)

[Alvaro Blazquez checa]

ok thank you all. My concern was not adapting use of library to new design but having custom libraries using different arrow versions than its clients so that will end up having different arrow versions at runtime in the classpath. As Raul points out it could lead into conflicts so I guess I have to update all codebase at once

[Alvaro Blazquez checa]

I think well do more tests with 0.12 and 0.13 but the effort of upgrading all codebase, well do it with 1.0 as mentioned.