From dev-return-80-archive-asf-public=cust-asf.ponee.io@streampipes.apache.org Tue Dec 3 21:54:18 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id D72DA180629 for ; Tue, 3 Dec 2019 22:54:17 +0100 (CET) Received: (qmail 31076 invoked by uid 500); 3 Dec 2019 21:54:17 -0000 Mailing-List: contact dev-help@streampipes.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@streampipes.apache.org Delivered-To: mailing list dev@streampipes.apache.org Received: (qmail 31064 invoked by uid 99); 3 Dec 2019 21:54:17 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2019 21:54:17 +0000 Received: from ipeente (HSI-KBW-46-223-163-192.hsi.kabel-badenwuerttemberg.de [46.223.163.192]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 9CA831004 for ; Tue, 3 Dec 2019 21:54:16 +0000 (UTC) From: "Dominik Riemer" To: References: In-Reply-To: Subject: RE: Exclude timestamp from mapping properties Date: Tue, 3 Dec 2019 22:54:14 +0100 Message-ID: <00eb01d5aa24$355f24b0$a01d6e10$@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHVqUhuINWXjp5eME2Eiic8vDj9+qenZKfAgAGPr4A= Content-Language: de Hi Patrick, I just did committed some minor changes to the UI to enable the exclusion of timestamps from mapping properties. The "show only recommended elements" switch in the pipeline element configuration should now be turned on by default and if both (event properties and processor requirements) do provide a PropertyScope, non-matching event properties are excluded from MappingProperty selections. Would be great if you could give it a try ;-) Dominik -----Original Message----- From: Dominik Riemer Sent: Monday, December 2, 2019 11:03 PM To: 'dev@streampipes.apache.org' Subject: RE: Exclude timestamp from mapping properties 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 Sent: Monday, December 2, 2019 8:41 PM To: dev@streampipes.apache.org 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