[jira] [Updated] (BEAM-7665) Support TypeDefinition options in beam.Combine()

["Tianyang Hu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tianyang Hu updated BEAM-7665:
------------------------------
    Description: 
Today, CombineFn's output type must be either concrete or a generic type that can be inferred from the input type. This doesn't work if the input type is struct\{U, V\} while the output type is V (where U and V are generic types).

Similar to ParDo, we could add TypeDefinition options support to Combine. This will bind generic types in the CombineFn to the specified concrete types at pipeline construction time.

  was:
Today, CombineFn's output type must be either concrete or a generic type that can be inferred from the input type. This doesn't work if the input type is struct{U, V} while the output type is V (where U and V are generic types).

Similar to ParDo, we could add TypeDefinition options support to Combine. This will bind generic types in the CombineFn to the specified concrete types at pipeline construction time.


> Support TypeDefinition options in beam.Combine()
> ------------------------------------------------
>
>                 Key: BEAM-7665
>                 URL: https://issues.apache.org/jira/browse/BEAM-7665
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>            Reporter: Tianyang Hu
>            Assignee: Tianyang Hu
>            Priority: Major
>
> Today, CombineFn's output type must be either concrete or a generic type that can be inferred from the input type. This doesn't work if the input type is struct\{U, V\} while the output type is V (where U and V are generic types).
> Similar to ParDo, we could add TypeDefinition options support to Combine. This will bind generic types in the CombineFn to the specified concrete types at pipeline construction time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)