-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ML] ScheduledEvent takes and stores ZonedDateTime but then discards the timezone #38620
Comments
Pinging @elastic/ml-core |
Hello, I am getting this error when trying to run lang.IllegalArgumentException: transport type setting [transport.type] must be [security4] or [security-nio] but is [mock-nio]
I did the required setup based on the documentation in the project but didn't find anything regarding setup for integration tests. Can you help me please? |
Thanks for looking at this @Mehrank64. How did you run Try running this from the top level of your clone of the repo:
Does the test pass on your machine when run like that? If not, how about on a clean clone without your changes? If it doesn't pass on a clean clone, what is the exact error you get from this |
@droberts195 Thanks for your help. The test passes when I run it with the above command I did run the Unit test from the IDE and all should be fine now. |
That’s great @Mehrank64. Once the change is complete please open a PR to merge from the branch in your fork to master and @ mention me in it so I get notified. |
@droberts195 just did. let me know if you can't see it/any amendment is required |
(Noticed while fixing #38506)
The
ScheduledEvent
class's constructor takesZonedDateTime
for bothstartTime
andendTime
. However, when serialising both on the wire and asXContent
it ditches the time zone and converts to anInstant
. It would make more sense to storeInstant
, takeInstant
s in the constructor and returnInstant
s from the accessors. Then it would be completely clear to all users that the class was not preserving the time zone.The text was updated successfully, but these errors were encountered: