[
https://issues.apache.org/jira/browse/SQOOP-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754122#comment-15754122
]
ASF subversion and git services commented on SQOOP-2983:
--------------------------------------------------------
Commit 7783f85f805d54f8377a438aebffb06593aec858 in sqoop's branch
refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=7783f85 ]
SQOOP-3083: Fixing fault injection targets to work
together with try with resources statements
(introduced in SQOOP-2983)
(Anna Szonyi via Attila Szabo)
> OraOop export has degraded performance with wide tables
> -------------------------------------------------------
>
> Key: SQOOP-2983
> URL: https://issues.apache.org/jira/browse/SQOOP-2983
> Project: Sqoop
> Issue Type: Bug
> Reporter: Attila Szabo
> Assignee: Attila Szabo
> Priority: Critical
> Fix For: 1.4.7
>
> Attachments: SQOOP-2983-5.patch, SQOOP-2983-6.patch,
> SQOOP-2983-7.patch
>
>
> The current version of OraOOP seems to perform very low from performance POV
> when --direct mode turned on (regardless if the partitioned feature is turned
> of).
> Just as a baseline from the current trunk version:
> Inserting 100.000 rows into a 800 column wide Oracle table has 400-600 kb/sec
> with direct mode on my cluster, while the standard oracle driver can produce
> up to 1.2-1.8 mb/sec. (depending on the number of mappers, batch size).
> Inserting 1.000.000 rows into the same table goes up to 800k-1mb/sec with
> OraOOP, however with the standard Oracle connector it's around 3.5mb/sec.
> It seems OraOOP export needs a thorough review and some fixing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
