You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@streampipes.apache.org by "bossenti (via GitHub)" <gi...@apache.org> on 2023/02/23 07:16:52 UTC

[I] [WIP] Code Insights for Apache StreamPipes (streampipes)

bossenti opened a new issue, #1343:
URL: https://github.com/apache/streampipes/issues/1343

### Body

### *****Apache StreamPipes*****

Apache StreamPipes (incubating) is a self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams. StreamPipes offers several modules including StreamPipes Connect to easily connect data from industrial IoT sources, the Pipeline Editor to quickly create processing pipelines and several visualization modules for live and historic data exploration. Under the hood, StreamPipes utilizes an event-driven microservice paradigm of standalone, so-called analytics microservices making the system easy to extend for individual needs.

### *****Background*****

StreamPipes is grown significantly throughout recent years. We were able to introduce a lot of new features and attracted both users and contributors. Putting the cherry on the cake, we were graduated as an Apache top level project in December 2022. We will of course continue developing new features and never rest to make StreamPipes even more amazing. Although, since we are approaching with full stream towards our `1.0` release, we want to project also to get more mature. Therefore, we want to address one of our Achilles' heels: our test coverage.

Don't worry, this issue is not about implementing myriads of tests for our code base. As a first step, we would like to make the status quo transparent. That means we want to measure our code coverage consistently across the whole codebase (Backend, UI, Python library) and report the coverage to [codecov](https://about.codecov.io/). Furthermore, to benchmark ourselves and motivate us to provide tests with every contributing, we would like to lock the current test coverage as an lower threshold that we always want to achieve (meaning in case we drop CI builds fail etc). With time we then can increase the required coverage lever step to step.

More than monitoring our test coverage, we also want to invest in better and more clean code. Therefore, we would like to adopt [sonarcloud](https://www.sonarsource.com/products/sonarcloud/) for our repository.

Currently, window logic can be individually defined per pipeline element. The whole windowing logic needs to be declared in the controller and runtime logic needs to be individually added based on the selected runtime wrapper (Java, Siddhi, Flink, etc...).

### *****Tasks*****
tbc

### *****Relevant Skills*****
tbc

### *****Learning Material*****

****For StreamPipes:****
tbc

****For Streaming Analytics:****
tbc

*****Mentor*****
- Tim Bossenmaier (bossenti[at]apache.org).

### StreamPipes Committer

I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@streampipes.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Code Insights for Apache StreamPipes (streampipes)

Posted by "Kshitiz-Mhto (via GitHub)" <gi...@apache.org>.

Kshitiz-Mhto commented on issue #1343:
URL: https://github.com/apache/streampipes/issues/1343#issuecomment-1460444909

   hello @bossenti , i am interested in this project to contribute in this issue for GSOC 2023,  Currently i am exploring its components and playing with it a little bit and understanding it.
   thank you!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@streampipes.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org