Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0DD6997B0 for ; Wed, 13 Jun 2012 22:08:43 +0000 (UTC) Received: (qmail 75435 invoked by uid 500); 13 Jun 2012 22:08:42 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 75415 invoked by uid 500); 13 Jun 2012 22:08:42 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 75405 invoked by uid 99); 13 Jun 2012 22:08:42 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2012 22:08:42 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id B0A5514001F for ; Wed, 13 Jun 2012 22:08:42 +0000 (UTC) Date: Wed, 13 Jun 2012 22:08:42 +0000 (UTC) From: "John Vines (JIRA)" To: dev@accumulo.apache.org Message-ID: <423540068.13792.1339625322726.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1743693677.13157.1339607143146.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (ACCUMULO-633) FirstEntryInRowIterator is broken and has no test MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294683#comment-13294683 ] John Vines commented on ACCUMULO-633: ------------------------------------- So the middle row behavior can have some interesting edge cases. If we take the literal name, then the attempting to return only the first Key is the proper thing to do. And I like that. But you need to be careful there, as someone could seek to a specific Key, which could actually be the first entry in the row. So this iterator will require seeking to the row and then checking the top key to see if the Key specified is teh first entry before seeking to the next possible row. > FirstEntryInRowIterator is broken and has no test > ------------------------------------------------- > > Key: ACCUMULO-633 > URL: https://issues.apache.org/jira/browse/ACCUMULO-633 > Project: Accumulo > Issue Type: Bug > Components: client > Affects Versions: 1.4.0, 1.3.5 > Reporter: Billie Rinaldi > Assignee: Billie Rinaldi > Priority: Minor > Fix For: 1.5.0, 1.4.1 > > > In 1.4 and trunk, the iterator throws a NullPointerException when seeked. > In 1.3 the iterator runs, but there is a question as to what it should do when it is seeked to the middle of a row. Currently, it returns the first key found within the range. I believe this should be changed to ignore the remaining portion of that row and return the first key of the next row. Should this change be made in 1.3, or should I leave it as is and just change it in 1.4 and greater? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira