Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 25 Nov 2012 21:08:58 +0000 (UTC)
From: =?utf-8?Q?Piotr_Ko=C5=82aczkowski_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <34631405.21571.1353877738221.JavaMail.jiratomcat@arcas>
In-Reply-To: <5127739.41100.1350116223089.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (CASSANDRA-4803) CFRR wide row iterators
 improvements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-4803?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Ko=C5=82aczkowski updated CASSANDRA-4803:
------------------------------------------

    Attachment:     (was: 0007-Fallback-to-describe-splits-v2.patch)
   =20
> CFRR wide row iterators improvements
> ------------------------------------
>
>                 Key: CASSANDRA-4803
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4803
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>    Affects Versions: 1.1.0
>            Reporter: Piotr Ko=C5=82aczkowski
>            Assignee: Piotr Ko=C5=82aczkowski
>             Fix For: 1.1.7
>
>         Attachments: 0007-Fallback-to-describe_splits-v3.patch
>
>
> {code}
>  public float getProgress()
>     {
>         // TODO this is totally broken for wide rows
>         // the progress is likely to be reported slightly off the actual =
but close enough
>         float progress =3D ((float) iter.rowsRead() / totalRowCount);
>         return progress > 1.0F ? 1.0F : progress;
>     }
> {code}
> The problem is iter.rowsRead() does not return the number of rows read fr=
om the wide row iterator, but returns number of *columns* (every row is cou=
nted multiple times).=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira