[#28] Updated flink jpmml examples #39
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
…es for ADT evaluator
…he needed structures, insert test for it
…eature/28-introducing_updated_flink-jpmml_examples
riccardo14
approved these changes
Sep 20, 2017
…eature/28-introducing_updated_flink-jpmml_examples
spi-x-i
requested changes
Sep 20, 2017
added 2 commits
September 20, 2017 17:29
spi-x-i
requested changes
Sep 20, 2017
flink-jpmml-examples/README.md
Outdated
| This module contains the examples running simple predictions from an iris Source. | ||
| The source emits the following data: | ||
| ``` | ||
| Iris(sepalLength: Double, sepalWidth: Double, petalLength: Double, petalWidth: Double) | ||
| Iris(,sepalLength: Double, sepalWidth: Double, petalLength: Double, petalWidth: Double) |
There was a problem hiding this comment.
I still haven't finished the Readme!
flink-jpmml-examples/README.md
Outdated
| @@ -25,5 +25,19 @@ Either you can employ the _quick_ predictor: | |||
| ./path/to/bin/flink run -c io.radicalbit.examples.QuickEvaluateKmeans <path/to/project/root>/flink-jpmml/flink-jpmml-examples/target/scala-2.x/flink-jpmml-examples-assembly-0.6.0-SNAPSHOT.jar --model path/to/pmml/model.pmml --output /path/to/output | |||
| ``` | |||
|
|
|||
| ## Fault-Tolerant | |||
flink-jpmml-examples/README.md
Outdated
| @@ -25,5 +25,19 @@ Either you can employ the _quick_ predictor: | |||
| ./path/to/bin/flink run -c io.radicalbit.examples.QuickEvaluateKmeans <path/to/project/root>/flink-jpmml/flink-jpmml-examples/target/scala-2.x/flink-jpmml-examples-assembly-0.6.0-SNAPSHOT.jar --model path/to/pmml/model.pmml --output /path/to/output | |||
| ``` | |||
|
|
|||
| ## Fault-Tolerant | |||
|
|
|||
| if you like testing a fault-tolerant of the operator you can run a `CheckpointEvaluate` example. | |||
There was a problem hiding this comment.
If you like testing the fault-tolerance feature ..
flink-jpmml-examples/README.md
Outdated
|
|
||
| 2) Run the flink-cluster | ||
|
|
||
|
|
|
|
||
| val env = StreamExecutionEnvironment.getExecutionEnvironment | ||
|
|
||
| env.enableCheckpointing(parameters.ckpInterval, CheckpointingMode.EXACTLY_ONCE) |
There was a problem hiding this comment.
Please, if you use parameter here, then bring this best practice also on CheckpointEvaluate
|
|
||
| val env = StreamExecutionEnvironment.getExecutionEnvironment | ||
|
|
||
| env.enableCheckpointing(1000, CheckpointingMode.EXACTLY_ONCE) |
spi-x-i
requested changes
Sep 20, 2017
flink-jpmml-examples/README.md
Outdated
| _if you like testing a fault-tolerance of the operator you can run a `CheckpointEvaluate` example._ |
There was a problem hiding this comment.
testing the fault-tolerance behaviour of the operator
flink-jpmml-examples/README.md
Outdated
| ``` | ||
|
|
||
| 4) Put the model via socket, in this case you can use the models in `flink-jpmml-assets`: |
flink-jpmml-examples/README.md
Outdated
| ./path/to/flink-1.3.2/bin/taskmanager.sh stop | ||
| ``` | ||
| _you can show the job's status in Flink UI on http://localhost:8081_ |
flink-jpmml-examples/README.md
Outdated
| ``` | ||
|
|
||
| _At this point, when the job is restarted, there's no need to reload the models in control stream because you should see the models from the last checkpoint_ |
There was a problem hiding this comment.
there's no need to re-send the models info by control stream
| /* | ||
| * Make a prediction withSupportStream that represents the stream from the socket | ||
| * evaluate the model with model upload in ControlStream | ||
| * */ |
There was a problem hiding this comment.
breakline for closing comments
spi-x-i
approved these changes
Sep 20, 2017
maocorte
approved these changes
Sep 21, 2017
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.
this PR refers to #28 issue.