zeroshade commented on code in PR #38385:
URL: https://github.com/apache/arrow/pull/38385#discussion_r1428476176


##########
go/arrow/flight/flightsql/client.go:
##########
@@ -218,6 +218,58 @@ func (c *Client) ExecuteSubstraitUpdate(ctx 
context.Context, plan SubstraitPlan,
        return updateResult.GetRecordCount(), nil
 }
 
+var ErrTooManyPutResults = fmt.Errorf("%w: server sent multiple PutResults, 
expected one ", arrow.ErrInvalid)
+
+// ExecuteIngest is for executing a bulk ingestion and only returns the number 
of affected rows.
+func (c *Client) ExecuteIngest(ctx context.Context, rdr array.RecordReader, 
reqOptions *ExecuteIngestOpts, opts ...grpc.CallOption) (n int64, err error) {
+       var (
+               desc         *flight.FlightDescriptor
+               stream       pb.FlightService_DoPutClient
+               wr           *flight.Writer
+               res          *pb.PutResult
+               updateResult pb.DoPutUpdateResult
+       )
+
+       cmd := (*pb.CommandStatementIngest)(reqOptions)
+       if desc, err = descForCommand(cmd); err != nil {
+               return
+       }
+
+       if stream, err = c.Client.DoPut(ctx, opts...); err != nil {
+               return
+       }
+
+       wr = flight.NewRecordWriter(stream, ipc.WithAllocator(c.Alloc), 
ipc.WithSchema(rdr.Schema()))
+       defer wr.Close()
+
+       wr.SetFlightDescriptor(desc)
+
+       for rdr.Next() {
+               rec := rdr.Record()
+               wr.Write(rec)
+       }
+

Review Comment:
   there's some error handling to be done here...
   
   We should check the return of `wr.Write(rec)` which returns an `error`, in 
case we encounter an error while writing.
   
   In addition, after this loop we should probably check `rdr.Err()` in case 
the reader itself encountered an error.
   
   Also, is this function responsible for calling `Release` on the reader? or 
is the calling function responsible?



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