paul-rogers commented on a change in pull request #1892: DRILL-7437: Storage 
Plugin for Generic HTTP REST API
URL: https://github.com/apache/drill/pull/1892#discussion_r390535951
 
 

 ##########
 File path: 
contrib/storage-http/src/main/java/org/apache/drill/exec/store/http/HttpAPIConfig.java
 ##########
 @@ -0,0 +1,131 @@
+/*
+ * 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.
+ */
+
+package org.apache.drill.exec.store.http;
 
 Review comment:
   HTTP could fetch movies, images, CSV files, Parquet files... pretty much 
anything. REST, however, is a request, with data encoded in the URL query 
string (usually, or in a POST), with response in the form of JSON. People wage 
huge battles about the "one true, pure REST", but most folks are pragmatic. 
This code fits the pragmatic description.
   
   If we did eventually do a file-over-http plugin what would we call that if 
not `http`? `filehttp`? If so, then wouldn't this be `resthttp`? Or, since REST 
implies HTTP, maybe just `rest`?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to