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

Srikanth Sundarrajan commented on FALCON-85:
--------------------------------------------

{quote}
I think I have all the required sub tasks complete (post review & commit) to be 
merged to trunk. I'll address others on trunk itself. Thoughts?
{quote}

Yes. Sooner we merge, better it would be. However I feel we need to add more 
integration tests before we merge. If we can put down scenarios we want 
verified and add these tests, it will help us merge this large and important 
feature with a higher confidence.

While on this subject, can we add {code} export MAVEN_OPTS="-Xmx1024m 
-XX:MaxPermSize=256m" {code} to build scripts in hudson to resume the falcon 
nightly build. This will also unblock FALCON-43

> Hive (HCatalog) integration
> ---------------------------
>
>                 Key: FALCON-85
>                 URL: https://issues.apache.org/jira/browse/FALCON-85
>             Project: Falcon
>          Issue Type: Improvement
>    Affects Versions: 0.4, 0.3
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>         Attachments: FalconHiveIntegrationProposal.pdf
>
>
> This proposal addresses Falcon allowing users to represent feed location as 
> Hive tables. Falcon should support both managed and external tables and 
> provide data management services for tables such as replication, eviction, 
> archival, etc. Falcon will notify Hive as a side effect of either acquiring, 
> replicating or evicting a data set instance and adds the missing capability 
> of Hive table replication.
> As a natural progression, Falcon will allow users to express pipeline 
> processing in Hive scripts apart from Pig and Oozie workflows.
> This will be worked on a separate branch and will be merged back to trunk 
> once complete.



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

Reply via email to