Request
After #1848 timestamp literals can only be compared against integer and float columns in kv-ir. This can lead to a behaviour mismatch between kv-ir and clp-s archive search since the same column might exist as a string in kv-ir and a parsed timestamp in the corresponding clp-s archive.
Possible implementation
- Have the kv-ir search code carry around a default set of timestamp patterns that can be used to attempt to parse string columns as timestamps no demand for comparison against timestamp literals.
- Modify the column resolution code in kv-ir to allow timestamp literals to resolve to string columns (and have comparisons (besides NEXISTS?) always evaluate to false when the string value can not be parsed as a timestamp).