[
https://issues.apache.org/jira/browse/HCATALOG-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mithun Radhakrishnan updated HCATALOG-561:
------------------------------------------
Attachment: HCATALOG-561.rebased.trunk.patch
HCATALOG-561.rebased.branch4.patch
> HCatClient should differentiate between "partition not available" and other
> generic errors.
> -------------------------------------------------------------------------------------------
>
> Key: HCATALOG-561
> URL: https://issues.apache.org/jira/browse/HCATALOG-561
> Project: HCatalog
> Issue Type: Bug
> Components: client
> Affects Versions: 0.4
> Reporter: Mithun Radhakrishnan
> Assignee: Mithun Radhakrishnan
> Fix For: 0.5, 0.4.1
>
> Attachments: HCATALOG-561.branch4.patch,
> HCATALOG-561.rebased.branch4.patch, HCATALOG-561.rebased.trunk.patch,
> HCATALOG-561.trunk.patch
>
>
> In its current form, HCatClient::getPartition() throws the same HCatException
> for the following cases:
> 1. When the client fails to connect to the HCat-server (because of network
> error or downtime).
> 2. When the partition specified by the partition-spec doesn't exist.
> There really should be a distinction between these cases. #1 is an
> exceptional case that we don't expect to happen often. #2, on the other hand,
> is a valid return, that's likely to happen. It might make sense to continue
> to throw exceptions for #1, but return a null (or throw a different, more
> specific exception) for #2.
> The same holds for HCatClient::listPartitionsByFilter().
--
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
