github  

Messages by Thread

• • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
  • Re: [PR] feat: metadata columns [datafusion] via GitHub
• [PR] feat: Upgrade to DataFusion 45 [datafusion-comet] via GitHub
  • Re: [PR] feat: Upgrade to DataFusion 45 [datafusion-comet] via GitHub
  • Re: [PR] feat: Upgrade to DataFusion 45 [datafusion-comet] via GitHub
  • Re: [PR] feat: Upgrade to DataFusion 45 [datafusion-comet] via GitHub
  • Re: [PR] feat: Upgrade to DataFusion 45 [datafusion-comet] via GitHub
  • Re: [PR] feat: Upgrade to DataFusion 45 [datafusion-comet] via GitHub
• [PR] Fix list Type Coercion List with inner type struct which has large/view types [datafusion] via GitHub
  • Re: [PR] Fix regression list Type Coercion List with inner type struct which has large/view types [datafusion] via GitHub
  • Re: [PR] Fix regression list Type Coercion List with inner type struct which has large/view types [datafusion] via GitHub
  • Re: [PR] Fix regression list Type Coercion List with inner type struct which has large/view types [datafusion] via GitHub
  • Re: [PR] Fix regression list Type Coercion List with inner type struct which has large/view types [datafusion] via GitHub
• [PR] Support array_position [datafusion-comet] via GitHub
• Re: [PR] fix: fetch is missed during EnforceDistribution [datafusion] via GitHub
  • Re: [PR] fix: fetch is missed during EnforceDistribution [datafusion] via GitHub
  • Re: [PR] fix: fetch is missed during EnforceDistribution [datafusion] via GitHub
  • Re: [PR] fix: fetch is missed during EnforceDistribution [datafusion] via GitHub
