amol- commented on a change in pull request #12452: URL: https://github.com/apache/arrow/pull/12452#discussion_r822422219
########## File path: python/pyarrow/_exec_plan.pyx ########## @@ -0,0 +1,199 @@ +# 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. + +# --------------------------------------------------------------------- +# Implement Internal ExecPlan bindings + +# cython: profile=False +# distutils: language = c++ +# cython: language_level = 3 + +from cython.operator cimport dereference as deref, preincrement as inc + +from pyarrow.includes.common cimport * +from pyarrow.includes.libarrow cimport * +from pyarrow.lib cimport (Table, pyarrow_unwrap_table, pyarrow_wrap_table) +from pyarrow.lib import tobytes + + +cdef execplan(inputs, output_type, vector[CDeclaration] plan): Review comment: For now the plan is to avoid exposing `execplan` to end user, so the interface is low level. We should discuss in the near future about what we want to expose given that I think it would be reasonable to have an interface to lazily evaluate expressions (compared to doing `table.join().group_by()` which evaluates them step by step). But that shouldn't probably expose `execplan` itself, it should instead build one. -- 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]
