Why sort and uniq in pipelines in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if you could clean messy lists in seconds instead of hours?

The Scenario

Imagine you have a long list of names written on paper, some repeated many times. You want to find out which names appear only once and organize them alphabetically. Doing this by hand means reading each name, remembering if you saw it before, and then rewriting the list in order.

The Problem

Manually checking for duplicates and sorting is slow and tiring. You might miss some repeats or make mistakes when ordering. If the list grows, it becomes impossible to handle without errors or frustration.

The Solution

Using sort and uniq in a pipeline automates this work. sort arranges the list alphabetically, and uniq removes duplicates easily. Together, they quickly give you a clean, ordered list without any repeats.

Before vs After

✗ Before

cat names.txt
# Then manually sort and remove duplicates on paper

✓ After

cat names.txt | sort | uniq

What It Enables

This lets you quickly clean and organize data, making it easy to analyze or share without errors.

Real Life Example

Suppose you collect email addresses from a signup form. Using sort | uniq helps you find unique emails and sort them before sending a newsletter.

Key Takeaways

Manual sorting and duplicate removal is slow and error-prone.

sort and uniq automate organizing and cleaning lists.

They save time and reduce mistakes in data handling.

Practice

1. What is the main purpose of using sort | uniq together in a bash pipeline?

easy

A. To get a sorted list with duplicates removed

B. To count the number of lines in a file

C. To sort lines but keep duplicates

D. To find the longest line in a file

Solution

1. Step 1: Understand what sort does

   The sort command arranges lines in alphabetical or numerical order.

2. Step 2: Understand what uniq does after sorting

   The uniq command removes duplicate adjacent lines, so sorting first groups duplicates together for removal.

3. Final Answer:

   To get a sorted list with duplicates removed -> Option A

4. Quick Check:

   sort + uniq = sorted unique lines [OK]

Hint: Always sort before uniq to remove all duplicates [OK]

Common Mistakes:

• Using uniq before sort, which misses duplicates
• Thinking uniq counts lines instead of removing duplicates
• Assuming sort removes duplicates by itself

2. Which of the following is the correct syntax to remove duplicate lines from file.txt and sort the output?

easy

A. uniq file.txt | sort

B. sort file.txt | uniq

C. sort | uniq file.txt

D. uniq | sort file.txt

Solution

1. Step 1: Identify correct command order

   The file must be sorted first, so sort file.txt comes before uniq.

2. Step 2: Check syntax correctness

   sort file.txt | uniq correctly pipes sorted output to uniq for duplicate removal.

3. Final Answer:

   sort file.txt | uniq -> Option B

4. Quick Check:

   sort first, then uniq = correct syntax [OK]

Hint: Pipe sorted output into uniq: sort file | uniq [OK]

Common Mistakes:

• Placing uniq before sort, which fails to remove all duplicates
• Incorrect pipe placement causing syntax errors
• Trying to pass file as argument to uniq instead of sort

3. Given a file names.txt with contents:

bob
alice
bob
carol
alice
bob

What is the output of sort names.txt | uniq?

medium

A. alice
bob
bob
carol
alice
bob

B. bob
alice
carol

C. bob
carol
alice

D. alice
bob
carol

Solution

1. Step 1: Sort the file contents

   Sorting lines alphabetically gives: alice, alice, bob, bob, bob, carol.

2. Step 2: Apply uniq to remove duplicates

   Uniq removes repeated adjacent lines, resulting in: alice, bob, carol.

3. Final Answer:

   alice\nbob\ncarol -> Option D

4. Quick Check:

   sort + uniq = unique sorted lines [OK]

Hint: Sort first to group duplicates, then uniq removes repeats [OK]

Common Mistakes:

• Not sorting first, so uniq misses duplicates
• Expecting original order instead of sorted
• Confusing uniq output with counting duplicates

4. You run uniq file.txt | sort to remove duplicates and sort lines, but duplicates remain. What is the likely problem?

medium

A. uniq only removes adjacent duplicates, so sorting after uniq misses duplicates

B. sort command is not working without options

C. file.txt is empty, so no output

D. uniq requires -c option to remove duplicates

Solution

1. Step 1: Understand uniq behavior

   Uniq removes only adjacent duplicate lines, so if duplicates are scattered, it won't remove them.

2. Step 2: Analyze command order effect

   Sorting after uniq means duplicates are not grouped before uniq runs, so duplicates remain.

3. Final Answer:

   uniq only removes adjacent duplicates, so sorting after uniq misses duplicates -> Option A

4. Quick Check:

   uniq needs sorted input to remove all duplicates [OK]

Hint: Sort before uniq to group duplicates for removal [OK]

Common Mistakes:

• Thinking uniq removes all duplicates regardless of order
• Believing sort alone removes duplicates
• Using uniq -c instead of uniq for removal

5. You have a log file access.log with many repeated IP addresses scattered randomly. You want a sorted list of unique IPs. Which command pipeline correctly achieves this?

hard

A. cat access.log | uniq | sort

B. uniq access.log | sort

C. sort -u access.log

D. uniq access.log | sort -u

Solution

1. Step 1: Understand sort -u option

   sort -u sorts and removes duplicates in one step efficiently.

2. Step 2: Why others fail

   Options A, B, and D all apply uniq before sorting, missing non-adjacent duplicates since IPs are scattered randomly.

3. Final Answer:

   sort -u access.log -> Option C

4. Quick Check:

   sort -u = sorted unique lines in one command [OK]

Hint: Use sort -u for sorted unique lines in one step [OK]

Common Mistakes:

• Using uniq before sort, missing duplicates
• Not knowing sort -u combines sorting and uniqueness
• Using unnecessary cat command