• Re: [PR] chore: improve tests for array expressions [datafusion-comet] via GitHub
• [PR] Alamb/fix field coercion [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
  • Re: [PR] Do not rename struct fields when coercing types in `CASE` [datafusion] via GitHub
• [I] `Case` coercion of Structs loses field names (regression introduced in DataFusion 44) [datafusion] via GitHub
  • Re: [I] `Case` coercion of Structs loses field names [datafusion] via GitHub
  • Re: [I] `Case` coercion of Structs loses field names [datafusion] via GitHub
  • Re: [I] `Case` coercion of Structs loses field names [datafusion] via GitHub
  • Re: [I] `Case` coercion of Structs loses field names [datafusion] via GitHub
  • Re: [I] `Case` coercion of Structs loses field names [datafusion] via GitHub
• [PR] DFParser should skip unsupported COPY INTO [datafusion] via GitHub
  • Re: [PR] DFParser should skip unsupported COPY INTO [datafusion] via GitHub
  • Re: [PR] DFParser should skip unsupported COPY INTO [datafusion] via GitHub
• [PR] Support `array_union` scalar expr [datafusion-comet] via GitHub
  • Re: [PR] Support `array_union` scalar expr [datafusion-comet] via GitHub
• Re: [I] Incorrect result for IS NOT NULL predicate over UNION ALL query [datafusion] via GitHub
• [PR] Add tests for coercing structs [datafusion] via GitHub
  • Re: [PR] Add tests for coercing sub fields of `List`s / `LargeList`s of structs [datafusion] via GitHub
  • Re: [PR] Add tests for coercing sub fields of `List`s / `LargeList`s of structs [datafusion] via GitHub
  • Re: [PR] Add tests for coercing sub fields of `List`s / `LargeList`s of structs [datafusion] via GitHub
• Re: [I] Add Span to Tokens, AST nodes [datafusion-sqlparser-rs] via GitHub
  • Re: [I] Add Span to Tokens, AST nodes [datafusion-sqlparser-rs] via GitHub
  • Re: [I] Add Span to Tokens, AST nodes [datafusion-sqlparser-rs] via GitHub
• Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
  • Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
  • Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
  • Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
  • Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
  • Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
  • Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
  • Re: [PR] feat: Speed up `struct` and `named_struct` using `invoke_with_args` [datafusion] via GitHub
• Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
  • Re: [I] Release DataFusion `45.0.0` [datafusion] via GitHub
• Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
  • Re: [PR] Remove use of deprecated dict_id in datafusion-proto (#14173) [datafusion] via GitHub
• Re: [PR] feat: implement `invoke_with_args` for `struct` and `named_struct` [datafusion] via GitHub
• [I] Format for Value renders incorrect escaping of quote characters in BigQuery [datafusion-sqlparser-rs] via GitHub
• Re: [PR] Provide documentation of expose APIs to enable handling of type coercion at UNION plan construction. [datafusion] via GitHub
  • Re: [PR] Provide documentation of expose APIs to enable handling of type coercion at UNION plan construction. [datafusion] via GitHub
• [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
  • Re: [I] Create UNION plan node with correct schema [datafusion] via GitHub
• Re: [I] Enable TableScan to return multiple arbitrary table references [datafusion] via GitHub
• Re: [I] bug: array_position not working as expected [datafusion] via GitHub
  • Re: [I] bug: array_position not working as expected [datafusion] via GitHub
  • Re: [I] bug: array_position not working as expected [datafusion] via GitHub
  • Re: [I] bug: array_position not working as expected [datafusion] via GitHub
• Re: [I] `make_array` -> `unnest` w/ dict-encoded strings fails [datafusion] via GitHub
  • Re: [I] `make_array` -> `unnest` w/ dict-encoded strings fails [datafusion] via GitHub
  • Re: [I] `make_array` -> `unnest` w/ dict-encoded strings fails [datafusion] via GitHub
  • Re: [I] `make_array` -> `unnest` w/ dict-encoded strings fails [datafusion] via GitHub
• Re: [I] column types must match schema types occurs after `unnest_columns` on another column [datafusion] via GitHub
  • Re: [I] column types must match schema types occurs after `unnest_columns` on another column [datafusion] via GitHub
  • Re: [I] column types must match schema types occurs after `unnest_columns` on another column [datafusion] via GitHub
• Re: [I] Simple Functions [datafusion] via GitHub
  • Re: [I] Simple Functions [datafusion] via GitHub
  • Re: [I] Simple Functions [datafusion] via GitHub
  • Re: [I] Simple Functions [datafusion] via GitHub
  • Re: [I] Simple Functions [datafusion] via GitHub
  • Re: [I] Simple Functions [datafusion] via GitHub
  • Re: [I] Simple Functions [datafusion] via GitHub
• Re: [I] SQL/PGQ or even GQL support [datafusion] via GitHub
  • Re: [I] SQL/PGQ or even GQL support [datafusion] via GitHub
  • Re: [I] SQL/PGQ or even GQL support [datafusion] via GitHub
• Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
  • Re: [PR] Example for using a separate threadpool for CPU bound work (try 2) [datafusion] via GitHub
• Re: [PR] Fix UNION field nullability tracking [datafusion] via GitHub
  • Re: [PR] Fix UNION field nullability tracking [datafusion] via GitHub
  • Re: [PR] Fix UNION field nullability tracking [datafusion] via GitHub
  • Re: [PR] Fix UNION field nullability tracking [datafusion] via GitHub
  • Re: [PR] Fix UNION field nullability tracking [datafusion] via GitHub
  • Re: [PR] Fix UNION field nullability tracking [datafusion] via GitHub
  • Re: [PR] Fix UNION field nullability tracking [datafusion] via GitHub
• Re: [PR] Support within group syntax for existing aggregate functions [datafusion] via GitHub
• Re: [PR] Feat: Add support for `array_min`, `array_max`, `sort_array`, `array_zip` & `array_union` [datafusion-comet] via GitHub
  • Re: [PR] Feat: Add support for `array_min`, `array_max`, `sort_array`, `array_zip` & `array_union` [datafusion-comet] via GitHub
• Re: [I] Concat error while testing "array_repeat" [datafusion-comet] via GitHub
  • Re: [I] Concat error while testing "array_repeat" [datafusion-comet] via GitHub
• Re: [I] External Error prefix is repeated multiple times [datafusion] via GitHub
  • Re: [I] External Error prefix is repeated multiple times [datafusion] via GitHub
  • Re: [I] External Error prefix is repeated multiple times [datafusion] via GitHub
  • Re: [I] External Error prefix is repeated multiple times [datafusion] via GitHub
• Re: [PR] Add RETURNS TABLE() support for CREATE FUNCTION in Postgresql [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add RETURNS TABLE() support for CREATE FUNCTION in Postgresql [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add RETURNS TABLE() support for CREATE FUNCTION in Postgresql [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add RETURNS TABLE() support for CREATE FUNCTION in Postgresql [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add RETURNS TABLE() support for CREATE FUNCTION in Postgresql [datafusion-sqlparser-rs] via GitHub
  • Re: [PR] Add RETURNS TABLE() support for CREATE FUNCTION in Postgresql [datafusion-sqlparser-rs] via GitHub

• Earlier messages
• Later messages