falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-435) Archive Data to a Cloud storage
Date Tue, 26 Aug 2014 20:37:58 GMT

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

Venkatesh Seetharam commented on FALCON-435:
--------------------------------------------

[~sanjay.radia], you could do one of 2 things:

1. represent your archive interface as S3 or HDFS or Azure endpoint with in a cluster
Here, falcon does not assume you have a cluster, which means you cannot enable processing
this data, sort of cold store. This jira attempts to add this capability.

2. reuse the current semantics for a cluster and reuse write interface for S3 OR Azure Storage
Vault
This is a classic cluster which can process as well. A static EMR or Azure cluster. This capability
already exists.

Makes sense?


> Archive Data to a Cloud storage
> -------------------------------
>
>                 Key: FALCON-435
>                 URL: https://issues.apache.org/jira/browse/FALCON-435
>             Project: Falcon
>          Issue Type: Improvement
>          Components: archival, replication
>    Affects Versions: 0.5
>            Reporter: Venkatesh Seetharam
>
> Falcon must be able to archive data to a cloud storage, like Windows Azure or Amazon
S3.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message