You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Dominik Riemer <ri...@apache.org> on 2020/05/06 17:39:38 UTC

Plans/Ideas for next release

Hi all,

 

as RC 0.66.0 is already out for testing, our dev branch is updated to the next release version, and quite a few new people have appeared on our mailing list, I think now is a good time to inform ourselves about things we’re currently working on.

 

So what do you plan to do for the next release?

 

For myself, I plan to migrate the last AngularJS UI components to Angular (which is important for some upcoming features such as user and role management), to work on a new user-faced module for better management of available data streams and to play a bit with ways how to improve the SDK with annotations (maybe getting rid of the controller class by directly declaring settings in the parameter class).

 

And another thing that would be very cool IMO and has already often been asked by users is definition and deployment of pipelines in code, e.g., by downloading registered pipeline elements, triggering a code generation component to create convenience classes and then providing developers a fluent API to create pipelines.

 

I think it would also be great to discuss things that you would like to see in StreamPipes although you don’t plan to implement it 😉

 

Dominik

 


Re: Plans/Ideas for next release

Posted by Philipp Zehnder <ze...@apache.org>.
Hi all,

one big feature that we should include in the next release is the data explorer.
In our development branch we already have a first prototype, which we currently refactor [1]
In this view users should be able to explore data stored in the data lake. Additionally, it will be possible to label image data, as well as time-series data.
Once the data is labeled, it can be exported (e.g. in a csv file)

For the adapters I would like to add a new feature for our PLC4X S7 adapter to automatically detect the properties of the S7 by uploading a CSV file instead of configuring all of them manually [2]


Philipp


[1] https://issues.apache.org/jira/browse/STREAMPIPES-79 <https://issues.apache.org/jira/browse/STREAMPIPES-79> 
[2] https://issues.apache.org/jira/browse/STREAMPIPES-118 <https://issues.apache.org/jira/browse/STREAMPIPES-118>

> On 6. May 2020, at 19:39, Dominik Riemer <ri...@apache.org> wrote:
> 
> Hi all,
> 
> 
> 
> as RC 0.66.0 is already out for testing, our dev branch is updated to the next release version, and quite a few new people have appeared on our mailing list, I think now is a good time to inform ourselves about things we’re currently working on.
> 
> 
> 
> So what do you plan to do for the next release?
> 
> 
> 
> For myself, I plan to migrate the last AngularJS UI components to Angular (which is important for some upcoming features such as user and role management), to work on a new user-faced module for better management of available data streams and to play a bit with ways how to improve the SDK with annotations (maybe getting rid of the controller class by directly declaring settings in the parameter class).
> 
> 
> 
> And another thing that would be very cool IMO and has already often been asked by users is definition and deployment of pipelines in code, e.g., by downloading registered pipeline elements, triggering a code generation component to create convenience classes and then providing developers a fluent API to create pipelines.
> 
> 
> 
> I think it would also be great to discuss things that you would like to see in StreamPipes although you don’t plan to implement it 😉
> 
> 
> 
> Dominik
> 
> 
>