Closed Woljtek closed 1 year ago
Because the ingestion redeployments are rare, the priority is minor.
This behaviour is not a bug, but indeed wanted behaviour. Unfortunately, the JIRA from the S1PRO development is not active anymore, so I am unable to refer to the original request as to why this was implemented (If you have access to it still the issue number was S1PRO-2098).
The current behavior is not described in the inboxes section10. Is there a place where this mechanism inherited from S1PRO is described?
The behaviour might be described in the story of the old jira system. As it is down, it is difficult to trace the intensions. The idea behind the ignoreFilter is to avoid that the whole data of a server is transferred when a fresh installation is setup. The intension was not to allow a timing of when the ingestion trigger start to pull in files.
My assumption is that there was a request to set the data to know, if it its in the future as someone was confused why the system is not pulling in data. This behaviour was existing since the S1PRO and thus would be technically a change of behaviour. The code is clearily indicating that the current behaviour was wanted:
// S1PRO-2098: If the configured date is in the future, take the current date as the
// reference value
if (ignoreFilesBeforeDate.after(now)) {
return now;
}
Removing this behaviour would be easy however.
IVV_CCB_2023_w18 : Moved into "Accepted Werum" to be discussed if documentation or code should be changed, Priority minor, no need for phase 1
Werum_CCB_2023_w18 : Moved into "Product Backlog", documentation issue
Documentation was updated to reflect that a future data will be set to the current time.
This issue was tackled in V1.13.1 and thus will be contained in V2. (refer to https://github.com/COPRS/production-common/releases/tag/1.13.1-rc1)
SYS_CCB_w29 : A comment has been added on the default configuration from release 1.13.1.
Environment:
Traçability:
Current Behavior: During the preparation of the 24h test, we redeployed the ingestion chains with a
ignoreFilesBefore
date in the future. TheignoreFilesBefore
date is replaced by the deployment date. So we started the ingestion earlier than expected.Expected Behavior: The configured
ignoreFilesBefore
date in stream.parameters.properties shall be used.Steps To Reproduce: 1- Set a
ignoreFilesBefore
in the future 2- Deploy the ingestion chain 3- Obverve that chunks are ingested after the deployment dateTest execution artifacts (i.e. logs, screenshots…) Example with ingestion-pedc:
=> MinimumModificationDateFilter [ignoreFilesBefore=Thu Apr 27 13:05:12 UTC 2023]
3- Deployed configuration:
Whenever possible, first analysis of the root cause
Bug Generic Definition of Ready (DoR)
Bug Generic Definition of Done (DoD)