[
https://issues.apache.org/jira/browse/CASSANDRA-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995960#comment-14995960
]
Stefania commented on CASSANDRA-9302:
-------------------------------------
This is ready for review. The patch is based on CASSANDRA-9304. [~thobbs] do
you have time to review this one as well?
[~aholmber], I noticed that for CASSANDRA-10365/PYTHON-422 we removed
{{data_type}} from the column metadata in favor of the CQL name, {{cql_type}}
and this is still WIP. I just want to confirm that the same thing will not
happen to the type stored in the prepared statement column metadata. We need
access to cql types and their sub-types to convert a string into a value that
can be used to bind a prepared statement. You can take a look
[here|https://github.com/stef1927/cassandra/commit/5e3fa29a0e9d60e72e4c6b53f101b78bd05d0cd4#diff-2c522499936bef16ad42d171722ef3a2R833]
for more details.
> Optimize cqlsh COPY FROM, part 3
> --------------------------------
>
> Key: CASSANDRA-9302
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9302
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Stefania
> Priority: Critical
> Fix For: 2.1.x
>
>
> We've had some discussion moving to Spark CSV import for bulk load in 3.x,
> but people need a good bulk load tool now. One option is to add a separate
> Java bulk load tool (CASSANDRA-9048), but if we can match that performance
> from cqlsh I would prefer to leave COPY FROM as the preferred option to which
> we point people, rather than adding more tools that need to be supported
> indefinitely.
> Previous work on COPY FROM optimization was done in CASSANDRA-7405 and
> CASSANDRA-8225.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
