github  

Messages by Thread

• • 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
  • 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
  • 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
• [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
  • Re: [PR] chore: Refactor with assert_or_internal_err!() in datafusion/spark. [datafusion] via GitHub
• [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
  • Re: [PR] chore: update Repartition DisplayAs to indicate maintained sort order [datafusion] via GitHub
• Re: [I] Enforce lint rule `clippy::needless_pass_by_value` to `datafusion-datasource-avro` [datafusion] via GitHub
• Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add PostgreSQL Operator DDL Support [datafusion-sqlparser-rs] via GitHub
• Re: [I] WASM UDFs [datafusion] via GitHub
• [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] Reduce FFI wrappers when round tripping code [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
  • Re: [PR] FFI: return underlying trait type when converting from FFI structs [datafusion] via GitHub
• [I] Support user defined functions as expressions in FFI calls [datafusion] via GitHub
  • Re: [I] Support user defined functions as expressions in FFI calls [datafusion] via GitHub
• Re: [PR] Support `not(expr)` for `build_predicate_expression` [datafusion] via GitHub
  • Re: [PR] Support `not(expr)` for `build_predicate_expression` [datafusion] via GitHub
  • Re: [PR] Support `not(expr)` for `build_predicate_expression` [datafusion] via GitHub
  • Re: [PR] Support `not(expr)` for `build_predicate_expression` [datafusion] via GitHub
• Re: [PR] refactor: merge CoalesceAsyncExecInput into CoalesceBatches [datafusion] via GitHub
  • Re: [PR] refactor: merge CoalesceAsyncExecInput into CoalesceBatches [datafusion] via GitHub
  • Re: [PR] refactor: merge CoalesceAsyncExecInput into CoalesceBatches [datafusion] via GitHub
• [PR] chore(deps): bump crate-ci/typos from 1.39.0 to 1.39.1 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump crate-ci/typos from 1.39.0 to 1.39.1 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump crate-ci/typos from 1.39.0 to 1.39.1 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump crate-ci/typos from 1.39.0 to 1.39.1 [datafusion-sandbox] via GitHub
• Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
  • Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
  • Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
  • Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
  • Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
  • Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
  • Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
  • Re: [I] Release DataFusion `51.0.0` (Nov 2025) [datafusion] via GitHub
• [I] Make `GenericDistinctBuffer` generic over both `Hashable` and native types [datafusion] via GitHub
  • Re: [I] Make `GenericDistinctBuffer` generic over both `Hashable` and native types [datafusion] via GitHub
• Re: [PR] Refactor distinct aggregate implementations to use common buffer [datafusion] via GitHub
  • Re: [PR] Refactor distinct aggregate implementations to use common buffer [datafusion] via GitHub
• [I] Refactor `make_udf_function` in datafusion-functions [datafusion] via GitHub
  • Re: [I] Refactor `make_udf_function` in datafusion-functions [datafusion] via GitHub
  • Re: [I] Refactor `make_udf_function` in datafusion-functions [datafusion] via GitHub
• Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
  • Re: [PR] docs: Move TopK example code to extending-operators documentation [datafusion] via GitHub
• Re: [PR] Enforce explicit opt-in for `WITHIN GROUP` syntax in aggregate UDAFs [datafusion] via GitHub
  • Re: [PR] Enforce explicit opt-in for `WITHIN GROUP` syntax in aggregate UDAFs [datafusion] via GitHub
  • Re: [PR] Enforce explicit opt-in for `WITHIN GROUP` syntax in aggregate UDAFs [datafusion] via GitHub
  • Re: [PR] Enforce explicit opt-in for `WITHIN GROUP` syntax in aggregate UDAFs [datafusion] via GitHub
• Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
  • Re: [PR] Remove FilterExec from CoalesceBatches optimization rule, add fetch support [datafusion] via GitHub
• [I] Can't put `map_extract(MAP {'a': 1, 'b': NULL, 'c': 3}, 'a') = 1` as filter [datafusion] via GitHub
  • Re: [I] Can't put `map_extract(MAP {'a': 1}, 'a') = 1` as filter [datafusion] via GitHub
  • Re: [I] Can't put `map_extract(MAP {'a': 1}, 'a') = 1` as filter [datafusion] via GitHub
  • Re: [I] Can't put `map_extract(MAP {'a': 1}, 'a') = 1` as filter [datafusion] via GitHub
  • Re: [I] Can't put `map_extract(MAP {'a': 1}, 'a') = 1` as filter [datafusion] via GitHub
  • Re: [I] Can't put `map_extract(MAP {'a': 1}, 'a') = 1` as filter [datafusion] via GitHub
  • Re: [I] Can't put `map_extract(MAP {'a': 1}, 'a') = 1` as filter [datafusion] via GitHub
  • Re: [I] Can't put `map_extract(MAP {'a': 1}, 'a') = 1` as filter [datafusion] via GitHub
• Re: [PR] [main] Update Changelog (#18592) [datafusion] via GitHub
• Re: [I] Enforce lint rule `clippy::needless_pass_by_value` to `datafusion-catalog` [datafusion] via GitHub
• Re: [PR] chore: Enforce lint rule `clippy::needless_pass_by_value` to `datafusion-catalog` [datafusion] via GitHub
  • Re: [PR] chore: Enforce lint rule `clippy::needless_pass_by_value` to `datafusion-catalog` [datafusion] via GitHub

• Earlier messages
• Later messages