lidavidm commented on PR #193:
URL: https://github.com/apache/arrow-cookbook/pull/193#issuecomment-1136305145

   @davisusanibar it looks like 
   
   ```java
               try {
                   flightServer.start();
                   System.out.println("S1: Server (Location): Listening on port 
" + flightServer.getPort());
               } catch (IOException e) {
                   System.exit(1);
               }
   ```
   
   in one of the examples actually hit the `catch` and that `System.exit` 
causes jshell to print the `State engine terminated`
   
   ```
   Expected:
       S1: Server (Location): Listening on port 33333
       C1: Client (Location): Connected to grpc+tcp://0.0.0.0:33333
       C2: Client (Populate Data): Wrote 2 batches with 3 rows each
       C3: Client (Get Metadata): FlightInfo{schema=Schema<name: Utf8>, 
descriptor=profiles, 
endpoints=[FlightEndpoint{locations=[Location{uri=grpc+tcp://0.0.0.0:33333}], 
ticket=org.apache.arrow.flight.Ticket@58871b0a}], bytes=-1, records=6}
       C4: Client (Get Stream):
       Client Received batch #1, Data:
       name
       Ronald
       David
       Francisco
       Client Received batch #2, Data:
       name
       Manuel
       Felipe
       JJ
       C5: Client (List Flights Info): FlightInfo{schema=Schema<name: Utf8>, 
descriptor=profiles, 
endpoints=[FlightEndpoint{locations=[Location{uri=grpc+tcp://0.0.0.0:33333}], 
ticket=org.apache.arrow.flight.Ticket@58871b0a}], bytes=-1, records=6}
       C6: Client (Do Delete Action): Delete completed
       C7: Client (List Flights Info): After delete - No records
       C8: Server shut down successfully
   Got:
       State engine terminated.
   **********************************************************************
   ```
   
   IMO we should have `e.printStackTrace()` there for debugging
   
   but in the meantime I'll kick the CI 


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