accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corey J. Nolet (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1663) Multi-table/Composite InputFormat example
Date Sun, 25 Aug 2013 01:57:51 GMT


Corey J. Nolet commented on ACCUMULO-1663:

I was only proposing an example class in the case where nobody else felt that this was a feature
for the core codebase. I do have a use-case for utilizing data in a single map/reduce that
comes from multiple map/reduce jobs (see comment in ACCUMULO-391)
> Multi-table/Composite InputFormat example 
> ------------------------------------------
>                 Key: ACCUMULO-1663
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Corey J. Nolet
>            Priority: Minor
>              Labels: proposed
> For services that need to span more than a single table, it would be massively useful
to either:
> 1) Provide a new input format capable to loading data from multiple tables  or
> 2) Provide an example of extending/wrapping the current input format to provide such
> It's not uncommon to have services that may span multiple tables and for each to require
their own separate server-side iterators. Curent, in order to make this possible, the AccumuloInputFormat
needs to be re-written. Adding the other table is really just a matter of running more scanners
and generating the input splits for another table. It would be useful if the Accumulo core
code base could provide some sort of composite or multi-table input format by default.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message