spring-cloud-stream-samples

Files

Spring Operator de71d4bffd URL Cleanup

This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).

# Fixed URLs

## Fixed But Review Recommended
These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended.

* http://packages.confluent.io/maven/ (404) migrated to:
  https://packages.confluent.io/maven/ ([https](https://packages.confluent.io/maven/) result 404).

## Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

* http://www.apache.org/licenses/LICENSE-2.0 migrated to:
  https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200).
* http://repo.spring.io/libs-milestone-local migrated to:
  https://repo.spring.io/libs-milestone-local ([https](https://repo.spring.io/libs-milestone-local) result 302).
* http://repo.spring.io/libs-release-local migrated to:
  https://repo.spring.io/libs-release-local ([https](https://repo.spring.io/libs-release-local) result 302).
* http://repo.spring.io/libs-snapshot-local migrated to:
  https://repo.spring.io/libs-snapshot-local ([https](https://repo.spring.io/libs-snapshot-local) result 302).
* http://repo.spring.io/release migrated to:
  https://repo.spring.io/release ([https](https://repo.spring.io/release) result 302).

# Ignored
These URLs were intentionally ignored.

* http://maven.apache.org/POM/4.0.0
* http://maven.apache.org/xsd/maven-4.0.0.xsd
* http://www.w3.org/2001/XMLSchema-instance

2019-03-21 15:21:19 -04:00

.mvn/wrapper

Refactoring samples

2018-03-09 10:47:22 -05:00

src

URL Cleanup

2019-03-21 15:19:36 -04:00

.gitignore

Refactoring samples

2018-03-09 10:47:22 -05:00

docker-compose.yml

Refactoring samples

2018-03-09 10:47:22 -05:00

mvnw

URL Cleanup

2019-03-21 15:21:19 -04:00

mvnw.cmd

URL Cleanup

2019-03-21 15:21:19 -04:00

pom.xml

URL Cleanup

2019-03-21 15:19:50 -04:00

README.adoc

Update interactive query sample

2018-06-08 15:36:27 -04:00

README.adoc

== What is this app?

This is an example of a Spring Cloud Stream processor using Kafka Streams support.

This example is a Spring Cloud Stream adaptation of this Kafka Streams sample: https://github.com/confluentinc/kafka-streams-examples/tree/4.0.0-post/src/main/java/io/confluent/examples/streams/interactivequeries/kafkamusic

This sample demonstrates the concept of interactive queries in kafka streams.
There is a REST service provided as part of the application that can be used to query the store interactively.

=== Running the app:

We will run 2 instances of the processor application to demonstrate that regardless of which instance hosts the keys, the REST endpoint will serve the requests.
For more information on how this is done, please take a look at the application code.

1. `docker-compose up -d`

2. Start the confluent schema registry: The following command is based on the confluent platform and assume that you are at the root of the confluent platform's root directory.

`./bin/schema-registry-start ./etc/schema-registry/schema-registry.properties`

3. Go to the root of the repository and do: `./mvnw clean package`

4. `java -jar target/kafka-streams-interactive-query-advanced-0.0.1-SNAPSHOT.jar`

5. On another terminal session:

`java -jar target/kafka-streams-interactive-query-advanced-0.0.1-SNAPSHOT.jar --server.port=8082 --spring.cloud.stream.kafka.streams.binder.configuration.application.server=localhost:8082'

5. Run the stand-alone `Producers` application to generate data and start the processing.
Keep it running for a while.

6. Go to the URL: http://localhost:8080/charts/top-five?genre=Punk
keep refreshing the URL and you will see the song play count information changes.

Take a look at the console sessions for the applications and you will see that it may not be the processor started on 8080 that serves this request.

7. Go to the URL: http://localhost:8082/charts/top-five?genre=Punk

Take a look at the console sessions for the applications and you will see that it may not be the processor started on 8082 that serves this request.

8. Once you are done with running the sample, stop the docker containers and the schema registry.