github  

Messages by Thread

• • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
  • Re: [PR] #17801 Improve nullability reporting of case expressions [datafusion] via GitHub
• [PR] impl `Spanned` for MERGE statements [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] impl `Spanned` for MERGE statements [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] impl `Spanned` for MERGE statements [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] impl `Spanned` for MERGE statements [datafusion-sqlparser-rs] via GitHub
• Re: [D] why datafusion consume 2g of memory?? [datafusion] via GitHub
  • Re: [D] why datafusion consume 2g of memory?? [datafusion] via GitHub
  • Re: [D] why datafusion consume 2g of memory?? [datafusion] via GitHub
• [PR] fix: remove `WorkTableExec` special case in `reset_plan_states` [datafusion] via GitHub
  • Re: [PR] fix: remove `WorkTableExec` special case in `reset_plan_states` [datafusion] via GitHub
• [I] Support for in-memory file format tables [datafusion] via GitHub
  • Re: [I] Support for in-memory file format tables [datafusion] via GitHub
• Re: [D] Is there a join type that can pushdown join filter to one side's scan? [datafusion] via GitHub
• Re: [PR] Support csv truncated rows in datafusion [datafusion] via GitHub
  • Re: [PR] Support csv truncated rows in datafusion [datafusion] via GitHub
• [PR] Najib.boutaib/cherry pick commit 5765a08 [datafusion] via GitHub
  • Re: [PR] Najib.boutaib/cherry pick commit 5765a08 [datafusion] via GitHub
• Re: [D] how to write a UDTF read_pg? [datafusion] via GitHub
  • Re: [D] how to write a UDTF read_pg? [datafusion] via GitHub
