src/java/org/apache/cassandra/db/ColumnFamilyStore.java
/*
     * Called after a BinaryMemtable flushes its in-memory data, or we add a file
     * via bootstrap. This information is cached in the ColumnFamilyStore.
     * This is useful for reads because the ColumnFamilyStore first looks in
     * the in-memory store and the into the disk to find the key. If invoked
     * during recoveryMode the onMemtableFlush() need not be invoked.
     *
     * param @ filename - filename just flushed to disk
     */
Called after a BinaryMemtable flushes its in-memory data, or we add a file
via bootstrap. This information is cached in the ColumnFamilyStore.
This is useful for reads because the ColumnFamilyStore first looks in
the in-memory store and the into the disk to find the key. If invoked
during recoveryMode the onMemtableFlush() need not be invoked.

param @ filename - filename just flushed to disk
Called after a BinaryMemtable flushes its in - memory data or we add a file via bootstrap . This information is cached in the ColumnFamilyStore . This is useful for reads because the ColumnFamilyStore first looks in the in - memory store and the into the disk to find the key . If invoked during recoveryMode the onMemtableFlush () need not be invoked . param @ filename - filename just flushed to disk
public void addSSTable(SSTableReader sstable)
    {
        assert sstable.getColumnFamilyName().equals(columnFamily);
        data.addSSTables(Arrays.asList(sstable));
        CompactionManager.instance.submitBackground(this);
    }
public void addSSTable ( SSTableReader sstable ) { assert sstable . getColumnFamilyName ( ) . equals ( columnFamily ) ; data . addSSTables ( Arrays . asList ( sstable ) ) ; CompactionManager . instance . submitBackground ( this ) ; }
Called after a BinaryMemtable flushes its in-memory data, or we add a file
 via bootstrap.
Called after a BinaryMemtable flushes its in - memory data or we add a file via bootstrap .