# mulesoft Hadoop (HDFS) Connector - Full Documentation --- product: Hadoop (HDFS) Connector version: 6.0 is-latest-version: true --- # Hadoop (HDFS) Connector > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Hadoop (HDFS) Connector Version 6.0 Anypoint Connector for Hadoop (HDFS) works as a bidirectional gateway between Mule applications and Apache Hadoop Distributed File System (HDFS). You can use the Hadoop (HDFS) Connector to poll the content of a file at a configurable rate or interval, or to manipulate data in an HDFS server. For information about compatibility and fixed issues, see [Hadoop (HDFS) Connector Release Notes](https://docs.mulesoft.com/release-notes/connector/hdfs-connector-release-notes-mule-4) ## Before You Begin To use this connector, you must be familiar with: - Anypoint Connectors - Mule runtime engine (Mule) - Elements in a Mule flow - Global elements - How to create a Mule app using Anypoint Studio Before creating an app, you must have: - Access to the Hadoop (HDFS) target resource and Anypoint Platform - Anypoint Studio version 7.0 or later - A running instance of Hadoop Distributed File System (HDFS) ## Connection Authentication Types Hadoop (HDFS) Connector supports the following connection authentication types: - Kerberos This connection type uses the Kerberos principal as the username. The keytab path you specify obtains a ticket-granting ticket (TGT) from the authorization server. - Simple This connection type passes the name of the node that contains the file system you want to connect to as the default name key. ## Next Step After you complete the prerequisites and experiment with templates and examples, you are ready to create an app with [Anypoint Studio](https://docs.mulesoft.com/hdfs-connector/latest/hdfs-connector-studio). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Hadoop (HDFS) Connector on Exchange](https://www.mulesoft.com/exchange/?search=hdfs&type=connector) - [Salesforce Help](https://help.salesforce.com) --- product: Hadoop (HDFS) Connector version: 6.0 is-latest-version: true --- # Hadoop (HDFS) Connector - Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## Create a Text File in HDFS The following example shows how to use the connector to create a text file in HDFS: 1. In Anypoint Studio, click **File > New > Mule Project**, name the project, and click **Finish**. 2. In the **Mule Palette** search field, type `http`. 3. Drag the **HTTP > Listener** operation to the canvas. 4. In **General** settings, click the green plus sign (+) to the right of **Connector Configuration**. 5. Click **OK** to accept the default settings. 6. In **Path**, enter `/createFile`. 7. In the **Mule Palette** search field, type `hdfs`. 8. Drag the HDFS **Write** operation to the canvas. 9. Set **Path** to `/test.txt` and leave the default values for the other options. This is the path of the file that HDFS creates. 10. Right-click in the project canvas and select **Run project** to start the application. 11. From an HTTP client such as Postman or curl, make a POST request, set the value for `Content-type:plain/text` to `localhost:8081/createFile`, and add the content you want to write as a payload, as shown in the following example: `curl -X POST -H "Content-Type:plain/text" -d "payload to write to file" localhost:8090/createFile` 12. Use an HDFS explorer to verify that the `/test.txt` file exists and contains your content. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: Hadoop (HDFS) Connector version: 6.0 is-latest-version: true --- # Hadoop (HDFS) Connector - XML and Maven Support > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If you manually code a Mule app in XML, either from the Anypoint Studio XML editor or from a text editor, configure access to the connector in your app by adding reference namespace statements to your XML Mule flow and a dependency in the Apache Maven POM file. > [!NOTE] You can avoid this manual process by using Anypoint Studio. When you add the connector in > Studio, Studio automatically populates the XML code with the connector’s namespace and schema > location, and adds a dependency to the `pom.xml` file. ## Add a Reference Namespace Statement for the Connector Paste the following code inside the `mule` tag of the header of your configuration XML: ```xml http://www.mulesoft.org/schema/mule/hdfs http://www.mulesoft.org/schema/mule/hdfs/current/mule-hdfs.xsd ``` This example shows how the namespace statements are placed in the XML: ```xml ``` ## Add a POM File Dependency The Apache Maven `pom.xml` file generated by Anypoint Studio contains Mule app connector dependencies. When you code a Mule app manually, include this XML snippet in your POM file to enable access to this connector: ```xml org.mule.connectors mule-hdfs-connector 6.0.3 mule-plugin ``` Verify that the connector `version` corresponds to the one you are using. To obtain the most up-to-date `pom.xml` file information: 1. Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/). 2. In Exchange, click **Login** and supply your Anypoint Platform username and password. 3. In Exchange, search for `hdfs`. 4. Click **Dependency Snippets**. ## See Also [Salesforce Help](https://help.salesforce.com) --- product: Hadoop (HDFS) Connector version: 6.0 is-latest-version: true --- # HDFS (Hadoop) Connector Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Connector for Hadoop (HDFS) v6.0 Release Notes: [Hadoop (HDFS) Connector Release Notes](https://docs.mulesoft.com/release-notes/connector/hdfs-connector-release-notes-mule-4) ## HDFS Configurations ### Parameters
NameTypeDescriptionDefault ValueRequired

