cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6641) Switch stress to use ITransportFactory to obtain client connections
Date Thu, 30 Jan 2014 22:36:09 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887191#comment-13887191
] 

Sam Tunnicliffe commented on CASSANDRA-6641:
--------------------------------------------

I didn't as I was targetting this at 2.0, I'll check it out & submit a further patch if
necessary 

> Switch stress to use ITransportFactory to obtain client connections
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-6641
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6641
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>         Attachments: 0001-cassandra-stress-uses-ITransportFactory-to-provide-c.patch,
0002-Set-supplied-encryption-options-on-transport-factory.patch
>
>
> CASSANDRA-6062 & CASSANDRA-6378 changed cassandra-cli and sstableloader respectively
to use o.a.c.thrift.ITransportFactory rather than o.a.thrift.transport.TTransportFactory implementations.
This ticket is to do likewise for cassandra-stress, so that users can have more control over
the connection options when running stress.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message