[
https://issues.apache.org/jira/browse/CASSANDRA-11646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257809#comment-15257809
]
Stefania commented on CASSANDRA-11646:
--------------------------------------
I agree, {{TypeCodec}} is correct because then {{rawAddRow}} calls the insert
statement {{addUpdateForKey()}}, which will then binds the parameters and so
forth. I've definitely verified that if I change that line back then the size
of the sstable returns as small as it was before.
I'll investigate why {{TypeCodec}} produces a different size then, rather than
trying to re-instate {{TypeSerializer}}, thanks.
> SSTableWriter output discrepancy
> --------------------------------
>
> Key: CASSANDRA-11646
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11646
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: Stefania
> Fix For: 3.6
>
>
> Since CASSANDRA-10624 there is a non-trivial difference in the size of the
> output in CQLSSTableWriter.
> I've written the following code:
> {code}
> String KS = "cql_keyspace";
> String TABLE = "table1";
> File tempdir = Files.createTempDir();
> File dataDir = new File(tempdir.getAbsolutePath() + File.separator +
> KS + File.separator + TABLE);
> assert dataDir.mkdirs();
> String schema = "CREATE TABLE cql_keyspace.table1 ("
> + " k int PRIMARY KEY,"
> + " v1 text,"
> + " v2 int"
> + ");";// with compression = {};";
> String insert = "INSERT INTO cql_keyspace.table1 (k, v1, v2) VALUES
> (?, ?, ?)";
> CQLSSTableWriter writer = CQLSSTableWriter.builder()
> .sorted()
> .inDirectory(dataDir)
> .forTable(schema)
> .using(insert).build();
> for (int i = 0; i < 10000000; i++)
> writer.addRow(i, "test1", 24);
> writer.close();
> {code}
> Pre CASSANDRA-10624 the data file is ~63MB. Post it's ~69MB
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
