incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Paliwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-18) Rework the MapReduce Library to implement Input/OutputFormats
Date Tue, 06 Nov 2012 02:44:12 GMT

    [ https://issues.apache.org/jira/browse/BLUR-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491139#comment-13491139
] 

Ashish Paliwal commented on BLUR-18:
------------------------------------

@Gagan - String is not recommended. Encoding would play spoil sport. Text is the way to go.
There is more discussion on this in various authoritative text :)

@Aaron - Does this means that BlurDocLocation won't be the output key from the Mapper? Let
me play more with Blur today, and get back to you.
                
> Rework the MapReduce Library to implement Input/OutputFormats
> -------------------------------------------------------------
>
>                 Key: BLUR-18
>                 URL: https://issues.apache.org/jira/browse/BLUR-18
>             Project: Apache Blur
>          Issue Type: Improvement
>            Reporter: Aaron McCurry
>             Fix For: 0.2.0
>
>         Attachments: 0001-BLUR-ID-18-Created-New-Version-of-Files.patch, 0001-BLUR-ID-18-New-Writables.patch
>
>
> Currently the only way to implement indexing is to use the BlurReducer.  A better way
to implement this would be to support Hadoop input/outputformats in both the new and old api's.
 This would allow an easier integration with other Hadoop projects such as Hive and Pig.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message