westonpace commented on code in PR #12872:
URL: https://github.com/apache/arrow/pull/12872#discussion_r851066060


##########
cpp/src/arrow/compute/light_array.h:
##########
@@ -0,0 +1,384 @@
+// 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.
+
+#pragma once
+
+#include <cstdint>
+
+#include "arrow/array.h"
+#include "arrow/compute/exec.h"
+#include "arrow/type.h"
+#include "arrow/util/logging.h"
+
+/// This file contains lightweight containers for Arrow buffers.  These 
containers
+/// makes compromises in terms of strong ownership and the range of data types 
supported
+/// in order to gain performance and reduced overhead.

Review Comment:
   Yes, this isn't intended to be a wholesale replacement of ExecBatch, rather 
something that is small enough to get a PR through improving the hash-join 
performance.  Once that is done we can either grow these tools to support more 
types, replace them with something more complete but more efficient, or accept 
multiple variations of kernels/nodes depending on benchmarks and need.
   
   I think, by having these tools here, it will be easier to evaluate and work 
on potential replacements for ExecBatch, even if someone doesn't know the ins 
and outs of the join algorithm.



-- 
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]

Reply via email to