-
# Summary
Currently, in order to facilitate the CI of our SDKs efficiently, we use local references in the dependency management files of the examples. If a user just copies the examples folder wit…
-
# Summary
Numaflow pipeline authors should be able to test the end-to-end pipeline spec and validate the outputs from the Sink based on the data they sent to the Source. The testing framework shoul…
-
### Problem Statement
Currently when a user wants to define a UDSource, couple of volumes are required to hold data like config map and secrets. An example is as below.
```
apiVersion: numaflow…
-
# Summary
Currently `AbstractPodTemplate` and `ContainerTemplate` need to be specified within each pipeline component (`daemon`, `job`, `vertex`). It would be useful to be able to set defaults for…
-
**Describe the bug**
If an excludedPath or path to a field does not currently exist in the original spec of a Rollout object, the USDE method `ResourceNeedsUpdating` will not return the strategy `D…
-
**Describe the bug**
We have noticed that in certain pipelines, the map udf stops consuming the events from the ISB completely.
This behaviour is intermittent, and we couldn’t find any error logs on…
-
# Problem definition
Currently, we keep the proto files in all the SDKs, if we have to change anything we will need to manually update the proto files in all the SDK repos. Which isn't easy to mai…
yhl25 updated
3 months ago
-
# Summary
As per https://github.com/numaproj/numaflow/pull/1683#discussion_r1569625987. We should also in the same file mention that `version_mapping.go` should be updated after each new release.
…
-
Document event_time and how it is affected by reduce.
-
# Summary
Currently, the paths to the example images are hardcoded in the build-push workflow and passed to the script. This means when adding a new or updating an existing example, a developer nee…