Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3DB3E18388 for ; Mon, 17 Aug 2015 23:30:59 +0000 (UTC) Received: (qmail 78384 invoked by uid 500); 17 Aug 2015 23:30:46 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 78350 invoked by uid 500); 17 Aug 2015 23:30:46 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 78337 invoked by uid 99); 17 Aug 2015 23:30:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2015 23:30:46 +0000 Date: Mon, 17 Aug 2015 23:30:46 +0000 (UTC) From: "Blake Eggleston (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8671) Give compaction strategy more control over where sstables are created, including for flushing and streaming. 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/CASSANDRA-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700430#comment-14700430 ] Blake Eggleston commented on CASSANDRA-8671: -------------------------------------------- Here's the branch: https://github.com/bdeggleston/cassandra/tree/8671-2 and the last test runs: http://cassci.datastax.com/job/bdeggleston-8671-2-testall/2/ http://cassci.datastax.com/job/bdeggleston-8671-2-dtest/2/ Doesn't look like there's anything failing that isn't already failing on cassandra-3.0 > Give compaction strategy more control over where sstables are created, including for flushing and streaming. > ------------------------------------------------------------------------------------------------------------ > > Key: CASSANDRA-8671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8671 > Project: Cassandra > Issue Type: Improvement > Reporter: Blake Eggleston > Assignee: Blake Eggleston > Fix For: 3.x > > Attachments: 0001-C8671-creating-sstable-writers-for-flush-and-stream-.patch, 8671-giving-compaction-strategies-more-control-over.txt > > > This would enable routing different partitions to different disks based on some user defined parameters. > My initial take on how to do this would be to make an interface from SSTableWriter, and have a table's compaction strategy do all SSTableWriter instantiation. Compaction strategies could then implement their own SSTableWriter implementations (which basically wrap one or more normal sstablewriters) for compaction, flushing, and streaming. -- This message was sent by Atlassian JIRA (v6.3.4#6332)