github  

Messages by Thread

• • Re: [I] arrow-buffer: Potential Undefined Behavior Reported by Miri [arrow-rs] via GitHub
• Re: [I] [Parquet] Allow sampling some values to decide the encoding pattern [arrow-rs] via GitHub
• Re: [PR] GH-48961: [Docs][Python] Doctest fails on pandas 3.0 [arrow] via GitHub
  • Re: [PR] GH-48961: [Docs][Python] Doctest fails on pandas 3.0 [arrow] via GitHub
  • Re: [PR] GH-48961: [Docs][Python] Doctest fails on pandas 3.0 [arrow] via GitHub
• [I] Support for GCS requester pays [arrow-rs-object-store] via GitHub
  • Re: [I] Support for GCS requester pays [arrow-rs-object-store] via GitHub
• Re: [PR] GH-48764: [C++] Update xsimd [arrow] via GitHub
  • Re: [PR] GH-48764: [C++] Update xsimd [arrow] via GitHub
  • Re: [PR] GH-48764: [C++] Update xsimd [arrow] via GitHub
  • Re: [PR] GH-48764: [C++] Update xsimd [arrow] via GitHub
  • Re: [PR] GH-48764: [C++] Update xsimd [arrow] via GitHub
  • Re: [PR] GH-48764: [C++] Update xsimd [arrow] via GitHub
  • Re: [PR] GH-48764: [C++] Update xsimd [arrow] via GitHub
• Re: [PR] GH-48254: [Python][Parquet] Support extension types in read_schema [arrow] via GitHub
• [PR] [regression] Error with adaptive predicate pushdown: "Invalid offset in sparse column chunk data: 754, no matching page found." [arrow-rs] via GitHub
  • Re: [PR] [regression] Error with adaptive predicate pushdown: "Invalid offset in sparse column chunk data: 754, no matching page found." [arrow-rs] via GitHub
  • Re: [PR] [regression] Error with adaptive predicate pushdown: "Invalid offset in sparse column chunk data: 754, no matching page found." [arrow-rs] via GitHub
  • Re: [PR] [regression] Error with adaptive predicate pushdown: "Invalid offset in sparse column chunk data: 754, no matching page found." [arrow-rs] via GitHub
  • Re: [PR] [regression] Error with adaptive predicate pushdown: "Invalid offset in sparse column chunk data: 754, no matching page found." [arrow-rs] via GitHub
  • Re: [PR] [regression] Error with adaptive predicate pushdown: "Invalid offset in sparse column chunk data: 754, no matching page found." [arrow-rs] via GitHub
  • Re: [PR] [regression] Error with adaptive predicate pushdown: "Invalid offset in sparse column chunk data: 754, no matching page found." [arrow-rs] via GitHub
