mirror of
https://github.com/apache/sqoop.git
synced 2025-05-12 06:51:09 +08:00
SQOOP-2881: Sqoop2: EnrichOraOop Connector resource file
(Jarek Jarcec Cecho via Abraham Fine)
This commit is contained in:
Abraham Fine
parent
ee42b1028f
commit
bfcfedfa7d
@ -13,130 +13,160 @@
|
||||
# See the License for the specific language governing permissions and
|
||||
# limitations under the License.
|
||||
|
||||
# Oracle JDBC Connector Resources
|
||||
############################
|
||||
# Connection Config
|
||||
#
|
||||
connector.name = Oracle connector
|
||||
|
||||
connectionConfig.label = Oracle connection configuration
|
||||
connectionConfig.help = You must supply the information requested in order to \
|
||||
create an Oracle connection object.
|
||||
connectionConfig.help = Information required to connect to an Oracle server.
|
||||
|
||||
# connect string
|
||||
connectionConfig.connectionString.label = JDBC connection string
|
||||
connectionConfig.connectionString.help = Enter the value of JDBC connection string to be \
|
||||
used by this connector for creating Oracle connections.
|
||||
connectionConfig.connectionString.label = Connection string
|
||||
connectionConfig.connectionString.example = jdbc:oracle:thin:@oracle.sqoop.org:1521:sqoop_db
|
||||
connectionConfig.connectionString.help = JDBC connection string associated with your Oracle database.
|
||||
|
||||
# username string
|
||||
connectionConfig.username.label = Username
|
||||
connectionConfig.username.help = Enter the username to be used for connecting to the \
|
||||
database.
|
||||
connectionConfig.username.example = sqoop-user
|
||||
connectionConfig.username.help = Username to be used for connection to the Oracle server.
|
||||
|
||||
# password string
|
||||
connectionConfig.password.label = Password
|
||||
connectionConfig.password.help = Enter the password to be used for connecting to the \
|
||||
database.
|
||||
connectionConfig.password.label = Sup3rS3rcr3t!
|
||||
connectionConfig.password.help = Password to be used for connection to the Oracle server.
|
||||
|
||||
# jdbc properties
|
||||
connectionConfig.jdbcProperties.label = JDBC connection properties
|
||||
connectionConfig.jdbcProperties.help = Enter any JDBC properties that should be \
|
||||
supplied during the creation of connection.
|
||||
connectionConfig.jdbcProperties.label = Connection properties
|
||||
connectionConfig.jdbcProperties.example = defaultRowPrefetch=1000
|
||||
connectionConfig.jdbcProperties.help = Key-value pairs that should be passed down to JDBC driver when establishing connection.
|
||||
|
||||
connectionConfig.timeZone.label = Session time zone
|
||||
connectionConfig.timeZone.help = timeZone
|
||||
connectionConfig.timeZone.label = Time zone
|
||||
connectionConfig.timeZone.example = GMT
|
||||
connectionConfig.timeZone.help = Time zone that will be used for all created sessions.
|
||||
|
||||
connectionConfig.actionName.label = Session action name
|
||||
connectionConfig.actionName.help = actionName
|
||||
connectionConfig.actionName.example = sqoop-import
|
||||
connectionConfig.actionName.help = The connector will call DMS_APPLICATION_INFO.SET_MODULE procedure with action_name set to this value.
|
||||
|
||||
connectionConfig.fetchSize.label = JDBC fetch size
|
||||
connectionConfig.fetchSize.help = fetchSize
|
||||
connectionConfig.fetchSize.label = fetch size
|
||||
connectionConfig.fetchSize.example = 1000
|
||||
connectionConfig.fetchSize.help = Optional hint specifying requested JDBC fetch size.
|
||||
|
||||
connectionConfig.initializationStatements.label = Session initialization statements
|
||||
connectionConfig.initializationStatements.help = initializationStatements
|
||||
connectionConfig.initializationStatements.label = Initialization statements
|
||||
connectionConfig.initializationStatements.example = alter session disable parallel query
|
||||
connectionConfig.initializationStatements.help = List of statements that will be executed on each connection immediately after opening and before any metadata/data retrieving queries.
|
||||
|
||||
connectionConfig.jdbcUrlVerbatim.label = Use JDBC connection string verbatim
|
||||
connectionConfig.jdbcUrlVerbatim.help = jdbcUrlVerbatim
|
||||
connectionConfig.jdbcUrlVerbatim.label = Strict connection string
|
||||
connectionConfig.jdbcUrlVerbatim.example = false
|
||||
connectionConfig.jdbcUrlVerbatim.help = By default, OraOop will use specified connection string only to retrieve all instances of your RAC and \
|
||||
then for actual data transfer jobs will generate connection strings to distribute the load across all nodes. This distribution can be turned \
|
||||
off by setting this property to false.
|
||||
|
||||
connectionConfig.racServiceName.label = RAC service name
|
||||
connectionConfig.racServiceName.help = racServiceName
|
||||
connectionConfig.racServiceName.example = sales.sqoop.org
|
||||
connectionConfig.racServiceName.help = Service name that will be used for automatically generated connection strings when connecting to RAC.
|
||||
|
||||
# ToJob Config
|
||||
#
|
||||
toJobConfig.label = To database configuration
|
||||
toJobConfig.help = You must supply the information requested in order to create \
|
||||
the TO part of the job object.
|
||||
|
||||
# To table name
|
||||
toJobConfig.label = Database target
|
||||
toJobConfig.help = Describes target destination and way how data should be persisted on the RDBMS system.
|
||||
|
||||
toJobConfig.tableName.label = Table name
|
||||
toJobConfig.tableName.help = Table name to write data into
|
||||
toJobConfig.tableName.example = target_table
|
||||
toJobConfig.tableName.help = Destination table name to store transfer results.
|
||||
|
||||
toJobConfig.columns.label = Columns
|
||||
toJobConfig.columns.help = Columns
|
||||
toJobConfig.columns.example = id,text,city
|
||||
toJobConfig.columns.help = Subset of columns that will will be written to. Omitted columns have to either allow \
|
||||
NULL values or have defined default value.
|
||||
|
||||
toJobConfig.templateTable.label = Template table name
|
||||
toJobConfig.templateTable.help = templateTable
|
||||
toJobConfig.templateTable.example = existing_table
|
||||
toJobConfig.templateTable.help = If this field is not empty, then target table will get created with the same structure as the \
|
||||
template table.
|
||||
|
||||
toJobConfig.partitioned.label = Partitioned
|
||||
toJobConfig.partitioned.help = partitioned
|
||||
toJobConfig.partitioned.example = true
|
||||
toJobConfig.partitioned.help = If creating a new target table with structure from template table, this option controls whether \
|
||||
the new table should be partitioned or not.
|
||||
|
||||
toJobConfig.nologging.label = Nologging
|
||||
toJobConfig.nologging.help = nologging
|
||||
toJobConfig.nologging.example = Nologging
|
||||
toJobConfig.nologging.help = If creating a new target table with structure from template table, when set to true, this option will \
|
||||
add NOLOGGING clause to the CREATE TABLE statement.
|
||||
|
||||
toJobConfig.updateKey.label = Update key columns
|
||||
toJobConfig.updateKey.help = updateKey
|
||||
toJobConfig.updateKey.label = Update columns
|
||||
toJobConfig.updateKey.example = id,date
|
||||
toJobConfig.updateKey.help = Specifying this option will switch OraOop to update mode. Instead of generating INSERT statements to \
|
||||
insert data to Oracle, it will generate UPDATE statements. Configured options will then be used in WHERE clause.
|
||||
|
||||
toJobConfig.updateMerge.label = Merge updates
|
||||
toJobConfig.updateMerge.help = updateMerge
|
||||
toJobConfig.updateMerge.example = true
|
||||
toJobConfig.updateMerge.help = Instead of generating only UPDATE statements, OraOop will generate MERGE statement that will do so \
|
||||
called upsert - will either update existing rows or insert new rows.
|
||||
|
||||
toJobConfig.dropTableIfExists.label = Drop table if exists
|
||||
toJobConfig.dropTableIfExists.help = dropTableIfExists
|
||||
toJobConfig.dropTableIfExists.label = Drop table
|
||||
toJobConfig.dropTableIfExists.example = true
|
||||
toJobConfig.dropTableIfExists.help = If set to true then, then OraOop will drop existing target table and re-create it using the \
|
||||
template table structure.
|
||||
|
||||
toJobConfig.storageClause.label = Template table storage clause
|
||||
toJobConfig.storageClause.help = storageClause
|
||||
toJobConfig.storageClause.label = Template storage clause
|
||||
toJobConfig.storageClause.example = STORAGE (INITIAL 100K NEXT 50K MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 5)
|
||||
toJobConfig.storageClause.help = If target table will get created, insert specified storage clause to the CREATE TABLE statement.
|
||||
|
||||
toJobConfig.temporaryStorageClause.label = Temporary table storage clause
|
||||
toJobConfig.temporaryStorageClause.help = temporaryStorageClause
|
||||
toJobConfig.temporaryStorageClause.label = Temporary storage clause
|
||||
toJobConfig.temporaryStorageClause.example = STORAGE (INITIAL 100K NEXT 50K MINEXTENTS 1 MAXEXTENTS 50 PCTINCREASE 5)
|
||||
toJobConfig.temporaryStorageClause.help = Storage clause that will be used for all temporary tables that OraOop might need to create.
|
||||
|
||||
toJobConfig.appendValuesHint.label = Append values hint usage
|
||||
toJobConfig.appendValuesHint.help = appendValuesHint
|
||||
toJobConfig.appendValuesHint.label = Append values hint
|
||||
toJobConfig.appendValuesHint.example = AUTO
|
||||
toJobConfig.appendValuesHint.help = Specifies whether generated INSERT queries should take advantage of Oracle's APPEND hint.
|
||||
|
||||
toJobConfig.parallel.label = Parallel
|
||||
toJobConfig.parallel.help = parallel
|
||||
toJobConfig.parallel.example = true
|
||||
toJobConfig.parallel.help = When moving data from temporary tables, this option controls whether generated queries shoud include \
|
||||
PARALLEL keyword.
|
||||
|
||||
# FromJob Config
|
||||
#
|
||||
fromJobConfig.label = From Oracle configuration
|
||||
fromJobConfig.help = You must supply the information requested in order to create \
|
||||
the FROM part of the job object.
|
||||
|
||||
fromJobConfig.label = Database source
|
||||
fromJobConfig.help = Specifies source and way how the data should be fetched from source database.
|
||||
|
||||
fromJobConfig.tableName.label = Table name
|
||||
fromJobConfig.tableName.help = tableName
|
||||
fromJobConfig.tableName.example = input_table
|
||||
fromJobConfig.tableName.help = Input table name from from which data will be retrieved.
|
||||
|
||||
fromJobConfig.columns.label = Columns
|
||||
fromJobConfig.columns.help = Columns
|
||||
fromJobConfig.columns.example = id,text,city
|
||||
fromJobConfig.columns.help = Subset of columns that should be retrieved from source table.
|
||||
|
||||
fromJobConfig.consistentRead.label = Consistent read
|
||||
fromJobConfig.consistentRead.help = consistentRead
|
||||
fromJobConfig.consistentRead.example = true
|
||||
fromJobConfig.consistentRead.help = If true, connector will use Oracle Flashback technology to achieve consistency across \
|
||||
independent connections.
|
||||
|
||||
fromJobConfig.consistentReadScn.label = Consistent read SCN
|
||||
fromJobConfig.consistentReadScn.help = consistentReadScn
|
||||
fromJobConfig.consistentReadScn.example = 10093466
|
||||
fromJobConfig.consistentReadScn.help = Optional SCN value that should be used to read the consistent point in time. Connector \
|
||||
will use latest value during initialization if not specified.
|
||||
|
||||
fromJobConfig.partitionList.label = Partitions
|
||||
fromJobConfig.partitionList.help = partitionList
|
||||
fromJobConfig.partitionList.example = PART1,PART2
|
||||
fromJobConfig.partitionList.help = Subset of partitions that should be retrieved from source table.
|
||||
|
||||
fromJobConfig.dataChunkMethod.label = Data chunk method
|
||||
fromJobConfig.dataChunkMethod.help = dataChunkMethod
|
||||
fromJobConfig.dataChunkMethod.example = ROWID
|
||||
fromJobConfig.dataChunkMethod.help = Method that will be used to slice the data in source table to transfer them in parallel.
|
||||
|
||||
fromJobConfig.dataChunkAllocationMethod.label = Data chunk allocation method
|
||||
fromJobConfig.dataChunkAllocationMethod.help = dataChunkAllocationMethod
|
||||
fromJobConfig.dataChunkAllocationMethod.example = ROUNDROBIN
|
||||
fromJobConfig.dataChunkAllocationMethod.help = Specific way in which various data chunks gets distributed to partitions.
|
||||
|
||||
fromJobConfig.whereClauseLocation.label = Where clause location
|
||||
fromJobConfig.whereClauseLocation.help = whereClauseLocation
|
||||
fromJobConfig.whereClauseLocation.label = Where clause
|
||||
fromJobConfig.whereClauseLocation.example = SUBSPLIT
|
||||
fromJobConfig.whereClauseLocation.help = Determines whether the where clause should be used inside each data chunk separately \
|
||||
or for union of all chunks that are selected in single partition.
|
||||
|
||||
fromJobConfig.omitLobColumns.label = Omit LOB columns
|
||||
fromJobConfig.omitLobColumns.help = omitLobColumns
|
||||
fromJobConfig.omitLobColumns.example = true
|
||||
fromJobConfig.omitLobColumns.help = If set to true, then OraOop will ignore importing all LOB based columns (CLOB, BLOB).
|
||||
|
||||
fromJobConfig.queryHint.label = Query hint
|
||||
fromJobConfig.queryHint.help = queryHint
|
||||
fromJobConfig.queryHint.example = ALL_ROWS
|
||||
fromJobConfig.queryHint.help = Hints that should be used for queries that are transferring data.
|
||||
|
||||
fromJobConfig.conditions.label = Conditions
|
||||
fromJobConfig.conditions.help = conditions
|
||||
fromJobConfig.conditions.example = id > 100
|
||||
fromJobConfig.conditions.help = Additional conditions that should be used inside WHERE clause to limit imported data.
|
||||
Loading…
Reference in New Issue
Block a user