You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by tz...@apache.org on 2020/03/28 15:41:52 UTC
[flink-statefun] branch release-2.0 updated (7eb114b -> 6e8d855)
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a change to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git.
from 7eb114b [hotfix] [legal] Add font-awesome dependency to source NOTICE and LICENSE
new 6de1987 [FLINK-16730][docs] Python SDK Getting Started (#77)
new 621a6ee [FLINK-16841] Do not bundle Protobuf .proto source files in jars
new c0934bb [FLINK-16843] [py] Add LICENSE and NOTICE to Python SDK dists
new 767e428 [FLINK-16842] Use maven-shade-plugin to package ridesharing example simulator
new 9ac2d38 [FLINK-16842] Add NOTICE and licenses for statefun-ridesharing-example-simulator
new 2b77e20 [FLINK-16842] Add explicit NOTICE file for statefun-flink-core
new 541f957 [FLINK-16838] [docker] Build image with version tag
new c379227 [FLINK-16838] Let Dockerfile in quickstart point to a specific image version tag
new 95ef9d4 [FLINK-16838] Update base image definitions in examples and E2E tests
new bc3c424 [FLINK-16838] Update image name in docs and README.
new 1a98294 [FLINK-16838] Update base image version tag in update_branch_version.sh
new d0d6e47 [hofix] [docs] Fix image name and version tag in walkthrough.md
new 6e8d855 [hotfix] [docs] Fix github_branch value in _config.yml
The 13 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
README.md | 2 +-
docs/_config.yml | 2 +-
docs/deployment-and-operations/packaging.md | 2 +-
.../greeter => docs/downloads}/Dockerfile | 3 -
.../downloads/build-walkthrough-dist.sh | 17 +-
.../main.py => docs/downloads/greeter.py | 22 +-
docs/getting-started/walkthrough.md | 450 +++++++++---
pom.xml | 1 -
.../src/test/resources/Dockerfile | 2 +-
.../src/test/resources/Dockerfile | 2 +-
.../statefun-greeter-example/Dockerfile | 2 +-
.../statefun-python-greeter/Dockerfile | 2 +-
.../statefun-python-k8s/Dockerfile.statefun | 2 +-
.../Dockerfile.functions | 2 +-
.../Dockerfile | 2 +-
.../statefun-ridesharing-example-simulator/pom.xml | 48 +-
.../src/main/resources/META-INF/NOTICE | 82 +++
.../licenses/LICENSE.animal-sniffer-annotations | 19 +
.../META-INF/licenses/LICENSE.checker-qual | 22 +
.../META-INF/licenses/LICENSE.javax.annotation-api | 759 +++++++++++++++++++++
.../META-INF/licenses/LICENSE.jul-to-slf4j | 21 +
.../META-INF/licenses/LICENSE.logback-classic | 24 +
.../META-INF/licenses/LICENSE.logback-core | 24 +
.../META-INF/licenses/LICENSE.protobuf-java | 0
.../resources/META-INF/licenses/LICENSE.slf4j-api | 21 +
.../META-INF/licenses/LICENSE.sockjs-client | 21 +
.../statefun-shopping-cart-example/Dockerfile | 2 +-
.../src/main/resources/META-INF/NOTICE | 10 +
LICENSE => statefun-python-sdk/LICENSE | 0
statefun-python-sdk/NOTICE | 5 +
statefun-python-sdk/setup.py | 1 +
.../main/resources/archetype-resources/Dockerfile | 2 +-
tools/docker/README.md | 22 +
tools/docker/build-stateful-functions.sh | 8 +-
tools/releasing/update_branch_version.sh | 4 +
35 files changed, 1455 insertions(+), 153 deletions(-)
copy {statefun-examples/statefun-python-greeter/greeter => docs/downloads}/Dockerfile (89%)
copy statefun-python-sdk/build-distribution.sh => docs/downloads/build-walkthrough-dist.sh (66%)
copy statefun-examples/statefun-python-k8s/main.py => docs/downloads/greeter.py (74%)
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/NOTICE
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.animal-sniffer-annotations
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.checker-qual
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.javax.annotation-api
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.jul-to-slf4j
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-classic
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-core
copy {statefun-flink/statefun-flink-distribution => statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator}/src/main/resources/META-INF/licenses/LICENSE.protobuf-java (100%)
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.slf4j-api
create mode 100644 statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.sockjs-client
create mode 100644 statefun-flink/statefun-flink-core/src/main/resources/META-INF/NOTICE
copy LICENSE => statefun-python-sdk/LICENSE (100%)
create mode 100644 statefun-python-sdk/NOTICE
create mode 100644 tools/docker/README.md
[flink-statefun] 01/13: [FLINK-16730][docs] Python SDK Getting
Started (#77)
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 6de1987ad8cf2e3511a762f4889554059d9067a0
Author: Seth Wiesman <sj...@gmail.com>
AuthorDate: Fri Mar 27 15:34:16 2020 -0500
[FLINK-16730][docs] Python SDK Getting Started (#77)
---
docs/downloads/Dockerfile | 31 +++
docs/downloads/build-walkthrough-dist.sh | 30 +++
docs/downloads/greeter.py | 53 ++++
docs/getting-started/walkthrough.md | 450 +++++++++++++++++++++++--------
4 files changed, 456 insertions(+), 108 deletions(-)
diff --git a/docs/downloads/Dockerfile b/docs/downloads/Dockerfile
new file mode 100644
index 0000000..23b62c5
--- /dev/null
+++ b/docs/downloads/Dockerfile
@@ -0,0 +1,31 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+FROM python:3.7-alpine
+
+RUN mkdir -p /app
+WORKDIR /app
+
+COPY requirements.txt /app
+RUN pip install -r requirements.txt
+
+COPY greeter.py /app
+COPY messages_pb2.py /app
+
+EXPOSE 8000
+
+CMD ["gunicorn", "-b", "0.0.0.0:8000", "-w 4", "greeter:app"]
+
diff --git a/docs/downloads/build-walkthrough-dist.sh b/docs/downloads/build-walkthrough-dist.sh
new file mode 100755
index 0000000..0fe14d8
--- /dev/null
+++ b/docs/downloads/build-walkthrough-dist.sh
@@ -0,0 +1,30 @@
+#!/bin/sh
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+rm -f walkthrough.zip
+cp -r ../../statefun-examples/statefun-python-greeter statefun-walkthrough
+
+rm statefun-walkthrough/build-example.sh
+
+rm statefun-walkthrough/greeter/greeter.py
+cp greeter.py statefun-walkthrough/greeter/greeter.py
+
+rm statefun-walkthrough/greeter/Dockerfile
+cp Dockerfile statefun-walkthrough/greeter/Dockerfile
+
+zip -r walkthrough.zip statefun-walkthrough
+rm -rf statefun-walkthrough
diff --git a/docs/downloads/greeter.py b/docs/downloads/greeter.py
new file mode 100644
index 0000000..daf5240
--- /dev/null
+++ b/docs/downloads/greeter.py
@@ -0,0 +1,53 @@
+################################################################################
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+################################################################################
+from messages_pb2 import SeenCount, GreetRequest, GreetResponse
+
+from statefun import StatefulFunctions
+from statefun import RequestReplyHandler
+from statefun import kafka_egress_record
+
+functions = StatefulFunctions()
+
+
+@functions.bind("example/greeter")
+def greet(context, message):
+ pass
+
+handler = RequestReplyHandler(functions)
+
+#
+# Serve the endpoint
+#
+
+from flask import request
+from flask import make_response
+from flask import Flask
+
+app = Flask(__name__)
+
+
+@app.route('/statefun', methods=['POST'])
+def handle():
+ response_data = handler(request.data)
+ response = make_response(response_data)
+ response.headers.set('Content-Type', 'application/octet-stream')
+ return response
+
+
+if __name__ == "__main__":
+ app.run()
\ No newline at end of file
diff --git a/docs/getting-started/walkthrough.md b/docs/getting-started/walkthrough.md
index b55b0a4..6b9bf59 100644
--- a/docs/getting-started/walkthrough.md
+++ b/docs/getting-started/walkthrough.md
@@ -24,177 +24,411 @@ specific language governing permissions and limitations
under the License.
-->
+Stateful Functions offers a platform for building robust, stateful event-driven applications.
+It provides fine-grained control over state and time, which allows for the implementation of advanced systems.
+In this step-by-step guide you’ll learn how to build a stateful applications with the Stateful Functions API.
+
+* This will be replaced by the TOC
+{:toc}
+
+## What Are You Building?
+
Like all great introductions in software, this walkthrough will start at the beginning: saying hello.
The application will run a simple function that accepts a request and responds with a greeting.
It will not attempt to cover all the complexities of application development, but instead focus on building a stateful function — which is where you will implement your business logic.
-* This will be replaced by the TOC
-{:toc}
+## Prerequisites
+
+This walkthrough assumes that you have some familiarity with Python, but you should be able to follow along even if you are coming from a different programming language.
+
+## Help, I’m Stuck!
+
+If you get stuck, check out the [community support resources](https://flink.apache.org/gettinghelp.html).
+In particular, Apache Flink's [user mailing list](https://flink.apache.org/community.html#mailing-lists) is consistently ranked as one of the most active of any Apache project and a great way to get help quickly.
-## A Basic Hello
+## How to Follow Along
+
+If you want to follow along, you will require a computer with [Python 3](https://www.python.org/) along with [Docker](https://www.docker.com/).
+
+{% panel **Note:** Each code block within this walkthrough may not contain the full surrounding class for brevity.
+The full code is available on [at the bottom of this page](#full-application). %}
+
+You can download a zip file with a skeleton project by clicking [here]({{ site.baseurl }}/downloads/walkthrough.zip).
+
+{% unless site.is_stable %}
+<p style="border-radius: 5px; padding: 5px" class="bg-danger">
+ <b>Note</b>: The Stateful Functions project does not publish snapshot versions of the Python SDK to PyPy.
+ Please consider using a stable version of this guide.
+</p>
+{% endunless %}
+
+After unzipping the package, you will find a number of files.
+These include dockerfiles and data generators to run this walkthrough in a local self contained environment.
+
+{% highlight bash %}
+$ tree statefun-walkthrough
+statefun-walkthrough
+├── Dockerfile
+├── README.md
+├── docker-compose.yml
+├── generator
+│ ├── Dockerfile
+│ ├── event-generator.py
+│ └── messages_pb2.py
+├── greeter
+│ ├── Dockerfile
+│ ├── greeter.py
+│ ├── messages.proto
+│ ├── messages_pb2.py
+│ └── requirements.txt
+└── module.yaml
+{% endhighlight %}
-Greeting actions are triggered by consuming, routing and passing messages that are defined using ProtoBuf.
+## Start With Events
+
+Stateful Functions is an event driven system, so development begins by defining our events.
+The greeter application will define its events using [protocol buffers](https://developers.google.com/protocol-buffers).
+When a greet request for a particular user is ingested, it will be routed to the appropriate function.
+The response will be returned with an appropriate greeting.
+The third type, `SeenCount`, is a utility class that will be used latter on to help manage the number of times a user has been seen so far.
{% highlight proto %}
syntax = "proto3";
+package example;
+
+// External request sent by a user who wants to be greeted
message GreetRequest {
- string who = 1;
+ // The name of the user to greet
+ string name = 1;
}
-
+// A customized response sent to the user
message GreetResponse {
- string who = 1;
+ // The name of the user being greeted
+ string name = 1;
+ // The users customized greeting
string greeting = 2;
}
+// An internal message used to store state
+message SeenCount {
+ // The number of times a users has been seen so far
+ int64 seen = 1;
+}
{% endhighlight %}
-Under the hood, messages are processed using [stateful functions]({{ site.baseurl }}/sdk/java.html), by definition any class that implements the ``StatefulFunction`` interface.
-{% highlight java %}
-package org.apache.flink.statefun.examples.greeter;
+## Our First Function
-import org.apache.flink.statefun.sdk.Context;
-import org.apache.flink.statefun.sdk.StatefulFunction;
+Under the hood, messages are processed using [stateful functions]({{ site.baseurl }}/sdk/python.html), which is any two argument function that is bound to the ``StatefulFunction`` runtime.
+Functions are bound to the runtime with the `@function.bind` decorator.
+When binding a function, it is annotated with a function type.
+This is the name used to reference this function when sending it messages.
-public final class GreetFunction implements StatefulFunction {
+When you open the file `greeter/greeter.py` you should see the following code.
- @Override
- public void invoke(Context context, Object input) {
- GreetRequest greetMessage = (GreetRequest) input;
+{% highlight python %}
+from statefun import StatefulFunctions
- GreetResponse response = GreetResponse.newBuilder()
- .setWho(greetMessage.getWho())
- .setGreeting("Hello " + greetMessage.getWho())
- .build();
+functions = StatefulFunctions()
- context.send(GreetingConstants.GREETING_EGRESS_ID, response);
- }
-}
+@functions.bind("example/greeter")
+def greet(context, greet_request):
+ pass
{% endhighlight %}
+A stateful function takes two arguments, a context and message.
+The [context]({{ site.baseurl }}/sdk/python.html#context-reference) provides access to stateful functions runtime features such as state management and message passing.
+You will explore some of these features as you progress through this walkthrough.
-This function takes in a request and sends a response to an external system (or [egress]({{ site.baseurl }}/io-module/index.html#egress)).
-While this is nice, it does not show off the real power of stateful functions: handling state.
+The other parameter is the input message that has been passed to this function.
+By default messages are passed around as protobuf [Any](https://developers.google.com/protocol-buffers/docs/reference/python-generated#wkt).
+If a function only accepts a known type, you can override the message type using Python 3 type syntax.
+This way you do not need to unwrap the message or check types.
-## A Stateful Hello
+{% highlight python %}
+from messages_pb2 import GreetRequest
+from statefun import StatefulFunctions
-Suppose you want to generate a personalized response for each user depending on how many times they have sent a request.
+functions = StatefulFunctions()
-{% highlight java %}
-private static String greetText(String name, int seen) {
- switch (seen) {
- case 0:
- return String.format("Hello %s !", name);
- case 1:
- return String.format("Hello again %s !", name);
- case 2:
- return String.format("Third times the charm! %s!", name);
- case 3:
- return String.format("Happy to see you once again %s !", name);
- default:
- return String.format("Hello at the %d-th time %s", seen + 1, name);
-}
+@functions.bind("example/greeter")
+def greet(context, greet_request: GreetRequest):
+ pass
{% endhighlight %}
-## Routing Messages
+## Sending A Response
-To send a user a personalized greeting, the system needs to keep track of how many times it has seen each user so far.
-Speaking in general terms, the simplest solution would be to create one function for every user and independently track the number of times they have been seen. Using most frameworks, this would be prohibitively expensive.
-However, stateful functions are virtual and do not consume any CPU or memory when not actively being invoked.
-That means your application can create as many functions as necessary — in this case, users — without worrying about resource consumption.
+Stateful Functions accept messages and can also send them out.
+Messages can be sent to other functions, as well as external systems (or [egress]({{ site.baseurl }}/io-module/index.html#egress)).
-Whenever data is consumed from an external system (or [ingress]({{ site.baseurl }}/io-module/index.html#ingress)), it is routed to a specific function based on a given function type and identifier.
-The function type represents the Class of function to be invoked, such as the Greeter function, while the identifier (``GreetRequest#getWho``) scopes the call to a specific virtual instance based on some key.
+One popular external system is [Apache Kafka](http://kafka.apache.org/).
+As a first step, lets update our function in `greeter/greeter.py` to respond to each input by sending a greeting to a Kafka topic.
-{% highlight java %}
-package org.apache.flink.statefun.examples.greeter;
+{% highlight python %}
+from messages_pb2 import GreetRequest, GreetResponse
+from statefun import StatefulFunctions
-import org.apache.flink.statefun.examples.kafka.generated.GreetRequest;
-import org.apache.flink.statefun.sdk.io.Router;
+functions = StatefulFunctions()
-final class GreetRouter implements Router<GreetRequest> {
+@functions.bind("example/greeter")
+def greet(context, message: GreetRequest):
+ response = GreetResponse()
+ response.name = message.name
+ response.greeting = "Hello {}".format(message.name)
+
+ egress_message = kafka_egress_record(topic="greetings", key=message.name, value=response)
+ context.pack_and_send_egress("example/greets", egress_message)
+{% endhighlight %}
- @Override
- public void route(GreetRequest message, Downstream<GreetRequest> downstream) {
- downstream.forward(GreetingConstants.GREETER_FUNCTION_TYPE, message.getWho(), message);
- }
-}
+For each message, a response is constructed and sent to a kafka topic call `greetings` partitioned by `name`.
+The `egress_message` is sent to a an `egress` named `example/greets`.
+This identifier points to a particular Kafka cluster and is configured on deployment below.
+
+## A Stateful Hello
+
+This is a great start, but does not show off the real power of stateful functions - working with state.
+Suppose you want to generate a personalized response for each user depending on how many times they have sent a request.
+
+{% highlight python %}
+def compute_greeting(name, seen):
+ """
+ Compute a personalized greeting, based on the number of times this @name had been seen before.
+ """
+ templates = ["", "Welcome %s", "Nice to see you again %s", "Third time is a charm %s"]
+ if seen < len(templates):
+ greeting = templates[seen] % name
+ else:
+ greeting = "Nice to see you at the %d-nth time %s!" % (seen, name)
+
+ response = GreetResponse()
+ response.name = name
+ response.greeting = greeting
+
+ return response
{% endhighlight %}
-So, if a message for a user named John comes in, it will be shipped to John’s dedicated Greeter function.
-In case there is a following message for a user named Jane, a new instance of the Greeter function will be spawned.
+To “remember” information across multiple greeting messages, you then need to associate a persisted value field (``seen_count``) to the Greet function.
+For each user, functions can now track how many times they have been seen.
-## Persistence
+{% highlight python %}
+@functions.bind("example/greeter")
+def greet(context, greet_message: GreetRequest):
+ state = context.state('seen_count').unpack(SeenCount)
+ if not state:
+ state = SeenCount()
+ state.seen = 1
+ else:
+ state.seen += 1
+ context.state('seen_count').pack(state)
-[Persisted value]({{ site.baseurl }}/sdk/java.html#persistence) is a special data type that enables stateful functions to maintain fault-tolerant state scoped to their identifiers, so that each instance of a function can track state independently.
-To “remember” information across multiple greeting messages, you then need to associate a persisted value field (``count``) to the Greet function. For each user, functions can now track how many times they have been seen.
+ response = compute_greeting(greet_request.name, state.seen)
-{% highlight java %}
-package org.apache.flink.statefun.examples.greeter;
+ egress_message = kafka_egress_record(topic="greetings", key=greet_request.name, value=response)
+ context.pack_and_send_egress("example/greets", egress_message)
+{% endhighlight %}
-import org.apache.flink.statefun.sdk.Context;
-import org.apache.flink.statefun.sdk.StatefulFunction;
-import org.apache.flink.statefun.sdk.annotations.Persisted;
-import org.apache.flink.statefun.sdk.state.PersistedValue;
+The state, `seen_count` is always scoped to the current name so it can track each user independently.
-public final class GreetFunction implements StatefulFunction {
+## Wiring It All Together
- @Persisted
- private final PersistedValue<Integer> count = PersistedValue.of("count", Integer.class);
+Stateful Function applications communicate with the Apache Flink runtime using `http`.
+The Python SDK ships with a ``RequestReplyHandler`` that automatically dispatches function calls based on RESTful HTTP ``POSTS``.
+The ``RequestReplyHandler`` may be exposed using any HTTP framework.
- @Override
- public void invoke(Context context, Object input) {
- GreetRequest greetMessage = (GreetRequest) input;
+One popular Python web framework is [Flask](https://palletsprojects.com/p/flask/).
+It can be used to quickly and easily expose an application to the Apache Flink runtime.
- GreetResponse response = computePersonalizedGreeting(greetMessage);
+{% highlight python %}
+from statefun import StatefulFunctions
+from statefun import RequestReplyHandler
- context.send(GreetingConstants.GREETING_EGRESS_ID, response);
- }
+functions = StatefulFunctions()
- private GreetResponse computePersonalizedGreeting(GreetRequest greetMessage) {
- final String name = greetMessage.getWho();
- final int seen = count.getOrDefault(0);
- count.set(seen + 1);
+@functions.bind("walkthrough/greeter")
+def greeter(context, message: GreetRequest):
+ pass
- String greeting = greetText(name, seen);
+handler = RequestReplyHandler(functions)
- return GreetResponse.newBuilder()
- .setWho(name)
- .setGreeting(greeting)
- .build();
- }
-}
+# Serve the endpoint
+
+from flask import request
+from flask import make_response
+from flask import Flask
+
+app = Flask(__name__)
+
+@app.route('/statefun', methods=['POST'])
+def handle():
+ response_data = handler(request.data)
+ response = make_response(response_data)
+ response.headers.set('Content-Type', 'application/octet-stream')
+ return response
+
+
+if __name__ == "__main__":
+ app.run()
{% endhighlight %}
-Each time a message is processed, the function computes a personalized message for that user.
-It reads and updates the number of times that user has been seen and sends a greeting to the egress.
+## Configuring for Runtime
+
+The Stateful Function runtime makes requests to the greeter function by making `http` calls to the `Flask` server.
+To do that, it needs to know what endpoint it can use to reach the server.
+This is also a good time to configure our connection to the input and output Kafka topics.
+The configuration is in a file called `module.yaml`.
+
+{% highlight yaml %}
+version: "1.0"
+module:
+ meta:
+ type: remote
+ spec:
+ functions:
+ - function:
+ meta:
+ kind: http
+ type: example/greeter
+ spec:
+ endpoint: http://python-worker:8000/statefun
+ states:
+ - seen_count
+ maxNumBatchRequests: 500
+ timeout: 2min
+ ingresses:
+ - ingress:
+ meta:
+ type: statefun.kafka.io/routable-protobuf-ingress
+ id: example/names
+ spec:
+ address: kafka-broker:9092
+ consumerGroupId: my-group-id
+ topics:
+ - topic: names
+ typeUrl: com.googleapis/example.GreetRequest
+ targets:
+ - example/greeter
+ egresses:
+ - egress:
+ meta:
+ type: statefun.kafka.io/generic-egress
+ id: example/greets
+ spec:
+ address: kafka-broker:9092
+ deliverySemantic:
+ type: exactly-once
+ transactionTimeoutMillis: 100000
+{% endhighlight %}
-You can check the full code for the application described in this walkthrough [here]({{ site.github_url }}/tree/{{ site.github_branch }}/statefun-examples/statefun-greeter-example).
-In particular, take a look at the module ``GreetingModule``, which is the main entry point for the full application, to see how everything gets tied together.
-You can run this example locally using the provided Docker setup.
+This configuration does a few interesting things.
-{% highlight bash %}
-$ docker-compose build
-$ docker-compose up
+The first is to declare our function, `example/greeter`.
+It includes the endpoint by which it is reachable along with the states the function has access to.
+
+The ingress is the input Kafka topic that routes `GreetRequest` messages to the function.
+Along with basic properties like broker address and consumer group, it contains a list of targets.
+These are the functions each message will be sent to.
+
+The egress is the output Kafka cluster.
+It contains broker specific configurations but allows each message to route to any topic.
+
+## Deployment
+
+Now that the greeter application has been built it is time to deploy.
+The simplest way to deploy a Stateful Function application is by using the community provided base image and loading your module.
+The base image provides the Stateful Function runtime, it will use the provided `module.yaml` to configure for this specific job.
+This can be found in the `Dockerfile` in the root directory.
+
+{% highlight docker %}
+FROM statefun
+
+RUN mkdir -p /opt/statefun/modules/greeter
+ADD module.yaml /opt/statefun/modules/greeter
{% endhighlight %}
-Then, send some messages to the topic "names", and observe what comes out of "greetings".
+You can now run this application locally using the provided Docker setup.
{% highlight bash %}
-$ docker-compose exec kafka-broker kafka-console-producer.sh \
- --broker-list localhost:9092 \
- --topic names
+$ docker-compose up -d
+{% endhighlight %}
+
+Then, to see the example in actions, see what comes out of the topic `greetings`:
-$ docker-compose exec kafka-broker kafka-console-consumer.sh \
- --bootstrap-server localhost:9092 \
- --topic greetings
+{% highlight bash %}
+docker-compose logs -f event-generator
{% endhighlight %}
-<p class="text-center">
- <img width="80%" src="{{ site.baseurl }}/fig/greeter-function.gif"/>
-</p>
## Want To Go Further?
This Greeter never forgets a user.
-Try and modify the function so that it will reset the ``count`` for any user that spends more than 60 seconds without interacting with the system.
+Try and modify the function so that it will reset the ``seen_count`` for any user that spends more than 60 seconds without interacting with the system.
+
+## Full Application
+
+{% highlight python %}
+from messages_pb2 import SeenCount, GreetRequest, GreetResponse
+
+from statefun import StatefulFunctions
+from statefun import RequestReplyHandler
+from statefun import kafka_egress_record
+
+functions = StatefulFunctions()
+
+@functions.bind("example/greeter")
+def greet(context, greet_request: GreetRequest):
+ state = context.state('seen_count').unpack(SeenCount)
+ if not state:
+ state = SeenCount()
+ state.seen = 1
+ else:
+ state.seen += 1
+ context.state('seen_count').pack(state)
+
+ response = compute_greeting(greet_request.name, state.seen)
+
+ egress_message = kafka_egress_record(topic="greetings", key=greet_request.name, value=response)
+ context.pack_and_send_egress("example/greets", egress_message)
+
+
+def compute_greeting(name, seen):
+ """
+ Compute a personalized greeting, based on the number of times this @name had been seen before.
+ """
+ templates = ["", "Welcome %s", "Nice to see you again %s", "Third time is a charm %s"]
+ if seen < len(templates):
+ greeting = templates[seen] % name
+ else:
+ greeting = "Nice to see you at the %d-nth time %s!" % (seen, name)
+
+ response = GreetResponse()
+ response.name = name
+ response.greeting = greeting
+
+ return response
+
+
+handler = RequestReplyHandler(functions)
+
+#
+# Serve the endpoint
+#
+
+from flask import request
+from flask import make_response
+from flask import Flask
+
+app = Flask(__name__)
+
+
+@app.route('/statefun', methods=['POST'])
+def handle():
+ response_data = handler(request.data)
+ response = make_response(response_data)
+ response.headers.set('Content-Type', 'application/octet-stream')
+ return response
+
+
+if __name__ == "__main__":
+ app.run()
+
+{% endhighlight %}
[flink-statefun] 07/13: [FLINK-16838] [docker] Build image with
version tag
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 541f9572a176d3a9ef0621436ef27271d0360201
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 14:00:50 2020 +0800
[FLINK-16838] [docker] Build image with version tag
We also change the image name from statefun to flink-statefun, to have a
more consistent naming with other distributions like the Python SDK.
---
tools/docker/README.md | 22 ++++++++++++++++++++++
tools/docker/build-stateful-functions.sh | 4 +++-
2 files changed, 25 insertions(+), 1 deletion(-)
diff --git a/tools/docker/README.md b/tools/docker/README.md
new file mode 100644
index 0000000..0b8cc43
--- /dev/null
+++ b/tools/docker/README.md
@@ -0,0 +1,22 @@
+# Stateful Functions Docker Image
+
+This directory contains scripts to build images using the current source version.
+
+The scripts here assumes that distribution and core artifacts are already built from the current source, and adds them to the image build context.
+Therefore, before executing the scripts, make sure to build the project first using `mvn clean package -DskipTests`.
+
+## Building the image
+
+```
+./build-stateful-functions.sh
+```
+
+This builds the `flink-statefun` image, tagged with the current source version.
+
+## Code examples and E2E tests
+
+There are several [examples](../../statefun-examples) and [end-to-end tests](../../statefun-e2e-tests) that rely
+on images built with the corresponding source version.
+
+For released versions, the required image should be available in the Docker Hub registry.
+For snapshots / unstable versions, you would need to build the image locally with the scripts here.
diff --git a/tools/docker/build-stateful-functions.sh b/tools/docker/build-stateful-functions.sh
index 0c950dc..eef29d6 100755
--- a/tools/docker/build-stateful-functions.sh
+++ b/tools/docker/build-stateful-functions.sh
@@ -17,6 +17,8 @@
set -e
+VERSION_TAG=2.0-SNAPSHOT
+
#
# setup the environment
#
@@ -56,7 +58,7 @@ cp ${core_jar} ${docker_context_flink}/lib/statefun-flink-core.jar
cd ${docker_context_root}
cp ${basedir}/Dockerfile ${docker_context_root}
cp ${basedir}/docker-entry-point.sh ${docker_context_root}
-docker build . -t statefun
+docker build . -t flink-statefun:${VERSION_TAG}
# clean again
rm -rf ${docker_context_root}
[flink-statefun] 03/13: [FLINK-16843] [py] Add LICENSE and NOTICE
to Python SDK dists
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit c0934bbe53723d4e955d32bfc7da73f92681cffd
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 18:45:39 2020 +0800
[FLINK-16843] [py] Add LICENSE and NOTICE to Python SDK dists
---
statefun-python-sdk/LICENSE | 201 +++++++++++++++++++++++++++++++++++++++++++
statefun-python-sdk/NOTICE | 5 ++
statefun-python-sdk/setup.py | 1 +
3 files changed, 207 insertions(+)
diff --git a/statefun-python-sdk/LICENSE b/statefun-python-sdk/LICENSE
new file mode 100644
index 0000000..261eeb9
--- /dev/null
+++ b/statefun-python-sdk/LICENSE
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/statefun-python-sdk/NOTICE b/statefun-python-sdk/NOTICE
new file mode 100644
index 0000000..76a0e4a
--- /dev/null
+++ b/statefun-python-sdk/NOTICE
@@ -0,0 +1,5 @@
+Python SDK for Apache Flink Stateful Functions
+Copyright 2014-2020 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
diff --git a/statefun-python-sdk/setup.py b/statefun-python-sdk/setup.py
index c55a064..c098875 100644
--- a/statefun-python-sdk/setup.py
+++ b/statefun-python-sdk/setup.py
@@ -31,6 +31,7 @@ setup(
packages=["statefun"],
url='https://github.com/apache/flink-statefun',
license='https://www.apache.org/licenses/LICENSE-2.0',
+ license_files=["LICENSE", "NOTICE"],
author='Apache Software Foundation',
author_email='dev@flink.apache.org',
description='Python SDK for Apache Flink Stateful functions',
[flink-statefun] 12/13: [hofix] [docs] Fix image name and version
tag in walkthrough.md
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit d0d6e4763b6ca3f60f55b1527a78e6cd39eb2cde
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 23:23:19 2020 +0800
[hofix] [docs] Fix image name and version tag in walkthrough.md
---
docs/getting-started/walkthrough.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/getting-started/walkthrough.md b/docs/getting-started/walkthrough.md
index 6b9bf59..fd705f8 100644
--- a/docs/getting-started/walkthrough.md
+++ b/docs/getting-started/walkthrough.md
@@ -339,7 +339,7 @@ The base image provides the Stateful Function runtime, it will use the provided
This can be found in the `Dockerfile` in the root directory.
{% highlight docker %}
-FROM statefun
+FROM flink-statefun:{{ site.version }}
RUN mkdir -p /opt/statefun/modules/greeter
ADD module.yaml /opt/statefun/modules/greeter
[flink-statefun] 02/13: [FLINK-16841] Do not bundle Protobuf .proto
source files in jars
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 621a6eefbd3a06321521cea9b456d6be39a26cbd
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 16:54:48 2020 +0800
[FLINK-16841] Do not bundle Protobuf .proto source files in jars
---
pom.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/pom.xml b/pom.xml
index f1bf7e0..cf994c6 100644
--- a/pom.xml
+++ b/pom.xml
@@ -117,7 +117,6 @@ under the License.
</goals>
<configuration>
<includeStdTypes>true</includeStdTypes>
- <addProtoSources>all</addProtoSources>
<protocVersion>${protobuf.version}</protocVersion>
<inputDirectories>
<include>src/test/protobuf</include>
[flink-statefun] 13/13: [hotfix] [docs] Fix github_branch value in
_config.yml
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 6e8d8553ae9128b98b623792558125d5eabb75b1
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 23:40:35 2020 +0800
[hotfix] [docs] Fix github_branch value in _config.yml
---
docs/_config.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/_config.yml b/docs/_config.yml
index 2a4a328..1c68dad 100644
--- a/docs/_config.yml
+++ b/docs/_config.yml
@@ -32,7 +32,7 @@ version: "2.0-SNAPSHOT"
# release this should be the same as the regular version
version_title: "2.0-SNAPSHOT"
# Branch on Github for this version
-github_branch: "master"
+github_branch: "release-2.0"
# Plain Scala version is needed for e.g. the Gradle quickstart.
scala_version: "2.11"
[flink-statefun] 06/13: [FLINK-16842] Add explicit NOTICE file for
statefun-flink-core
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 2b77e200df3595101deba6a6f7c2d95f02f3735f
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 22:55:31 2020 +0800
[FLINK-16842] Add explicit NOTICE file for statefun-flink-core
The artifact needs a specific NOTICE file, since the copied sources from
fastutil (http://fastutil.di.unimi.it/) will be bundled in the jar, and
therefore needs to be acknowledged.
---
.../statefun-flink-core/src/main/resources/META-INF/NOTICE | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/statefun-flink/statefun-flink-core/src/main/resources/META-INF/NOTICE b/statefun-flink/statefun-flink-core/src/main/resources/META-INF/NOTICE
new file mode 100644
index 0000000..cf33983
--- /dev/null
+++ b/statefun-flink/statefun-flink-core/src/main/resources/META-INF/NOTICE
@@ -0,0 +1,10 @@
+statefun-flink-core
+Copyright 2014-2020 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+This project contains copied and modified source code that is licensed under the Apache Software License 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt) from the following projects:
+
+- fastutil (http://fastutil.di.unimi.it/) Copyright (c) - Sebastiano Vigna
+ The copied sources can be located under it/unimi/dsi/fastutil/
[flink-statefun] 09/13: [FLINK-16838] Update base image definitions
in examples and E2E tests
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 95ef9d4f76a96baa8ea96203683f2cc09d862fb3
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 14:23:58 2020 +0800
[FLINK-16838] Update base image definitions in examples and E2E tests
---
.../statefun-routable-kafka-e2e/src/test/resources/Dockerfile | 2 +-
statefun-e2e-tests/statefun-sanity-e2e/src/test/resources/Dockerfile | 2 +-
statefun-examples/statefun-greeter-example/Dockerfile | 2 +-
statefun-examples/statefun-python-greeter/Dockerfile | 2 +-
statefun-examples/statefun-python-k8s/Dockerfile.statefun | 2 +-
statefun-examples/statefun-ridesharing-example/Dockerfile.functions | 2 +-
statefun-examples/statefun-shopping-cart-example/Dockerfile | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/statefun-e2e-tests/statefun-routable-kafka-e2e/src/test/resources/Dockerfile b/statefun-e2e-tests/statefun-routable-kafka-e2e/src/test/resources/Dockerfile
index 2b025c7..66d5051 100644
--- a/statefun-e2e-tests/statefun-routable-kafka-e2e/src/test/resources/Dockerfile
+++ b/statefun-e2e-tests/statefun-routable-kafka-e2e/src/test/resources/Dockerfile
@@ -13,7 +13,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:2.0-SNAPSHOT
RUN mkdir -p /opt/statefun/modules/statefun-routable-kafka-e2e
COPY statefun-routable-kafka-e2e*.jar /opt/statefun/modules/statefun-routable-kafka-e2e/
diff --git a/statefun-e2e-tests/statefun-sanity-e2e/src/test/resources/Dockerfile b/statefun-e2e-tests/statefun-sanity-e2e/src/test/resources/Dockerfile
index d72fa73..9b5b2fe 100644
--- a/statefun-e2e-tests/statefun-sanity-e2e/src/test/resources/Dockerfile
+++ b/statefun-e2e-tests/statefun-sanity-e2e/src/test/resources/Dockerfile
@@ -13,7 +13,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:2.0-SNAPSHOT
RUN mkdir -p /opt/statefun/modules/statefun-sanity-e2e
COPY statefun-sanity-e2e*.jar /opt/statefun/modules/statefun-sanity-e2e/
diff --git a/statefun-examples/statefun-greeter-example/Dockerfile b/statefun-examples/statefun-greeter-example/Dockerfile
index 7466f36..10e2f6d 100644
--- a/statefun-examples/statefun-greeter-example/Dockerfile
+++ b/statefun-examples/statefun-greeter-example/Dockerfile
@@ -13,7 +13,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:2.0-SNAPSHOT
RUN mkdir -p /opt/statefun/modules/statefun-greeter-example
COPY target/statefun-greeter-example*jar /opt/statefun/modules/statefun-greeter-example/
diff --git a/statefun-examples/statefun-python-greeter/Dockerfile b/statefun-examples/statefun-python-greeter/Dockerfile
index 9f3a803..1f39589 100644
--- a/statefun-examples/statefun-python-greeter/Dockerfile
+++ b/statefun-examples/statefun-python-greeter/Dockerfile
@@ -14,7 +14,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:2.0-SNAPSHOT
RUN mkdir -p /opt/statefun/modules/greeter
ADD module.yaml /opt/statefun/modules/greeter
diff --git a/statefun-examples/statefun-python-k8s/Dockerfile.statefun b/statefun-examples/statefun-python-k8s/Dockerfile.statefun
index 9f3a803..1f39589 100644
--- a/statefun-examples/statefun-python-k8s/Dockerfile.statefun
+++ b/statefun-examples/statefun-python-k8s/Dockerfile.statefun
@@ -14,7 +14,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:2.0-SNAPSHOT
RUN mkdir -p /opt/statefun/modules/greeter
ADD module.yaml /opt/statefun/modules/greeter
diff --git a/statefun-examples/statefun-ridesharing-example/Dockerfile.functions b/statefun-examples/statefun-ridesharing-example/Dockerfile.functions
index e36083c..d05813d 100644
--- a/statefun-examples/statefun-ridesharing-example/Dockerfile.functions
+++ b/statefun-examples/statefun-ridesharing-example/Dockerfile.functions
@@ -13,7 +13,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:2.0-SNAPSHOT
RUN mkdir -p /opt/statefun/modules/statefun-ridesharing-example
COPY statefun-ridesharing-example-functions/target/statefun-ridesharing-example*jar /opt/statefun/modules/statefun-ridesharing-example/
diff --git a/statefun-examples/statefun-shopping-cart-example/Dockerfile b/statefun-examples/statefun-shopping-cart-example/Dockerfile
index 3c45b28..9f7a52c 100644
--- a/statefun-examples/statefun-shopping-cart-example/Dockerfile
+++ b/statefun-examples/statefun-shopping-cart-example/Dockerfile
@@ -13,7 +13,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:2.0-SNAPSHOT
RUN mkdir -p /opt/statefun/modules/statefun-shopping-cart-example
COPY target/statefun-shopping-cart-example*jar /opt/statefun/modules/statefun-shopping-cart-example/
[flink-statefun] 08/13: [FLINK-16838] Let Dockerfile in quickstart
point to a specific image version tag
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit c379227fbf32ecd5142ae92538b0e8ae6ae6177e
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 14:04:27 2020 +0800
[FLINK-16838] Let Dockerfile in quickstart point to a specific image version tag
With this change, the quickstart archetype now always uses a specific
image version.
If the archetype is a released artifact, then the version tag used will
be x.y.z, e.g. 2.0.0. Images in this case should be available in the
Docker Hub registry.
Otherwise, if the archetype is a snapshot distribution built from
development branches, then the version tag used wil be snapshot
versions, e.g. 2.1-SNAPSHOT. In this case, you would have to locally
build the image from the corresponding source version.
---
statefun-quickstart/src/main/resources/archetype-resources/Dockerfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/statefun-quickstart/src/main/resources/archetype-resources/Dockerfile b/statefun-quickstart/src/main/resources/archetype-resources/Dockerfile
index aef83ec..966c302 100644
--- a/statefun-quickstart/src/main/resources/archetype-resources/Dockerfile
+++ b/statefun-quickstart/src/main/resources/archetype-resources/Dockerfile
@@ -13,7 +13,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM statefun
+FROM flink-statefun:@project.version@
RUN mkdir -p /opt/statefun/modules/${artifactId}
COPY target/${artifactId}*jar /opt/statefun/modules/${artifactId}/
[flink-statefun] 10/13: [FLINK-16838] Update image name in docs and
README.
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit bc3c4246440ac19aed69377ccdf330a0a242799d
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 14:28:43 2020 +0800
[FLINK-16838] Update image name in docs and README.
---
README.md | 2 +-
docs/deployment-and-operations/packaging.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 02a09c3..2d9e166 100755
--- a/README.md
+++ b/README.md
@@ -184,7 +184,7 @@ submitted to a Flink cluster.
Below is an example Dockerfile for building an image for an application called `statefun-example`:
```
-FROM statefun
+FROM flink-statefun[:version-tag]
RUN mkdir -p /opt/statefun/modules/statefun-example
COPY target/statefun-example*jar /opt/statefun/modules/statefun-example/
diff --git a/docs/deployment-and-operations/packaging.md b/docs/deployment-and-operations/packaging.md
index 5507666..e6a11c4 100644
--- a/docs/deployment-and-operations/packaging.md
+++ b/docs/deployment-and-operations/packaging.md
@@ -38,7 +38,7 @@ The provided base image allows teams to package their applications with all the
Below is an example Dockerfile for building a Stateful Functions image with both an [embedded module]({{ site.baseurl }}/sdk/modules.html#embedded-module) and a [remote module]({{ site.baseurl }}/sdk/modules.html#remote-module) for an application called ``statefun-example``.
{% highlight dockerfile %}
-FROM statefun
+FROM flink-statefun:{{ site.version }}
RUN mkdir -p /opt/statefun/modules/statefun-example
RUN mkdir -p /opt/statefun/modules/remote
[flink-statefun] 04/13: [FLINK-16842] Use maven-shade-plugin to
package ridesharing example simulator
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 767e428354c70a7a473c644dc833a5696462d19e
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 21:42:05 2020 +0800
[FLINK-16842] Use maven-shade-plugin to package ridesharing example simulator
We need to use the maven-shade-plugin instead of the
spring-boot-maven-plugin for packaging, since we need to add our own
transformers that merges Apache release NOTICE files.
---
.../Dockerfile | 2 +-
.../statefun-ridesharing-example-simulator/pom.xml | 43 ++++++++++++++++++++--
2 files changed, 41 insertions(+), 4 deletions(-)
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/Dockerfile b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/Dockerfile
index 12973cb..c8066d9 100644
--- a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/Dockerfile
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/Dockerfile
@@ -22,7 +22,7 @@ VOLUME /tmp
# Make port 5656 available to the world outside this container
EXPOSE 5656
-ADD target/*-simulator-*.jar simulator.jar
+ADD target/statefun-ridesharing-example-simulator-*.jar simulator.jar
ADD application.yaml application.yaml
# Run the jar file
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml
index c312108..97d8daa 100644
--- a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml
@@ -119,16 +119,53 @@ under the License.
<build>
<plugins>
<plugin>
- <groupId>org.springframework.boot</groupId>
- <artifactId>spring-boot-maven-plugin</artifactId>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-shade-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
- <goal>repackage</goal>
+ <goal>shade</goal>
</goals>
+ <configuration>
+ <transformers>
+ <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
+ <resource>META-INF/spring.handlers</resource>
+ </transformer>
+ <transformer implementation="org.springframework.boot.maven.PropertiesMergingResourceTransformer">
+ <resource>META-INF/spring.factories</resource>
+ </transformer>
+ <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
+ <resource>META-INF/spring.schemas</resource>
+ </transformer>
+ <transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
+ <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
+ <mainClass>org.apache.flink.statefun.examples.ridesharing.simulator.Main</mainClass>
+ </transformer>
+ </transformers>
+ </configuration>
</execution>
</executions>
+ <dependencies>
+ <dependency>
+ <groupId>org.springframework.boot</groupId>
+ <artifactId>spring-boot-maven-plugin</artifactId>
+ <version>2.1.6.RELEASE</version>
+ </dependency>
+ </dependencies>
+ <configuration>
+ <createDependencyReducedPom>false</createDependencyReducedPom>
+ <filters>
+ <filter>
+ <artifact>*:*</artifact>
+ <excludes>
+ <exclude>META-INF/*.SF</exclude>
+ <exclude>META-INF/*.DSA</exclude>
+ <exclude>META-INF/*.RSA</exclude>
+ </excludes>
+ </filter>
+ </filters>
+ </configuration>
</plugin>
</plugins>
</build>
[flink-statefun] 05/13: [FLINK-16842] Add NOTICE and licenses for
statefun-ridesharing-example-simulator
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 9ac2d38c3a6bcf2f91fd154f2591107a0f1fa3fb
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 22:50:02 2020 +0800
[FLINK-16842] Add NOTICE and licenses for statefun-ridesharing-example-simulator
---
.../statefun-ridesharing-example-simulator/pom.xml | 5 +
.../src/main/resources/META-INF/NOTICE | 82 +++
.../licenses/LICENSE.animal-sniffer-annotations | 19 +
.../META-INF/licenses/LICENSE.checker-qual | 22 +
.../META-INF/licenses/LICENSE.javax.annotation-api | 759 +++++++++++++++++++++
.../META-INF/licenses/LICENSE.jul-to-slf4j | 21 +
.../META-INF/licenses/LICENSE.logback-classic | 24 +
.../META-INF/licenses/LICENSE.logback-core | 24 +
.../META-INF/licenses/LICENSE.protobuf-java | 32 +
.../resources/META-INF/licenses/LICENSE.slf4j-api | 21 +
.../META-INF/licenses/LICENSE.sockjs-client | 21 +
11 files changed, 1030 insertions(+)
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml
index 97d8daa..d561a87 100644
--- a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/pom.xml
@@ -142,6 +142,11 @@ under the License.
<transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
<mainClass>org.apache.flink.statefun.examples.ridesharing.simulator.Main</mainClass>
</transformer>
+ <transformer
+ implementation="org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer">
+ <projectName>Apache Flink Stateful Functions (flink-statefun)</projectName>
+ <encoding>UTF-8</encoding>
+ </transformer>
</transformers>
</configuration>
</execution>
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/NOTICE b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/NOTICE
new file mode 100644
index 0000000..5dee0e1
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/NOTICE
@@ -0,0 +1,82 @@
+statefun-ridesharing-example-simulator
+Copyright 2014-2020 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+This project bundles the following dependencies under the Apache Software License 2.0 (http://www.apache.org/licenses/LICENSE-2.0.txt)
+
+- org.springframework.boot:spring-boot:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-autoconfigure:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-starter-web:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-starter:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-starter-logging:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-starter-json:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-starter-tomcat:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-starter-websocket:2.1.6.RELEASE
+- org.springframework.boot:spring-boot-devtools:2.1.6.RELEASE
+- org.springframework:spring-web:5.1.8.RELEASE
+- org.springframework:spring-beans:5.1.8.RELEASE
+- org.springframework:spring-webmvc:5.1.8.RELEASE
+- org.springframework:spring-aop:5.1.8.RELEASE
+- org.springframework:spring-expression:5.1.8.RELEASE
+- org.springframework:spring-messaging:5.1.8.RELEASE
+- org.springframework:spring-websocket:5.1.8.RELEASE
+- org.springframework:spring-context:5.1.8.RELEASE
+- org.springframework:spring-tx:5.1.8.RELEASE
+- org.springframework:spring-core:5.1.8.RELEASE
+- org.springframework:spring-jcl:5.1.8.RELEASE
+- org.springframework.kafka:spring-kafka:2.2.7.RELEASE
+- org.springframework.retry:spring-retry:1.2.4.RELEASE
+- org.apache.tomcat.embed:tomcat-embed-core:9.0.21
+- org.apache.tomcat.embed:tomcat-embed-el:9.0.21
+- org.apache.tomcat.embed:tomcat-embed-websocket:9.0.21
+- org.apache.logging.log4j:log4j-to-slf4j:2.11.2
+- org.apache.logging.log4j:log4j-api:2.11.2
+- org.yaml:snakeyaml:1.23
+- com.fasterxml.jackson.core:jackson-databind:2.9.9
+- com.fasterxml.jackson.core:jackson-annotations:2.9.0
+- com.fasterxml.jackson.core:jackson-core:2.9.9
+- com.fasterxml.jackson.datatype:jackson-datatype-jdk8:2.9.9
+- com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.9.9
+- com.fasterxml.jackson.module:jackson-module-parameter-names:2.9.9
+- com.fasterxml:classmate:1.4.0
+- org.hibernate.validator:hibernate-validator:6.0.17
+- javax.validation:validation-api:2.0.1.Final
+- org.jboss.logging:jboss-logging:3.3.2
+- org.apache.kafka:kafka-clients:2.0.1
+- org.lz4:lz4-java:1.4.1
+- org.xerial.snappy:snappy-java:1.1.7.1
+- org.webjars:stomp-websocket:2.3.3
+- com.google.guava:guava:28.0-jre
+- com.google.guava:failureaccess:1.0.1
+- com.google.guava:listenablefuture:9999.0-empty-to-avoid-conflict-with-guava
+- com.google.code.findbugs:jsr305:3.0.2:compile
+- com.google.errorprone:error_prone_annotations:2.3.2
+- com.google.j2objc:j2objc-annotations:1.3
+- com.google.auto.service:auto-service-annotations:1.0-rc6
+
+This project bundles the following dependencies under the MIT license.
+See bundled license files under "META-INF/licenses" for details.
+
+- org.slf4j:jul-to-slf4j:1.7.26
+- org.webjars:sockjs-client:1.0.2
+- org.checkerframework:checker-qual:2.8.1
+- org.codehaus.mojo:animal-sniffer-annotations:1.17
+- org.slf4j:slf4j-api:1.7.26
+
+This project bundles the following dependencies under the BSD license.
+See bundled license files under "META-INF/licenses" for details.
+
+- com.google.protobuf:protobuf-java:3.8.0
+
+This project bundles the following dependencies under the CDDL license.
+See bundled license files under "META-INF/licenses" for details.
+
+- javax.annotation:javax.annotation-api:1.3.2
+
+This project bundles the following dependencies under the EPL license.
+See bundled license files under "META-INF/licenses" for details.
+
+- ch.qos.logback:logback-classic:1.2.3
+- ch.qos.logback:logback-core:1.2.3
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.animal-sniffer-annotations b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.animal-sniffer-annotations
new file mode 100644
index 0000000..7f197e9
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.animal-sniffer-annotations
@@ -0,0 +1,19 @@
+MIT License:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.checker-qual b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.checker-qual
new file mode 100644
index 0000000..9837c6b
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.checker-qual
@@ -0,0 +1,22 @@
+Checker Framework qualifiers
+Copyright 2004-present by the Checker Framework developers
+
+MIT License:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.javax.annotation-api b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.javax.annotation-api
new file mode 100644
index 0000000..b1c74f9
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.javax.annotation-api
@@ -0,0 +1,759 @@
+COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.1
+
+1. Definitions.
+
+ 1.1. "Contributor" means each individual or entity that creates or
+ contributes to the creation of Modifications.
+
+ 1.2. "Contributor Version" means the combination of the Original
+ Software, prior Modifications used by a Contributor (if any), and
+ the Modifications made by that particular Contributor.
+
+ 1.3. "Covered Software" means (a) the Original Software, or (b)
+ Modifications, or (c) the combination of files containing Original
+ Software with files containing Modifications, in each case including
+ portions thereof.
+
+ 1.4. "Executable" means the Covered Software in any form other than
+ Source Code.
+
+ 1.5. "Initial Developer" means the individual or entity that first
+ makes Original Software available under this License.
+
+ 1.6. "Larger Work" means a work which combines Covered Software or
+ portions thereof with code not governed by the terms of this License.
+
+ 1.7. "License" means this document.
+
+ 1.8. "Licensable" means having the right to grant, to the maximum
+ extent possible, whether at the time of the initial grant or
+ subsequently acquired, any and all of the rights conveyed herein.
+
+ 1.9. "Modifications" means the Source Code and Executable form of
+ any of the following:
+
+ A. Any file that results from an addition to, deletion from or
+ modification of the contents of a file containing Original Software
+ or previous Modifications;
+
+ B. Any new file that contains any part of the Original Software or
+ previous Modification; or
+
+ C. Any new file that is contributed or otherwise made available
+ under the terms of this License.
+
+ 1.10. "Original Software" means the Source Code and Executable form
+ of computer software code that is originally released under this
+ License.
+
+ 1.11. "Patent Claims" means any patent claim(s), now owned or
+ hereafter acquired, including without limitation, method, process,
+ and apparatus claims, in any patent Licensable by grantor.
+
+ 1.12. "Source Code" means (a) the common form of computer software
+ code in which modifications are made and (b) associated
+ documentation included in or with such code.
+
+ 1.13. "You" (or "Your") means an individual or a legal entity
+ exercising rights under, and complying with all of the terms of,
+ this License. For legal entities, "You" includes any entity which
+ controls, is controlled by, or is under common control with You. For
+ purposes of this definition, "control" means (a) the power, direct
+ or indirect, to cause the direction or management of such entity,
+ whether by contract or otherwise, or (b) ownership of more than
+ fifty percent (50%) of the outstanding shares or beneficial
+ ownership of such entity.
+
+2. License Grants.
+
+ 2.1. The Initial Developer Grant.
+
+ Conditioned upon Your compliance with Section 3.1 below and subject
+ to third party intellectual property claims, the Initial Developer
+ hereby grants You a world-wide, royalty-free, non-exclusive license:
+
+ (a) under intellectual property rights (other than patent or
+ trademark) Licensable by Initial Developer, to use, reproduce,
+ modify, display, perform, sublicense and distribute the Original
+ Software (or portions thereof), with or without Modifications,
+ and/or as part of a Larger Work; and
+
+ (b) under Patent Claims infringed by the making, using or selling of
+ Original Software, to make, have made, use, practice, sell, and
+ offer for sale, and/or otherwise dispose of the Original Software
+ (or portions thereof).
+
+ (c) The licenses granted in Sections 2.1(a) and (b) are effective on
+ the date Initial Developer first distributes or otherwise makes the
+ Original Software available to a third party under the terms of this
+ License.
+
+ (d) Notwithstanding Section 2.1(b) above, no patent license is
+ granted: (1) for code that You delete from the Original Software, or
+ (2) for infringements caused by: (i) the modification of the
+ Original Software, or (ii) the combination of the Original Software
+ with other software or devices.
+
+ 2.2. Contributor Grant.
+
+ Conditioned upon Your compliance with Section 3.1 below and subject
+ to third party intellectual property claims, each Contributor hereby
+ grants You a world-wide, royalty-free, non-exclusive license:
+
+ (a) under intellectual property rights (other than patent or
+ trademark) Licensable by Contributor to use, reproduce, modify,
+ display, perform, sublicense and distribute the Modifications
+ created by such Contributor (or portions thereof), either on an
+ unmodified basis, with other Modifications, as Covered Software
+ and/or as part of a Larger Work; and
+
+ (b) under Patent Claims infringed by the making, using, or selling
+ of Modifications made by that Contributor either alone and/or in
+ combination with its Contributor Version (or portions of such
+ combination), to make, use, sell, offer for sale, have made, and/or
+ otherwise dispose of: (1) Modifications made by that Contributor (or
+ portions thereof); and (2) the combination of Modifications made by
+ that Contributor with its Contributor Version (or portions of such
+ combination).
+
+ (c) The licenses granted in Sections 2.2(a) and 2.2(b) are effective
+ on the date Contributor first distributes or otherwise makes the
+ Modifications available to a third party.
+
+ (d) Notwithstanding Section 2.2(b) above, no patent license is
+ granted: (1) for any code that Contributor has deleted from the
+ Contributor Version; (2) for infringements caused by: (i) third
+ party modifications of Contributor Version, or (ii) the combination
+ of Modifications made by that Contributor with other software
+ (except as part of the Contributor Version) or other devices; or (3)
+ under Patent Claims infringed by Covered Software in the absence of
+ Modifications made by that Contributor.
+
+3. Distribution Obligations.
+
+ 3.1. Availability of Source Code.
+
+ Any Covered Software that You distribute or otherwise make available
+ in Executable form must also be made available in Source Code form
+ and that Source Code form must be distributed only under the terms
+ of this License. You must include a copy of this License with every
+ copy of the Source Code form of the Covered Software You distribute
+ or otherwise make available. You must inform recipients of any such
+ Covered Software in Executable form as to how they can obtain such
+ Covered Software in Source Code form in a reasonable manner on or
+ through a medium customarily used for software exchange.
+
+ 3.2. Modifications.
+
+ The Modifications that You create or to which You contribute are
+ governed by the terms of this License. You represent that You
+ believe Your Modifications are Your original creation(s) and/or You
+ have sufficient rights to grant the rights conveyed by this License.
+
+ 3.3. Required Notices.
+
+ You must include a notice in each of Your Modifications that
+ identifies You as the Contributor of the Modification. You may not
+ remove or alter any copyright, patent or trademark notices contained
+ within the Covered Software, or any notices of licensing or any
+ descriptive text giving attribution to any Contributor or the
+ Initial Developer.
+
+ 3.4. Application of Additional Terms.
+
+ You may not offer or impose any terms on any Covered Software in
+ Source Code form that alters or restricts the applicable version of
+ this License or the recipients' rights hereunder. You may choose to
+ offer, and to charge a fee for, warranty, support, indemnity or
+ liability obligations to one or more recipients of Covered Software.
+ However, you may do so only on Your own behalf, and not on behalf of
+ the Initial Developer or any Contributor. You must make it
+ absolutely clear that any such warranty, support, indemnity or
+ liability obligation is offered by You alone, and You hereby agree
+ to indemnify the Initial Developer and every Contributor for any
+ liability incurred by the Initial Developer or such Contributor as a
+ result of warranty, support, indemnity or liability terms You offer.
+
+ 3.5. Distribution of Executable Versions.
+
+ You may distribute the Executable form of the Covered Software under
+ the terms of this License or under the terms of a license of Your
+ choice, which may contain terms different from this License,
+ provided that You are in compliance with the terms of this License
+ and that the license for the Executable form does not attempt to
+ limit or alter the recipient's rights in the Source Code form from
+ the rights set forth in this License. If You distribute the Covered
+ Software in Executable form under a different license, You must make
+ it absolutely clear that any terms which differ from this License
+ are offered by You alone, not by the Initial Developer or
+ Contributor. You hereby agree to indemnify the Initial Developer and
+ every Contributor for any liability incurred by the Initial
+ Developer or such Contributor as a result of any such terms You offer.
+
+ 3.6. Larger Works.
+
+ You may create a Larger Work by combining Covered Software with
+ other code not governed by the terms of this License and distribute
+ the Larger Work as a single product. In such a case, You must make
+ sure the requirements of this License are fulfilled for the Covered
+ Software.
+
+4. Versions of the License.
+
+ 4.1. New Versions.
+
+ Oracle is the initial license steward and may publish revised and/or
+ new versions of this License from time to time. Each version will be
+ given a distinguishing version number. Except as provided in Section
+ 4.3, no one other than the license steward has the right to modify
+ this License.
+
+ 4.2. Effect of New Versions.
+
+ You may always continue to use, distribute or otherwise make the
+ Covered Software available under the terms of the version of the
+ License under which You originally received the Covered Software. If
+ the Initial Developer includes a notice in the Original Software
+ prohibiting it from being distributed or otherwise made available
+ under any subsequent version of the License, You must distribute and
+ make the Covered Software available under the terms of the version
+ of the License under which You originally received the Covered
+ Software. Otherwise, You may also choose to use, distribute or
+ otherwise make the Covered Software available under the terms of any
+ subsequent version of the License published by the license steward.
+
+ 4.3. Modified Versions.
+
+ When You are an Initial Developer and You want to create a new
+ license for Your Original Software, You may create and use a
+ modified version of this License if You: (a) rename the license and
+ remove any references to the name of the license steward (except to
+ note that the license differs from this License); and (b) otherwise
+ make it clear that the license contains terms which differ from this
+ License.
+
+5. DISCLAIMER OF WARRANTY.
+
+ COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS,
+ WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
+ INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE
+ IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR
+ NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF
+ THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE
+ DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY
+ OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING,
+ REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN
+ ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS
+ AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
+
+6. TERMINATION.
+
+ 6.1. This License and the rights granted hereunder will terminate
+ automatically if You fail to comply with terms herein and fail to
+ cure such breach within 30 days of becoming aware of the breach.
+ Provisions which, by their nature, must remain in effect beyond the
+ termination of this License shall survive.
+
+ 6.2. If You assert a patent infringement claim (excluding
+ declaratory judgment actions) against Initial Developer or a
+ Contributor (the Initial Developer or Contributor against whom You
+ assert such claim is referred to as "Participant") alleging that the
+ Participant Software (meaning the Contributor Version where the
+ Participant is a Contributor or the Original Software where the
+ Participant is the Initial Developer) directly or indirectly
+ infringes any patent, then any and all rights granted directly or
+ indirectly to You by such Participant, the Initial Developer (if the
+ Initial Developer is not the Participant) and all Contributors under
+ Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice
+ from Participant terminate prospectively and automatically at the
+ expiration of such 60 day notice period, unless if within such 60
+ day period You withdraw Your claim with respect to the Participant
+ Software against such Participant either unilaterally or pursuant to
+ a written agreement with Participant.
+
+ 6.3. If You assert a patent infringement claim against Participant
+ alleging that the Participant Software directly or indirectly
+ infringes any patent where such claim is resolved (such as by
+ license or settlement) prior to the initiation of patent
+ infringement litigation, then the reasonable value of the licenses
+ granted by such Participant under Sections 2.1 or 2.2 shall be taken
+ into account in determining the amount or value of any payment or
+ license.
+
+ 6.4. In the event of termination under Sections 6.1 or 6.2 above,
+ all end user licenses that have been validly granted by You or any
+ distributor hereunder prior to termination (excluding licenses
+ granted to You by any distributor) shall survive termination.
+
+7. LIMITATION OF LIABILITY.
+
+ UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
+ (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE
+ INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF
+ COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE
+ TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR
+ CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT
+ LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER
+ FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR
+ LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE
+ POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT
+ APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH
+ PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH
+ LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
+ LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION
+ AND LIMITATION MAY NOT APPLY TO YOU.
+
+8. U.S. GOVERNMENT END USERS.
+
+ The Covered Software is a "commercial item," as that term is defined
+ in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer
+ software" (as that term is defined at 48 C.F.R. §
+ 252.227-7014(a)(1)) and "commercial computer software documentation"
+ as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent
+ with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4
+ (June 1995), all U.S. Government End Users acquire Covered Software
+ with only those rights set forth herein. This U.S. Government Rights
+ clause is in lieu of, and supersedes, any other FAR, DFAR, or other
+ clause or provision that addresses Government rights in computer
+ software under this License.
+
+9. MISCELLANEOUS.
+
+ This License represents the complete agreement concerning subject
+ matter hereof. If any provision of this License is held to be
+ unenforceable, such provision shall be reformed only to the extent
+ necessary to make it enforceable. This License shall be governed by
+ the law of the jurisdiction specified in a notice contained within
+ the Original Software (except to the extent applicable law, if any,
+ provides otherwise), excluding such jurisdiction's conflict-of-law
+ provisions. Any litigation relating to this License shall be subject
+ to the jurisdiction of the courts located in the jurisdiction and
+ venue specified in a notice contained within the Original Software,
+ with the losing party responsible for costs, including, without
+ limitation, court costs and reasonable attorneys' fees and expenses.
+ The application of the United Nations Convention on Contracts for
+ the International Sale of Goods is expressly excluded. Any law or
+ regulation which provides that the language of a contract shall be
+ construed against the drafter shall not apply to this License. You
+ agree that You alone are responsible for compliance with the United
+ States export administration regulations (and the export control
+ laws and regulation of any other countries) when You use, distribute
+ or otherwise make available any Covered Software.
+
+10. RESPONSIBILITY FOR CLAIMS.
+
+ As between Initial Developer and the Contributors, each party is
+ responsible for claims and damages arising, directly or indirectly,
+ out of its utilization of rights under this License and You agree to
+ work with Initial Developer and Contributors to distribute such
+ responsibility on an equitable basis. Nothing herein is intended or
+ shall be deemed to constitute any admission of liability.
+
+------------------------------------------------------------------------
+
+NOTICE PURSUANT TO SECTION 9 OF THE COMMON DEVELOPMENT AND DISTRIBUTION
+LICENSE (CDDL)
+
+The code released under the CDDL shall be governed by the laws of the
+State of California (excluding conflict-of-law provisions). Any
+litigation relating to this License shall be subject to the jurisdiction
+of the Federal Courts of the Northern District of California and the
+state courts of the State of California, with venue lying in Santa Clara
+County, California.
+
+
+
+ The GNU General Public License (GPL) Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor
+Boston, MA 02110-1335
+USA
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
+
+Preamble
+
+The licenses for most software are designed to take away your freedom to
+share and change it. By contrast, the GNU General Public License is
+intended to guarantee your freedom to share and change free software--to
+make sure the software is free for all its users. This General Public
+License applies to most of the Free Software Foundation's software and
+to any other program whose authors commit to using it. (Some other Free
+Software Foundation software is covered by the GNU Library General
+Public License instead.) You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price.
+Our General Public Licenses are designed to make sure that you have the
+freedom to distribute copies of free software (and charge for this
+service if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid anyone
+to deny you these rights or to ask you to surrender the rights. These
+restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+For example, if you distribute copies of such a program, whether gratis
+or for a fee, you must give the recipients all the rights that you have.
+You must make sure that they, too, receive or can get the source code.
+And you must show them these terms so they know their rights.
+
+We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+Finally, any free program is threatened constantly by software patents.
+We wish to avoid the danger that redistributors of a free program will
+individually obtain patent licenses, in effect making the program
+proprietary. To prevent this, we have made it clear that any patent must
+be licensed for everyone's free use or not licensed at all.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License applies to any program or other work which contains a
+notice placed by the copyright holder saying it may be distributed under
+the terms of this General Public License. The "Program", below, refers
+to any such program or work, and a "work based on the Program" means
+either the Program or any derivative work under copyright law: that is
+to say, a work containing the Program or a portion of it, either
+verbatim or with modifications and/or translated into another language.
+(Hereinafter, translation is included without limitation in the term
+"modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of running
+the Program is not restricted, and the output from the Program is
+covered only if its contents constitute a work based on the Program
+(independent of having been made by running the Program). Whether that
+is true depends on what the Program does.
+
+1. You may copy and distribute verbatim copies of the Program's source
+code as you receive it, in any medium, provided that you conspicuously
+and appropriately publish on each copy an appropriate copyright notice
+and disclaimer of warranty; keep intact all the notices that refer to
+this License and to the absence of any warranty; and give any other
+recipients of the Program a copy of this License along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Program or any portion of
+it, thus forming a work based on the Program, and copy and distribute
+such modifications or work under the terms of Section 1 above, provided
+that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any part
+ thereof, to be licensed as a whole at no charge to all third parties
+ under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a notice
+ that there is no warranty (or else, saying that you provide a
+ warranty) and that users may redistribute the program under these
+ conditions, and telling the user how to view a copy of this License.
+ (Exception: if the Program itself is interactive but does not
+ normally print such an announcement, your work based on the Program
+ is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program, and
+can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based on
+the Program, the distribution of the whole must be on the terms of this
+License, whose permissions for other licensees extend to the entire
+whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of a
+storage or distribution medium does not bring the other work under the
+scope of this License.
+
+3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections 1
+ and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your cost
+ of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer to
+ distribute corresponding source code. (This alternative is allowed
+ only for noncommercial distribution and only if you received the
+ program in object code or executable form with such an offer, in
+ accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source code
+means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to control
+compilation and installation of the executable. However, as a special
+exception, the source code distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies the
+executable.
+
+If distribution of executable or object code is made by offering access
+to copy from a designated place, then offering equivalent access to copy
+the source code from the same place counts as distribution of the source
+code, even though third parties are not compelled to copy the source
+along with the object code.
+
+4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt otherwise
+to copy, modify, sublicense or distribute the Program is void, and will
+automatically terminate your rights under this License. However, parties
+who have received copies, or rights, from you under this License will
+not have their licenses terminated so long as such parties remain in
+full compliance.
+
+5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and all
+its terms and conditions for copying, distributing or modifying the
+Program or works based on it.
+
+6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further restrictions
+on the recipients' exercise of the rights granted herein. You are not
+responsible for enforcing compliance by third parties to this License.
+
+7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot distribute
+so as to satisfy simultaneously your obligations under this License and
+any other pertinent obligations, then as a consequence you may not
+distribute the Program at all. For example, if a patent license would
+not permit royalty-free redistribution of the Program by all those who
+receive copies directly or indirectly through you, then the only way you
+could satisfy both it and this License would be to refrain entirely from
+distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is implemented
+by public license practices. Many people have made generous
+contributions to the wide range of software distributed through that
+system in reliance on consistent application of that system; it is up to
+the author/donor to decide if he or she is willing to distribute
+software through any other system and a licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be
+a consequence of the rest of this License.
+
+8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License may
+add an explicit geographical distribution limitation excluding those
+countries, so that distribution is permitted only in or among countries
+not thus excluded. In such case, this License incorporates the
+limitation as if written in the body of this License.
+
+9. The Free Software Foundation may publish revised and/or new
+versions of the General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Program does not specify a version
+number of this License, you may choose any version ever published by the
+Free Software Foundation.
+
+10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the
+author to ask for permission. For software which is copyrighted by the
+Free Software Foundation, write to the Free Software Foundation; we
+sometimes make exceptions for this. Our decision will be guided by the
+two goals of preserving the free status of all derivatives of our free
+software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND,
+EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
+ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
+YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
+NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
+DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
+DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM
+(INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
+INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
+THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR
+OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest to
+attach them to the start of each source file to most effectively convey
+the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ One line to give the program's name and a brief idea of what it does.
+ Copyright (C) <year> <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1335 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type
+ `show w'. This is free software, and you are welcome to redistribute
+ it under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the
+appropriate parts of the General Public License. Of course, the commands
+you use may be called something other than `show w' and `show c'; they
+could even be mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ program `Gnomovision' (which makes passes at compilers) written by
+ James Hacker.
+
+ signature of Ty Coon, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications
+with the library. If this is what you want to do, use the GNU Library
+General Public License instead of this License.
+
+#
+
+Certain source files distributed by Oracle America, Inc. and/or its
+affiliates are subject to the following clarification and special
+exception to the GPLv2, based on the GNU Project exception for its
+Classpath libraries, known as the GNU Classpath Exception, but only
+where Oracle has expressly included in the particular source file's
+header the words "Oracle designates this particular file as subject to
+the "Classpath" exception as provided by Oracle in the LICENSE file
+that accompanied this code."
+
+You should also note that Oracle includes multiple, independent
+programs in this software package. Some of those programs are provided
+under licenses deemed incompatible with the GPLv2 by the Free Software
+Foundation and others. For example, the package includes programs
+licensed under the Apache License, Version 2.0. Such programs are
+licensed to you under their original licenses.
+
+Oracle facilitates your further distribution of this package by adding
+the Classpath Exception to the necessary parts of its GPLv2 code, which
+permits you to use that code in combination with other independent
+modules not licensed under the GPLv2. However, note that this would
+not permit you to commingle code under an incompatible license with
+Oracle's GPLv2 licensed code by, for example, cutting and pasting such
+code into a file also containing Oracle's GPLv2 licensed code and then
+distributing the result. Additionally, if you were to remove the
+Classpath Exception from any of the files to which it applies and
+distribute the result, you would likely be required to license some or
+all of the other code in that distribution under the GPLv2 as well, and
+since the GPLv2 is incompatible with the license terms of some items
+included in the distribution by Oracle, removing the Classpath
+Exception could therefore effectively compromise your ability to
+further distribute the package.
+
+Proceed with caution and we recommend that you obtain the advice of a
+lawyer skilled in open source matters before removing the Classpath
+Exception or making modifications to this package which may
+subsequently be redistributed and/or involve the use of third party
+software.
+
+CLASSPATH EXCEPTION
+Linking this library statically or dynamically with other modules is
+making a combined work based on this library. Thus, the terms and
+conditions of the GNU General Public License version 2 cover the whole
+combination.
+
+As a special exception, the copyright holders of this library give you
+permission to link this library with independent modules to produce an
+executable, regardless of the license terms of these independent
+modules, and to copy and distribute the resulting executable under
+terms of your choice, provided that you also meet, for each linked
+independent module, the terms and conditions of the license of that
+module. An independent module is a module which is not derived from or
+based on this library. If you modify this library, you may extend this
+exception to your version of the library, but you are not obligated to
+do so. If you do not wish to do so, delete this exception statement
+from your version.
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.jul-to-slf4j b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.jul-to-slf4j
new file mode 100644
index 0000000..744377c
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.jul-to-slf4j
@@ -0,0 +1,21 @@
+Copyright (c) 2004-2017 QOS.ch
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-classic b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-classic
new file mode 100644
index 0000000..44f8eb8
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-classic
@@ -0,0 +1,24 @@
+Logback License
+As of release 0.9.18, logback source code and binaries are dual-licensed under the EPL v1.0 and the LGPL 2.1, or more formally:
+
+Logback: the reliable, generic, fast and flexible logging framework.
+Copyright (C) 1999-2017, QOS.ch. All rights reserved.
+
+This program and the accompanying materials are dual-licensed under
+either the terms of the Eclipse Public License v1.0 as published by
+the Eclipse Foundation
+
+ or (per the licensee's choosing)
+
+under the terms of the GNU Lesser General Public License version 2.1
+as published by the Free Software Foundation.
+
+The EPL/LGPL dual-license serves several purposes. The LGPL license ensures continuity in terms of licensing of the logback project. Prior to version 0.9.18, logback was licensed (exclusively) under the LGPL v2.1. Moreover, since the EPL is deemed incompatible by the Free Software Foundation, the LGPL will allow various licensees, in particular software distributors who may be already bound by the terms of the GPL or the LGPL, to distribute our software.
+
+On the other hand, the EPL license will placate organizations which refuse certain restrictions imposed by the LGPL.
+
+Please note that logback-classic is intended to be used behind the SLF4J API, which is licensed under the MIT license.
+
+If you wish to make a significant contribution to the logback project, you are invited to file a Contributor License Agreement. The purpose of this agreement is to formalize the terms of your contribution and to protect the project in case of litigation.
+
+Upon request, we may exempt open-source projects from LGPL and EPL's reciprocity clauses so that the said projects can develop logback extensions under the license of their choice. Exemptions are granted on a case by case basis.
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-core b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-core
new file mode 100644
index 0000000..44f8eb8
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.logback-core
@@ -0,0 +1,24 @@
+Logback License
+As of release 0.9.18, logback source code and binaries are dual-licensed under the EPL v1.0 and the LGPL 2.1, or more formally:
+
+Logback: the reliable, generic, fast and flexible logging framework.
+Copyright (C) 1999-2017, QOS.ch. All rights reserved.
+
+This program and the accompanying materials are dual-licensed under
+either the terms of the Eclipse Public License v1.0 as published by
+the Eclipse Foundation
+
+ or (per the licensee's choosing)
+
+under the terms of the GNU Lesser General Public License version 2.1
+as published by the Free Software Foundation.
+
+The EPL/LGPL dual-license serves several purposes. The LGPL license ensures continuity in terms of licensing of the logback project. Prior to version 0.9.18, logback was licensed (exclusively) under the LGPL v2.1. Moreover, since the EPL is deemed incompatible by the Free Software Foundation, the LGPL will allow various licensees, in particular software distributors who may be already bound by the terms of the GPL or the LGPL, to distribute our software.
+
+On the other hand, the EPL license will placate organizations which refuse certain restrictions imposed by the LGPL.
+
+Please note that logback-classic is intended to be used behind the SLF4J API, which is licensed under the MIT license.
+
+If you wish to make a significant contribution to the logback project, you are invited to file a Contributor License Agreement. The purpose of this agreement is to formalize the terms of your contribution and to protect the project in case of litigation.
+
+Upon request, we may exempt open-source projects from LGPL and EPL's reciprocity clauses so that the said projects can develop logback extensions under the license of their choice. Exemptions are granted on a case by case basis.
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.protobuf-java b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.protobuf-java
new file mode 100644
index 0000000..97a6e3d
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.protobuf-java
@@ -0,0 +1,32 @@
+Copyright 2008 Google Inc. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+ * Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above
+copyright notice, this list of conditions and the following disclaimer
+in the documentation and/or other materials provided with the
+distribution.
+ * Neither the name of Google Inc. nor the names of its
+contributors may be used to endorse or promote products derived from
+this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Code generated by the Protocol Buffer compiler is owned by the owner
+of the input file used when generating it. This code is not
+standalone and requires a support library to be linked with it. This
+support library is itself covered by the above license.
\ No newline at end of file
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.slf4j-api b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.slf4j-api
new file mode 100644
index 0000000..744377c
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.slf4j-api
@@ -0,0 +1,21 @@
+Copyright (c) 2004-2017 QOS.ch
+All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.sockjs-client b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.sockjs-client
new file mode 100644
index 0000000..fe0c249
--- /dev/null
+++ b/statefun-examples/statefun-ridesharing-example/statefun-ridesharing-example-simulator/src/main/resources/META-INF/licenses/LICENSE.sockjs-client
@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2011-2018 The sockjs-client Authors.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
[flink-statefun] 11/13: [FLINK-16838] Update base image version tag
in update_branch_version.sh
Posted by tz...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tzulitai pushed a commit to branch release-2.0
in repository https://gitbox.apache.org/repos/asf/flink-statefun.git
commit 1a98294f6ba1713b11c43ac3eb534974439ae56d
Author: Tzu-Li (Gordon) Tai <tz...@apache.org>
AuthorDate: Sat Mar 28 14:47:14 2020 +0800
[FLINK-16838] Update base image version tag in update_branch_version.sh
This closes #78.
---
tools/docker/build-stateful-functions.sh | 4 ++++
tools/releasing/update_branch_version.sh | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/tools/docker/build-stateful-functions.sh b/tools/docker/build-stateful-functions.sh
index eef29d6..c3942fb 100755
--- a/tools/docker/build-stateful-functions.sh
+++ b/tools/docker/build-stateful-functions.sh
@@ -17,6 +17,10 @@
set -e
+#
+# Do not change the name of this variable;
+# it is referenced in the tools/releasing/update_branch_version.sh script
+#
VERSION_TAG=2.0-SNAPSHOT
#
diff --git a/tools/releasing/update_branch_version.sh b/tools/releasing/update_branch_version.sh
index 95cf897..26552b2 100755
--- a/tools/releasing/update_branch_version.sh
+++ b/tools/releasing/update_branch_version.sh
@@ -73,6 +73,10 @@ perl -pi -e "s#version: $OLD_VERSION#version: $NEW_VERSION#" tools/k8s/Chart.yam
perl -pi -e "s#version: \"$OLD_VERSION\"#version: \"$NEW_VERSION\"#" docs/_config.yml
perl -pi -e "s#version_title: \"$OLD_VERSION\"#version_title: \"$NEW_VERSION\"#" docs/_config.yml
+# change Stateful Functions image version tags in all Dockerfiles and image build script
+find . -name 'Dockerfile*' -type f -exec perl -pi -e "s#FROM flink-statefun:$OLD_VERSION#FROM flink-statefun:$NEW_VERSION#" {} \;
+perl -pi -e "s#VERSION_TAG=$OLD_VERSION#VERSION_TAG=$NEW_VERSION#" tools/docker/build-stateful-functions.sh
+
git commit -am "[release] Update version to ${NEW_VERSION}"
NEW_VERSION_COMMIT_HASH=`git rev-parse HEAD`