[
https://issues.apache.org/jira/browse/ASTERIXDB-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ali Alsuliman updated ASTERIXDB-2574:
-------------------------------------
Description:
min() and max() functions used on record/array fields sometimes throw an
exception and other times process input. That's because if the field type is
known the compiler will validate and check the field is numeric, string or
datetime. If the field type is not known (ANY), it would pass and the function
runtime would process the input data.
Need to align the min() and max() behavior with the less-than and greater-than
comparisons.
was:min() and max() functions used on record/array fields sometimes throw an
exception and other times process input. That's because if the field type is
known the compiler will validate and check the field is numeric, string or
datetime. If the field type is not known (ANY), it would pass and the function
runtime would process the input data.
> Inconsistency in min() and max() with respect to arrays/records
> ---------------------------------------------------------------
>
> Key: ASTERIXDB-2574
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2574
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: FUN - Functions
> Affects Versions: 0.9.4.1
> Reporter: Ali Alsuliman
> Assignee: Ali Alsuliman
> Priority: Major
>
> min() and max() functions used on record/array fields sometimes throw an
> exception and other times process input. That's because if the field type is
> known the compiler will validate and check the field is numeric, string or
> datetime. If the field type is not known (ANY), it would pass and the
> function runtime would process the input data.
> Need to align the min() and max() behavior with the less-than and
> greater-than comparisons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
