[ 
https://issues.apache.org/jira/browse/SPARK-59526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luka Zdravic updated SPARK-59526:
---------------------------------
    Description: 
ASOF JOIN checks MATCH_CONDITION operands with a dedicated policy that does not 
match how Spark checks the same operators and operands elsewhere.

This umbrella tracks three defects, one sub-task each:
1. MATCH_CONDITION rejects a DATE vs STRING pair that the comparison operator 
accepts and coerces.
2. MATCH_CONDITION rejects arrays with different but coercible element types 
that the comparison operator accepts.
3. MATCH_CONDITION accepts a constant operand that references no join input, 
which makes the as-of match ill-defined.
4. MATCH_CONDITION rejects empty STRUCT operands, also when nested, that the 
comparison operator accepts.

Defects 1 and 2 and 4 make ASOF stricter than a plain comparison. Defect 3 
makes it too lenient.

  was:
ASOF JOIN checks MATCH_CONDITION operands with a dedicated policy that does not 
match how Spark checks the same operators and operands elsewhere.

This umbrella tracks three defects, one sub-task each:
1. MATCH_CONDITION rejects a DATE vs STRING pair that the comparison operator 
accepts and coerces.
2. MATCH_CONDITION rejects arrays with different but coercible element types 
that the comparison operator accepts.
3. MATCH_CONDITION accepts a constant operand that references no join input, 
which makes the as-of match ill-defined.

Defects 1 and 2 make ASOF stricter than a plain comparison. Defect 3 makes it 
too lenient.


> ASOF JOIN MATCH_CONDITION operand validation defects
> ----------------------------------------------------
>
>                 Key: SPARK-59526
>                 URL: https://issues.apache.org/jira/browse/SPARK-59526
>             Project: Spark
>          Issue Type: Umbrella
>          Components: SQL
>    Affects Versions: 5.0.0
>            Reporter: Luka Zdravic
>            Priority: Minor
>
> ASOF JOIN checks MATCH_CONDITION operands with a dedicated policy that does 
> not match how Spark checks the same operators and operands elsewhere.
> This umbrella tracks three defects, one sub-task each:
> 1. MATCH_CONDITION rejects a DATE vs STRING pair that the comparison operator 
> accepts and coerces.
> 2. MATCH_CONDITION rejects arrays with different but coercible element types 
> that the comparison operator accepts.
> 3. MATCH_CONDITION accepts a constant operand that references no join input, 
> which makes the as-of match ill-defined.
> 4. MATCH_CONDITION rejects empty STRUCT operands, also when nested, that the 
> comparison operator accepts.
> Defects 1 and 2 and 4 make ASOF stricter than a plain comparison. Defect 3 
> makes it too lenient.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to