[
https://issues.apache.org/jira/browse/HBASE-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Newman updated HBASE-4587:
-------------------------------
Description:
Some requirements:
- Being able to have multiple tables as your input path
- Being able to filter on specific columns/column families
- Providing the source location (table/row/column) to the results
- Multiple clusters
- Different schemas.
Overall this seems difficult for now so I am going to punt on it. On the other
hand it would be easy enough to write all of the MR values into an intermediate
table and then work from there.
was:
Some requirements:
- Being able to have multiple tables as your input path
- Being able to filter on specific columns/column families
- Providing the source location (table/row/column) to the results
Summary: HBase MR support for multiple tables as input (was: HBase MR
needs to support multiple tables as input)
> HBase MR support for multiple tables as input
> ---------------------------------------------
>
> Key: HBASE-4587
> URL: https://issues.apache.org/jira/browse/HBASE-4587
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.90.3
> Reporter: Rajeev Rao
> Assignee: Alex Newman
>
> Some requirements:
> - Being able to have multiple tables as your input path
> - Being able to filter on specific columns/column families
> - Providing the source location (table/row/column) to the results
> - Multiple clusters
> - Different schemas.
> Overall this seems difficult for now so I am going to punt on it. On the
> other hand it would be easy enough to write all of the MR values into an
> intermediate table and then work from there.
--
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
