github  

Messages by Thread

• • Re: [PR] [codex] Fix time interval arithmetic wrapping [datafusion] via GitHub
  • Re: [PR] [codex] Fix time interval arithmetic wrapping [datafusion] via GitHub
• [PR] fixing array length for empty array [datafusion] via GitHub
  • Re: [PR] fixing array length for empty array [datafusion] via GitHub
  • Re: [PR] fixing array length for empty array [datafusion] via GitHub
  • Re: [PR] fixing array length for empty array [datafusion] via GitHub
  • Re: [PR] fixing array length for empty array [datafusion] via GitHub
  • Re: [PR] fixing array length for empty array [datafusion] via GitHub
• Re: [PR] feat: add array_normalize scalar function [datafusion] via GitHub
  • Re: [PR] feat: add array_normalize scalar function [datafusion] via GitHub
  • Re: [PR] feat: add array_normalize scalar function [datafusion] via GitHub
• Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
  • Re: [PR] Resolve MIN/MAX from Parquet metadata for Single-mode aggregates and CAST projections [datafusion] via GitHub
• [PR] build(deps): bump arrow-select from 58.1.0 to 58.3.0 [datafusion-python] via GitHub
  • Re: [PR] build(deps): bump arrow-select from 58.1.0 to 58.3.0 [datafusion-python] via GitHub
  • Re: [PR] build(deps): bump arrow-select from 58.1.0 to 58.3.0 [datafusion-python] via GitHub
• [PR] build(deps): bump datafusion-substrait from 53.0.0 to 53.1.0 [datafusion-python] via GitHub
  • Re: [PR] build(deps): bump datafusion-substrait from 53.0.0 to 53.1.0 [datafusion-python] via GitHub
  • Re: [PR] build(deps): bump datafusion-substrait from 53.0.0 to 53.1.0 [datafusion-python] via GitHub
• [PR] fixing factorial negative values [datafusion] via GitHub
  • Re: [PR] fixing factorial negative values [datafusion] via GitHub
  • Re: [PR] fixing factorial negative values [datafusion] via GitHub
  • Re: [PR] fixing factorial negative values [datafusion] via GitHub
  • Re: [PR] fixing factorial negative values [datafusion] via GitHub
• [PR] fixing negative power to zero [datafusion] via GitHub
  • Re: [PR] fixing negative power to zero [datafusion] via GitHub
  • Re: [PR] fixing negative power to zero [datafusion] via GitHub
  • Re: [PR] fixing negative power to zero [datafusion] via GitHub
  • Re: [PR] fixing negative power to zero [datafusion] via GitHub
  • Re: [PR] fixing negative power to zero [datafusion] via GitHub
• Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
  • Re: [PR] fix: Set Substrait output types for expressions [datafusion] via GitHub
• Re: [I] Ensure Substrait producer for `BinaryExpr` includes `output_type` [datafusion] via GitHub
• [PR] Reject negative ln inputs [datafusion] via GitHub
  • Re: [PR] Reject negative ln inputs [datafusion] via GitHub
  • Re: [PR] Reject negative ln inputs [datafusion] via GitHub
• [PR] fix: make replace no-op for empty search [datafusion] via GitHub
  • Re: [PR] fix: make replace no-op for empty search [datafusion] via GitHub
  • Re: [PR] fix: make replace no-op for empty search [datafusion] via GitHub
  • Re: [PR] fix: make replace no-op for empty search [datafusion] via GitHub
• [PR] array_repeat scalar path overflows total repeated-value count [datafusion] via GitHub
  • Re: [PR] fix array_repeat scalar path overflows total repeated-value count [datafusion] via GitHub
  • Re: [PR] fix array_repeat scalar path overflows total repeated-value count [datafusion] via GitHub
• [PR] fix: translate SIMILAR TO pattern to PostgreSQL-compatible regex [datafusion] via GitHub
  • Re: [PR] fix: translate SIMILAR TO pattern to PostgreSQL-compatible regex [datafusion] via GitHub
