Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyGOBBLIN-164

Package Rename

Status

In Progress

Steps

  1. Rename packages and schema namespaces from gobblin and com.linkedin.gobblin to org.apache.gobblin 
    The entities to take care of: 
    • 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
  2. The existing configuration will continue to remain the same so that no migration is required for it. 
  3. The class names will have new packages, so users will have to rename them in configs; and custom implementations will have to be updated. 
  4. The state-store will be unreadable with new changes, so we would need a shim for that. 
  5. Two versions must be maintained (previous major version v0.x for gobblin / com.linkedin.gobblin namespace and v1.x for org.apache.gobblin)

Jiras

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyGOBBLIN-178

Notes

Email to send out on Google Groups announcing the migration 

...