github  

Messages by Thread

• • Re: [PR] GH-47075: [Release][Dev] Use GH_TOKEN as GitHub token environment variable [arrow] via GitHub
  • Re: [PR] GH-47075: [Release][Dev] Use GH_TOKEN as GitHub token environment variable [arrow] via GitHub
  • Re: [PR] GH-47075: [Release][Dev] Use GH_TOKEN as GitHub token environment variable [arrow] via GitHub
  • Re: [PR] GH-47075: [Release][Dev] Use GH_TOKEN as GitHub token environment variable [arrow] via GitHub
  • Re: [PR] GH-47075: [Release][Dev] Use GH_TOKEN as GitHub token environment variable [arrow] via GitHub
• Re: [I] [C++] Compilation Failure - SortAndMarkDuplicate lacks expected .Run() method [arrow] via GitHub
  • Re: [I] [C++] Compilation Failure - SortAndMarkDuplicate lacks expected .Run() method [arrow] via GitHub
  • Re: [I] [C++] Compilation Failure - SortAndMarkDuplicate lacks expected .Run() method [arrow] via GitHub
  • Re: [I] [C++] Compilation Failure - SortAndMarkDuplicate lacks expected .Run() method [arrow] via GitHub
• [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
  • Re: [PR] [Variant] Avoid extra buffer allocation in ListBuilder [arrow-rs] via GitHub
• [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
  • Re: [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
  • Re: [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
  • Re: [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
  • Re: [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
  • Re: [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
  • Re: [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
  • Re: [PR] Implement full-range `i256::to_f64` to eliminate ±∞ saturation for Decimal256 → Float64 casts [arrow-rs] via GitHub
• [PR] feat(postgresql): add test for composite type behavior [arrow-adbc] via GitHub
  • Re: [PR] feat(c/driver/postgresql): add test for composite type behavior [arrow-adbc] via GitHub
  • Re: [PR] feat(c/driver/postgresql): add test for composite type behavior [arrow-adbc] via GitHub
  • Re: [PR] feat(c/driver/postgresql): add test for composite type behavior [arrow-adbc] via GitHub
  • Re: [PR] feat(c/driver/postgresql): add test for composite type behavior [arrow-adbc] via GitHub
  • Re: [PR] feat(c/driver/postgresql): add test for composite type behavior [arrow-adbc] via GitHub
  • Re: [PR] feat(c/driver/postgresql): add test for composite type behavior [arrow-adbc] via GitHub
• [I] Implement full-range `i256::to_f64` to replace current ±∞ saturation for Decimal256 → Float64 [arrow-rs] via GitHub
  • Re: [I] Implement full-range `i256::to_f64` to replace current ±∞ saturation for Decimal256 → Float64 [arrow-rs] via GitHub
• [PR] docs: add arrow struct <> postgresql composite status [arrow-adbc] via GitHub
  • Re: [PR] docs: add arrow struct <> postgresql composite status [arrow-adbc] via GitHub
  • Re: [PR] docs: add arrow struct <> postgresql composite status [arrow-adbc] via GitHub
• [PR] docs: fix typo in python/adbc_driver_postgresql/README.md [arrow-adbc] via GitHub
  • Re: [PR] docs: fix typo in python/adbc_driver_postgresql/README.md [arrow-adbc] via GitHub
• [PR] Use Vec directly in generic_bytes_builder [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [PR] Use `Vec` directly in builders [arrow-rs] via GitHub
• [PR] Fix ShouldReturnEmptyPkFkResult_WorksAsExpected test case [arrow-adbc] via GitHub
  • Re: [PR] fix(csharp/test/Drivers/Databricks): Fix Pkfk Testcase [arrow-adbc] via GitHub
• Re: [I] [C++] Define an official support policy [arrow] via GitHub
• Re: [PR] feat(go/adbc/driver/snowflake): Add support for table constraints when calling GetObjects [arrow-adbc] via GitHub
• Re: [I] Composite Postgres types <-> Arrow structs [arrow-adbc] via GitHub
• Re: [I] Python's `FileSystem.from_uri` changed to be a non-staticmethod [arrow] via GitHub
• [PR] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
  • Re: [PR] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
  • Re: [PR] GH-47179: [Python] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
  • Re: [PR] GH-47179: [Python] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
  • Re: [PR] GH-47179: [Python] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
  • Re: [PR] GH-47179: [Python] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
  • Re: [PR] GH-47179: [Python] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
  • Re: [PR] GH-47179: [Python] Revert FileSystem.from_uri to be a staticmethod again [arrow] via GitHub
• [PR] feat(csharp/test/Drivers/Databricks): Add mandatory token exchange [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/test/Drivers/Databricks): Add mandatory token exchange [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/test/Drivers/Databricks): Add mandatory token exchange [arrow-adbc] via GitHub
• [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
  • Re: [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
  • Re: [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
  • Re: [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
  • Re: [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
  • Re: [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
  • Re: [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
  • Re: [I] [DISCUSS] Decouple IO and CPU operations in the Parquet Reader (push decoder?) [arrow-rs] via GitHub
• Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
  • Re: [PR] GH-47016: [C++][FlightSQL] Fix negative timestamps to date types [arrow] via GitHub
• Re: [D] Is there any advantage to preallocate memory with Builder::with_capacity? [arrow-rs] via GitHub
  • Re: [D] Is there any advantage to preallocate memory with Builder::with_capacity? [arrow-rs] via GitHub
• [PR] GH-47137: [PYTHON] Switch to `[dependency-groups]` [arrow] via GitHub
  • Re: [PR] GH-47137: [PYTHON] Switch to `[dependency-groups]` [arrow] via GitHub
• [PR] [WIP] Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
  • Re: [PR] feat(csharp/src/Drivers/Databricks): Implement Telemetry Reporting for Databricks [arrow-adbc] via GitHub
• Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
  • Re: [I] 5000x performance degradation in RecordFromJSON vs NewJSONReader (yes really) [arrow-go] via GitHub
• [I] Field metadata for dictionary-encoded extension types is lost [arrow-rs] via GitHub
• Re: [PR] feat: Implement IPC RecordBatch body buffer compression [arrow-js] via GitHub
  • Re: [PR] feat: Implement IPC RecordBatch body buffer compression [arrow-js] via GitHub
• Re: [I] [C++] Nightly verification jobs fail on Ubuntu 24.04 to build byte_stream_split_internal.cc due to XSIMD failure [arrow] via GitHub
  • Re: [I] [C++] Nightly verification jobs fail on Ubuntu 24.04 to build byte_stream_split_internal.cc due to XSIMD failure [arrow] via GitHub
  • Re: [I] [C++] Nightly verification jobs fail on Ubuntu 24.04 to build byte_stream_split_internal.cc due to XSIMD failure [arrow] via GitHub
  • Re: [I] [C++] Nightly verification jobs fail on Ubuntu 24.04 to build byte_stream_split_internal.cc due to XSIMD failure [arrow] via GitHub
  • Re: [I] [C++] Nightly verification jobs fail on Ubuntu 24.04 to build byte_stream_split_internal.cc due to XSIMD failure [arrow] via GitHub
• [PR] [C++] Stricter data validation on Run-end encoded [arrow] via GitHub
  • Re: [PR] [C++] Stricter data validation on Run-end encoded [arrow] via GitHub
• Re: [I] [Python] Unable to import arrow table to pandas if it has categorical columns with index types of unsigned ints [arrow] via GitHub
  • Re: [I] [Python] Unable to import arrow table to pandas if it has categorical columns with index types of unsigned ints [arrow] via GitHub
  • Re: [I] [Python] Unable to import arrow table to pandas if it has categorical columns with index types of unsigned ints [arrow] via GitHub
• [PR] Derive `Serialize` and `Deserialize` on `CastOptions` [arrow-rs] via GitHub
  • Re: [PR] Derive `Serialize` and `Deserialize` on `CastOptions` [arrow-rs] via GitHub
  • Re: [PR] Derive `Serialize` and `Deserialize` on `CastOptions` [arrow-rs] via GitHub
  • Re: [PR] Derive `Serialize` and `Deserialize` on `CastOptions` [arrow-rs] via GitHub
  • Re: [PR] Derive `Serialize` and `Deserialize` on `CastOptions` [arrow-rs] via GitHub
• Re: [I] Panic when casting large Decimal256 to f64 due to unchecked `unwrap()` [arrow-rs] via GitHub
  • Re: [I] Panic when casting large Decimal256 to f64 due to unchecked `unwrap()` [arrow-rs] via GitHub
• [I] Consider updating `i256::to_f64` to handle overflow [arrow-rs] via GitHub
• Re: [I] [C++][Python] Duplicate csv header when table batches start with empty [arrow] via GitHub
• [PR] TESTING: Use standard BitIndexIterator instead of specialized u32 iterator [arrow-rs] via GitHub
  • Re: [PR] TESTING: Use standard BitIndexIterator instead of specialized u32 iterator [arrow-rs] via GitHub
  • Re: [PR] TESTING: Use standard BitIndexIterator instead of specialized u32 iterator [arrow-rs] via GitHub
  • Re: [PR] TESTING: Use standard BitIndexIterator instead of specialized u32 iterator [arrow-rs] via GitHub
  • Re: [PR] TESTING: Use standard BitIndexIterator instead of specialized u32 iterator [arrow-rs] via GitHub
  • Re: [PR] TESTING: Use standard BitIndexIterator instead of specialized u32 iterator [arrow-rs] via GitHub
• Re: [I] [C++] Add JSON/NDJSON writer to Arrow C++ core — then expose via PyArrow/Java [arrow] via GitHub
• Re: [I] Unable to import arrow table to pandas if it has categorical columns with index types of unsigned ints [arrow] via GitHub
• Re: [PR] GH-46942: [Docs] Quote the version argument in versionadded directives [arrow] via GitHub
  • Re: [PR] GH-46942: [Docs] Quote the version argument in versionadded directives [arrow] via GitHub
• Re: [I] [Python] Pyarrow drop support for old Linux distros? [arrow] via GitHub
  • Re: [I] [Python] Pyarrow drop support for old Linux distros? [arrow] via GitHub
  • Re: [I] [Python] Pyarrow drop support for old Linux distros? [arrow] via GitHub
  • Re: [I] [Python] Pyarrow drop support for old Linux distros? [arrow] via GitHub
• [I] Optimize the object header generation logic in ObjectBuilder::finish [arrow-rs] via GitHub
  • Re: [I] Optimize the object header generation logic in ObjectBuilder::finish [arrow-rs] via GitHub
• [I] Avoid extra allocation in list builder [arrow-rs] via GitHub
  • Re: [I] Avoid extra allocation in list builder [arrow-rs] via GitHub
  • Re: [I] [Variant] Avoid extra allocation in list builder [arrow-rs] via GitHub
  • Re: [I] [Variant] Avoid extra allocation in list builder [arrow-rs] via GitHub
• Re: [I] Consider using `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [I] Consider using `Vec` directly in builders [arrow-rs] via GitHub
  • Re: [I] Consider using `Vec` directly in builders [arrow-rs] via GitHub
• [PR] MINOR: [Docs][Python] Fix usage of pyarrow and PyArrow in extending_types.rst [arrow] via GitHub
  • Re: [PR] MINOR: [Docs][Python] Fix usage of pyarrow and PyArrow in extending_types.rst [arrow] via GitHub
• [PR] Add implementation specific attributes [arrow-rs-object-store] via GitHub
• [I] Support implementation-specific attributes [arrow-rs-object-store] via GitHub
  • Re: [I] Support implementation-specific attributes [arrow-rs-object-store] via GitHub
  • Re: [I] Support implementation-specific attributes [arrow-rs-object-store] via GitHub
  • Re: [I] Support implementation-specific attributes [arrow-rs-object-store] via GitHub
  • Re: [I] Support implementation-specific attributes [arrow-rs-object-store] via GitHub
  • Re: [I] Support implementation-specific attributes [arrow-rs-object-store] via GitHub
• Re: [PR] GH-46315 [C#] Apache Arrow Flight Middleware [arrow] via GitHub
  • Re: [PR] GH-46315 [C#] Apache Arrow Flight Middleware [arrow] via GitHub
  • Re: [PR] GH-46315 [C#] Apache Arrow Flight Middleware [arrow] via GitHub

• Earlier messages
• Later messages