Sounds good. Let us do the commit of Sqoop-1493. There is also quite a few functionality updates (phoenix, hive-merge etc). I am doing these review by this Friday.
And I heard couple of folks interested in doing the release management of this. Hopefully we can do the community RM model again. Thanks Venkat On 1/26/16, 7:36 AM, "Jarek Jarcec Cecho" <[email protected] on behalf of [email protected]> wrote: >You read my mind Venkat. Just yesterday I’ve started going through the review >queue as there is quite large number of pending reviews (~25). Any reviews >will be greatly appreciated! > >Looking through the review queue, it seems that SQOOP-1493 is done and waiting >on upstream Avro 1.8.0 release. We have few other patches that are waiting on >committing this one (for example SQOOP-2666). Hence I’m wondering if there is >any concern with me committing SQOOP-1493 and unblocking progress on the >subsequent patches? Avro 1.8.0 is not released yet, so it would use the >snapshot dependency for now and I would create blocker to upgrade the version >to final 1.8.0 when it will be available. > >Jarcec > >> On Jan 25, 2016, at 5:23 PM, Venkat Ranganathan >> <[email protected]> wrote: >> >> There are quite a few contributions targeted to 1.4.7. And it has been a >> few months since we release 1.4.6. So, I am proposing that we have a hack >> day dedicated to Sqoop 1.x >> >> Thoughts? >> >> Venkat > >
