[jira] [Commented] (CASSANDRA-2807) ColumnFamilyInputFormat configuration should support multiple initial addresses
[
https://issues.apache.org/jira/browse/CASSANDRA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13055780#comment-13055780
]
Jeremy Hanna commented on CASSANDRA-2807:
-
is this an easy thing to commit to 0.7-branch as well?
ColumnFamilyInputFormat configuration should support multiple initial
addresses
---
Key: CASSANDRA-2807
URL: https://issues.apache.org/jira/browse/CASSANDRA-2807
Project: Cassandra
Issue Type: Improvement
Components: Hadoop
Affects Versions: 0.6
Reporter: Greg Katz
Assignee: Mck SembWever
Priority: Minor
Fix For: 0.8.1
Attachments: CASSANDRA-2807.patch
The {{ColumnFamilyInputFormat}} class only allows a single initial node to be
specified through the cassandra.thrift.address configuration property. The
configuration should support a list of nodes in order to account for the
possibility that the initial node becomes unavailable.
By contrast, the {{RingCache}} class used by the {{ColumnFamilyRecordWriter}}
reads the exact same {{cassandra.thrift.address}} property but splits its
value on commas to allow multiple initial nodes to be specified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2807) ColumnFamilyInputFormat configuration should support multiple initial addresses
[
https://issues.apache.org/jira/browse/CASSANDRA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13055789#comment-13055789
]
Jonathan Ellis commented on CASSANDRA-2807:
---
It's time to be rigorous about keeping 0.7 stable -- if you want new features
that are probably safe, like this one, you should be using 0.8.x.
ColumnFamilyInputFormat configuration should support multiple initial
addresses
---
Key: CASSANDRA-2807
URL: https://issues.apache.org/jira/browse/CASSANDRA-2807
Project: Cassandra
Issue Type: Improvement
Components: Hadoop
Affects Versions: 0.6
Reporter: Greg Katz
Assignee: Mck SembWever
Priority: Minor
Fix For: 0.8.1
Attachments: CASSANDRA-2807.patch
The {{ColumnFamilyInputFormat}} class only allows a single initial node to be
specified through the cassandra.thrift.address configuration property. The
configuration should support a list of nodes in order to account for the
possibility that the initial node becomes unavailable.
By contrast, the {{RingCache}} class used by the {{ColumnFamilyRecordWriter}}
reads the exact same {{cassandra.thrift.address}} property but splits its
value on commas to allow multiple initial nodes to be specified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2807) ColumnFamilyInputFormat configuration should support multiple initial addresses
[
https://issues.apache.org/jira/browse/CASSANDRA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13055881#comment-13055881
]
Hudson commented on CASSANDRA-2807:
---
Integrated in Cassandra-0.8 #194 (See
[https://builds.apache.org/job/Cassandra-0.8/194/])
Add support for multiple (comma-delimited) coordinator addresses to CFIF
patch by Mck SembWever; reviewed by jbellis for CASSANDRA-2807
jbellis :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1140333
Files :
* /cassandra/branches/cassandra-0.8/CHANGES.txt
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/hadoop/ColumnFamilyInputFormat.java
ColumnFamilyInputFormat configuration should support multiple initial
addresses
---
Key: CASSANDRA-2807
URL: https://issues.apache.org/jira/browse/CASSANDRA-2807
Project: Cassandra
Issue Type: Improvement
Components: Hadoop
Affects Versions: 0.6
Reporter: Greg Katz
Assignee: Mck SembWever
Priority: Minor
Fix For: 0.8.1
Attachments: CASSANDRA-2807.patch
The {{ColumnFamilyInputFormat}} class only allows a single initial node to be
specified through the cassandra.thrift.address configuration property. The
configuration should support a list of nodes in order to account for the
possibility that the initial node becomes unavailable.
By contrast, the {{RingCache}} class used by the {{ColumnFamilyRecordWriter}}
reads the exact same {{cassandra.thrift.address}} property but splits its
value on commas to allow multiple initial nodes to be specified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2807) ColumnFamilyInputFormat configuration should support multiple initial addresses
[
https://issues.apache.org/jira/browse/CASSANDRA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13053873#comment-13053873
]
Mck SembWever commented on CASSANDRA-2807:
--
Right. the comment was only meant for background/history sake, for example to
see a use case where this is wanted.
ColumnFamilyInputFormat configuration should support multiple initial
addresses
---
Key: CASSANDRA-2807
URL: https://issues.apache.org/jira/browse/CASSANDRA-2807
Project: Cassandra
Issue Type: Improvement
Components: Hadoop
Affects Versions: 0.8.0
Reporter: Greg Katz
Priority: Minor
The {{ColumnFamilyInputFormat}} class only allows a single initial node to be
specified through the cassandra.thrift.address configuration property. The
configuration should support a list of nodes in order to account for the
possibility that the initial node becomes unavailable.
By contrast, the {{RingCache}} class used by the {{ColumnFamilyRecordWriter}}
reads the exact same {{cassandra.thrift.address}} property but splits its
value on commas to allow multiple initial nodes to be specified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2807) ColumnFamilyInputFormat configuration should support multiple initial addresses
[
https://issues.apache.org/jira/browse/CASSANDRA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13053143#comment-13053143
]
Mck SembWever commented on CASSANDRA-2807:
--
there was a brief mention of this in
https://issues.apache.org/jira/browse/CASSANDRA-2388?focusedCommentId=13046450page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13046450
ColumnFamilyInputFormat configuration should support multiple initial
addresses
---
Key: CASSANDRA-2807
URL: https://issues.apache.org/jira/browse/CASSANDRA-2807
Project: Cassandra
Issue Type: Improvement
Components: Hadoop
Affects Versions: 0.8.0
Reporter: Greg Katz
The {{ColumnFamilyInputFormat}} class only allows a single initial node to be
specified through the cassandra.thrift.address configuration property. The
configuration should support a list of nodes in order to account for the
possibility that the initial node becomes unavailable.
By contrast, the {{RingCache}} class used by the {{ColumnFamilyRecordWriter}}
reads the exact same {{cassandra.thrift.address}} property but splits its
value on commas to allow multiple initial nodes to be specified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2807) ColumnFamilyInputFormat configuration should support multiple initial addresses
[
https://issues.apache.org/jira/browse/CASSANDRA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13053264#comment-13053264
]
Jonathan Ellis commented on CASSANDRA-2807:
---
But this is not actually addressed by the 2388 patch, right? I don't mind
addressing this separately.
ColumnFamilyInputFormat configuration should support multiple initial
addresses
---
Key: CASSANDRA-2807
URL: https://issues.apache.org/jira/browse/CASSANDRA-2807
Project: Cassandra
Issue Type: Improvement
Components: Hadoop
Affects Versions: 0.8.0
Reporter: Greg Katz
The {{ColumnFamilyInputFormat}} class only allows a single initial node to be
specified through the cassandra.thrift.address configuration property. The
configuration should support a list of nodes in order to account for the
possibility that the initial node becomes unavailable.
By contrast, the {{RingCache}} class used by the {{ColumnFamilyRecordWriter}}
reads the exact same {{cassandra.thrift.address}} property but splits its
value on commas to allow multiple initial nodes to be specified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
