hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-2773) HiveStorageHandler.configureTableJobProperites() should let the handler know wether it is configuration for input or output
Date Wed, 22 Feb 2012 21:37:48 GMT

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

Ashutosh Chauhan commented on HIVE-2773:
----------------------------------------

This will effectively break backwards compatibility since you are removing a method from an
interface. You can get around this by keeping original method as well as introducing new ones.
Then, at the time of invocation of these methods, you can check if newer methods exists, if
they do then invoke them else invoke old method. Then, we can deprecate old method. But, before
you go down that path and introduce code complexity I suggest you send an email on user@hive
to check with people if they are ok with your current approach as is and will be able to upgrade
their storage handlers, in which case we can go ahead with this current approach.
                
> HiveStorageHandler.configureTableJobProperites() should let the handler know wether it
is configuration for input or output
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-2773
>                 URL: https://issues.apache.org/jira/browse/HIVE-2773
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Francis Liu
>              Labels: hcatalog, storage_handler
>         Attachments: HIVE-2773.D1815.1.patch, HIVE-2773.patch
>
>
> HiveStorageHandler.configureTableJobProperties() is called to allow the storage handler
to setup any properties that the underlying inputformat/outputformat/serde may need. But the
handler implementation does not know whether it is being called for configuring input or output.
This makes it a problem for handlers which sets an external state. In the case of HCatalog's
HBase storageHandler, whenever a write needs to be configured we create a write transaction
which needs to be committed or aborted later on. In this case configuring for both input and
output each time configureTableJobProperties() is called would not be desirable. This has
become an issue since HCatalog is dropping storageDrivers for SerDe and StorageHandler (see
HCATALOG-237).
> My proposal is to replace configureTableJobProperties() with two methods:
> configureInputJobProperties()
> configureOutputJobProperties()
> Each method will have the same signature. I cursory look at the code and I believe changes
should be straighforward also given that we are not really changing anything just splitting
responsibility. If the community is fine with this approach I will go ahead and create a aptch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message