[
https://issues.apache.org/jira/browse/CASSANDRA-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877557#action_12877557
]
Jeremy Hanna commented on CASSANDRA-1047:
-----------------------------------------
Jonathan - it may be that we need to have a cassandra configuration file for
things that use hadoop. I have it in a state where it works fine without the
configuration file for the word_count example. But then when I was going to
see what needed to happen for the pig code, I found that there really isn't any
code involved. It just uses the cassandra.yaml (on trunk) to get the
configuration and uses the pig with the cassandra storage to do everything - no
code required.
So in effect we would have to write another configuration mechanism other than
cassandra.yaml for just those bits that it or MapReduce needs.
I can do that - maybe a simpler version of the configuration file or something
which is then passed in so that it never touches DatabaseDescriptor. I just
wasn't sure if it was worth it since we know we'll need some sort of
configuration file it appears.
> Get hadoop ColumnFamily metadata from describe_keyspace instead of config file
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-1047
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1047
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Reporter: Jonathan Ellis
> Assignee: Jeremy Hanna
> Fix For: 0.7
>
>
> Requiring the Hadoop job to contain a copy of the Cassandra configuration
> file is clunky and error-prone. Instead, the Hadoop job should get an IP and
> port to contact for the range map and for CF metadata (with
> describe_keyspace).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
