github  

Messages by Thread

• • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
  • Re: [PR] feat: cost-based join order enumeration [datafusion] via GitHub
• Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
  • Re: [PR] Add nested struct schema evolution support for Map types [datafusion] via GitHub
• [PR] Fix unparse union all nested distinct [datafusion] via GitHub
  • Re: [PR] Fix unparse union all nested distinct [datafusion] via GitHub
  • Re: [PR] Fix unparse union all nested distinct [datafusion] via GitHub
• [PR] perf(scheduler): run one stage when the plan asks for the same stage twice [datafusion-ballista] via GitHub
  • Re: [PR] perf(scheduler): run one stage when the plan asks for the same stage twice [datafusion-ballista] via GitHub
  • Re: [PR] perf(scheduler): run one stage when the plan asks for the same stage twice [datafusion-ballista] via GitHub
• Re: [PR] DRAFT - 21566 [datafusion] via GitHub
• [PR] perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
  • Re: [PR] (benchmaxx) perf: slice instead of take when probe indices are a contiguous run [datafusion] via GitHub
• [PR] perf(scheduler): push filters once, not on every replan [datafusion-ballista] via GitHub
  • Re: [PR] perf(scheduler): push filters once, not on every replan [datafusion-ballista] via GitHub
• Re: [PR] perf: improve ArrowWriter performance for fixed-length vectors [datafusion-comet] via GitHub
  • Re: [PR] perf: improve ArrowWriter performance for fixed-length vectors [datafusion-comet] via GitHub
  • Re: [PR] perf: improve ArrowWriter performance for fixed-length vectors [datafusion-comet] via GitHub
  • Re: [PR] perf: improve ArrowWriter performance for fixed-length vectors [datafusion-comet] via GitHub
  • Re: [PR] perf: improve ArrowWriter performance for fixed-length vectors [datafusion-comet] via GitHub
• [PR] perf: avoid processing discarded rows for negative `nth_value` [datafusion] via GitHub
  • Re: [PR] perf: avoid processing discarded rows for negative `nth_value` [datafusion] via GitHub
  • Re: [PR] perf: avoid processing discarded rows for negative `nth_value` [datafusion] via GitHub
  • Re: [PR] perf: avoid processing discarded rows for negative `nth_value` [datafusion] via GitHub
• Re: [PR] perf: reuse Arrow IPC compression context across shuffle blocks [datafusion-comet] via GitHub
  • Re: [PR] perf: reuse Arrow IPC compression context across shuffle blocks [datafusion-comet] via GitHub
  • Re: [PR] perf: reuse Arrow IPC compression context across shuffle blocks [datafusion-comet] via GitHub
  • Re: [PR] perf: reuse Arrow IPC compression context across shuffle blocks [datafusion-comet] via GitHub
• Re: [PR] refactor: use arrow make_comparator for nested structural equality in arrays_overlap and array_position [2/2] [datafusion-comet] via GitHub
• Re: [PR] feat: remove extra Rows from ReusableRows [datafusion] via GitHub
  • Re: [PR] feat: remove extra Rows from ReusableRows [datafusion] via GitHub
  • Re: [PR] feat: remove extra Rows from ReusableRows [datafusion] via GitHub
• Re: [PR] fix: preserve Spark semantics for dictionary-encoded Parquet inputs and reject dictionary targets [datafusion-comet] via GitHub
  • Re: [PR] fix: preserve Spark semantics for dictionary-encoded Parquet inputs and reject dictionary targets [datafusion-comet] via GitHub
  • Re: [PR] fix: preserve Spark semantics for dictionary-encoded Parquet inputs and reject dictionary targets [datafusion-comet] via GitHub
• Re: [PR] feat: full native make_interval with 2.6x faster than spark and 1.1x faster than codegen dispatch [datafusion-comet] via GitHub
• [PR] chore(deps): bump astral-sh/setup-uv from 9.0.0 to 10.0.1 [datafusion] via GitHub
  • Re: [PR] chore(deps): bump astral-sh/setup-uv from 9.0.0 to 10.0.1 [datafusion] via GitHub
• [PR] chore(deps): bump taiki-e/install-action from 2.85.11 to 2.86.1 [datafusion] via GitHub
  • Re: [PR] chore(deps): bump taiki-e/install-action from 2.85.11 to 2.86.1 [datafusion] via GitHub
• [PR] chore(deps): bump the all-other-cargo-deps group with 2 updates [datafusion] via GitHub
  • Re: [PR] chore(deps): bump the all-other-cargo-deps group across 1 directory with 2 updates [datafusion] via GitHub
  • [PR] chore(deps): bump the all-other-cargo-deps group with 2 updates [datafusion] via GitHub
  • Re: [PR] chore(deps): bump the all-other-cargo-deps group with 2 updates [datafusion] via GitHub
