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

Alan Gates commented on HIVE-17981:
-----------------------------------

I don't know what your timeline looks like, but waiting might mean waiting for 
a while.  On average it's taking a couple of weeks per patch to get these into 
master, which means a month or more before the builders or test moves are in.

I agree it looks like we're working in the same areas and likely to bump into 
each other.  

Does it make sense for you to put your work into the standalone-metastore 
branch as well?  That is assuming you're ok with the builders and test moves 
(HIVE-17982) that I put in there.  That would mean waiting a while until your 
work is in master, but it would avoid us duplicating work or invalidating each 
other's patches.

> Create a set of builders for Thrift classes
> -------------------------------------------
>
>                 Key: HIVE-17981
>                 URL: https://issues.apache.org/jira/browse/HIVE-17981
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Standalone Metastore
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>            Priority: Major
>
> Instantiating some of the Thrift classes is painful.  Consider building a 
> {{Table}} object, which requires a {{StorageDescriptor}}, which requires a 
> {{SerDeInfo}} and a list of {{FieldInfo}}.  All that is really necessary for 
> a Table in the most simple case is a name, a database, and some columns.  But 
> currently creating even a simple Table requires 20+ lines of code.  This is 
> particularly painful in tests.  
> I propose to add a set of builders.  These will come with reasonable defaults 
> to minimize the boilerplate code.  They will also include simple methods for 
> common operations (like adding columns, or a parameter) without requiring the 
> user to create all the sub-objects (like {{StorageDescriptor}}).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to