You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ryan Thompson (Jira)" <ji...@apache.org> on 2022/03/31 14:51:00 UTC

[jira] [Created] (BEAM-14217) Figure out how type hints should work

Ryan Thompson created BEAM-14217:
------------------------------------

             Summary: Figure out how type hints should work
                 Key: BEAM-14217
                 URL: https://issues.apache.org/jira/browse/BEAM-14217
             Project: Beam
          Issue Type: Sub-task
          Components: sdk-py-core
            Reporter: Ryan Thompson


RunInference main interface could have many different types of input and ouput types.

 

It probably should have generice typehints of some sort, but the code that infers them will need to be specified.

 

I haven't yet figured out how to do this, but I'm convinced that getting really specific type hints will help our users find errors.

 

We have

@input output types unknown

RunInference(PTransform)
  has RunInferenceDoFun (also input output types unknown)
    calls composedRunInferenceFn (input/output types known)

we need to get correct type hints into the RunInference PTransform and it's not apparent how to do that exactly since annotations won't be possible.

 

I think we'll need some correct values to put into the with_output_type chain in the ptransform.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)