Hi, yes, exactly. When a user creates a new adapter it can be defined whether a property is a dimension property (can later be used to group the streams), a header property (like the timestamp), or a measurement property (containing usually sensor values and other measurements).
This information can then later be used for the recommended settings. @Dominik, should’t it be a PropertyScope of MEASUREMENT? Cheers, Philipp On 2019/12/02 22:03:28, Dominik Riemer <[email protected]> wrote: > Hi Patrick,> > > I like this idea!> > We could use the PropertyScope (Header/Dimension/Measurement) of each event > property to implement this feature - I think that Philipp or Johannes added > the opportunity to assign the PropertyScope in StreamPipes Connect for the > last release.> > To exclude the timestamp, we could then assign a required PropertyScope > DIMENSION to the mapping property. In the UI, when you configure a pipeline > element, there is already a switch called "Show recommended settings only" - > this could be on by default and filter event properties for properties that > match the required scope.> > > Dominik> > > -----Original Message-----> > From: Patrick Wiener <[email protected]> > > Sent: Monday, December 2, 2019 8:41 PM> > To: [email protected]> > Subject: Exclude timestamp from mapping properties> > > > Hi,> > > I was just working on updating the aggregation pipeline element in flink to > support nary-mappings, when I stumbled upon this. > > > Currently, we show the timestamp fields as potential mapping properties in > the user dialog as suitable candidates, e.g. to perform aggregation such as > calculating an average. I guess, it make sense to exclude the timestamp > field(s) from the list of mapping properties, such that timestamps are not > shown to the user - if not necessarily be required by the pipeline element.> > > What do you think?> > > Cheers,> > Patrick> >
