1)
In Search, the documentation refers to a "ta" field being mandatory. This isn't in the service definition yaml and it doesn't seem like this field is needed.
2)
In Events, if I put in a "since" date before 19th September 2024 I get an Internal Server Error. I would expect historical dates to still return everything, rather than an error.
3)
For Search, the 'page' and 'pageSize' is mandatory
For Events, the 'page', 'pageSize' and 'since' is mandatory
In the documentation, both refer to "at least one other field" being provided (e.g. traCreator).
It's currently working without needing to provide another field. This is what we'd prefer it to (although more fine grained parameters are useful too).
As a global consumer, we'd want to get everything (using the Event search) since the last time we searched. This would be across all d-tro and therefore we wouldn't want to refine the search beyond 'since'.
1) In Search, the documentation refers to a "ta" field being mandatory. This isn't in the service definition yaml and it doesn't seem like this field is needed.
2) In Events, if I put in a "since" date before 19th September 2024 I get an Internal Server Error. I would expect historical dates to still return everything, rather than an error.
3) For Search, the 'page' and 'pageSize' is mandatory For Events, the 'page', 'pageSize' and 'since' is mandatory
In the documentation, both refer to "at least one other field" being provided (e.g. traCreator).
It's currently working without needing to provide another field. This is what we'd prefer it to (although more fine grained parameters are useful too).
As a global consumer, we'd want to get everything (using the Event search) since the last time we searched. This would be across all d-tro and therefore we wouldn't want to refine the search beyond 'since'.