tree 46688e5ca382e17c70ebbfdd5a97707832da068e
parent 8aef78f350c2cea79d3220d570c58d160c88bd1b
author Dmitry Lychagin <dmitry.lychagin@couchbase.com> 1555114503 -0700
committer Dmitry Lychagin <dmitry.lychagin@couchbase.com> 1555377505 +0000

[NO ISSUE][COMP][RT] Handle type mismatch in window frame boundaries

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- If window frame boundary is defined as N preceding/following
  and the incoming value is not of a numeric or temporal type
  then assume that the frame is empty for this value because
  its boundaries cannot be computed
- Add tests for NULL/MISSING/complex types for window operator
- Fix typo in the name resolution documentation

Change-Id: I4dc1b010674eb9a8b679039dc68c81163d156956
Reviewed-on: https://asterix-gerrit.ics.uci.edu/3342
Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Ali Alsuliman <ali.al.solaiman@gmail.com>