ianmcook commented on code in PR #44: URL: https://github.com/apache/arrow-experiments/pull/44#discussion_r1863919284
########## http/get_indirect/python/client/README.md: ########## @@ -0,0 +1,32 @@ +<!--- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> + +# HTTP GET Arrow Data: Indirect Python Client Example with `requests` + +This directory contains an example of an HTTP client implemented in Python using the built-in [`urllib.request`](https://docs.python.org/3/library/urllib.request.html) module. The client: +1. Sends a GET request to the server to get a JSON listing of the filenames of available `.arrows` files. +2. Sends GET requests to download each of the `.arrows` files from the server. +3. Loads the contents of each file into an in-memory PyArrow Table. + Review Comment: I added the JSON to the server example README. For purposes of these examples, the structure of the JSON is completely arbitrary and is provided only as an illustrative example. I do not want readers templating their applications on the exact structure of the JSON used in these examples. I added a note to the server README to say that. I think we should avoid trying to standardize the JSON at this stage. Later that might be an interesting piece of follow-up. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