Name

String

The name for this configuration. Connectors reference the configuration with this name.

x

Connection

The connection types to provide to this configuration.

x

Expiration Policy

Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. Mule purges the instances as appropriate.

## Connection Types To access the data in a Hadoop (HDFS) instance, you must authenticate your application’s requests using a supported authentication method. For Hadoop (HDFS) Connector, the following connection authentication types are supported: - [Kerberos](#hdfs_kerberos) - [Simple](#hdfs_simple) ### Kerberos Use the following fields in the Global Element Properties dialog window to configure the **Kerberos** connection type:
NameTypeDescriptionDefault ValueRequired

Username

String

The Kerberos principal. The Username is passed to the HDFS client as the hadoop.job.ugi configuration entry. The Username can be overridden by values you specify in Configuration Resources and Configuration Entries. This parameter is called Username for backward compatibility reasons.

Keytab Path

String

Enter the path to the keytab file associated with the Username you specified. The path is used to obtain a ticket granting ticket (TGT) from the authorization server. If this value is not provided Kerberos looks for a TGT associated with the specified Username within your local Kerberos cache.

Name Node Uri

String

The name of the file system to connect to. The Name Node is passed to the HDFS client as the FileSystem#FS_DEFAULT_NAME_KEY configuration entry. The Name Node can be overridden by values you specify in Configuration Resources and Configuration Entries.

x

Configuration Resources

Array of String

A java.util.List of configuration resource files for the HDFS client to load. You can provide additional configuration files, for example, core-site.xml.

Configuration Entries

Object

A java.util.Map of configuration entries to use by the HDFS client. You can provide additional configuration entries as key-value pairs.

Reconnection

When the application is deployed, a connectivity test is performed on all connectors. If reconnection is enabled, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.

### Simple Use the following fields in the Global Element Properties dialog window to configure the **Simple** connection type:
NameTypeDescriptionDefault ValueRequired

Username

String

User identity that Hadoop uses for permissions in HDFS. When Simple authentication is used, Hadoop requires that the user is set as a system property called HADOOP_USER_NAME. If a value is not provided, Hadoop uses the username of the OS user who is currently logged in.

Name Node Uri

String

The name of the file system to which to connect. The Name Node is passed to the HDFS client as the FileSystem#FS_DEFAULT_NAME_KEY configuration entry. The Name Node can be overridden by values you specify in Configuration Resources and Configuration Entries.

x

Configuration Resources

Array of String

A java.util.List of configuration resource files for the HDFS client to load. You can provide additional configuration files, for example, core-site.xml.

Configuration Entries

Object

A java.util.Map of configuration entries for the HDFS client to use. You can provide additional configuration entries as key-value pairs.

Reconnection

When the application is deployed, a connectivity test is performed on all connectors. If reconnection is enabled, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.

## Operations - [Append](#append) - [Copy From Local File](#copyFromLocalFile) - [Copy To Local File](#copyToLocalFile) - [Delete Directory](#deleteDirectory) - [Delete File](#deleteFile) - [Get Metadata](#getMetadata) - [Glob Status](#globStatus) - [List Status](#listStatus) - [Make Directories](#makeDirectories) - [Read Operation](#readOperation) - [Rename](#rename) - [Set Owner](#setOwner) - [Set Permission](#setPermission) - [Write](#write) ### Associated Sources - [Read](#read) ### Append `` Append the current payload to a file located at the designated path. **Note:** by default the Hadoop server has the append option disabled. To append data to an existing file, refer to the dfs.support.append configuration parameter. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path of the file to write to.

x

Buffer Size

Number

The buffer size to use when appending to the file.

4096

Payload

Binary

The payload to append to the file.

#[payload]

