tanger007:

Try something like putting a file handle for each column value in a hash, and then looking up the file handle on demand:

my %OFH;
my $OFH;
while (<$IFH>) {
    my @fields = split /\t/,$_;
    $OFH = $OFH{$fields[$key_column]};
    if (! defined $OFH) {
        # We don't have this value yet, so open another file
        open $OFH, '>', 'key_value.' . $fields[$key_column];
        $OFH{$fields[$key_column]} = $OFH;
    }
    print $OFH join("\t",@fields);
}

[download]

Note: It's rough, untested and needs some error handling and such. But the basic concept should work fine for you.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

In reply to Re^3: Merge huge files (individually sorted) by order by roboticus
in thread Merge huge files (individually sorted) by order by tanger007

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.