Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 12 Feb 2016 15:21:18 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12844382.1436631182000.37730.1455290478347@Atlassian.JIRA>
In-Reply-To: <JIRA.12844382.1436631182000@Atlassian.JIRA>
References: <JIRA.12844382.1436631182000@Atlassian.JIRA>
 <JIRA.12844382.1436631182612@arcas>
Subject: [jira] [Updated] (CASSANDRA-9779) Append-only optimization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-9779:
-----------------------------------------
    Flagged: Impediment

> Append-only optimization
> ------------------------
>
>                 Key: CASSANDRA-9779
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9779
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: CQL
>            Reporter: Jonathan Ellis
>             Fix For: 3.x
>
>
> Many common workloads are append-only: that is, they insert new rows but do not update existing ones.  However, Cassandra has no way to infer this and so it must treat all tables as if they may experience updates in the future.
> If we added syntax to tell Cassandra about this ({{WITH INSERTS ONLY}} for instance) then we could do a number of optimizations:
> - Compaction would only need to worry about defragmenting partitions, not rows.  We could default to DTCS or similar.
> - CollationController could stop scanning sstables as soon as it finds a matching row
> - Most importantly, materialized views wouldn't need to worry about deleting prior values, which would eliminate the majority of the MV overhead


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)