Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <33397188.1158273025015.JavaMail.jira@brutus>
Date: Thu, 14 Sep 2006 15:30:25 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-531) Need to sort on more than the
 primary key
In-Reply-To: <23568129.1158183922358.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-531?page=comments#action_12434835 ] 
            
Doug Cutting commented on HADOOP-531:
-------------------------------------

So do HADOOP-485 and HADOOP-531 solve this issue?  If so, then we should mark it duplicate, or at least dependent.


> Need to sort on more than the primary key
> -----------------------------------------
>
>                 Key: HADOOP-531
>                 URL: http://issues.apache.org/jira/browse/HADOOP-531
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: contrib/streaming
>    Affects Versions: 0.5.0
>            Reporter: Richard Kasperski
>
> There are many tasks where I need to have finer control over the ordering in the reduce than a sort on a single key provides. Most of these situations arise when a merge two sources of data and am attaching a single instance of one source to multiple instances of a second source. I know that I can read all the the records with a single key. It's possible that there might be many millions of these making memory demands that cannot be satisfied.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira