Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 12 Jun 2014 19:47:02 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12720962.1402602409379.120893.1402602422766@arcas>
In-Reply-To: <JIRA.12720962.1402602409379@arcas>
References: <JIRA.12720962.1402602409379@arcas>
Subject: [jira] [Created] (CASSANDRA-7394) Optimize
 CollationController#collectTimeOrderedData() to potentially skip the
 sstables altogether
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksey Yeschenko created CASSANDRA-7394:
--------------------------------------------

             Summary: Optimize CollationController#collectTimeOrderedData() to potentially skip the sstables altogether
                 Key: CASSANDRA-7394
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7394
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Aleksey Yeschenko
            Priority: Minor


As of now, collectTimeOrderedData() will try to read from at least one sstable, even if the request can be fulfilled from the memtable exclusively.

If we initiate mostRecentRowTombstone with the value from the memtables and not Long.MIN_VALUE, reading from the sstables can be avoided entirely.


--
This message was sent by Atlassian JIRA
(v6.2#6252)