[ https://issues.apache.org/jira/browse/CASSANDRA-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402620#comment-16402620 ]
Dikang Gu commented on CASSANDRA-14118: --------------------------------------- [~bdeggleston], on the local write path, the memtable/sstables are hidden inside the CassandraWriteHandler.apply(...) already. Only the CommitLogPosition is passed as a parameter in the apply signature: {quote}void apply(PartitionUpdate update, UpdateTransaction indexer, OpOrder.Group opGroup, CommitLogPosition commitLogPosition) {quote} I think storage engine implementation can use the commitLogPosition if it needs, or ignore the commitLogPosition if it doesn't. What do you think? > 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