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

Srikanth Sundarrajan commented on FALCON-113:
---------------------------------------------

This should perhaps appear earlier in the docs, as there are references to this 
in earlier sections.
{code}
+---+++ Storage
+Falcon introduces a new abstraction to encapsulate the storage for a given 
feed which can either be
+expressed as a path on the file system, File System Storage or a table in a 
catalog, Catalog Storage.
{code}

>From the example it is not clear what would the values for input_database & 
>input_table and similarly output_database and output_table be. Can this be 
>illustrated more clearly.
{code}
+---++++ Pig Script
+
+<verbatim>
+A = load '$input_database.$input_table' using 
org.apache.hcatalog.pig.HCatLoader();
+B = FILTER A BY $input_filter;
+C = foreach B generate id, value;
+store C into '$output_database.$output_table' USING 
org.apache.hcatalog.pig.HCatStorer('$output_dataout_partitions');
+</verbatim>
{code}

This is perhaps true today but I feel that this shouldn't be part of the doc, 
perhaps is an apt candidate for the main page of falcon.incubator.apache.org. 
We dont want to update system documentation & user guide should an alternate 
solution become available. 
{code}
+Falcon is the only platform that provides OOTB [[HiveIntegration][lifecycle 
management for Tables in Hive (HCatalog)]]
+such as table replication for BCP and table eviction.
{code}

> Update documentation for Hive integration
> -----------------------------------------
>
>                 Key: FALCON-113
>                 URL: https://issues.apache.org/jira/browse/FALCON-113
>             Project: Falcon
>          Issue Type: Sub-task
>    Affects Versions: 0.3
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>         Attachments: FALCON-113.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to