Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 6 Dec 2011 19:49:40 +0000 (UTC)
From: "Brandon Williams (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1094520232.46538.1323200980056.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <782050808.21577.1315911489290.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3197) Separate input and output
 connection details in ConfigHelper
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-3197:
---------------------------------------------

It looks like the output partitioner/rpcport/initial address aren't being set for pig or the word count so jobs with output NPE at org.apache.cassandra.utils.FBUtilities.newPartitioner.
                
> Separate input and output connection details in ConfigHelper
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-3197
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3197
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Hadoop
>    Affects Versions: 0.7.0
>            Reporter: Mck SembWever
>            Assignee: Mck SembWever
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: CASSANDRA-3197.patch
>
>
> Currently ConfigHelper's getInitialAddress(..) getRpcPort(..) and getPartitioner(..) 
> presume CFIF will be using the same cluster as CFOF.
> The latter two are a problem for me as on the same servers i'm running two clusters, one w/ ByteOrderingPartitioner and the other with RP), and i would like to read from the BOP cluster and write to the RP cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira