Introduce performance measurement example #162
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Generate example data for byte manipulation example - Have byte manipulation example read from alternative topic
# Conflicts: # ksml-data-avro/NOTICE.txt # ksml-query/NOTICE.txt # ksml-reporting/NOTICE.txt # ksml-runner/NOTICE.txt # ksml-runner/src/main/java/io/axual/ksml/runner/KSMLRunner.java # ksml/NOTICE.txt # pom.xml
* DataObject interface extended with Printer enum, used to consistently print data object schema and/or value * Updated all DataObject implementing classes to implement the new toString() method * Make calls to toString() explicitly use a Printer type
* Add batchSize option to KSML config * Rework producer logic to allow producing messages in batches per interval * Pretty print ksml-language-spec.json for easier future diffs
… notation to use headers
Fix docker compose producer version and depends_on statements
* Split up example message generator into a normal one (interval), a binary one (intended to run example 12) and a batch one (intended for performance measurements) * Introduce example 19 to perform generic performance measurements on any KSML pipeline * Remove reading back from binary topic in example 1 to allow running all examples in parallel (ie no conflict with example 12) * Remove dead code from TopologyGenerator * Improve error message in UserTypeParser
- Generate example data for byte manipulation example - Have byte manipulation example read from alternative topic
# Conflicts: # ksml-runner/src/main/java/io/axual/ksml/runner/KSMLRunner.java # ksml-runner/src/main/java/io/axual/ksml/runner/config/KSMLRunnerConfig.java
… notation to use headers
# Conflicts: # docker-compose.yml # examples/ksml-data-generator.yaml # examples/ksml-runner.yaml # ksml-data-avro/NOTICE.txt # ksml-data-avro/pom.xml # ksml-query/NOTICE.txt # ksml-reporting/NOTICE.txt # ksml-runner/NOTICE.txt # ksml-runner/src/main/java/io/axual/ksml/runner/KSMLRunner.java # ksml-runner/src/main/java/io/axual/ksml/runner/config/ErrorHandlingConfig.java # ksml-runner/src/main/java/io/axual/ksml/runner/config/KSMLConfig.java # ksml-runner/src/main/java/io/axual/ksml/runner/config/KSMLRunnerConfig.java # ksml-runner/src/main/java/io/axual/ksml/runner/config/NotationConfig.java # ksml-runner/src/main/java/io/axual/ksml/runner/producer/ExecutableProducer.java # ksml/NOTICE.txt # ksml/src/main/java/io/axual/ksml/parser/UserTypeParser.java # pom.xml
# Conflicts: # pom.xml
- Generate example data for byte manipulation example - Have byte manipulation example read from alternative topic # Conflicts: # examples/00-example-generate-sensordata.yaml
# Conflicts: # examples/ksml-data-generator.yaml # examples/ksml-runner.yaml
# Conflicts: # pom.xml
… notation to use headers
* Split up example message generator into a normal one (interval), a binary one (intended to run example 12) and a batch one (intended for performance measurements) * Introduce example 19 to perform generic performance measurements on any KSML pipeline * Remove reading back from binary topic in example 1 to allow running all examples in parallel (ie no conflict with example 12) * Remove dead code from TopologyGenerator * Improve error message in UserTypeParser
# Conflicts: # ksml-runner/src/main/java/io/axual/ksml/runner/KSMLRunner.java
# Conflicts: # pom.xml
… notation to use headers
jeroenvandisseldorp
deleted the
introduce-performance-measurement-example
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.