• [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
  • Re: [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
  • Re: [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
  • Re: [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
  • Re: [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
  • Re: [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
  • Re: [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
  • Re: [PR] Fix: Align sort_merge_join filter output with join schema to fix right-anti panic [datafusion] via GitHub
• [PR] chore(deps): bump taiki-e/install-action from 2.62.47 to 2.62.53 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump taiki-e/install-action from 2.62.47 to 2.62.53 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump taiki-e/install-action from 2.62.47 to 2.62.53 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump taiki-e/install-action from 2.62.47 to 2.62.53 [datafusion-sandbox] via GitHub
• [PR] chore(deps): bump actions/checkout from 5.0.0 to 5.0.1 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 5.0.0 to 5.0.1 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 5.0.0 to 5.0.1 [datafusion-sandbox] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 5.0.0 to 5.0.1 [datafusion-sandbox] via GitHub
• [PR] Add field to DynamicPhysicalExpr to indicate the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete or updated [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete or updated [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete or updated [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete or updated [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete or updated [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete or updated [datafusion] via GitHub
  • Re: [PR] Add field to DynamicPhysicalExpr to indicate when the filter is complete or updated [datafusion] via GitHub
• [PR] Implement Substrait Support for `GROUPING SET CUBE` [datafusion] via GitHub
  • Re: [PR] Implement Substrait Support for `GROUPING SET CUBE` [datafusion] via GitHub
  • Re: [PR] Implement Substrait Support for `GROUPING SET CUBE` [datafusion] via GitHub
  • Re: [PR] Implement Substrait Support for `GROUPING SET CUBE` [datafusion] via GitHub
  • Re: [PR] Implement Substrait Support for `GROUPING SET CUBE` [datafusion] via GitHub
  • Re: [PR] Implement Substrait Support for `GROUPING SET CUBE` [datafusion] via GitHub
• Re: [I] Dependency conflict with rquest due to async-compression and xz2 linking to lzma [datafusion] via GitHub
• Re: [I] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [I] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [I] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [I] Support "pre-image" for pruning predicate evaluation [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
• [PR] chore(deps): bump taiki-e/install-action from 2.62.51 to 2.62.53 [datafusion] via GitHub
  • Re: [PR] chore(deps): bump taiki-e/install-action from 2.62.51 to 2.62.53 [datafusion] via GitHub
• [PR] chore(deps): bump actions/checkout from 5.0.0 to 5.0.1 [datafusion] via GitHub
  • Re: [PR] chore(deps): bump actions/checkout from 5.0.0 to 5.0.1 [datafusion] via GitHub
• [I] Elapsed compute time not tracked for file scan [datafusion] via GitHub
  • Re: [I] Elapsed compute time not tracked for `csv` file scan [datafusion] via GitHub
• [I] [substrait] [sqllogictest] Operator precedence in SQL parsing [datafusion] via GitHub
  • Re: [I] [substrait] [sqllogictest] Operator precedence in SQL parsing [datafusion] via GitHub
  • Re: [I] [substrait] [sqllogictest] Operator precedence in SQL parsing [datafusion] via GitHub
  • Re: [I] [substrait] [sqllogictest] Operator precedence in SQL parsing [datafusion] via GitHub
  • Re: [I] [substrait] [sqllogictest] Operator precedence in SQL parsing [datafusion] via GitHub
• [I] [datafusion-spark] Support year-month interval and day-time interval in spark sqllogictest [datafusion] via GitHub
  • Re: [I] [datafusion-spark] Support year-month interval and day-time interval in spark sqllogictest [datafusion] via GitHub
  • Re: [I] [datafusion-spark] Support year-month interval and day-time interval in spark sqllogictest [datafusion] via GitHub
• [PR] CI: Fix `main` branch CI test failure [datafusion] via GitHub
  • Re: [PR] CI: Fix `main` branch CI test failure [datafusion] via GitHub
• Re: [PR] chore: Add script to protect RC branches during the release [datafusion] via GitHub
  • Re: [PR] chore: Add script to protect RC branches during the release [datafusion] via GitHub
  • Re: [PR] chore: Add script to protect RC branches during the release [datafusion] via GitHub
• Re: [D] Windows build fails in CI: `blake3_sse41_x86-64_windows_msvc.o(2) : fatal error A1009:line too long` [datafusion] via GitHub
  • Re: [D] Windows build fails in CI: `blake3_sse41_x86-64_windows_msvc.o(2) : fatal error A1009:line too long` [datafusion] via GitHub
• Re: [D] Can we add `udtf` to `FunctionRegistry`? [datafusion] via GitHub
  • Re: [D] Can we add `udtf` to `FunctionRegistry`? [datafusion] via GitHub
• Re: [D] Parse JSON array containing tuples [datafusion] via GitHub
• Re: [D] How do I create a UDF and enable datafusion to parse it in datafusion rust? [datafusion] via GitHub
• Re: [D] How can I construct a table with a field that is List of String? [datafusion] via GitHub
• [I] Add `UnionArray` tests exercising hashing, group-by, distinct, and aggregates [datafusion] via GitHub
• Re: [D] What if create table schema not match CSV file schema? [datafusion] via GitHub
  • Re: [D] What if create table schema not match CSV file schema? [datafusion] via GitHub
• Re: [I] `SubqueryAlias`, `Values`, and/or `EmptyRelation` have incorrect schemas after replacing `Placeholder` values [datafusion] via GitHub
• [PR] chore: Finish refactor with `assert_or_internal_err!()` [datafusion] via GitHub
  • Re: [PR] chore: Finish refactor with `assert_or_internal_err!()` [datafusion] via GitHub
  • Re: [PR] chore: Finish refactor with `assert_or_internal_err!()` [datafusion] via GitHub
  • Re: [PR] chore: Finish refactor with `assert_or_internal_err!()` [datafusion] via GitHub
  • Re: [PR] chore: Finish refactor with `assert_or_internal_err!()` [datafusion] via GitHub
  • Re: [PR] chore: Finish refactor with `assert_or_internal_err!()` [datafusion] via GitHub
• Re: [I] Enable the `ListFilesCache` to be available for partitioned tables [datafusion] via GitHub
  • Re: [I] Enable the `ListFilesCache` to be available for partitioned tables [datafusion] via GitHub
  • Re: [I] Enable the `ListFilesCache` to be available for partitioned tables [datafusion] via GitHub
  • Re: [I] Enable the `ListFilesCache` to be available for partitioned tables [datafusion] via GitHub
  • Re: [I] Enable the `ListFilesCache` to be available for partitioned tables [datafusion] via GitHub
• Re: [I] Enable sorting on floating-point when running Spark SQL tests [datafusion-comet] via GitHub
  • Re: [I] Enable sorting on floating-point when running Spark SQL tests [datafusion-comet] via GitHub
• Re: [I] Push down entire hash table from HashJoinExec into scans [datafusion] via GitHub
  • Re: [I] Push down entire hash table from HashJoinExec into scans [datafusion] via GitHub
  • Re: [I] Push down entire hash table from HashJoinExec into scans [datafusion] via GitHub
• Re: [PR] feat: Support for StringSplit [datafusion-comet] via GitHub
• [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
  • Re: [PR] Support "pre-image" for pruning predicate evaluation [datafusion] via GitHub
• [PR] test: add for join fuzz tests different amount of columns [datafusion] via GitHub
  • Re: [PR] test: add for join fuzz tests different amount of columns [datafusion] via GitHub
  • Re: [PR] test: add for join fuzz tests different amount of columns [datafusion] via GitHub
  • Re: [PR] test: add for join fuzz tests different amount of columns [datafusion] via GitHub
• Re: [I] Comet 0.10.1 Release [datafusion-comet] via GitHub
• [I] Panic when having right anti join with filter in `sort_merge_join` and different number of columns between each side [datafusion] via GitHub
  • Re: [I] Panic when having right anti join with filter in `sort_merge_join` and different number of columns between each side [datafusion] via GitHub
  • Re: [I] Panic when having right anti join with filter in `sort_merge_join` and different number of columns between each side [datafusion] via GitHub
• Re: [I] Investigate whether we should be wrapping inputs to WindowAggExec in CopyExec [datafusion-comet] via GitHub
  • Re: [I] Investigate whether we should be wrapping inputs to WindowAggExec in CopyExec [datafusion-comet] via GitHub
• [PR] Use `pastey` instead of `paste` which is unmaintained [datafusion] via GitHub
  • Re: [PR] Use `pastey` instead of `paste` which is unmaintained [datafusion] via GitHub
  • Re: [PR] Use `pastey` instead of `paste` which is unmaintained [datafusion] via GitHub
  • Re: [PR] Use `pastey` instead of `paste` which is unmaintained [datafusion] via GitHub
  • Re: [PR] Use `pastey` instead of `paste` which is unmaintained [datafusion] via GitHub
• Re: [I] [Spark 4.0] MakeDecimal is not supported [datafusion-comet] via GitHub
  • Re: [I] [Spark 4.0] MakeDecimal is not supported [datafusion-comet] via GitHub
• [I] feat: Plan node `CometTakeOrderedAndProject` has invalid missingInput` [datafusion-comet] via GitHub
  • Re: [I] feat: Plan node `CometTakeOrderedAndProject` has invalid missingInput` [datafusion-comet] via GitHub
  • Re: [I] feat: Plan node `CometTakeOrderedAndProject` has invalid missingInput [datafusion-comet] via GitHub
  • Re: [I] feat: Plan node `CometTakeOrderedAndProject` has invalid missingInput [datafusion-comet] via GitHub
• [I] Track span of DISTINCT [datafusion-sqlparser-rs] via GitHub
• [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
  • Re: [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
  • Re: [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
  • Re: [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
  • Re: [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
  • Re: [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
  • Re: [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
  • Re: [PR] fix: display the failed sqllogictest file and query that failed in case of a panic [datafusion] via GitHub
• [I] panic in DataFusion is propegated but no failed query and file is logged in sqllogictest [datafusion] via GitHub
  • Re: [I] panic in DataFusion is propegated but no failed query and file is logged in sqllogictest [datafusion] via GitHub
• Re: [I] Support resetting config options to defaults [datafusion] via GitHub
• [PR] Use `LimitedBatchCoalescer` in FilterExec [datafusion] via GitHub
  • Re: [PR] Use `LimitedBatchCoalescer` in FilterExec [datafusion] via GitHub
  • Re: [PR] Use `LimitedBatchCoalescer` in FilterExec [datafusion] via GitHub
• [PR] [WIP]chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
  • Re: [PR] [WIP]chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
  • Re: [PR] [WIP]chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
  • Re: [PR] chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
  • Re: [PR] chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
  • Re: [PR] chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
  • Re: [PR] chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
  • Re: [PR] chore: check `missingInput` for Comet plan nodes [datafusion-comet] via GitHub
• [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub
  • Re: [I] Integrate `BatchCoalescer` into `RepartitionExec` and remove from `CoalesceBatches` optimization rule [datafusion] via GitHub

• Earlier messages
• Later messages