-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(#3179): new processor sensorlimitalert #3180
Conversation
@@ -36,7 +36,7 @@ | |||
import org.apache.streampipes.wrapper.params.compat.ProcessorParams; | |||
import org.apache.streampipes.wrapper.standalone.StreamPipesDataProcessor; | |||
|
|||
public class QualityControlLimitsEnrichment extends StreamPipesDataProcessor { | |||
public class QualityControlLimitsEnrichmentProcessor extends StreamPipesDataProcessor { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use the IStreamPipesDataProcessor
interface instead of extending StreamPipesDataProcessor
?
https://streampipes.apache.org/docs/extend-tutorial-data-processors/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I changed it. Is there a reason why we did not deprecate StreamPipesDataProcessor
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably because we didn't want to refactor all existing pipeline elements ;-)
Purpose
Implement process described in #3179
Remarks
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no