> ## Documentation Index > Fetch the complete documentation index at: https://www.integrate.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # ETL: HDFS Destination > How to configure the HDFS destination component to write files to a Hadoop Distributed File System cluster in your Integrate.io ETL pipeline. The HDFS destination writes pipeline output to a Hadoop Distributed File System cluster. It supports CSV, TSV, JSON, Parquet, and Fixed width output formats, with optional compression and PGP encryption. Once your connection is set up, see [File Storage Options](/docs/etl/file-storage-options) for the full set of write options (output formats, compression, PGP, and more) shared across every file storage provider. ## Connection Setup See [HDFS Source](/docs/etl/using-components-hdfs-source#connection-setup) for steps to create and configure an HDFS connection in Integrate.io ETL, including HttpFS gateway requirements. *** ## Destination Configuration ### Connection Select your HDFS connection from the dropdown, or create a new one. ### Target Directory The path on the HDFS cluster where output files will be written. One or more files are created in this directory. By default, the job fails if the directory already exists. Use [package variables](/docs/etl/using-and-setting-variables-in-your-packages) to generate unique directory names per run (e.g. `/output/${_JOB_ID}`). HDFS has no bucket or container field. The path is relative to the HDFS root. *** ## FAQ **Which destination actions are available for HDFS?** All five destination actions are available: fail if exists, delete and recreate, replace files, copy to existing directory (with character encoding), and copy to new directory. **Can I write to a different HDFS cluster than the one I read from?** Yes. The source and destination components each have their own connection. You can use different clusters or paths. *** ## Related