[
https://issues.apache.org/jira/browse/GOBBLIN-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Tiwari updated GOBBLIN-39:
-----------------------------------
Fix Version/s: 0.12
> JobHistoryDB migration files have been incorrectly modified
> -----------------------------------------------------------
>
> Key: GOBBLIN-39
> URL: https://issues.apache.org/jira/browse/GOBBLIN-39
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Joel Baranick
> Fix For: 0.12
>
>
> The flyway DB migration files cannot be changed after they are committed. If
> you need to make a schema change they need to be done in a newly versioned
> file. The way these changes have been made screw up the migration:
> 58389c95dc00b23cb1c63ce88a18be9239aa465e,
> a4dbf76d17c39f8282d3b765c32de61f2eb23404,
> 82678450952a7de194b810dbd82cd0c5b4752e63.
> Changing previous migration files changes the checksums. The flyway
> migration then fails because of the differing checksums. This check is here
> to ensure that flyway can always know what changes, and in what order, need
> to be applied. The DB migration is done by running:
> `./historystore-manager.sh migrate -Durl=jdbc:mysql://<SERVER>/gobblin
> -Duser=<USER> -Dpassword=<PASSWORD>`.
> More details can be found in:
> https://github.com/linkedin/gobblin/tree/master/gobblin-metastore/src/main/resources
> As a short term work around, the following can be added to the migration
> command: `-DvalidateOnMigrate=false`. This removes much of the safety net,
> but allows the changes to be processed. Please don't rely on this mechanism.
>
> *Github Url* : https://github.com/linkedin/gobblin/issues/1823
> *Github Reporter* : [~jbaranick]
> *Github Created At* : 2017-05-02T00:27:27Z
> *Github Updated At* : 2017-05-02T00:27:27Z
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
