github  

Messages by Thread

• • Re: [I] Deduplicate Spark function code with native/default datafusion function code [datafusion] via GitHub
  • Re: [I] Deduplicate Spark function code with native/default datafusion function code [datafusion] via GitHub
  • Re: [I] Deduplicate Spark function code with native/default datafusion function code [datafusion] via GitHub
  • Re: [I] Deduplicate Spark function code with native/default datafusion function code [datafusion] via GitHub
  • Re: [I] Deduplicate Spark function code with native/default datafusion function code [datafusion] via GitHub
• [I] CI failing on main due to storage issues [datafusion] via GitHub
  • Re: [I] CI failing on main due to storage issues [datafusion] via GitHub
  • Re: [I] CI failing on main due to storage issues [datafusion] via GitHub
  • Re: [I] CI failing on main due to storage issues [datafusion] via GitHub
  • Re: [I] CI failing on main due to storage issues [datafusion] via GitHub
  • Re: [I] CI failing on main due to storage issues [datafusion] via GitHub
• [PR] Add Explicit Error Handling for Unsupported SQL `FETCH` Clause in Planner and CLI [datafusion] via GitHub
  • Re: [PR] Add Explicit Error Handling for Unsupported SQL `FETCH` Clause in Planner and CLI [datafusion] via GitHub
