Shell Programming and Scripting

grep -f searches thru the entire small file for each line of input from the bigfile.
Some grep implementations map the -f file into memory. This peeds up traversing the -f dataset.

Hi. sorry to come back to this a day later, but I've found that the awk doesn't capture all the lines that I wanted.

I abbreviated the ids I gave you but I adjusted for that in the script you gave me.

The files look like this.

Id and property:
HELIUM:7:100:1000:1007#0/1 abbaabbbbb

Id only
:7:100:1000:1586#0/1

The code I used was

Code:

awk -F':'  ' FILENAME=="ids_to_purge.txt" {arr[$2 $3 $4 $5]++}
    FILENAME=="id_property.txt" {tmp=$2 $3 $4 $5; if(tmp in arr) {next}; print $0 }
    ' ids_to_purge.txt id_property.txt >  output.txt

Since we've used the ":" at the field delim, wont the tab and property be at the end of $5 in tmp? Thus the match wont be found.

I'd really appreciated your thoughts for fixing this.
J

you can have multiple delimiters - I am going to use a \t to represent, but when you hit the tab key it will not make a \t appear on your screen

Code:

awk -F '[\t :]'  ' { awk program goes here }'  inputfile > outputfile

This make tab, space, and colon characters into field delimiters. This also shows why
presenting a real data sample from the get-go would have made things work right the first time.

N.B.:
On Solaris try nawk instead of awk.