• [PR] chore(deps): bump the codeql-actions group across 1 directory with 2 updates [datafusion] via GitHub
  • Re: [PR] chore(deps): bump the codeql-actions group across 1 directory with 2 updates [datafusion] via GitHub
  • [PR] chore(deps): bump the codeql-actions group across 1 directory with 2 updates [datafusion] via GitHub
  • Re: [PR] chore(deps): bump the codeql-actions group across 1 directory with 2 updates [datafusion] via GitHub
• [PR] chore(deps): bump tomlkit from 0.14.0 to 0.15.1 [datafusion] via GitHub
  • Re: [PR] chore(deps): bump tomlkit from 0.14.0 to 0.15.1 [datafusion] via GitHub
• [I] FuzzDataGenerator silently drops nulls for Boolean/Byte/Short/Integer columns [datafusion-comet] via GitHub
  • Re: [I] FuzzDataGenerator silently drops nulls for Boolean/Byte/Short/Integer columns [datafusion-comet] via GitHub
• Re: [PR] feat(spark): add `to_binary` and `try_to_binary` [datafusion] via GitHub
  • Re: [PR] feat(spark): add `to_binary` and `try_to_binary` [datafusion] via GitHub
  • Re: [PR] feat(spark): add `to_binary` and `try_to_binary` [datafusion] via GitHub
  • Re: [PR] feat(spark): add `to_binary` and `try_to_binary` [datafusion] via GitHub
  • Re: [PR] feat(spark): add `to_binary` and `try_to_binary` [datafusion] via GitHub
  • Re: [PR] feat(spark): add `to_binary` and `try_to_binary` [datafusion] via GitHub
• [PR] test(scheduler): pin the expected static and distributed plans [datafusion-ballista] via GitHub
• Re: [PR] fix(tui): use the shared API wire types instead of local copies [datafusion-ballista] via GitHub
  • Re: [PR] fix(tui): use the shared API wire types instead of local copies [datafusion-ballista] via GitHub
  • Re: [PR] fix(tui): use the shared API wire types instead of local copies [datafusion-ballista] via GitHub
• Re: [PR] fix: Support RANGE window frames over binary ORDER BY keys [datafusion] via GitHub
  • Re: [PR] fix: Support RANGE window frames over binary ORDER BY keys [datafusion] via GitHub
  • Re: [PR] fix: Support RANGE window frames over binary ORDER BY keys [datafusion] via GitHub
  • Re: [PR] fix: Support RANGE window frames over binary ORDER BY keys [datafusion] via GitHub
  • Re: [PR] fix: Support RANGE window frames over binary ORDER BY keys [datafusion] via GitHub
  • Re: [PR] fix: Support RANGE window frames over binary ORDER BY keys [datafusion] via GitHub
• [PR] perf(scheduler): only give a broadcast build side its own stage when the probe is partitioned [datafusion-ballista] via GitHub
  • Re: [PR] perf(scheduler): only give a broadcast build side its own stage when the probe is partitioned [datafusion-ballista] via GitHub
• [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
  • Re: [PR] perf: raise perfect hash join small build threshold to 256K [datafusion] via GitHub
• [I] Correctness issue with unparsing UNION & UNION ALL [datafusion] via GitHub
  • Re: [I] Correctness issue with unparsing UNION & UNION ALL [datafusion] via GitHub
  • Re: [I] Correctness issue with unparsing UNION & UNION ALL [datafusion] via GitHub
• Re: [PR] Snowflake: Add support for ->> (pipe) operator for chaining SQL stmts [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Snowflake: Add support for ->> (pipe) operator for chaining SQL stmts [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Snowflake: Add support for ->> (pipe) operator for chaining SQL stmts [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Snowflake: Add support for ->> (pipe) operator for chaining SQL stmts [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Snowflake: Add support for ->> (pipe) operator for chaining SQL stmts [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Snowflake: Add support for ->> (pipe) operator for chaining SQL stmts [datafusion-sqlparser-rs] via GitHub
• [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
  • Re: [PR] perf: reuse the projected equivalence group when only child orderings change [datafusion] via GitHub
• [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
  • Re: [PR] fix: evaluate grouped aggregate arguments after FILTER [datafusion] via GitHub
• [I] Grouped aggregate FILTER evaluates arguments for rejected rows [datafusion] via GitHub
  • Re: [I] Grouped aggregate FILTER evaluates arguments for rejected rows [datafusion] via GitHub

• Earlier messages
• Later messages