• [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
  • Re: [PR] Orasort based sort kernels [arrow-rs] via GitHub
• [PR] GH-49059: [C++] Fix issues found by OSS-Fuzz in IPC reader [arrow] via GitHub
  • Re: [PR] GH-49059: [C++] Fix issues found by OSS-Fuzz in IPC reader [arrow] via GitHub
  • Re: [PR] GH-49059: [C++] Fix issues found by OSS-Fuzz in IPC reader [arrow] via GitHub
  • Re: [PR] GH-49059: [C++] Fix issues found by OSS-Fuzz in IPC reader [arrow] via GitHub
  • Re: [PR] GH-49059: [C++] Fix issues found by OSS-Fuzz in IPC reader [arrow] via GitHub
  • Re: [PR] GH-49059: [C++] Fix issues found by OSS-Fuzz in IPC reader [arrow] via GitHub
• [PR] GH-49059: Add IPC fuzz regression files [arrow-testing] via GitHub
  • Re: [PR] GH-49059: Add IPC fuzz regression files [arrow-testing] via GitHub
• Re: [PR] GH-28859: [Doc][Python] Use only code-block directive and set up doctest for the python user guide [arrow] via GitHub
  • Re: [PR] GH-28859: [Doc][Python] Use only code-block directive and set up doctest for the python user guide [arrow] via GitHub
  • Re: [PR] GH-28859: [Doc][Python] Use only code-block directive and set up doctest for the python user guide [arrow] via GitHub
  • Re: [PR] GH-28859: [Doc][Python] Use only code-block directive and set up doctest for the python user guide [arrow] via GitHub
  • Re: [PR] GH-28859: [Doc][Python] Use only code-block directive and set up doctest for the python user guide [arrow] via GitHub
  • Re: [PR] GH-28859: [Doc][Python] Use only code-block directive and set up doctest for the python user guide [arrow] via GitHub
• Re: [I] [Python][Packaging] Missing license files in 23.0.0 wheels [arrow] via GitHub
  • Re: [I] [Python][Packaging] Missing license files in 23.0.0 wheels [arrow] via GitHub
• [PR] Remove some unsafe and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
  • Re: [PR] Remove some `unsafe` and allocations when creating PrimitiveArrays from Vec and `from_trusted_len_iter` [arrow-rs] via GitHub
• Re: [I] [Parquet] Remove uses of ArrayData in favor of Direct Array construction [arrow-rs] via GitHub
• [I] [Epic] Replace `ArrayData` with direct Array construction, when possible [arrow-rs] via GitHub
• Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
  • Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
  • Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
  • Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
  • Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
  • Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
  • Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
  • Re: [PR] GH-36411: [C++][Python] Use meson-python for PyArrow build system [arrow] via GitHub
• [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] [WIP] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
  • Re: [PR] Use platform specific `read_at` when available [arrow-rs-object-store] via GitHub
• Re: [I] [CI][Python] Win job started failing on test_download_tzdata_on_windows [arrow] via GitHub
• Re: [I] Supporting Sets (HashSets) [arrow] via GitHub
• Re: [I] [C++] Fix ToStringWithoutContextLines to check for :\d+ pattern before removing lines [arrow] via GitHub
• Re: [I] [C++] [Gandiva] Enable Gandiva to run the LLVM in Interpreted mode [arrow] via GitHub
• Re: [I] [Website] FAQ page (and others) should allow linking to a heading [arrow] via GitHub
• Re: [I] [C++][Compute][Python] Move (majority of) kernel unit tests to python [arrow] via GitHub
• Re: [I] [Docs] Describe supported OS + client languages [arrow] via GitHub
• Re: [I] [C++] CSV add convert option to attempt 32bit number inferences [arrow] via GitHub
• Re: [I] [C++] Add/improve documentation about employing Arrow in downstream CMake projects [arrow] via GitHub
• Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
  • Re: [PR] GH-48467: [C++][Parquet] Add configure to limit the row group size in bytes [arrow] via GitHub
• Re: [PR] Add a crate for HeapSize trait [arrow-rs] via GitHub
  • Re: [PR] Add a crate for HeapSize trait [arrow-rs] via GitHub
  • Re: [PR] Add a crate for HeapSize trait [arrow-rs] via GitHub
  • Re: [PR] Add a crate for HeapSize trait [arrow-rs] via GitHub
  • Re: [PR] Add a crate for HeapSize trait [arrow-rs] via GitHub
• Re: [PR] Clarify behavior of `parse_url_opts` with regards to case sensitivity [arrow-rs-object-store] via GitHub
  • Re: [PR] Clarify behavior of `parse_url_opts` with regards to case sensitivity [arrow-rs-object-store] via GitHub
• [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` for byte aligned case [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
  • Re: [PR] Optimize `from_bitwise_unary_op` [arrow-rs] via GitHub
• Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub
  • Re: [PR] GH-49057: [Python][Packaging] Remove test base docker image and use single windows base image for both build and test containers [arrow] via GitHub

• Earlier messages
• Later messages