accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1854) AccumuloInputFormat can be less strict about contents of Configuration
Date Tue, 26 Nov 2013 18:20:37 GMT


ASF subversion and git services commented on ACCUMULO-1854:

Commit f8e14c794992bd5d8d530b50338b16436088c243 in branch refs/heads/1.6.0-SNAPSHOT from [~ctubbsii]
[;h=f8e14c7 ]

ACCUMULO-1854 Remove compiler warnings

> AccumuloInputFormat can be less strict about contents of Configuration
> ----------------------------------------------------------------------
>                 Key: ACCUMULO-1854
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.4.5, 1.5.1, 1.6.0
> The AccumuloInputFormat required that the same exact Configuration object which was provided
to its static configuration methods is also provided to its getSplits() and createRecordReader()
> In practice, some tools, like MultipleInputs or Pig, don't guarantee that the same Configuration
object is provided to getSplits() and createRecordReader(). This tends to be a common method
of interaction to ensure that multiple InputFormats don't collide with one another in the
same Configuration object (e.g. FileInputFormat). By serialization the necessary information
from the Configuration regarding how to query Accumulo into the InputSplit AccumuloInputFormat
creates, we can alleviate this requirement and make client interaction a little more standard.

This message was sent by Atlassian JIRA

View raw message