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
Currently the LocationProviders class only load either DefaultLocationProvider which follows the Hive standard or the ObjectStoreLocationProvider that is optimized for cloud storage use case. Use cases like #1531 will become increasingly common, and we should allow users to load their custom location providers without the need to change core package.
Therefore, I propose dynamically loading the LocationProvider implementation in the method LocationProviders.locationsFor and use new table property write.location-provider.class to determine the class. Table property write.object-storage.enabled will still be supported to keep backwards compatibility.
Plan to submit a PR in 1-2 days, please let me know if there is any concern, thanks.
The text was updated successfully, but these errors were encountered:
Currently the
LocationProviders
class only load eitherDefaultLocationProvider
which follows the Hive standard or theObjectStoreLocationProvider
that is optimized for cloud storage use case. Use cases like #1531 will become increasingly common, and we should allow users to load their custom location providers without the need to change core package.Therefore, I propose dynamically loading the
LocationProvider
implementation in the methodLocationProviders.locationsFor
and use new table propertywrite.location-provider.class
to determine the class. Table propertywrite.object-storage.enabled
will still be supported to keep backwards compatibility.Plan to submit a PR in 1-2 days, please let me know if there is any concern, thanks.
The text was updated successfully, but these errors were encountered: