[ 
https://issues.apache.org/jira/browse/CASSANDRA-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412108#comment-16412108
 ] 

Dikang Gu commented on CASSANDRA-14118:
---------------------------------------

Then I misunderstood Blake's comment:
{quote}You haven't abstracted all of the storage layer implementation details 
though. You should be able to step through the entire local write path without 
seeing anything related to commit logs, caches, sstables, or memtables.|
{quote}
 I thought he wanted me to abstract the commit logs and caches as well.  

Let me put them back to the CassandraWriteHandler implementation then.

> Refactor write path
> -------------------
>
>                 Key: CASSANDRA-14118
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14118
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Dikang Gu
>            Assignee: Dikang Gu
>            Priority: Major
>
> As part of the pluggable storage engine effort, we'd like to modularize the 
> write path related code, make it to be independent from existing storage 
> engine implementation details.
> For now, refer to 
> https://docs.google.com/document/d/1suZlvhzgB6NIyBNpM9nxoHxz_Ri7qAm-UEO8v8AIFsc
>  for high level designs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to