gobblin-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Abhishek Tiwari <a...@apache.org>
Subject Re: IMPORTANT: Packages migrated to org.apache.gobblin
Date Mon, 31 Jul 2017 08:17:31 GMT
+ user@gobblin

On Mon, Jul 31, 2017 at 1:16 AM, Abhishek Tiwari <abti@apache.org> wrote:

> Hi all,
>
> We have migrated our code to use *org.apache.gobblin* package namespace.
> This includes renaming packages / schemas / namespaces for the following:
>
>    - Java packages
>    - Avro schema and namespaces
>    - RESTLi schema and namespaces
>    - META-INF services
>    - SQL references
>    - Reflection
>    - Alias Resolution
>    - Pull and config files
>    - Config store hierarchy
>    - Default config references
>    - Fully qualified names
>    - Hardcoded class and package names
>    - Powermock / mockito change in exclusion / inclusion params
>    - Build changes to operate on different package structure
>    - Typed references / imports / extension of classes and implementation
>    of interfaces
>    - Shell / launcher scripts
>    - Documentation / Javadocs
>
> What should you expect with this change:
>
>    - This is a *backwards incompatible change*, so please do not expect
>    to seamlessly migrate to the new code base (ie. the main branch and
>    upcoming first Apache release)
>    - Config keys (and their values) should continue to work unless
>    explicitly called out and notified here.
>    - Since class names are using new package names, the config properties
>    that specify the class will need to be updated.
>    - State store written by old code is un-readable by the new code,
>    however, a shim layer to read existing state store or tooling to migrate
>    state store files will be very helpful. There is an open jira for this (
>    GOBBLIN-179 <https://issues.apache.org/jira/browse/GOBBLIN-179> ).
>    Please let me know if you would want to volunteer to work on this?
>    - We have created a new branch: *version-0* that contains the codebase
>    with old package / namespace. Only selective fixes / patches will be
>    back-ported to it (depending on necessity / resource availability), so
>    please do not plan to use it unless absolutely necessary and instead
>    migrate to the latest code base.
>    - If you find anything broken, please feel free to fix and contribute
>    back or atleast create a JIRA to let us know about it.
>
> Regards,
> Abhishek
>

Mime
View raw message