Hi Bogi, Generally I think it's could be a good idea to change the current upgrade concept, and to store the SQL commands in versioned chain of files.
Although I'm a bit concerned about the validation and testing of such a change. I think it would be great if the community could discuss your thoughts in the related topic. If you could share with us how do you plan to ensure that the new approach is working in a robust way ( not having inconsistent behavior in the web of objects ( e.g. NPE, illegal states, illegal arguments ), what to do in case of missing file(s), what to do in case of failing step(s), how do we ensure the system does not end in an inconsistent state, how do we ensure in case of failure the system remains still in a usable state as before, etc. ) that would be awesome. Thanks, Maugli On Oct 12, 2016 5:19 PM, "Boglarka Egyed" <b...@cloudera.com> wrote: > Hi All, > > I would like to reach out to you because I'm currently working on a Sqoop2 > feature development issue related to the repository upgrade mechanism and I > have some open questions for the community which would be great to discuss > before starting the concrete implementation work. > > Please find my questions under the following JIRA ticket: > https://issues.apache.org/jira/browse/SQOOP-3007 > > Every opinion, suggestion or concern would be more than welcome. > > Thank you in advance! > > Best Regards, > Bogi >
