You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/10/03 23:47:07 UTC

[jira] [Updated] (CASSANDRA-4755) Bulk loader won't work with CQL3

     [ https://issues.apache.org/jira/browse/CASSANDRA-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-4755:
--------------------------------------

    Reviewer: yukim
    Assignee: Aleksey Yeschenko

I think I'd prefer just converting that code to use a CQL query or two, all it cares about is "is this ks/cf pair valid," which isn't a big deal to fix.

Side note: looks like some code duplication in BulkLoader.ExternalClient and BulkRecordWriter.External client, be nice to clean that up.
                
> Bulk loader won't work with CQL3
> --------------------------------
>
>                 Key: CASSANDRA-4755
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4755
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Nick Bailey
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.0
>
>
> Currently the bulk loader uses thrift to get the schema and validate it before bulk loading a cf. Since we stopped returning cql3 cfs through describe_keyspaces, the bulk loader will be unable to load those cfs.
> If we figure out/add a way to validate the schema over jmx, we could use that for getting token ranges as well and drop thrift completely from the bulk loader.
> Another option might be querying system tables manually to validate things.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira