Charles Earl 2012-12-30, 03:23
Jarek Jarcec Cecho 2012-12-30, 13:24
Charles Earl 2012-12-31, 22:40
first cut of Sqoop 2 was released as a Christmas present . You can download first bits from usual place , documentation is available online .
I would like to stress that this release is really a first cut of the Sqoop2 branch that we've provided to give our users chance to test first usable bits. Goal is to gather feedback and incorporate changes now, when it might be relatively cheap. This release is definitely not a feature complete and might not be as stable as current stable (1.4) branch.
On Mon, Dec 31, 2012 at 05:40:20PM -0500, Charles Earl wrote:
> What is anticipated release date of Sqoop 2?
> On Dec 30, 2012, at 8:24 AM, Jarek Jarcec Cecho wrote:
> > Hi Charles,
> > current stable Sqoop have parameter --password that can be used to specify password on command line and thus you do not need to prompt user for it every time.
> > In Sqoop2 which is major redesign of the project, we will introduce advanced metastore where you will store your credentials to external database system and simply reusing them for particular import and export jobs.
> > Jarcec
> > On Sat, Dec 29, 2012 at 10:23:04PM -0500, Charles Earl wrote:
> >> I believe that the capability to authenticate to the source database via a client is what is proposed in SQOOP-795, https://issues.apache.org/jira/browse/SQOOP-795? So that there is currently no way to authenticate in sqoop without a prompt on each database access.
> >> I assume that in practice for large numbers of transfers secure connection alternatives are custom engineered by users?
> >> C