• [PR] Consolidate query planning examples (#18142) [datafusion] via GitHub
  • Re: [PR] Consolidate query planning examples (#18142) [datafusion] via GitHub
  • Re: [PR] Consolidate query planning examples (#18142) [datafusion] via GitHub
• [I] Minor enhancements to `EXPLAIN ANALYZE` output formatting [datafusion] via GitHub
  • Re: [I] Minor enhancements to `EXPLAIN ANALYZE` output formatting [datafusion] via GitHub
  • Re: [I] Minor enhancements to `EXPLAIN ANALYZE` output formatting [datafusion] via GitHub
  • Re: [I] Minor enhancements to `EXPLAIN ANALYZE` output formatting [datafusion] via GitHub
• Re: [PR] feat(parquet): Implement `scan_efficiency_ratio` metric for parquet reading [datafusion] via GitHub
  • Re: [PR] feat(parquet): Implement `scan_efficiency_ratio` metric for parquet reading [datafusion] via GitHub
• [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
  • Re: [PR] feat: allow custom caching via logical node [datafusion] via GitHub
• [PR] minor: Use allow->expect to explicitly suppress Clippy lint checks [datafusion] via GitHub
  • Re: [PR] minor: Use allow->expect to explicitly suppress Clippy lint checks [datafusion] via GitHub
  • Re: [PR] minor: Use allow->expect to explicitly suppress Clippy lint checks [datafusion] via GitHub
• [I] More ergnomic way to specify (named) paramters in signature [datafusion] via GitHub
• Re: [I] Enforce lint rule `clippy::needless_pass_by_value` to `datafusion/core` [datafusion] via GitHub
• Re: [I] `WITHIN GROUP` needs to be more strict [datafusion] via GitHub
• [I] Question: should set FileScanConfig's batch_size to min(batch_size, limit) [datafusion] via GitHub
  • Re: [I] Question: should set FileScanConfig's batch_size to min(batch_size, limit) [datafusion] via GitHub
  • Re: [I] Discussion: should set FileScanConfig's batch_size to min(batch_size, limit) [datafusion] via GitHub
  • Re: [I] Discussion: should set FileScanConfig's batch_size to min(batch_size, limit) [datafusion] via GitHub
• [I] Schema error: No field named t.b. Valid fields are t.a. [datafusion] via GitHub
• [PR] feat: Add getSupportLevel to CometAggregateExpressionSerde trait [datafusion-comet] via GitHub
  • Re: [PR] feat: Add getSupportLevel to CometAggregateExpressionSerde trait [datafusion-comet] via GitHub
  • Re: [PR] feat: Add getSupportLevel to CometAggregateExpressionSerde trait [datafusion-comet] via GitHub
  • Re: [PR] feat: Add getSupportLevel to CometAggregateExpressionSerde trait [datafusion-comet] via GitHub
• Re: [PR] fix: Add strict floating point mode and fallback to Spark for min/max/sort on floating point inputs when enabled [datafusion-comet] via GitHub
  • Re: [PR] fix: Add strict floating point mode and fallback to Spark for min/max/sort on floating point inputs when enabled [datafusion-comet] via GitHub
  • Re: [PR] fix: Add strict floating point mode and fallback to Spark for min/max/sort on floating point inputs when enabled [datafusion-comet] via GitHub
  • Re: [PR] fix: Add strict floating point mode and fallback to Spark for min/max/sort on floating point inputs when enabled [datafusion-comet] via GitHub
  • Re: [PR] fix: Add strict floating point mode and fallback to Spark for min/max/sort on floating point inputs when enabled [datafusion-comet] via GitHub
• [PR] chore: Enforce lint rule `clippy::needless_pass_by_value` to datafusi… [datafusion] via GitHub
  • Re: [PR] chore: Enforce lint rule `clippy::needless_pass_by_value` to datafusion-datasource [datafusion] via GitHub
  • Re: [PR] chore: Enforce lint rule `clippy::needless_pass_by_value` to datafusion-datasource [datafusion] via GitHub
  • Re: [PR] chore: Enforce lint rule `clippy::needless_pass_by_value` to datafusion-datasource [datafusion] via GitHub
  • Re: [PR] chore: Enforce lint rule `clippy::needless_pass_by_value` to datafusion-datasource [datafusion] via GitHub
• [PR] [WIP] fix: Coalesced Partition [datafusion-comet] via GitHub
  • Re: [PR] [WIP] fix: Coalesced Partition [datafusion-comet] via GitHub
• [PR] Remove datafusion core crate from `datafusion-ffi` [datafusion] via GitHub
  • Re: [PR] Remove datafusion core crate from `datafusion-ffi` [datafusion] via GitHub
• [PR] Feat/ffi add session [datafusion] via GitHub
  • Re: [PR] Implement FFI_Session [datafusion] via GitHub
• [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
  • Re: [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
  • Re: [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
  • Re: [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
  • Re: [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
  • Re: [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
  • Re: [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
  • Re: [PR] chore: Remove many references to `COMET_EXPR_ALLOW_INCOMPATIBLE` [datafusion-comet] via GitHub
• [PR] [WIP] fix: do not ignore test SPARK-48037 [datafusion-comet] via GitHub
  • Re: [PR] [WIP] fix: do not ignore test SPARK-48037 [datafusion-comet] via GitHub
• [I] Remove COMET_EXPR_ALLOW_INCOMPATIBLE config [datafusion-comet] via GitHub
  • Re: [I] Remove COMET_EXPR_ALLOW_INCOMPATIBLE config [datafusion-comet] via GitHub
• [PR] Implement FFI_TaskContext and FFI_TaskContextProvider [datafusion] via GitHub
  • Re: [PR] Implement FFI_TaskContext and FFI_TaskContextProvider [datafusion] via GitHub
• [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] Support for StringSplit [datafusion-comet] via GitHub
  • Re: [PR] feat: Support for StringSplit [datafusion-comet] via GitHub
• [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
  • Re: [PR] Consolidate `EliminateNestedUnion` and `EliminateOneUnion` optimizer rules' [datafusion] via GitHub
• Re: [I] [CometFuzz] Add script to build and run fuzz testing [datafusion-comet] via GitHub
• Re: [PR] feat: support cot [datafusion-comet] via GitHub
• Re: [I] Consider adding a JoinGraph structure for representing joins [datafusion] via GitHub
  • Re: [I] Consider adding a JoinGraph structure for representing joins [datafusion] via GitHub
  • Re: [I] Consider adding a JoinGraph structure for representing joins [datafusion] via GitHub
  • Re: [I] Consider adding a JoinGraph structure for representing joins [datafusion] via GitHub
  • Re: [I] Consider adding a JoinGraph structure for representing joins [datafusion] via GitHub
  • Re: [I] Consider adding a JoinGraph structure for representing joins [datafusion] via GitHub
• [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
  • Re: [PR] feat: Handle edge case with `corr` with single row and `NaN` [datafusion] via GitHub
• [I] Potential Improved multiple column aggregation performance by using bitmasks rather than `Vec<bool>` [datafusion] via GitHub
  • Re: [I] Potential Improved multiple column aggregation performance by using bitmasks rather than `Vec<bool>` [datafusion] via GitHub
  • Re: [I] Potential Improved multiple column aggregation performance by using bitmasks rather than `Vec<bool>` [datafusion] via GitHub
  • Re: [I] Potential Improved multiple column aggregation performance by using bitmasks rather than `Vec<bool>` [datafusion] via GitHub
  • Re: [I] Potential Improved multiple column aggregation performance by using bitmasks rather than `Vec<bool>` [datafusion] via GitHub
  • Re: [I] Potential Improved multiple column aggregation performance by using bitmasks rather than `Vec<bool>` [datafusion] via GitHub
  • Re: [I] Potential Improved multiple column aggregation performance by using bitmasks rather than `Vec<bool>` [datafusion] via GitHub
• [PR] chore: Refactor CometExecRule handling of sink operators [WIP] [datafusion-comet] via GitHub
  • Re: [PR] chore: Refactor CometExecRule handling of sink operators [WIP] [datafusion-comet] via GitHub
  • Re: [PR] chore: Refactor CometExecRule handling of sink operators [datafusion-comet] via GitHub
  • Re: [PR] chore: Refactor CometExecRule handling of sink operators [datafusion-comet] via GitHub
  • Re: [PR] chore: Refactor CometExecRule handling of sink operators [datafusion-comet] via GitHub
• Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
  • Re: [PR] Refactor InListExpr to support structs by re-using existing hashing infrastructure [datafusion] via GitHub
• [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
  • Re: [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
  • Re: [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
  • Re: [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
  • Re: [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
  • Re: [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
  • Re: [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
  • Re: [I] Inconsistent `datafusion.sql_parser.enable_ident_normalization=false` behaviour [datafusion] via GitHub
• Re: [I] Provide a more ergonomic method to extract python data [datafusion-python] via GitHub
• Re: [PR] Add collect_column to dataframe [datafusion-python] via GitHub
• Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub
  • Re: [PR] perf: optimize CASE WHEN lookup table (2.5-22.5 times faster) [datafusion] via GitHub

• Earlier messages
• Later messages