You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of HiveTableDescriptor makes it difficult to create a table with a non-default location or a custom input/output format (there may be other limitations, but those are the two most notable that I've seen). Why not allow people to create a org.apache.hadoop.hive.metastore.api.Table object directly and then just pass it in to the HiveTableDescriptor constructor. The folks who don't want to know about storage descriptors, etc can keep using the existing constructors, but I think this new constructor would be essential for anyone who has even moderately customized Hive tables.
The text was updated successfully, but these errors were encountered:
I like the idea. Basically we would have to revert the logic within the class. I am currently pretty busy with other assignments, so if you want to give it a go, I can review your changes and integrate them.
The current implementation of HiveTableDescriptor makes it difficult to create a table with a non-default location or a custom input/output format (there may be other limitations, but those are the two most notable that I've seen). Why not allow people to create a org.apache.hadoop.hive.metastore.api.Table object directly and then just pass it in to the HiveTableDescriptor constructor. The folks who don't want to know about storage descriptors, etc can keep using the existing constructors, but I think this new constructor would be essential for anyone who has even moderately customized Hive tables.
The text was updated successfully, but these errors were encountered: