[
https://issues.apache.org/jira/browse/CASSANDRA-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877839#action_12877839
]
Jeremy Hanna commented on CASSANDRA-1047:
-----------------------------------------
No, sorry, it's just that with the word_count, there is a java program that
needs to be written for the map reduce anyway, so I could put the configuration
information into the config helper for that case.
For the pig stuff, all that's needed is the CassandraStorage file - which is
probably going to move into core. Other than that it's just relying on
libraries and you get to run pig scripts or the pig shell - no other java
programming needed. So for that, it's either that we need to use the
configuration file for cassandra that's already there - based on the static
initialization of the vars in DatabaseDescriptor, or we have to create a
mechanism to use configure it.
Does that make more sense?
> 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
>
> Attachments: add-reconciler-data-patch.txt
>
>
> 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.
