accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corey J. Nolet (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-1663) Multi-table/Composite InputFormat example
Date Sat, 05 Oct 2013 02:37:41 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Corey J. Nolet resolved ACCUMULO-1663.
--------------------------------------

    Resolution: Duplicate

> Multi-table/Composite InputFormat example 
> ------------------------------------------
>
>                 Key: ACCUMULO-1663
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1663
>             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
capability. 
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message