Skip to main content
Version: 1.3 (Latest)

FASTBCP_DBPARTITION_TARGET_MODE

Overview​

The FASTBCP_DBPARTITION_TARGET_MODE environment variable controls how the files produced by the DBPartition parallel method are named and laid out.

DBPartition runs one extraction per native partition / subpartition of the source table. Each extraction writes its own file, either as a numbered chunk (CHUNK) or in a Hive-style directory named after the partition (HIVE).

Syntax​

$env:FASTBCP_DBPARTITION_TARGET_MODE = "HIVE"

Configuration​

PropertyValue
TypeCHUNK / HIVE
DefaultCHUNK
Applies to-m DBPartition
SinceFastBCP 1.3

Modes​

CHUNK (default)​

Each partition is written as a numbered chunk next to the target file:

<file>_chunk_NNN.<ext>

For example, with --fileoutput "orders.parquet":

orders_chunk_001.parquet
orders_chunk_002.parquet
orders_chunk_003.parquet

HIVE​

Each partition is written into a Hive-style directory named after the partition, and the subpartition when there is one:

partition=<p>/[subpartition=<sp>/]<file>.<ext>

Some sources use their own directory naming:

SourceDirectory layout
SQL Serverbounds=<lower>_<upper>/<file>.<ext>
TeradataL1=<n>/[L2=<n>/]<file>.<ext>
PostgreSQL, Oracle, MySQLpartition=<p>/[subpartition=<sp>/]<file>.<ext>

For example, an Oracle table partitioned by month, with --fileoutput "orders.parquet":

partition=ORDERS_2024_01/orders.parquet
partition=ORDERS_2024_02/orders.parquet
partition=ORDERS_2024_03/orders.parquet
tip

The HIVE layout can be read directly as a partitioned dataset by engines such as Spark, DuckDB, Trino or Athena.

--merge works in both modes.

Example​

$env:FASTBCP_DBPARTITION_TARGET_MODE = "HIVE"

.\FastBCP.exe `
--connectiontype oraodp `
--server "dbserver:1521/ORCLPDB" `
--user "FastUser" `
--password "FastPassword" `
--sourceschema "SALES" `
--sourcetable "ORDERS" `
--directory "D:\export\orders" `
--fileoutput "orders.parquet" `
--parallelmethod DBPartition `
--paralleldegree 8 `
--merge false
Copyright © 2026 Architecture & Performance.