github  

Messages by Thread

• • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Allow dialects that use `->` as an operator to support `LAMBDA` syntax [datafusion-sqlparser-rs] via GitHub
• [PR] refactor: NLJ Stream Refactor (Part 1 - Semi/Anti/Mark) DRAFT [datafusion] via GitHub
  • Re: [PR] refactor: NLJ Stream Refactor (Part 1 - Semi/Anti/Mark) DRAFT [datafusion] via GitHub
  • Re: [PR] refactor: NLJ Stream Refactor (Part 1 - Semi/Anti/Mark) DRAFT [datafusion] via GitHub
  • Re: [PR] refactor: NLJ Stream Refactor (Part 1 - Semi/Anti/Mark) [datafusion] via GitHub
  • Re: [PR] refactor: NLJ Stream Refactor (Part 1 - Semi/Anti/Mark) [datafusion] via GitHub
  • Re: [PR] refactor: NLJ Stream Refactor (Part 1 - Semi/Anti/Mark) [datafusion] via GitHub
  • Re: [PR] refactor: NLJ Stream Refactor (Part 1 - Semi/Anti/Mark) [datafusion] via GitHub
• [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
  • Re: [PR] fix: preserve explicit Struct casts and evolved field semantics [datafusion] via GitHub
• [I] Struct-cast narrowing can suppress cast errors and change field semantics [datafusion] via GitHub
  • Re: [I] Struct-cast narrowing can suppress cast errors and change field semantics [datafusion] via GitHub
• [PR] fix(docker): base runtime images on ubuntu:26.04 [datafusion-ballista] via GitHub
  • Re: [PR] fix(docker): base runtime images on ubuntu:26.04 [datafusion-ballista] via GitHub
  • Re: [PR] fix(docker): base runtime images on ubuntu:26.04 [datafusion-ballista] via GitHub
• Re: [PR] feat: Sort-aware Iceberg reads in Comet via a per-partition streaming merge [datafusion-comet] via GitHub
  • Re: [PR] feat: Sort-aware Iceberg reads in Comet via a per-partition streaming merge [datafusion-comet] via GitHub
  • Re: [PR] feat: Sort-aware Iceberg reads in Comet via a per-partition streaming merge [datafusion-comet] via GitHub
  • Re: [PR] feat: Sort-aware Iceberg reads in Comet via a per-partition streaming merge [datafusion-comet] via GitHub
  • Re: [PR] feat: Sort-aware Iceberg reads in Comet via a per-partition streaming merge [datafusion-comet] via GitHub
• [I] Incorrect results: leaf expression pushdown duplicates volatile expressions (random() evaluated twice) [datafusion] via GitHub
  • Re: [I] Incorrect results: leaf expression pushdown duplicates volatile expressions (random() evaluated twice) [datafusion] via GitHub
  • Re: [I] Incorrect results: leaf expression pushdown duplicates volatile expressions (random() evaluated twice) [datafusion] via GitHub
• Re: [I] decimal support for agg function [datafusion] via GitHub
• Re: [I] Remove deprecated `ScalarUDF` / `ScalarUDFImpl` methods that are past the API health policy [datafusion] via GitHub
• [PR] fix: spill the NestedLoopJoin build side from the pass that consumed it [datafusion] via GitHub
  • Re: [PR] fix: spill the NestedLoopJoin build side from the pass that consumed it [datafusion] via GitHub
  • Re: [PR] fix: spill the NestedLoopJoin build side from the pass that consumed it [datafusion] via GitHub
• Re: [PR] [DRAFT] update PushedDown to have 3 states [datafusion] via GitHub
• Re: [I] Store example data directly inside the datafusion-examples [datafusion] via GitHub
• [I] NestedLoopJoin memory-limited fallback re-executes the build side, losing rows for non-replayable inputs [datafusion] via GitHub
  • Re: [I] NestedLoopJoin memory-limited fallback re-executes the build side, losing rows for non-replayable inputs [datafusion] via GitHub
• [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
  • Re: [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
  • Re: [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
  • Re: [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
  • Re: [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
  • Re: [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
  • Re: [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
  • Re: [PR] fix: refuse memory-limited NestedLoopJoin fallback for left-emission joins with a multi-partition probe side [datafusion] via GitHub
• [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
  • Re: [PR] fix: preserve projection metadata during optimization [datafusion] via GitHub
• [PR] fix: enforce fair memory share per reservation [datafusion-comet] via GitHub
  • Re: [PR] fix: enforce fair memory share per reservation [datafusion-comet] via GitHub
  • Re: [PR] fix: enforce fair memory share per reservation [datafusion-comet] via GitHub
  • Re: [PR] fix: enforce fair memory share per reservation [datafusion-comet] via GitHub
• [PR] Revert "remove redundant logic from ballista logical codec (#2348)" [datafusion-ballista] via GitHub
  • Re: [PR] Revert "remove redundant logic from ballista logical codec (#2348)" [datafusion-ballista] via GitHub
• [PR] feat: scheduler REST & GRPC return version headers [datafusion-ballista] via GitHub
  • Re: [PR] feat: scheduler REST & GRPC return version headers [datafusion-ballista] via GitHub
  • Re: [PR] feat: scheduler REST & GRPC return version headers [datafusion-ballista] via GitHub
  • Re: [PR] feat: scheduler REST & GRPC returns ballista version headers [datafusion-ballista] via GitHub
  • Re: [PR] feat: scheduler REST & GRPC returns ballista version headers [datafusion-ballista] via GitHub
• [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
  • Re: [PR] DO NOT REVIEW - BENCHMARK WINDOW [datafusion] via GitHub
• [PR] Fix sum by name in custom metrics [datafusion] via GitHub
  • Re: [PR] Fix sum by name in custom metrics [datafusion] via GitHub
  • Re: [PR] Fix sum by name in custom metrics [datafusion] via GitHub
  • Re: [PR] Fix sum by name in custom metrics [datafusion] via GitHub
  • Re: [PR] Fix sum by name in custom metrics [datafusion] via GitHub
  • Re: [PR] Fix sum by name in custom metrics [datafusion] via GitHub
• [PR] docs: Remove stale "temporary fix" note from `get_record_batch_memory_size` [datafusion] via GitHub
  • Re: [PR] docs: Remove stale "temporary fix" note from `get_record_batch_memory_size` [datafusion] via GitHub
  • Re: [PR] docs: Remove stale "temporary fix" note from `get_record_batch_memory_size` [datafusion] via GitHub
• [I] Vendored datafusion.proto sync check silently passes without checking datafusion.proto [datafusion-ballista] via GitHub
  • Re: [I] Vendored datafusion.proto sync check silently passes without checking datafusion.proto [datafusion-ballista] via GitHub
  • Re: [I] Vendored datafusion.proto sync check silently passes without checking datafusion.proto [datafusion-ballista] via GitHub
• Re: [I] Support of new Syntax [datafusion-sqlparser-rs] via GitHub
• Re: [PR] chore(core): remove unused diagram module [datafusion-ballista] via GitHub
• [PR] chore(deps): use the released DataFusion 55.0.0 crates from crates.io [datafusion-ballista] via GitHub
  • Re: [PR] chore(deps): use the released DataFusion 55.0.0 crates from crates.io [datafusion-ballista] via GitHub
  • Re: [PR] chore(deps): use the released DataFusion 55.0.0 crates from crates.io [datafusion-ballista] via GitHub
• [I] CopyTo plans from a 54 client silently decode as the wrong file format on a 55 scheduler [datafusion-ballista] via GitHub
  • Re: [I] CopyTo plans from a 54 client silently decode as the wrong file format on a 55 scheduler [datafusion-ballista] via GitHub
  • Re: [I] CopyTo plans from a 54 client silently decode as the wrong file format on a 55 scheduler [datafusion-ballista] via GitHub
  • Re: [I] CopyTo plans from a 54 client silently decode as the wrong file format on a 55 scheduler [datafusion-ballista] via GitHub
• Re: [PR] feat: preserve bitmap-backed RowSelection through ParquetAccessPlan [datafusion] via GitHub
• [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
  • Re: [I] Validate BALLISTA_PROTOCOL_VERSION for clients, not just executors [datafusion-ballista] via GitHub
• [PR] ci: run Python client tests against a cluster built from the branch [datafusion-ballista] via GitHub
• [PR] fix: make tracing memory pool registration lifecycle-safe [datafusion-comet] via GitHub
  • Re: [PR] fix: RAII for memory pool registration [datafusion-comet] via GitHub
  • Re: [PR] fix: RAII for memory pool registration [datafusion-comet] via GitHub

• Earlier messages
• Later messages