github  

Messages by Thread

• [PR] feat(spark): port Spark-compatible Parquet schema adapter from Comet [datafusion] via GitHub
  • Re: [PR] feat(spark): port Spark-compatible Parquet schema adapter from Comet [datafusion] via GitHub
• Re: [I] KEDA scaler `pending_jobs` metric appears insufficient for scaling due to rapid task assignment by scheduler [datafusion-ballista] via GitHub
  • Re: [I] KEDA scaler `pending_jobs` metric appears insufficient for scaling due to rapid task assignment by scheduler [datafusion-ballista] via GitHub
  • Re: [I] KEDA scaler `pending_jobs` metric appears insufficient for scaling due to rapid task assignment by scheduler [datafusion-ballista] via GitHub
• Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.0.0` (Apr 2026 / May 2026) [datafusion] via GitHub
• [PR] refactor: thread SubqueryContext explicitly through physical planning [datafusion] via GitHub
  • Re: [PR] refactor: thread SubqueryContext explicitly through physical planning [datafusion] via GitHub
  • Re: [PR] refactor: thread SubqueryContext explicitly through physical planning [datafusion] via GitHub
• [PR] feat(udf)!: switch ScalarFunction.evaluate to ColumnarValue API (closes #62) [datafusion-java] via GitHub
  • Re: [PR] feat(udf)!: switch ScalarFunction.evaluate to ColumnarValue API (closes #62) [datafusion-java] via GitHub
  • Re: [PR] feat(udf)!: switch ScalarFunction.evaluate to ColumnarValue API (closes #62) [datafusion-java] via GitHub
  • Re: [PR] feat(udf)!: switch ScalarFunction.evaluate to ColumnarValue API (closes #62) [datafusion-java] via GitHub
• [I] Add Spark-compatible Parquet reader [datafusion] via GitHub
• [I] Change UDF signature to use ColumnarValue rather than raw Arrow types [datafusion-comet] via GitHub
  • Re: [I] Change UDF signature to use ColumnarValue rather than raw Arrow types [datafusion-comet] via GitHub
• Re: [I] Frequent CI failures for Spark 4.0.2 / JDK 21 [datafusion-comet] via GitHub
  • Re: [I] Frequent CI failures for Spark 4.0.2 / JDK 21 [datafusion-comet] via GitHub
  • Re: [I] Frequent CI failures for Spark 4.0.2 / JDK 21 [datafusion-comet] via GitHub
• Re: [I] [DISCUSSION] Extending Partitioning to Support More Variants [datafusion] via GitHub
  • Re: [I] [DISCUSSION] Extending Partitioning to Support More Variants [datafusion] via GitHub
  • Re: [I] [DISCUSSION] Extending Partitioning to Support More Variants [datafusion] via GitHub
• Re: [PR] feat: cross-engine Spark-dialect SLT tests [datafusion] via GitHub
  • Re: [PR] feat: cross-engine Spark-dialect SLT tests [datafusion] via GitHub
• Re: [PR] feat: Add `FFI_QueryPlanner` to support foreign query planners across shared-library boundaries [datafusion] via GitHub
  • Re: [PR] feat: Add `FFI_QueryPlanner` to support foreign query planners across shared-library boundaries [datafusion] via GitHub
  • Re: [PR] feat: Add `FFI_QueryPlanner` to support foreign query planners across shared-library boundaries [datafusion] via GitHub
• [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
  • Re: [I] Simplified filter expression has a Null type instead of Int64 type across the FFI layer [datafusion-python] via GitHub
• Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
  • Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
  • Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
  • Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
  • Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
  • Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
  • Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
  • Re: [PR] feat: Credential provider support [datafusion-comet] via GitHub
• Re: [PR] Expose `ExecutionPlan` statistics across the FFI boundary [datafusion] via GitHub
  • Re: [PR] Expose `ExecutionPlan` statistics across the FFI boundary [datafusion] via GitHub
  • Re: [PR] Expose `ExecutionPlan` statistics across the FFI boundary [datafusion] via GitHub
  • Re: [PR] Expose `ExecutionPlan` statistics across the FFI boundary [datafusion] via GitHub
• [I] Add support for Java data sources [datafusion-java] via GitHub
  • Re: [I] Add support for Java data sources [datafusion-java] via GitHub
• [PR] feat: make task popup scrollable [datafusion-ballista] via GitHub
  • Re: [PR] feat: make task popup scrollable [datafusion-ballista] via GitHub
  • Re: [PR] feat: TUI make task popup scrollable [datafusion-ballista] via GitHub
  • Re: [PR] feat: TUI make task popup scrollable [datafusion-ballista] via GitHub
  • Re: [PR] feat: TUI make task popup scrollable [datafusion-ballista] via GitHub
  • Re: [PR] feat: TUI make task popup scrollable [datafusion-ballista] via GitHub
  • Re: [PR] feat: TUI make task popup scrollable [datafusion-ballista] via GitHub
  • Re: [PR] feat: TUI make task popup scrollable [datafusion-ballista] via GitHub
• [I] Change UDF signature to use `ColumnarValue` rather than raw Arrow types [datafusion-java] via GitHub
  • Re: [I] Change UDF signature to use `ColumnarValue` rather than raw Arrow types [datafusion-java] via GitHub
• Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
  • Re: [I] [EPIC] A collection of support for metadata columns in ListingTable [datafusion] via GitHub
• [PR] fix: lag i64::MIN offset overflow [datafusion] via GitHub
  • Re: [PR] fix: lag i64::MIN offset overflow [datafusion] via GitHub
  • Re: [PR] fix: lag i64::MIN offset overflow [datafusion] via GitHub
• [I] TUI: task for stage should be scrollable [datafusion-ballista] via GitHub
  • Re: [I] TUI: task for stage should be scrollable [datafusion-ballista] via GitHub
  • Re: [I] TUI: task for stage should be scrollable [datafusion-ballista] via GitHub
  • Re: [I] TUI: task for stage should be scrollable [datafusion-ballista] via GitHub
• [I] FFI: `FFI_SchemaProvider` missing `table_type` cheap-path [datafusion] via GitHub
• [I] FFI: confirm `FFI_RecordBatchStream` does not need `library_marker_id` [datafusion] via GitHub
  • Re: [I] FFI: confirm `FFI_RecordBatchStream` does not need `library_marker_id` [datafusion] via GitHub
  • Re: [I] FFI: confirm `FFI_RecordBatchStream` does not need `library_marker_id` [datafusion] via GitHub
  • Re: [I] FFI: confirm `FFI_RecordBatchStream` does not need `library_marker_id` [datafusion] via GitHub
• [I] FFI: `FFI_PartitionEvaluator` missing `memoize` [datafusion] via GitHub
  • Re: [I] FFI: `FFI_PartitionEvaluator` missing `memoize` [datafusion] via GitHub
• [I] FFI: `FFI_GroupsAccumulator` missing `size` [datafusion] via GitHub
  • Re: [I] FFI: `FFI_GroupsAccumulator` missing `size` [datafusion] via GitHub
  • Re: [I] FFI: `FFI_GroupsAccumulator` missing `size` [datafusion] via GitHub
  • Re: [I] FFI: `FFI_GroupsAccumulator` missing `size` [datafusion] via GitHub
• [I] FFI: `FFI_PhysicalOptimizerRule` missing `optimize_with_context` [datafusion] via GitHub
  • Re: [I] FFI: `FFI_PhysicalOptimizerRule` missing `optimize_with_context` [datafusion] via GitHub
  • Re: [I] FFI: `FFI_PhysicalOptimizerRule` missing `optimize_with_context` [datafusion] via GitHub
• [I] FFI: `FFI_WindowUDF` silently drops producer overrides of defaulted trait methods [datafusion] via GitHub
• [I] FFI: `FFI_AggregateUDF` silently drops producer overrides of defaulted trait methods [datafusion] via GitHub
• [I] FFI: `FFI_ExecutionPlan` silently drops producer overrides of optimizer-relevant defaults [datafusion] via GitHub
  • Re: [I] FFI: `FFI_ExecutionPlan` silently drops producer overrides of optimizer-relevant defaults [datafusion] via GitHub
• [I] FFI: `FFI_ScalarUDF` silently drops producer overrides of defaulted trait methods [datafusion] via GitHub
• [I] FFI: `FFI_TableProvider` silently drops producer overrides of defaulted trait methods [datafusion] via GitHub
• [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
  • Re: [PR] docs: add agent skill for datafusion-ffi crate patterns [datafusion] via GitHub
• [PR] feat(AQE): added empty join handling [datafusion-ballista] via GitHub
  • Re: [PR] feat(AQE): empty join handling [datafusion-ballista] via GitHub
• Re: [I] PostgreSQL compatibility: `time + interval` should wrap within the 24-hour time domain [datafusion] via GitHub
• Re: [I] How to check the execution time of stages? [datafusion-ballista] via GitHub
  • Re: [I] How to check the execution time of stages? [datafusion-ballista] via GitHub
• Re: [I] Create PyPi Release Process [datafusion-ballista] via GitHub
  • Re: [I] Create PyPi Release Process [datafusion-ballista] via GitHub
• Re: [I] feat: make it user configurable to display plans as tree renderer [datafusion-ballista] via GitHub
  • Re: [I] feat: make it user configurable to display plans as tree renderer [datafusion-ballista] via GitHub
• Re: [I] Reorder boolean expressions (including filter predicates) according to evaluation cost / selectivity [datafusion] via GitHub
  • Re: [I] Reorder boolean expressions (including filter predicates) according to evaluation cost / selectivity [datafusion] via GitHub
  • Re: [I] Reorder boolean expressions (including filter predicates) according to evaluation cost / selectivity [datafusion] via GitHub
  • Re: [I] Reorder boolean expressions (including filter predicates) according to evaluation cost / selectivity [datafusion] via GitHub
• Re: [I] PostgreSQL compatibility: `factorial(21)` should not overflow when PostgreSQL returns a numeric answer [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `factorial(21)` should not overflow when PostgreSQL returns a numeric answer [datafusion] via GitHub
• Re: [D] DISCUSSION: Apache DataFusion New York Meetup May 2026 [datafusion] via GitHub
• Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
  • Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
  • Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
  • Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
  • Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
  • Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
  • Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
  • Re: [PR] test: cover push scheduling in client integration tests [datafusion-ballista] via GitHub
• Re: [I] Semver CI should compare against last released API, not main [datafusion] via GitHub
  • Re: [I] Semver CI should compare against last released API, not main [datafusion] via GitHub
  • Re: [I] Semver CI should compare against last released API, not main [datafusion] via GitHub
  • Re: [I] Semver CI should compare against last released API, not main [datafusion] via GitHub
  • Re: [I] Semver CI should compare against last released API, not main [datafusion] via GitHub
  • Re: [I] Semver CI should compare against last released API, not main [datafusion] via GitHub
  • Re: [I] Semver CI should compare against last released API, not main [datafusion] via GitHub
• Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
• Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub
  • Re: [PR] feat(functions-nested): add array_filter higher-order function [datafusion] via GitHub

• Earlier messages
• Later messages