Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/3661
I'm currently in SF for http://sf.flink-forward.org and quite busy. That's
why my responses are quite slow, sorry for that.
A quick answer: There is the (slightly hard to find)
`InternalWindowFunctionTest` which tests that the internal window functions
correctly forward calls to a process window function and other (user facing)
window functions. We should test the internal logic of the new time access code
for `InternalWindowFunction` in `WindowOperatorContractTest`, (see, for example
`testPerWindowStateSetAndClearedOnEventTimePurge()`). We should add more tests
that verify that per-window state and also the new time access is correctly
forwarded in `InternalWindowFunctionTest`.
What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
