[
https://issues.apache.org/jira/browse/OOZIE-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510788#comment-13510788
]
Alejandro Abdelnur commented on OOZIE-1111:
-------------------------------------------
Having a common HCAT URI format across different projects will help users that
have to use these multiple projects. That is a big plus.
Technically, given that we are introducing a dataset scheme handler, I don't
think this is a big issue. We could have hcat:// and templeton:// schemes and
under the hood use most of the same code, just converting from one to the
other. Using /v#/ is also a valid option.
Personally, I would prefer the shorter form /<DB>/<TABLE>/<PARTITION>. But this
is just a personal preference.
Still, I don't see why HCAT would not want to formalize a recommendation on
HCAT URIs (even if they rubber stamp templeton URIs). That would make things
much easier for everybody. Can we try this?
> change HCatURI to comply with templeton URI format
> --------------------------------------------------
>
> Key: OOZIE-1111
> URL: https://issues.apache.org/jira/browse/OOZIE-1111
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Ryota Egashira
> Assignee: Ryota Egashira
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
