[SQOOP-3032] `setBindValueAtName() may need to be updated to cope with the data-type: 1` in --verbose output fills logs

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.4.6
• Component/s: connectors/oracle

Environment

sqoop export to Oracle

• Assignee: Unassigned
• Reporter: Ruslan Dautkhanov
• Created: 19/Oct/16 19:32
• Updated: 19/Oct/16 19:32

Description

2016-10-18 14:09:54,909 DEBUG [main] org.apache.sqoop.manager.oracle.OraOopOutputFormatBase: setBindValueAtName() may need to be updated to cope with the data-type: 1

was generating tens of Gb of logs on each node so we ran out of free space and a lot of services in CM ran into warning/alert state.

Table had 11 billion rows, and we had to cancel the job and rerun without verbose.

493      } else {
494        // LOB data-types are currently not supported during
495        // a Sqoop Export.
496        // JIRA: SQOOP-117
497        // OraOopConstants.SUPPORTED_EXPORT_ORACLE_DATA_TYPES_CLAUSE
498        // will already have excluded all LOB columns.
499
500        // case oracle.jdbc.OracleTypes.CLOB:
501        // {
502        // oracle.sql.CLOB clob = new
503        // oracle.sql.CLOB(connection);
504        // Object value = fieldMap.get(colName);
505        // //clob.set
506        // statement.setCLOBAtName(bindValueName, clob);
507        // break;
508        // }
509        String msg =
510            String.format(
511                "%s may need to be updated to cope with the data-type: %s",
512                OraOopUtilities.getCurrentMethodName(), column.getOracleType());
513        LOG.debug(msg);

It would be awesome to change that line's LOG.debug(msg) severity to `trace` from `debug`, so we can use --verbose on larger tables.