Brock, I just submitted a patch for the issue I was having: https://issues.apache.org/jira/browse/SQOOP-373
-Mark On Fri, Oct 21, 2011 at 2:50 PM, Brock Noland <br...@cloudera.com> wrote: > Hi. > > On Fri, Oct 21, 2011 at 2:46 PM, Mark Roddy <markro...@gmail.com> wrote: >> >> That did the trick. Thanks Brock. > > Great to hear. If the error message wasn't obvious, we should improve the > situation. You might consider filing a JIRA: > https://issues.apache.org/jira/browse/SQOOP > Brock > >> >> On Fri, Oct 21, 2011 at 2:40 PM, Brock Noland <br...@cloudera.com> wrote: >> > Hi, >> > On Fri, Oct 21, 2011 at 1:16 PM, Mark Roddy <markro...@gmail.com> wrote: >> >> >> >> I'm getting a less than useful error message, which I've tracked down >> >> to coming from inside a try/catch where the exception is re-raised if >> >> a certain property is set[1]. >> >> >> >> However, I'm not seeing the stack trace after setting the property. >> >> I'm specifying it on the command line like such: >> >> sqoop import \ >> >> -Dsqoop.throwOnError=1 \ >> >> ... "rest of the command" >> >> >> >> Is that not the accepted way to specify a system property? >> > >> > I am not familiar with that specific option, but that appears to be a >> > system >> > property. To set that System property, this should work: >> > env HADOOP_OPTS="-Dsqoop.throwOnError=1" sqoop >> > >> >> >> >> -Mark >> >> >> >> 1: >> >> } catch (IllegalArgumentException iea) { >> >> LOG.error("Imported Failed: " + iea.getMessage()); >> >> if (System.getProperty(Sqoop.SQOOP_RETHROW_PROPERTY) != null) { >> >> throw iea; >> >> } >> >> return 1; >> > >> > > >
