You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Ashvin (JIRA)" <ji...@apache.org> on 2015/07/06 23:20:04 UTC

[jira] [Comment Edited] (GEODE-10) HDFS Integration

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

Ashvin edited comment on GEODE-10 at 7/6/15 9:19 PM:
-----------------------------------------------------

Attached draft specification document for HdfsStore


was (Author: ashvin):
HdfsStore Proposal

> HDFS Integration
> ----------------
>
>                 Key: GEODE-10
>                 URL: https://issues.apache.org/jira/browse/GEODE-10
>             Project: Geode
>          Issue Type: Sub-task
>          Components: hdfs
>            Reporter: Dan Smith
>            Assignee: Ashvin
>         Attachments: GEODE-HDFSPersistence-Draft-060715-2109-21516.pdf
>
>
> This is a feature that has been under development for GemFire but was not part of the initial drop of code for geode.
> HDFS Integration: Geode as a transactional layer that microbatches data out to Hadoop. This capability makes Geode a NoSQL store that can sit on top of Hadoop and parallelize the process of moving data from the in memory tier into Hadoop, making it very useful for capturing and processing fast data while making it available for Hadoop jobs relatively quickly. The key requirements being met here are
> Ingest data into HDFS parallely
> Cache bloom filters and allow fast lookups of individual elements
> Have programmable policies for deciding what stays in memory
> Roll files in HDFS
> Index data that is in memory
> Have expiration policies that allows the transactional set to decay out older data
> Solution needs to support replicated and partitioned regions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)