tpalfy commented on a change in pull request #4721:
URL: https://github.com/apache/nifi/pull/4721#discussion_r542471394
##########
File path:
nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/list/AbstractListProcessor.java
##########
@@ -207,6 +225,39 @@
.defaultValue(BY_TIMESTAMPS.getValue())
.build();
+ public static final PropertyDescriptor TIME_ADJUSTMENT = new Builder()
+ .name("time-adjustment")
+ .displayName("Time Adjustment")
+ .description("If the system hosting the files is in a different time
zone than NiFi, either it's timezone or the numerical difference should be set
here." +
+ " If a timezone is specified, NiFi tries to calculate the time
difference." +
+ " If a numeric value is set, its value can be either a single
integer (milliseconds) or in HH:mm/HH:mm:ss format." +
+ " EXAMPLE: NiFi is hosted in UTC, File Server is hosted in EST. In
this case 'Time Adjustment' value should be -05:00:00 or 18000000." +
Review comment:
I think File Server is adequate. The main point is handling time zone
difference. The whole concept is realistically applicable only with remotely
hosted files.
Edit: To clarify: the new strategy theoretically could be applied to local
file systems as well. "File Server" is only mentioned in the example though,
which focuses on a scenario where there _is_ a time zone difference. In that
scenario "File Server" is adequate. (In other places I use the term "system
hosting the 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.
For queries about this service, please contact Infrastructure at:
[email protected]
