[
https://issues.apache.org/jira/browse/HCATALOG-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071301#comment-13071301
]
Francis Liu commented on HCATALOG-64:
-------------------------------------
Finally got things in order. Some extra info:
I added a properties field to *JobInfo classes. So that there's a way for a
user to pass implementation specific parameters. I'm not sure if this is the
best way. We will be needing something for HBase storage drivers.
With regards to implementation specific parameters. The "location" field seems
to be implementation specific since it assumes file-based. I see two ways to
remedy this. Change location to be a URI or include it as part of the mechanism
by which way we store implementation specific parameters. This is not in the
patch but I thought I'd bring it up since we're getting our hands dirty.
> Refactor HCatTableInfo, JobInfo and OutputJobInfo
> -------------------------------------------------
>
> Key: HCATALOG-64
> URL: https://issues.apache.org/jira/browse/HCATALOG-64
> Project: HCatalog
> Issue Type: Improvement
> Reporter: Francis Liu
> Assignee: Francis Liu
> Attachments: HCatTableInfo_JobInfo_OutputJobInfo_2.patch
>
>
> These classes and their roles has become convoluted. HCatTableInfo should be
> an HCat abstraction of table and thus not have any job specific information
> and should not contain different information depending on usage. *JobInfo
> classes should contain job specific information (user provided, derived from
> metastore info, etc). Since *JobInfo contains such information it should be
> the object which is passed to HCatInputFormat.setInput and
> HCatInputFormat.setOutput. Also JobInfo should be renamed to InputJobInfo for
> consistency and clarity. Also there needs to be a way to pass implementation
> specific configuration information down to the actual storage driver.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
