github  

Messages by Thread

• • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
  • Re: [I] TPC-H q18 hangs with 16 executors x 8 cores in EKS [datafusion-ballista] via GitHub
• Re: [I] High HashJoin probe latency under high fanout and key skew (Partitioned mode) [datafusion] via GitHub
  • Re: [I] High HashJoin probe latency under high fanout and key skew (Partitioned mode) [datafusion] via GitHub
• Re: [PR] Prune unread nested parquet leaves when a projected column is cast to a narrower type (nested schema pruning) [datafusion] via GitHub
• Re: [PR] feat: prune nested Parquet leaves when the projected schema narrows a nested column [datafusion] via GitHub
  • Re: [PR] feat: prune nested Parquet leaves when the projected schema narrows a nested column [datafusion] via GitHub
• [PR] Debug why sort ordering get messed up [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))` opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))` opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
  • Re: [PR] Allow expression to report whether they keep the same ordering of the input (`a.cmp(b) == f(a).cmp(f(b))`) opening up for more optimization [datafusion] via GitHub
• [PR] feat(core): report the actual sort shuffle spill trigger in logs [datafusion-ballista] via GitHub
  • Re: [PR] feat(core): report the actual sort shuffle spill trigger in logs [datafusion-ballista] via GitHub
  • Re: [PR] feat(core): report the actual sort shuffle spill trigger in logs [datafusion-ballista] via GitHub
• Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [datafusion] via GitHub
• [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [rebased from #22518] [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [rebased from #22518] [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [rebased from #22518] [datafusion] via GitHub
  • Re: [PR] feat(aggregate): cost-aware partial-aggregation skip (opt-in) [rebased from #22518] [datafusion] via GitHub
• [I] Release DataFusion `54.2.0` (minor/patch) Release [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.2.0` (minor/patch) Release [datafusion] via GitHub
  • Re: [I] Release DataFusion `54.2.0` (minor/patch) Release [datafusion] via GitHub
• [PR] fix: do not treat concat as preserving lexicographical ordering [datafusion] via GitHub
  • Re: [PR] fix: do not treat concat as preserving lexicographical ordering [datafusion] via GitHub
  • Re: [PR] fix: do not treat concat as preserving lexicographical ordering [datafusion] via GitHub
  • Re: [PR] fix: do not treat concat as preserving lexicographical ordering [datafusion] via GitHub
  • Re: [PR] fix: do not treat concat as preserving lexicographical ordering [datafusion] via GitHub
  • Re: [PR] fix: do not treat concat as preserving lexicographical ordering [datafusion] via GitHub
• [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
  • Re: [PR] benchmarks: count simulated object store GET requests per query [datafusion] via GitHub
• Re: [I] [EPIC] Split Aggregation Logic into Dedicated Streams [datafusion] via GitHub
  • Re: [I] [EPIC] Split Aggregation Logic into Dedicated Streams [datafusion] via GitHub
  • Re: [I] [EPIC] Split Aggregation Logic into Dedicated Streams [datafusion] via GitHub
• Re: [PR] refactor: Use cast preimages for cast predicate rewrites [datafusion] via GitHub
• Re: [PR] fix: preserve aggregate filter pushdown order [datafusion] via GitHub
• [PR] feat: remove extra Rows from ReusableRows [datafusion] via GitHub
• Re: [PR] feat: Add Native Support for In-Memory Cache [datafusion-comet] via GitHub
  • Re: [PR] feat: Add Native Support for In-Memory Cache [datafusion-comet] via GitHub
  • Re: [PR] feat: Add Native Support for In-Memory Cache [datafusion-comet] via GitHub
  • Re: [PR] feat: Add Native Support for In-Memory Cache [datafusion-comet] via GitHub
  • Re: [PR] feat: Add Native Support for In-Memory Cache [datafusion-comet] via GitHub
• [I] Remove the buffering of an extra Rows in ReusableRows [datafusion] via GitHub
  • Re: [I] Remove the buffering of an extra Rows in ReusableRows [datafusion] via GitHub
• Re: [I] Expose Range Partitioning Across FFI Boundaries [datafusion] via GitHub
• [PR] fix: preserve global limit for multi-partition fetch [datafusion] via GitHub
• [I] LimitPushdown can mistake per-partition fetch for a global limit [datafusion] via GitHub
• Re: [I] Shrink residual Vec in split_vec_min_alloc to fix capacity-based memory accounting on long split_off chains [datafusion] via GitHub
  • Re: [I] Shrink residual Vec in split_vec_min_alloc to fix capacity-based memory accounting on long split_off chains [datafusion] via GitHub
  • Re: [I] Shrink residual Vec in split_vec_min_alloc to fix capacity-based memory accounting on long split_off chains [datafusion] via GitHub
• [I] ProjectExec does not keep sorting information for passthrough expression [datafusion] via GitHub
  • Re: [I] ProjectExec does not keep sorting information for passthrough expression [datafusion] via GitHub
• [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
  • Re: [PR] feat: allow configuring datafusion-cli history file location [datafusion] via GitHub
• [I] datafusion-cli: allow configuring the location of the interactive shell's history file [datafusion] via GitHub
• [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
  • Re: [PR] Experimental: parquet bounded streaming of large column chunks (companion to arrow-rs#10410) [datafusion] via GitHub
• [PR] refactor(proto): migrate SortExec and SortPreservingMergeExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate SortExec and SortPreservingMergeExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate SortExec and SortPreservingMergeExec serde [datafusion] via GitHub
• [I] `concat` should NOT be reported as preserve lex ordering - wrong output [datafusion] via GitHub
  • Re: [I] `concat` should NOT be reported as preserve lex ordering - wrong output [datafusion] via GitHub
  • Re: [I] `concat` should NOT be reported as preserve lex ordering - wrong output [datafusion] via GitHub
• [PR] refactor(proto): migrate RepartitionExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate RepartitionExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate RepartitionExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate RepartitionExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate RepartitionExec serde [datafusion] via GitHub
• Re: [I] Proto: migrate ParquetSource [datafusion] via GitHub
• Re: [I] Proto: migrate the simple file scans (CsvSource, JsonSource, ArrowSource, AvroSource) [datafusion] via GitHub
• [PR] refactor(proto): migrate GlobalLimitExec and LocalLimitExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate GlobalLimitExec and LocalLimitExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate GlobalLimitExec and LocalLimitExec serde [datafusion] via GitHub
  • Re: [PR] refactor(proto): migrate GlobalLimitExec and LocalLimitExec serde [datafusion] via GitHub
• [PR] docs: add Supermetal to known users [datafusion] via GitHub
  • Re: [PR] docs: add Supermetal to known users [datafusion] via GitHub
  • Re: [PR] docs: add Supermetal to known users [datafusion] via GitHub
  • Re: [PR] docs: add Supermetal to known users [datafusion] via GitHub
  • Re: [PR] docs: add Supermetal to known users [datafusion] via GitHub
• [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
  • Re: [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
  • Re: [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
  • Re: [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
  • Re: [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
  • Re: [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
  • Re: [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
  • Re: [PR] refactor(unparser): centralize aggregate-scope rendering in the SQL unparser [datafusion] via GitHub
• [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
  • Re: [PR] fix: avoid overflow in join cardinality estimation [datafusion] via GitHub
• [I] Join cardinality estimation can overflow row count multiplication [datafusion] via GitHub
  • Re: [I] Join cardinality estimation can overflow row count multiplication [datafusion] via GitHub
• [PR] chore(deps): bump libc from 0.2.187 to 0.2.189 [datafusion-ballista] via GitHub
  • Re: [PR] chore(deps): bump libc from 0.2.187 to 0.2.189 [datafusion-ballista] via GitHub
• [PR] chore(deps): bump datafusion-proto-common from 54.0.0 to 54.1.0 in /python [datafusion-ballista] via GitHub
• [PR] chore(deps): bump datafusion-proto from 54.0.0 to 54.1.0 in /python [datafusion-ballista] via GitHub
• [PR] chore(deps): bump aws-config from 1.9.0 to 1.10.0 [datafusion-ballista] via GitHub
• [PR] chore(deps): bump ctor from 1.0.9 to 1.0.10 [datafusion-ballista] via GitHub
  • Re: [PR] chore(deps): bump ctor from 1.0.9 to 1.0.10 [datafusion-ballista] via GitHub
• [PR] chore(deps): bump datafusion-functions-aggregate-common from 54.0.0 to 54.1.0 in /python [datafusion-ballista] via GitHub
• [PR] chore(deps): bump datafusion from 54.0.0 to 54.1.0 in /python [datafusion-ballista] via GitHub
  • Re: [PR] chore(deps): bump datafusion from 54.0.0 to 54.1.0 in /python [datafusion-ballista] via GitHub
  • Re: [PR] chore(deps): bump datafusion from 54.0.0 to 54.1.0 in /python [datafusion-ballista] via GitHub
• [PR] chore(deps): bump tokio-util from 0.7.18 to 0.7.19 [datafusion-ballista] via GitHub
  • Re: [PR] chore(deps): bump tokio-util from 0.7.18 to 0.7.19 [datafusion-ballista] via GitHub
• [PR] chore(ci): bump astral-sh/setup-uv from 8.3.2 to 9.0.0 [datafusion-ballista] via GitHub
• [PR] chore(ci): bump the github-codeql group with 2 updates [datafusion-ballista] via GitHub
• [PR] feat: add GroupColumn support for Interval in multi-column GROUP BY [datafusion] via GitHub
  • Re: [PR] feat: add GroupColumn support for Interval in multi-column GROUP BY [datafusion] via GitHub
• [PR] feat: add GroupColumn support for Float16 in multi-column GROUP BY [datafusion] via GitHub
• [PR] fix: keep EmptyExec partition count intact across stage serialization (backport of #2062) [datafusion-ballista] via GitHub
  • Re: [PR] fix: [branch-54] keep EmptyExec partition count intact across stage serialization (backport of #2062) [datafusion-ballista] via GitHub
• [PR] feat: migrate EmptyExec and PlaceholderRowExec to ExecutionPlan proto hooks [datafusion] via GitHub
  • Re: [PR] feat: migrate EmptyExec and PlaceholderRowExec to ExecutionPlan proto hooks [datafusion] via GitHub
  • Re: [PR] feat: migrate EmptyExec and PlaceholderRowExec to ExecutionPlan proto hooks [datafusion] via GitHub
  • Re: [PR] feat: migrate EmptyExec and PlaceholderRowExec to ExecutionPlan proto hooks [datafusion] via GitHub
  • Re: [PR] feat: migrate EmptyExec and PlaceholderRowExec to ExecutionPlan proto hooks [datafusion] via GitHub
  • Re: [PR] feat: migrate EmptyExec and PlaceholderRowExec to ExecutionPlan proto hooks [datafusion] via GitHub
• [PR] fix: map a task's partition through UnionExec when restricting file scans (backport of #2070) [datafusion-ballista] via GitHub
  • Re: [PR] fix: [branch-54] map a task's partition through UnionExec when restricting file scans (backport of #2070) [datafusion-ballista] via GitHub
• Re: [PR] feat: add approx_top_k aggregate function [datafusion] via GitHub
  • Re: [PR] feat: add approx_top_k aggregate function [datafusion] via GitHub
• Re: [PR] Adaptive filter pushdown for the parquet scan [datafusion] via GitHub
• Re: [PR] Add OptionalFilterPhysicalExpr wrapper + proto support [datafusion] via GitHub
• Re: [PR] Add SelectivityTracker adaptive filter cost model [datafusion] via GitHub
• Re: [PR] fixing array length for empty array [datafusion] via GitHub
• Re: [PR] fix: float <-> decimal coercion should coerce to float [datafusion] via GitHub
• Re: [PR] Js/refactor/dynamic filter proto [datafusion] via GitHub
• [PR] fix: disable the SortMergeJoinExec broadcast conversion by default [datafusion-ballista] via GitHub

• Earlier messages
• Later messages