• [I] PostgreSQL compatibility: `power(0.0::float8, -1.0::float8)` should error, not return infinity [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `power(0.0::float8, -1.0::float8)` should error, not return infinity [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `power(0.0::float8, -1.0::float8)` should error, not return infinity [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `power(0.0::float8, -1.0::float8)` should error, not return infinity [datafusion] via GitHub
• [I] PostgreSQL compatibility: `factorial` of a negative value should error [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `factorial` of a negative value should error [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `factorial` of a negative value should error [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `factorial` of a negative value should error [datafusion] via GitHub
• [I] PostgreSQL compatibility: `regexp_like` should honor PostgreSQL multiline flag `m` [datafusion] via GitHub
• [I] PostgreSQL compatibility: `ln(-1.0::float8)` should error, not return NaN [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `ln(-1.0::float8)` should error, not return NaN [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `ln(-1.0::float8)` should error, not return NaN [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `ln(-1.0::float8)` should error, not return NaN [datafusion] via GitHub
• [I] PostgreSQL compatibility: `round(float8)` should match PostgreSQL half-tie behavior [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `round(float8)` should match PostgreSQL half-tie behavior [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `round(float8)` should match PostgreSQL half-tie behavior [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `round(float8)` should match PostgreSQL half-tie behavior [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `round(float8)` should match PostgreSQL half-tie behavior [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `round(float8)` should match PostgreSQL half-tie behavior [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `round(float8)` should match PostgreSQL half-tie behavior [datafusion] via GitHub
• [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(second ...)` should preserve fractional seconds [datafusion] via GitHub
• [I] PostgreSQL compatibility: `regexp_count` should count empty-pattern matches [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_count` should count empty-pattern matches [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_count` should count empty-pattern matches [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_count` should count empty-pattern matches [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_count` should count empty-pattern matches [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_count` should count empty-pattern matches [datafusion] via GitHub
• [I] PostgreSQL compatibility: `array_length` of an empty array dimension should be NULL [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `array_length` of an empty array dimension should be NULL [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `array_length` of an empty array dimension should be NULL [datafusion] via GitHub
• [I] PostgreSQL compatibility: `time + interval` should wrap within the 24-hour time domain [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `time + interval` should wrap within the 24-hour time domain [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `time + interval` should wrap within the 24-hour time domain [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `time + interval` should wrap within the 24-hour time domain [datafusion] via GitHub
• [I] PostgreSQL compatibility: `SIMILAR TO` should treat `%` as a wildcard [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `SIMILAR TO` should treat `%` as a wildcard [datafusion] via GitHub
• [PR] fix date_trunc overflows converting extreme non-ns timestamps to nanoseconds [datafusion] via GitHub
  • Re: [PR] fix date_trunc overflows converting extreme non-ns timestamps to nanoseconds [datafusion] via GitHub
• [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: negative array subscripts should not index from the end [datafusion] via GitHub
• [I] PostgreSQL compatibility: `log(0.0::float8)` should error, not return `-inf` [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `log(0.0::float8)` should error, not return `-inf` [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `log(0.0::float8)` should error, not return `-inf` [datafusion] via GitHub
• [I] PostgreSQL compatibility: `regexp_instr` with an empty pattern should return 1 [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_instr` with an empty pattern should return 1 [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_instr` with an empty pattern should return 1 [datafusion] via GitHub
• [I] PostgreSQL compatibility: `sqrt(-1.0::float8)` should error, not return NaN [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `sqrt(-1.0::float8)` should error, not return NaN [datafusion] via GitHub
• [I] PostgreSQL compatibility: `regexp_replace` should honor PostgreSQL multiline flag `m` [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_replace` should honor PostgreSQL multiline flag `m` [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `regexp_replace` should honor PostgreSQL multiline flag `m` [datafusion] via GitHub
• [I] PostgreSQL compatibility: `factorial(21)` should not overflow when PostgreSQL returns a numeric answer [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `factorial(21)` should not overflow when PostgreSQL returns a numeric answer [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `factorial(21)` should not overflow when PostgreSQL returns a numeric answer [datafusion] via GitHub
• [I] PostgreSQL compatibility: `replace` with an empty search string should be a no-op [datafusion] via GitHub
• [I] PostgreSQL compatibility: `time - interval` should wrap within the 24-hour time domain [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `time - interval` should wrap within the 24-hour time domain [datafusion] via GitHub
• [I] PostgreSQL compatibility: `^` evaluates as bitwise XOR instead of exponentiation [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `^` evaluates as bitwise XOR instead of exponentiation [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `^` evaluates as bitwise XOR instead of exponentiation [datafusion] via GitHub
• [I] PostgreSQL compatibility: `extract(milliseconds ...)` should preserve fractional milliseconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(milliseconds ...)` should preserve fractional milliseconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(milliseconds ...)` should preserve fractional milliseconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(milliseconds ...)` should preserve fractional milliseconds [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility: `extract(milliseconds ...)` should preserve fractional milliseconds [datafusion] via GitHub
• [PR] fix date_bin overflows subtracting extreme nanosecond timestamp origin [datafusion] via GitHub
  • Re: [PR] fix date_bin overflows subtracting extreme nanosecond timestamp origin [datafusion] via GitHub
• Re: [I] Avoid extra memory access in ArrowByteViewMap [datafusion] via GitHub
• [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
  • Re: [PR] fix generate_series table function overflows [datafusion] via GitHub
• [I] Optimize projections causes recursive CTEs to fail [datafusion] via GitHub
• [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend check_support to include ScalarFunctionExpr in interval analysis [datafusion] via GitHub
  • Re: [PR] feat: extend interval arithmetic to support scalar functions (UDFs) [datafusion] via GitHub
• [I] PostgreSQL compatibility mismatches in simple SQL expressions [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility mismatches in simple SQL expressions [datafusion] via GitHub
  • Re: [I] PostgreSQL compatibility mismatches in simple SQL expressions [datafusion] via GitHub
• Re: [PR] fix: complete native_datafusion Parquet schema-mismatch rejections [datafusion-comet] via GitHub
  • Re: [PR] fix: complete native_datafusion Parquet schema-mismatch rejections [datafusion-comet] via GitHub
  • Re: [PR] fix: complete native_datafusion Parquet schema-mismatch rejections [datafusion-comet] via GitHub
  • Re: [PR] fix: complete native_datafusion Parquet schema-mismatch rejections [datafusion-comet] via GitHub
  • Re: [PR] fix: complete native_datafusion Parquet schema-mismatch rejections [datafusion-comet] via GitHub
  • Re: [PR] fix: complete native_datafusion Parquet schema-mismatch rejections [datafusion-comet] via GitHub
• [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
  • Re: [PR] Make DiskManager max_temp_directory_size dynamically adjustable [datafusion] via GitHub
• [PR] Optimize arrays_zip for perfectly aligned arrays [datafusion] via GitHub
  • Re: [PR] Optimize arrays_zip for perfectly aligned arrays [datafusion] via GitHub
• [PR] feat: support binary and string types for concat UDFs [datafusion] via GitHub
  • Re: [PR] feat: support binary and string types for concat UDFs [datafusion] via GitHub
  • Re: [PR] feat: support binary and string types for concat UDFs [datafusion] via GitHub
  • Re: [PR] feat: support binary and string types for concat UDFs [datafusion] via GitHub
• Re: [PR] feat(aqe): CoalescePartitionsRule — shuffle-partition coalescing on resolved stats [datafusion-ballista] via GitHub
  • Re: [PR] feat(aqe): CoalescePartitionsRule — shuffle-partition coalescing on resolved stats [datafusion-ballista] via GitHub
  • Re: [PR] feat(aqe): CoalescePartitionsRule — shuffle-partition coalescing on resolved stats [datafusion-ballista] via GitHub
  • Re: [PR] feat(aqe): CoalescePartitionsRule — shuffle-partition coalescing on resolved stats [datafusion-ballista] via GitHub
  • Re: [PR] feat(aqe): CoalescePartitionsRule — shuffle-partition coalescing on resolved stats [datafusion-ballista] via GitHub
  • Re: [PR] feat(aqe): CoalescePartitionsRule — shuffle-partition coalescing on resolved stats [datafusion-ballista] via GitHub

• Earlier messages
• Later messages