TheGuptaEmpire commented on issue #37884:
URL: https://github.com/apache/arrow/issues/37884#issuecomment-1736026552

   Bug Report:
   
   Summary:
   When making a `FlightClient.doGet` call, processing UTF-8 data generated 
from the flight server using `arrow-rs` library leads to a fatal error due to 
misaligned raw pointer.
   
   Details:
   The issue arises when attempting to process a simple `testString` in a 
single `TEST` column. This problem specifically occurs in Swift and does not 
occur when using the Python flight server.
   
   Error Messages:
   ```
   Swift/UnsafeRawPointer.swift:1203: Fatal error: load from misaligned raw 
pointer
   ```
   
   System Details:
   - Xcode Version: 15.0 beta 8 (15A5229m)
   - Building for: Apple Vision Pro Simulator
   - Swift-Driver version: 1.87.1
   - Apple Swift version: 5.9 (swiftlang-5.9.0.128.106 clang-1500.0.40.1)
   
   Component(s):
   - Swift
   
   Steps to Reproduce:
   
   1. Use Xcode Version 15.0 beta 8 (15A5229m) with Swift-Driver version 1.87.1.
   2. Set up a FlightClient and attempt a `doGet` call.
   3. Ensure the data being processed is UTF-8 generated from the flight server 
using `arrow-rs`.
   4. Verify that the data contains a `testString` in a single `TEST` column.
   
   Expected Results:
   The `doGet` call should process the UTF-8 data without encountering any 
misaligned raw pointer errors.
   
   Actual Results:
   A fatal error occurs due to a misaligned raw pointer during the processing 
of the UTF-8 data.
   
   Additional Notes:
   - This issue does not occur when using the Python flight server, indicating 
that it is specific to the Swift implementation.
   - It is important to investigate and resolve the misalignment of raw 
pointers when processing the UTF-8 data in Swift.


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