Scrooge-McDucks opened a new pull request, #10975: URL: https://github.com/apache/nifi/pull/10975
<!-- Licensed to the Apache Software Foundation (ASF) under one or more --> <!-- contributor license agreements. See the NOTICE file distributed with --> <!-- this work for additional information regarding copyright ownership. --> <!-- The ASF licenses this file to You under the Apache License, Version 2.0 --> <!-- (the "License"); you may not use this file except in compliance with --> <!-- the License. You may obtain a copy of the License at --> <!-- http://www.apache.org/licenses/LICENSE-2.0 --> <!-- Unless required by applicable law or agreed to in writing, software --> <!-- distributed under the License is distributed on an "AS IS" BASIS, --> <!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --> <!-- See the License for the specific language governing permissions and --> <!-- limitations under the License. --> ## Summary [NIFI-15674](https://issues.apache.org/jira/browse/NIFI-15674) Adds two new Expression Language validation functions: - `isValidDate(format[, timezone])` - `isValidInstant()` These functions allow flows to validate date and instant values before attempting conversion. ## Motivation NiFi currently does not provide a simple top-level Expression Language function for validating whether a value can be parsed as a date or instant. Today, users often need to rely on regex, nested expressions, or extra processor logic in places like `UpdateAttribute` or `RouteOnAttribute` to guard parsing. Regex can validate shape, but it is not calendar-aware, so values like `31-02-2026` may still appear valid even though they are not real dates. This also creates operational risk. If invalid values are parsed directly, expression evaluation can fail, which in some flows can lead to repeated retries or queue looping instead of clean handling. These functions provide a lightweight and safe way to keep validation logic visible at the top level of an expression. ## Behavior ### `isValidDate(format)` Returns `true` if the subject can be parsed as a valid date using the supplied format, otherwise `false`. ### `isValidDate(format, timezone)` Returns `true` if the subject can be parsed as a valid date using the supplied format and timezone, otherwise `false`. ### `isValidInstant()` Returns `true` if the subject can be parsed as a valid ISO-8601 instant, otherwise `false`. Invalid input returns `false` rather than throwing an evaluation error. ## Examples `${myDate:isValidDate("dd-MM-yyyy"):ifElse("valid","invalid")}` `${myDate:isValidDate("yyyy-MM-dd HH:mm:ss", "UTC")}` `${eventTime:isValidInstant():ifElse("valid-instant","invalid-instant")}` # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` - [x] Pull request contains [commits signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) with a registered key indicating `Verified` status ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `./mvnw clean install -P contrib-check` - [x] JDK 21 - [ ] JDK 25 ### Licensing - [x] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [x] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [x] Documentation formatting appears as expected in rendered files -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
