github  

Messages by Thread

• [PR] fix: defer throwing literal casts to Spark at runtime [datafusion-comet] via GitHub
  • Re: [PR] fix: defer throwing literal casts to Spark at runtime [datafusion-comet] via GitHub
  • Re: [PR] fix: defer throwing literal casts to Spark at runtime [datafusion-comet] via GitHub
• [I] Audit Comet logical-link repair across AQE replanning [datafusion-comet] via GitHub
• Re: [PR] fix: validate map constructor row lengths and null short-circuiting [datafusion-comet] via GitHub
• [PR] refactor: factor SortMergeJoinExec::execute into a reusable sort_merge_join_stream [datafusion] via GitHub
  • Re: [PR] refactor: factor SortMergeJoinExec::execute into a reusable sort_merge_join_stream [datafusion] via GitHub
  • Re: [PR] refactor: factor SortMergeJoinExec::execute into a reusable sort_merge_join_stream [datafusion] via GitHub
  • Re: [PR] refactor: factor SortMergeJoinExec::execute into a reusable sort_merge_join_stream [datafusion] via GitHub
• [PR] fix: sort-merge join filter columns follow the filter's own column order [datafusion] via GitHub
  • Re: [PR] fix: sort-merge join filter columns follow the filter's own column order [datafusion] via GitHub
  • Re: [PR] fix: sort-merge join filter columns follow the filter's own column order [datafusion] via GitHub
  • Re: [PR] fix: sort-merge join filter columns follow the filter's own column order [datafusion] via GitHub
  • Re: [PR] fix: sort-merge join filter columns follow the filter's own column order [datafusion] via GitHub
  • Re: [PR] fix: sort-merge join filter columns follow the filter's own column order [datafusion] via GitHub
• Re: [PR] feat: drop provably-true IS NOT NULL conjuncts from FilterExec predicates via input null_count statistics [datafusion] via GitHub
  • Re: [PR] feat: drop provably-true IS NOT NULL conjuncts from FilterExec predicates via input null_count statistics [datafusion] via GitHub
  • Re: [PR] feat: drop provably-true IS NOT NULL conjuncts from FilterExec predicates via input null_count statistics [datafusion] via GitHub
  • Re: [PR] feat: drop provably-true IS NOT NULL conjuncts from FilterExec predicates via input null_count statistics [datafusion] via GitHub
• Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
  • Re: [PR] POC hash aggregate repartition subpartitions [datafusion] via GitHub
• [I] UDF: consider returning an enum for `return_type` [datafusion] via GitHub
  • Re: [I] UDF: consider returning an enum for `return_type` [datafusion] via GitHub
  • Re: [I] UDF: consider returning an enum for `return_type` [datafusion] via GitHub
• Re: [I] Support ARRAY<STRING> in CometSparkToColumnarExec [datafusion-comet] via GitHub
• Re: [PR] feat: support string arrays in Spark-to-Comet conversion [datafusion-comet] via GitHub
• Re: [I] Native Iceberg writes drop Hadoop GCS configuration for HadoopFileIO + gs:// [datafusion-comet] via GitHub
• Re: [PR] fix: fall back to Spark for native Iceberg writes to gs:// through HadoopFileIO [datafusion-comet] via GitHub
• [PR] docs: explain that Comet's memory comes out of the executor container [datafusion-comet] via GitHub
  • Re: [PR] docs: explain that Comet's memory comes out of the executor container [datafusion-comet] via GitHub
• [I] Tuning guide does not explain that Comet's memory comes out of the executor container [datafusion-comet] via GitHub
• [PR] feat: scope-aware object_store cache for the S3 credential SPI [datafusion-comet] via GitHub
  • Re: [PR] feat: scope-aware object_store cache for the S3 credential SPI [datafusion-comet] via GitHub
  • Re: [PR] feat: scope-aware object_store cache for the S3 credential SPI [datafusion-comet] via GitHub
  • Re: [PR] feat: scope-aware object_store cache for the S3 credential SPI [datafusion-comet] via GitHub
• [PR] docs: document the 24-hour review window for non-trivial pull requests [datafusion-comet] via GitHub
  • Re: [PR] docs: document the 24-hour review window for non-trivial pull requests [datafusion-comet] via GitHub
• [PR] docs: show which config value sizes each region in the memory cgroup diagram [datafusion-comet] via GitHub
  • Re: [PR] docs: show which config value sizes each region in the memory cgroup diagram [datafusion-comet] via GitHub
  • Re: [PR] docs: show which config value sizes each region in the memory cgroup diagram [datafusion-comet] via GitHub
  • Re: [PR] docs: show which config value sizes each region in the memory cgroup diagram [datafusion-comet] via GitHub
  • Re: [PR] docs: show which config value sizes each region in the memory cgroup diagram [datafusion-comet] via GitHub
  • Re: [PR] docs: show which config value sizes each region in the memory cgroup diagram [datafusion-comet] via GitHub
• [I] Memory management cgroup diagram does not show which config value sizes each region [datafusion-comet] via GitHub
• [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
  • Re: [PR] playground [datafusion] via GitHub
• Re: [PR] feat: route compatible xxhash64 args through SparkXxhash64 [datafusion-comet] via GitHub
• Re: [PR] fix: only propagate cast statistics through safe conversions [datafusion] via GitHub
  • Re: [PR] fix: only propagate cast statistics through safe conversions [datafusion] via GitHub
  • Re: [PR] fix: only propagate cast statistics through safe conversions [datafusion] via GitHub
  • Re: [PR] fix: only propagate cast statistics through safe conversions [datafusion] via GitHub
• Re: [I] `generate_series` over timestamps accepts only nanosecond precision, with a misleading error [datafusion] via GitHub
• Re: [PR] fix: accept all timestamp precisions in `generate_series`/`range` [datafusion] via GitHub
  • Re: [PR] fix: accept all timestamp precisions in `generate_series`/`range` [datafusion] via GitHub
• [PR] fix: count Parquet decoding in the scan's elapsed_compute [datafusion] via GitHub
  • Re: [PR] fix: count Parquet decoding in the scan's elapsed_compute [datafusion] via GitHub
  • Re: [PR] fix: count Parquet decoding in the scan's elapsed_compute [datafusion] via GitHub
  • Re: [PR] fix: count Parquet decoding in the scan's elapsed_compute [datafusion] via GitHub
  • Re: [PR] fix: count Parquet decoding in the scan's elapsed_compute [datafusion] via GitHub

• Earlier messages
• Later messages