Reconnection Strategy

A retry strategy in case of connectivity errors

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Copy From Local File `` Copy the source file on the local disk to the file system for a target path, set **Delete Source** if the source file should be removed. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Delete Source

Boolean

Whether to delete the source.

false

Overwrite

Boolean

Whether to overwrite destination content.

true

Source

String

The source path in the file system.

x

Destination

String

The target path on the local disk.

x

Reconnection Strategy

A retry strategy in case of connectivity errors

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Copy To Local File `` Copy the source file in the file system to a local disk at the given target path. Set **Delete Source** if the source file should be removed. **Use Raw Local File System** indicates whether to use RawLocalFileSystem as it is a non-CRC file system. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Delete Source

Boolean

Whether to delete the source.

false

Use Raw Local File System

Boolean

Whether to use RawLocalFileSystem as a local file system.

false

Source

String

The source path on the File System.

x

Destination

String

The target path on the local disk.

x

Reconnection Strategy

A retry strategy in case of connectivity errors

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Delete Directory `` Delete the file or directory located at the designated path. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path of the file to delete.

x

Reconnection Strategy

A retry strategy in case of connectivity errors

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Delete File `` Delete the file or directory located at the designated path. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path of the file to delete.

x

Reconnection Strategy

A retry strategy in case of connectivity errors

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Get Metadata `` Get the metadata of a path #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path of the file to delete.

x

Target Variable

String

The name of a variable to store the operation’s output.

Target Value

String

An expression to evaluate against the operation’s output and store the expression outcome in the target variable.

#[payload]

Reconnection Strategy

A retry strategy in case of connectivity errors

#### Output

Type

Metadata

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Glob Status `` Return all the files that match file pattern and are not checksum files. Results are sorted by their names. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path Pattern

String

A regular expression specifying the path pattern.

x

Filter

String

The user supplied path filter

Target Variable

String

The name of a variable to store the operation’s output.

Target Value

String

An expression to evaluate against the operation’s output and store the expression outcome in the target variable.

#[payload]

Reconnection Strategy

A retry strategy in case of connectivity errors

#### Output

Type

Array of File Status

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:RETRY\_EXHAUSTED ### List Status `` List the statuses of the files and directories in the given path if the path is a directory. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The given path

x

Filter

String

The user supplied path filter

Target Variable

String

The name of a variable to store the operation’s output.

Target Value

String

An expression to evaluate against the operation’s output and store the expression outcome in the target variable.

#[payload]

Reconnection Strategy

A retry strategy in case of connectivity errors

#### Output

Type

Array of File Status

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Make Directories `` Make the given file and all non-existent parents into directories. Has the semantics of Unix 'mkdir -p'. Existence of the directory hierarchy is not an error. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path to create one or more directories.

x

Permission

String

The file system permission to use when creating the directories, either in octal or symbolic format (umask).

Reconnection Strategy

A retry strategy in case of connectivity errors.

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Read Operation `` Read the content of a file designated by its path and streams it to the rest of the flow. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path of the file to read.

x

Buffer Size

Number

The buffer size to use when reading the file.

4096

Streaming Strategy

Configure if repeatable streams should be used and their behavior

Target Variable

String

The name of a variable to store the operation’s output.

Target Value

String

An expression to evaluate against the operation’s output and store the expression outcome in the target variable

#[payload]

Reconnection Strategy

A retry strategy in case of connectivity errors.

#### Output

Type

Binary

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Rename `` Renames path target to path destination. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Source

String

The source path to be renamed.

x

Destination

String

New path after rename.

x

Reconnection Strategy

A retry strategy in case of connectivity errors.

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Set Owner `` Set owner of a path for a file or a directory. The Ownername and Groupname cannot both be null. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path of the file or directory to set owner.

x

Ownername

String

If it is null, the original username remains unchanged.

x

Groupname

String

If it is null, the original groupname remains unchanged.

x

Reconnection Strategy

A retry strategy in case of connectivity errors.

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Set Permission `` Set permission of a path, that is, for a file or a directory. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

The path of the file or directory to set permission.

x

Permission

String

The file system permission to be set.

x

Reconnection Strategy

A retry strategy in case of connectivity errors.

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ### Write `` Write the current payload to the designated path, either creating a new file or appending to an existing one. #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Payload

Binary

the payload to write to the file.

#[payload]

Path

String

The path of the file to write to.

x

Permission

String

The file system permission to use if a new file is created, either in octal or symbolic format (umask).

700

Overwrite

Boolean

If a pre-existing file should be overwritten with the new content.

true

Buffer Size

Number

The buffer size to use when appending to the file.

4096

Replication

Number

Block replication for the file.

1

Block Size

Number

The block size to use when appending to the file.

1048576

Owner User Name

String

The username owner of the file.

Owner Group Name

String

The group owner of the file.

Reconnection Strategy

A retry strategy in case of connectivity errors.

### For Configurations [HDFS Configurations](#hdfs) #### Throws - HDFS:CONNECTIVITY - HDFS:INVALID\_REQUEST\_DATA - HDFS:INVALID\_STRUCTURE\_FOR\_INPUT\_DATA - HDFS:RETRY\_EXHAUSTED - HDFS:UNKNOWN ## Sources ### Read `` #### Parameters
NameTypeDescriptionDefault ValueRequired

Configuration

String

The name of the configuration to use.

x

Path

String

Read the content of a file designated by its path

x

Buffer Size

Number

4096

Primary Node Only

Boolean

Whether this source should be executed only on the primary node when running in a cluster.

Streaming Strategy

Configure if repeatable streams should be used and their behavior

Redelivery Policy

Defines a policy for processing the redelivery of the same message.

Reconnection Strategy

A retry strategy in case of connectivity errors.

#### Output

Type

Any

Attributes Type

Any

### For Configurations [HDFS Configurations](#hdfs) ## Types ### Reconnection
FieldTypeDescriptionDefault ValueRequired

Fails Deployment

Boolean

When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy.

Reconnection Strategy

The reconnection strategy to use.

### Reconnect
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often to reconnect (in milliseconds)

Count

Number

The number of reconnection attempts to make

blocking

Boolean

If false, the reconnection strategy runs in a separate, non-blocking thread.

true

### Reconnect Forever
FieldTypeDescriptionDefault ValueRequired

Frequency

Number

How often in milliseconds to reconnect

blocking

Boolean

If false, the reconnection strategy runs in a separate, non-blocking thread.

true

### Expiration Policy
FieldTypeDescriptionDefault ValueRequired

Max Idle Time

Number

A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it’s considered eligible for expiration.

Time Unit

Enumeration, one of:

  • NANOSECONDS

  • MICROSECONDS

  • MILLISECONDS

  • SECONDS

  • MINUTES

  • HOURS

  • DAYS

A time unit that qualifies the maxIdleTime attribute

### Repeatable In Memory Stream
FieldTypeDescriptionDefault ValueRequired

Initial Buffer Size

Number

The amount of memory that will be allocated to consume the stream and provide random access to it. If the stream contains more data than can be fit into this buffer, then the buffer expands according to the bufferSizeIncrement attribute, with an upper limit of maxInMemorySize.

Buffer Size Increment

Number

This is by how much the buffer size expands if it exceeds its initial size. Setting a value of zero or lower means that the buffer should not expand, meaning that a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised when the buffer gets full.

Max Buffer Size

Number

The maximum amount of memory to use. If more than that is used, the STREAM_MAXIMUM_SIZE_EXCEEDED error is raised. A value lower than or equal to zero means no limit.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

The unit in which all these attributes are expressed

### Repeatable File Store Stream
FieldTypeDescriptionDefault ValueRequired

Max In Memory Size

Number

Defines the maximum memory that the stream should use to keep data in memory. If more memory is consumed, content on the disk is buffered.

Buffer Unit

Enumeration, one of:

  • BYTE

  • KB

  • MB

  • GB

The unit in which maxInMemorySize is expressed.

### Redelivery Policy
FieldTypeDescriptionDefault ValueRequired

Max Redelivery Count

Number

The maximum number of times a message can be redelivered and processed unsuccessfully before triggering a process-failed message.

Use Secure Hash

Boolean

Whether to use a secure hash algorithm to identify a redelivered message.

Message Digest Algorithm

String

The secure hashing algorithm to use. If not set, the default is SHA-256.

Id Expression

String

Defines one or more expressions to use to determine when a message has been redelivered. This property can only be set if Use Secure Hash is false.

Object Store

Object Store

The object store where the redelivery counter for each message is stored.

### Metadata
FieldTypeDescriptionDefault ValueRequired

Check Summary

Content Summary

File Status

Path Exists

Boolean

### Check Summary
FieldTypeDescriptionDefault ValueRequired

Bytes Per CRC

Number

Crc Per Block

Number

Md5

String

### Content Summary
FieldTypeDescriptionDefault ValueRequired

Directory Count

Number

File Count

Number

Length

Number

Snapshot Directory Count

Number

Snapshot File Count

Number

Snapshot Length

Number

Snapshot Space Consumed

Number

### File Status
FieldTypeDescriptionDefault ValueRequired

Access Time

Number

Access time of file in milliseconds

Block Replication

Number

Replication factor of file

Block Size

Number

Block size of file

Directory

Boolean

Indicates whether path is a directory

Group

String

Group owner associated with file

Length

Number

Length of file in bytes

Modification Time

Number

Modification time of file in milliseconds

Owner

String

Owner of file

Path

String

Path name

Permission

String

Permission of file as an octal string

Symbolic Link

Boolean

Indicates whether a path is a symbolic link

## See Also [Salesforce Help](https://help.salesforce.com) --- product: Hadoop (HDFS) Connector version: 6.0 is-latest-version: true --- # Using Anypoint Studio to Configure Hadoop (HDFS) Connector > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files. To add and configure a connector in Studio: 1. Create a Mule project. 2. Add the connector to your Mule project 3. Configure an input source for the connector’s flow. 4. Configure global elements for the connector. If you are new to configuring Anypoint Connectors in Studio, see [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio). ## Create a Mule Project In Anypoint Studio, create a new Mule project in which to add and configure the connector. 1. In Anypoint Studio, from the main menu, select **File > New > Mule Project**. 2. Enter a name for your Mule project, and click **Finish**. ## Add the Connector to Your Mule Project Add Hadoop (HDFS) Connector to a Mule project to automatically populate the XML code with the connector’s namespace and schema location, as well as add the required dependencies to the project’s `pom.xml` file. 1. In the **Mule Palette** view, click **(X) Search in Exchange**. 2. In **Add Modules to Project**, type `hdfs` in the search field. 3. Click the name of the connector in **Available modules**. 4. Click **Add**. 5. Click **Finish**. Adding a connector to a Mule project in Studio does not make that same connector available to other projects in your Studio workspace. ## Configure an Input Source An input source initiates a flow when a specified condition is met. The act of dragging the connector’s operation from the palette onto the Anypoint Studio canvas automatically populates the XML code with the connector namespace and schema location. Possible input source operations for this connector are: - Read Starts your app when the content of a file is read and streamed to the rest of the flow. - HTTP Listener Starts your app using a browser or a command such as `curl`. - Scheduler Starts your app at timed intervals. In Studio, drag the input operation you choose from the **Mule Palette** to the **Source** panel in the canvas, and supply the required parameters. For example, the required fields for the `Read` input source are: - Configuration The name of the connector configuration to use - Path The path for the file to read ## Configure a Global Element for the Connector To configure a connector in your Mule app, configure a global element that can be used by all instances of that connector in the flow: 1. In the **Mule Palette** view, search for the connector and select an operation. 2. Drag the operation onto the canvas to the right of the input source. 3. In the configuration screen for the operation, click the plus sign (+) next to the **Connector configuration** field to add a global element for the connector. 4. In the **General** tab, enter a name for the configuration, and select the connection type from **Connection**. Supported connection types for this connector are: - [**Kerberos**](https://docs.mulesoft.com/hdfs-connector/latest/hdfs-connector-reference#hdfs_kerberos) - [**Simple**](https://docs.mulesoft.com/hdfs-connector/latest/hdfs-connector-reference#hdfs_simple) For information about how to configure the connections, see [Connection Types](https://docs.mulesoft.com/hdfs-connector/latest/hdfs-connector-reference#connection_types). You can provide your credentials in the global configuration properties, or you can reference a configuration file that contains those values. To simplify maintenance and improve project reusability, of your project, use a configuration file. Keeping these values in a separate file is useful if you need to deploy to different environments, such as production, development, and QA, where your access credentials differ. See [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview) for more information. 5. Click the **Advanced** tab to specify a reconnection strategy, if supported. 6. Click **Test Connection** to confirm that Mule can connect with the specified server. 7. Click **OK**. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview) - [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio) - [Hadoop (HDFS) Connector Reference](https://docs.mulesoft.com/hdfs-connector/latest/hdfs-connector-reference) - [Salesforce Help](https://help.salesforce.com)