ZwxwZ opened a new issue, #37736:
URL: https://github.com/apache/beam/issues/37736
### What happened?
In yaml provider,
this yaml working fine with "type: chain"
```
- type: yaml
transforms:
# Define the first transform of type "RaiseElementToPower"
RaiseElementToPower:
config_schema:
properties:
n: {type: integer}
body:
type: chain
transforms:
- type: MapToFields
config:
language: python
append: true
fields:
power: "element ** {{n}}"
```
If i change the type to "type: composite",
```
- type: yaml
transforms:
# Define the first transform of type "RaiseElementToPower"
RaiseElementToPower:
config_schema:
properties:
n: {type: integer}
body:
type: composite
transforms:
- type: MapToFields
input: xxxx
config:
language: python
append: true
fields:
power: "element ** {{n}}"
```
there will have error, beacause it's required an input for the transform,
"type: composite" require include the input into the sub-yaml,
do composite transform must including the input into one page?
### Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam YAML
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Infrastructure
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
