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
My only concern is that our Orc dialect for Hive Source and Sink delegates to the same code base for our native Orc Source and Sink and hence ignoring these table properties?
If this is the case we should automatically pick up these options from the Hive Metastore when using HiveSource and HiveSink, and support them natively when using the OrcSink and OrcSource?
The text was updated successfully, but these errors were encountered:
We completely ignore them at the moment, but you're right we should honour them where appropriate. We can still use the same source and sink, but when the dialect delegates it would need to pass in a config object pre-populated.
I just want to confirm that we respect the following Hive properties outlined in the documentation:
My only concern is that our Orc dialect for Hive Source and Sink delegates to the same code base for our native Orc Source and Sink and hence ignoring these table properties?
If this is the case we should automatically pick up these options from the Hive Metastore when using HiveSource and HiveSink, and support them natively when using the OrcSink and OrcSource?
The text was updated successfully, but these errors were encountered: