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-213) FeedEntityParses.validateStorageExists should be called only from the server(not from prism)
Date Fri, 22 Nov 2013 17:00:38 GMT

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

Venkatesh Seetharam commented on FALCON-213:
--------------------------------------------

I thought the conditional check of the colo that exists in org.apache.falcon.entity.parser.ClusterEntityParser
also exists here. My bad.
{code}
        if (!EntityUtil.responsibleFor(cluster.getColo())) {
            return;
        }
{code}

Before the fix, is this a hard requirement? I'm questioning my premise here. Say if I have
a process that ingests data into a table and produces output feeds, this makes it hard for
users to create a table even before configuring in Falcon but users can as well do this as
part of this ingest process.

Thoughts?

> FeedEntityParses.validateStorageExists should be called only from the server(not from
prism)
> --------------------------------------------------------------------------------------------
>
>                 Key: FALCON-213
>                 URL: https://issues.apache.org/jira/browse/FALCON-213
>             Project: Falcon
>          Issue Type: Bug
>          Components: prism
>    Affects Versions: 0.4
>         Environment: QA
>            Reporter: Samarth Gupta
>            Assignee: Venkatesh Seetharam
>            Priority: Critical
>
> if the FeedEntityParses.validateStorageExists is not able to find the table in hcat,
corresponding error messages is being logged in Prism application.log , but it should be going
to the falcon server where the cluster is registered and HCat is running. 
> Below is the error that is coming in prism log: 
> Caused by: org.apache.hcatalog.common.HCatException : 9001 : Exception occurred while
processing HCat request : NoSuchObjectException while fetching table.. Cause : NoSuchObjectExce
> ption(message:default.mytablepart table not found)
>        at org.apache.hcatalog.api.HCatClientHMSImpl.getTable(HCatClientHMSImpl.java:162)
>        at org.apache.falcon.catalog.HiveCatalogService.tableExists(HiveCatalogService.java:109)
>        ... 50 more
> Caused by: NoSuchObjectException(message:default.mytablepart table not found)
>        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$get_table_result$get_table_resultStandardScheme.read(ThriftHiveMetastore.java:27011)
>        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$get_table_result$get_table_resultStandardScheme.read(ThriftHiveMetastore.java:26979)
>        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$get_table_result.read(ThriftHiveMetastore.java:26910)
>        at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78)
>        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.recv_get_table(ThriftHiveMetastore.java:932)
>        at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Client.get_table(ThriftHiveMetastore.java:918)
>        at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.getTable(HiveMetaStoreClient.java:838)
>        at org.apache.hcatalog.api.HCatClientHMSImpl.getTable(HCatClientHMSImpl.java:155)
>        ... 51 more



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

Mime
View raw message