You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/04/06 08:15:38 UTC

[GitHub] [arrow-datafusion] thinkharderdev commented on issue #2136: No suitable object store found for ***

thinkharderdev commented on issue #2136:
URL: https://github.com/apache/arrow-datafusion/issues/2136#issuecomment-1089977567

   Hi @ZhangqyTJ as @yahoNanJing mentioned, the current implementation assumes that the `ObjectStore` will be registered on both the scheduler and executor and the only way to do that currently is to manually do the registration by creating your own entrypoint for those services. But that is not really ideal and there is an active discussion in #2111 on what the best way to proceed on that is. We can serialize parameters in the protobuf message but for the most part an extension `ObjectStore` will not be entirely serializable and at minimum require a dependency that is either included in the compiled binary or loaded through a plugin mechanism (similar to what is being done for UDF/UDAF in #1881)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org