DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Scaling Cloud Data Automation: A Practical Guide to Open Table Formats
  • Ten Years of Beam: From Google's Dataflow Paper to 4 Trillion Events at LinkedIn
  • Data Processing for Real Estate: Enabling Smart Analysis and Decision-Making
  • Hadoop on AmpereOne Reference Architecture

Trending

  • Build a GitHub Slack Bot With AWS Bedrock and MCP, Part 2
  • Detecting Plan Regression in SQL Server Using Query Store
  • Testing AI-Infused Apps: A Dual-Layer Framework for AI Quality Assurance
  • Beyond Manual Annotation: Engineering Self-Correcting Pseudo-Labeling Pipelines
  1. DZone
  2. Data Engineering
  3. Data
  4. Processing Files With Special Language Characters Using Mule 4

Processing Files With Special Language Characters Using Mule 4

Learn several scenarios for files with special characters or language-based characters and the two major connectors that are used while reading files.

By 
Sadik Ali user avatar
Sadik Ali
·
Feb. 28, 22 · Code Snippet
Likes (5)
Comment
Save
Tweet
Share
10.3K Views

Join the DZone community and get the full member experience.

Join For Free

Working with data, there are several scenarios to transform data from input files using the Mule 4 connector.

There are several scenarios for files with special characters or language-based characters.

  • Data will be trimmed in output.
  • Wrong format data will be converted in output.
  • Data for the rest of the row will be moved to unexpected columns.

There are two major connectors that are used while reading files.

  1. File connector: Maximum used while staged-based data processing
  2. SFTP connector: Largely used for reading files from external locations

Scenario 1

Data with special characters like '" "' or HTML tags

Requirement 

Process data to an output file with intact information. 

Sample Input Data 

Includes special characters:

Sample Input Data Scenario 1

Recommended Solution:

Use input connector (File/SFTP) to transform data while reading from input file.

XML
 
<file:read doc:name="Read" doc:id="23facb3c-774e-48a4-817d-21c79a8aa94f" config-ref="File_Config" path="sample.csv" outputMimeType='application/csv; escape="\"\""'/>

Configure the content of file and add escape character configuration in inbound connector configuration.

Scenario 2 

Data with special character like language specific (Latino) or HTML tags

Sample Input Data  

Includes special characters and language specific characters:

Sample Input Data Scenario 2

Recommended Solution  

Find below screenshot for example.

Screenshot of recommended solution

Escape characters and encodings are not fit for all scenarios. We need to validate a specific scenario and configuration to validate input.

Using the above configuration, we would able to transform files with required output format. Also, see MuleSoft SFTP Connector and MuleSoft File Connector for additional reference.

Data processing

Opinions expressed by DZone contributors are their own.

Related

  • Scaling Cloud Data Automation: A Practical Guide to Open Table Formats
  • Ten Years of Beam: From Google's Dataflow Paper to 4 Trillion Events at LinkedIn
  • Data Processing for Real Estate: Enabling Smart Analysis and Decision-Making
  • Hadoop on AmpereOne Reference Architecture

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook