cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-986) Make endpointsnitch per-cluster instead of per-keyspace
Date Mon, 19 Apr 2010 15:32:49 GMT


Gary Dusbabek commented on CASSANDRA-986:

I gave it a try too, but something else is stopping me up:

Traceback (most recent call last):
  File "/Library/Python/2.6/site-packages/nose-0.11.1-py2.6.egg/nose/", line 364, in
    try_run(self.inst, ('setup', 'setUp'))
  File "/Library/Python/2.6/site-packages/nose-0.11.1-py2.6.egg/nose/", line 487, in
    return func()
  File "/Users/gary.dusbabek/codes/apache/git-trunk/test/system/", line 124, in
  File "/Users/gary.dusbabek/codes/apache/git-trunk/test/system/", line 154, in
    Cassandra.CfDef(table='Keyspace1', name='Super4', column_type='Super', subcomparator_type='UTF8Type')
TypeError: __init__() takes at most 5 arguments (6 given)

If I open up I see that CfDef.__init__ takes 8 args.  I'm not sure what's going

> Make endpointsnitch per-cluster instead of per-keyspace
> -------------------------------------------------------
>                 Key: CASSANDRA-986
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.7
>         Attachments: 986-3.txt, 986.txt
> Looks like a deficiency in the EPS and/or ReplicationStrategy design is forcing this,
we should clean it up; it doesn't make sense for there to be multiple answers for "how close
is node X to me?"

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message