Thanks David,
Very valuable input. Will update the group with my findings.
Regards
Sunita
On Monday, November 11, 2013, David Morel wrote:
> On 12 Nov 2013, at 0:01, Sunita Arvind wrote:
>
> Just in case this acts as a workaround for someone:
>> The issue is resolved if I eliminate the "where"
Thanks Jarcec. You are right the map task log is what I am looking for but
I don't see it. The warning just below the 'caused by' line indicates its
not set up right.
I'll redirect the query to sqoop user group. Please let me know if you have
any pointers to get the map task log.
Sunita
On Monda
On 12 Nov 2013, at 0:01, Sunita Arvind wrote:
Just in case this acts as a workaround for someone:
The issue is resolved if I eliminate the "where" clause in the query
(just
keep "where $CONDITIONS"). So 2 workarounds I can think of now are:
1. Create views in Oracle and query without the where
Hi Sunita,
Sqoop specific questions are better asked on Sqoop user mailing list
u...@sqoop.apache.org. You can find instructions how to subscribe to that at
[1].
I would suggest to take a look into the failed map task log as that log usually
contain entire exception including all the chained ex
Just in case this acts as a workaround for someone:
The issue is resolved if I eliminate the "where" clause in the query (just
keep "where $CONDITIONS"). So 2 workarounds I can think of now are:
1. Create views in Oracle and query without the where clause in the sqoop
import command
2. Import every
