returnString opened a new issue #273: URL: https://github.com/apache/arrow-datafusion/issues/273
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** When [testing Ballista on a Raspberry Pi cluster](https://github.com/apache/arrow-datafusion/issues/243) using a 32-bit OS, it was noted that whilst we don't _officially_ support 32-bit builds at present, we only actually have one specific test case that fails for that arch. To ensure our continued robustness across architectures, I'd like to add some minimal CI support to ensure that this doesn't slip. **Describe the solution you'd like** - Add a new CI check that runs the tests using a 32-bit Linux build - Fix any existing arch-related assumptions in the codebase (e.g. hardcoding ptr sizes at 8 bytes instead of `std::mem::size_of::<usize>()`) **Describe alternatives you've considered** - Explicitly disallowing compilation for 32-bit targets: this might impact on future possibilities like targeting wasm32 for Rust-in-browser use cases (less important for DataFusion than Arrow perhaps, but I can personally envisage at least one use case for this) - Doing nothing: this feels lazy 🤷♂️ **Additional context** This work will depend on apache/arrow-rs#262 (equivalent work for Arrow proper). -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
