You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/01/28 23:07:32 UTC

[jira] [Created] (FALCON-283) Catalog Service implementation needs to be part an entity definition

Venkatesh Seetharam created FALCON-283:
------------------------------------------

             Summary: Catalog Service implementation needs to be part an entity definition
                 Key: FALCON-283
                 URL: https://issues.apache.org/jira/browse/FALCON-283
             Project: Falcon
          Issue Type: Improvement
    Affects Versions: 0.4
            Reporter: Venkatesh Seetharam


Catalog Service Factory uses startup properties to find the implementation and this is ok as long as its used with in falcon server. But, its being used in workflow actions such as retention, late data handler, etc. The overridden startup properties is not available to actions and hence always picks up the default. This is fine for now since there is only one implementation. 

There are 2 options: 

* make it part of cluster definition - ship cluster definition to actions is bad
* make it part of the table uri similar to what jdbc does and this mapping is global 

Thoughts?



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