Hi Marco, welcome to the mailing list.
It's great that you like StreamPipes. This is a very good point and I got similar feedback from multiple users and we should find a solution for that. I think the biggest problem is to find meaningful default values, because when we just use names like Data Lake 1 the user will not know what kind of data it represents. @all: Would it be possible to use the data source name (e.g. Flow Rate Sensor 2) as a default value? Since the user can do basically anything within a pipeline I think it is hard to realize this. Any thoughts? Philipp > On 1. Jul 2020, at 23:16, Marco Heyden <[email protected]> wrote: > > Hey everyone, > > I played around with streampipes during the last days and overall had a great > experience. > However, while setting up the adapters, pipelines, dashboards, data sinks, > etc. I found it a little annoying to come up with a meaningful identifier for > each component over and over again as there are no default values. For > example, I ended up calling the sinks S1, S2, S3 and so on. > > I’d like to ask if you had similar experiences and if you have any ideas > regarding good default values. For now, I suggest simple default values such > as > > • Data Lake 1, 2, 3 ... > • Dashbord 1, 2, 3 ... > > Although they are not really meaningful, prototyping would become more > convenient. Also I feel like most new users don’t know what the identifiers > are for. Default values could thus also help users to understand why and how > they should choose them. > > Let me know what you think. > > Best > Marco
