falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satish Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-266) HCatalog partition registration with same HDFS location format within process
Date Fri, 07 Feb 2014 09:38:20 GMT

     [ https://issues.apache.org/jira/browse/FALCON-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Satish Mittal updated FALCON-266:
---------------------------------

    Description: When an existing HDFS based falcon feed is converted to HCatalog external
table based feed, and falcon process workflow creates dynamic partitions, the underlying HDFS
path format of partitions created by HCatalog is different than the original HDFS feed based
format. This can break other applications that consume feed data directly from underlying
HDFS location and expect a particular path layout.  (was: When process workflow gets executed,
the newly created partitions should get registered in HCatalog. Also the HDFS location format
of the dynamic partitions registered in HCatalog should be configurable.)

> HCatalog partition registration with same HDFS location format within process
> -----------------------------------------------------------------------------
>
>                 Key: FALCON-266
>                 URL: https://issues.apache.org/jira/browse/FALCON-266
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Satish Mittal
>
> When an existing HDFS based falcon feed is converted to HCatalog external table based
feed, and falcon process workflow creates dynamic partitions, the underlying HDFS path format
of partitions created by HCatalog is different than the original HDFS feed based format. This
can break other applications that consume feed data directly from underlying HDFS location
and expect a particular path layout.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message