You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by tr...@apache.org on 2022/01/28 13:39:28 UTC
[flink-statefun-playground] branch dev updated: [hotfix] Bump dev branch to use v3.1.0
This is an automated email from the ASF dual-hosted git repository.
trohrmann pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/flink-statefun-playground.git
The following commit(s) were added to refs/heads/dev by this push:
new 76ecc30 [hotfix] Bump dev branch to use v3.1.0
76ecc30 is described below
commit 76ecc3061f5bb45b40ebb337bd89ac7ebd954a7a
Author: Till Rohrmann <tr...@apache.org>
AuthorDate: Fri Jan 28 14:37:16 2022 +0100
[hotfix] Bump dev branch to use v3.1.0
---
deployments/aws-lambda/README.md | 4 ++--
go/greeter/go.mod | 5 ++++-
go/greeter/go.sum | 4 ++++
java/greeter/README.md | 4 ++--
java/shopping-cart/README.md | 9 +++------
.../part6/serving/StatefulFunctionsRuntimeProcesses.java | 4 ++--
6 files changed, 17 insertions(+), 13 deletions(-)
diff --git a/deployments/aws-lambda/README.md b/deployments/aws-lambda/README.md
index 6036edf..a9d2b3a 100644
--- a/deployments/aws-lambda/README.md
+++ b/deployments/aws-lambda/README.md
@@ -38,9 +38,9 @@ for invoking your StateFun functions.
### Configure StateFun Module Specification
-The AWS Lambda endpoint URL should be configured as a function endpoint in your [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/).
+The AWS Lambda endpoint URL should be configured as a function endpoint in your [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.1/docs/deployment/module/).
-Note how you may use [templating](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/#url-template)
+Note how you may use [templating](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.1/docs/deployment/module/#url-template)
in the endpoint URL for multiple functions under the same namespace This allows you to add new AWS Lambda functions,
potentially individually serving different StateFun functions, under separate paths of the same AWS API Gateway endpoint.
This provides flexibility to upgrade your StateFun application by dynamically adding new functions without having to restart the StateFun runtime.
diff --git a/go/greeter/go.mod b/go/greeter/go.mod
index f4d5657..f6847d3 100644
--- a/go/greeter/go.mod
+++ b/go/greeter/go.mod
@@ -18,4 +18,7 @@ module statefun.io/greeter
go 1.16
-require github.com/apache/flink-statefun/statefun-sdk-go/v3 v3.1.0
+require (
+ github.com/apache/flink-statefun/statefun-sdk-go/v3 v3.1.1
+ google.golang.org/protobuf v1.27.1 // indirect
+)
diff --git a/go/greeter/go.sum b/go/greeter/go.sum
index c35cbea..8e6bfca 100644
--- a/go/greeter/go.sum
+++ b/go/greeter/go.sum
@@ -1,5 +1,7 @@
github.com/apache/flink-statefun/statefun-sdk-go/v3 v3.1.0 h1:uE56xfgn4c/ytXppcW/NQUNxtPM8NpvkbU/VFMuaXN4=
github.com/apache/flink-statefun/statefun-sdk-go/v3 v3.1.0/go.mod h1:uHiPJsi71a161NMH/ISkkSPIXenkcG9A2m+uhT8UlJ4=
+github.com/apache/flink-statefun/statefun-sdk-go/v3 v3.1.1 h1:p9WPjFR+6ebPMc/Cmn9EAZ2NouH5pYjkQUv2QXhrMU4=
+github.com/apache/flink-statefun/statefun-sdk-go/v3 v3.1.1/go.mod h1:uHiPJsi71a161NMH/ISkkSPIXenkcG9A2m+uhT8UlJ4=
github.com/davecgh/go-spew v1.1.0 h1:ZDRjVQ15GmhC3fiQ8ni8+OwkZQO4DARzQgrnXU1Liz8=
github.com/davecgh/go-spew v1.1.0/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
github.com/golang/protobuf v1.5.0/go.mod h1:FsONVRAS9T7sI+LIUmWTfcYkHO4aIWwzhcaSAoJOfIk=
@@ -15,6 +17,8 @@ golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543/go.mod h1:I/5z698sn9Ka8T
google.golang.org/protobuf v1.26.0-rc.1/go.mod h1:jlhhOSvTdKEhbULTjvd4ARK9grFBp09yW+WbY/TyQbw=
google.golang.org/protobuf v1.26.0 h1:bxAC2xTBsZGibn2RTntX0oH50xLsqy1OxA9tTL3p/lk=
google.golang.org/protobuf v1.26.0/go.mod h1:9q0QmTI4eRPtz6boOQmLYwt+qCgq0jsYwAQnmE0givc=
+google.golang.org/protobuf v1.27.1 h1:SnqbnDw1V7RiZcXPx5MEeqPv2s79L9i7BJUlG/+RurQ=
+google.golang.org/protobuf v1.27.1/go.mod h1:9q0QmTI4eRPtz6boOQmLYwt+qCgq0jsYwAQnmE0givc=
gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0=
gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c h1:dUUwHk2QECo/6vqA44rthZ8ie2QXMNeKRTHCNY2nXvo=
gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
diff --git a/java/greeter/README.md b/java/greeter/README.md
index 2e739b5..a26e843 100644
--- a/java/greeter/README.md
+++ b/java/greeter/README.md
@@ -22,9 +22,9 @@ that accepts user information to generate personalized greeting messages that ar
our functions service, hosting the `UserFn` and `UserLogin` behind a HTTP endpoint. Check out the source code under
`src/main/java`. The `Dockerfile` is used to build a Docker image for our functions service.
- `user-logins.txt`: A file with multiple JSON objects per line; this is used as test events produced to our application ingress.
-- `module.yaml`: The [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/) file to be mounted to the StateFun runtime process containers. This
+- `module.yaml`: The [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.1/docs/deployment/module/) file to be mounted to the StateFun runtime process containers. This
configures a few things for a StateFun application, such as the service endpoints of the application's functions, as
- well as definitions of [Ingresses and Egresses](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/io-module/overview/) which the application will use.
+ well as definitions of [Ingresses and Egresses](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.1/docs/io-module/overview/) which the application will use.
- `docker-compose.yml`: Docker Compose file to spin up everything.
## Prerequisites
diff --git a/java/shopping-cart/README.md b/java/shopping-cart/README.md
index 75233ad..7327f2c 100644
--- a/java/shopping-cart/README.md
+++ b/java/shopping-cart/README.md
@@ -9,9 +9,9 @@ If you are new to stateful functions, we recommend you to first look at a more s
- `src/`, `pom.xml` and `Dockerfile`: These files and directories are the contents of a Java Maven project which builds
our functions service, hosting the `UserShoppingCartFn` and `StockFn` behind a HTTP endpoint. Check out the source code under
`src/main/java`. The `Dockerfile` is used to build a Docker image for our functions service.
-- `module.yaml`: The [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/) file to be mounted to the StateFun runtime process containers. This
+- `module.yaml`: The [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.1/docs/deployment/module/) file to be mounted to the StateFun runtime process containers. This
configures a few things for a StateFun application, such as the service endpoints of the application's functions, as
- well as definitions of [Ingresses and Egresses](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/io-module/overview/) which the application will use.
+ well as definitions of [Ingresses and Egresses](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.1/docs/io-module/overview/) which the application will use.
- `docker-compose.yml`: Docker Compose file to spin up everything.
- `playthrough`: utilities for automatically playing through the interactions scenarios.
@@ -59,7 +59,7 @@ It will send a series of messages, results of which you can observe in the logs
```
docker-compose logs -f shopping-cart-functions
```
-Note: `Caller: Optional.empty` in the logs corresponds to the messages that came via an ingress rather than from another stateful function.
+Note: `Caller: Optional.empty` in the logs corresponds to the messages that came via an ingress rather than from another stateful function.
To see the results produced to the egress:
```
@@ -71,6 +71,3 @@ If you want to modify the code, you can do a hot redeploy of your functions serv
docker-compose up -d --build shopping-cart-functions
```
This rebuilds the functions service image with the updated code, and restarts the service with the new image.
-
-
-
diff --git a/java/showcase/src/main/java/org/apache/flink/statefun/playground/java/showcase/part6/serving/StatefulFunctionsRuntimeProcesses.java b/java/showcase/src/main/java/org/apache/flink/statefun/playground/java/showcase/part6/serving/StatefulFunctionsRuntimeProcesses.java
index efc12c5..1fd532d 100644
--- a/java/showcase/src/main/java/org/apache/flink/statefun/playground/java/showcase/part6/serving/StatefulFunctionsRuntimeProcesses.java
+++ b/java/showcase/src/main/java/org/apache/flink/statefun/playground/java/showcase/part6/serving/StatefulFunctionsRuntimeProcesses.java
@@ -86,7 +86,7 @@ public final class StatefulFunctionsRuntimeProcesses {
}
private static GenericContainer<?> managerContainer(Network network) {
- return new GenericContainer<>(DockerImageName.parse("apache/flink-statefun:3.0.0"))
+ return new GenericContainer<>(DockerImageName.parse("apache/flink-statefun:3.1.0"))
.withNetwork(network)
.withNetworkAliases("statefun-manager")
.withEnv("ROLE", "master")
@@ -98,7 +98,7 @@ public final class StatefulFunctionsRuntimeProcesses {
}
private static GenericContainer<?> workerContainer(Network network) {
- return new GenericContainer<>(DockerImageName.parse("apache/flink-statefun:3.0.0"))
+ return new GenericContainer<>(DockerImageName.parse("apache/flink-statefun:3.1.0"))
.withNetwork(network)
.withNetworkAliases("statefun-worker")
.withEnv("ROLE", "worker")