[
https://issues.apache.org/jira/browse/ARROW-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062166#comment-17062166
]
Clark Zinzow commented on ARROW-1231:
-------------------------------------
[~wesm] Ah I don't think I was very clear, sorry about that. I'm mostly
interested (as an Arrow user) in being able to use GCS as an external store for
Plasma, ARROW-8031; I was offering to work on the GCS filesystem implementation
issue since I thought that it was a prerequisite for the Plasma external store
issue. AFAICT, the only real blockers for working on the external store
implementation for Plasma is adding a google-cloud-cpp conda-forge recipe and
adding google-cloud-cpp to ThirdPartyToolchain, ARROW-8147 and ARROW-8148;
i.e., if those packaging/toolchain issues are broken out as separate from the
GCS filesystem issue, then this GCS filesystem implementation is _not_ a
prerequisite for the external store implementation for Plasma.
If that is the case, I'm asking if I (or someone else, if they are interested)
could take on the packaging/toolchain issues ARROW-8147 and ARROW-8148, and
once those are finished, I could work on the GCS external store implementation
for Plasma. This would leave the much larger effort around the GCS filesystem
implementation for later.
Does that make sense? And is my judgement of the actual GCS filesystem
implementation _not_ being a prerequisite for the GCS external store
implementation for Plasma correct?
> [C++] Add filesystem / IO implementation for Google Cloud Storage
> -----------------------------------------------------------------
>
> Key: ARROW-1231
> URL: https://issues.apache.org/jira/browse/ARROW-1231
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
> Labels: filesystem
>
> See example jumping off point
> https://github.com/tensorflow/tensorflow/tree/master/tensorflow/core/platform/cloud
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
