Peter Toth ca2fca1432 [SPARK-25816][SQL] Fix attribute resolution in nested extractors ... ## What changes were proposed in this pull request? Extractors are made of 2 expressions, one of them defines the the value to be extract from (called `child`) and the other defines the way of extraction (called `extraction`). In this term extractors have 2 children so they shouldn't be `UnaryExpression`s. `ResolveReferences` was changed in this commit: 36b826f5d1 which resulted a regression with nested extractors. An extractor need to define its children as the set of both `child` and `extraction`; and should try to resolve both in `ResolveReferences`. This PR changes `UnresolvedExtractValue` to a `BinaryExpression`. ## How was this patch tested? added UT Closes #22817 from peter-toth/SPARK-25816. Authored-by: Peter Toth <peter.toth@gmail.com> Signed-off-by: gatorsmile <gatorsmile@gmail.com>		2018-10-28 17:51:35 -07:00
..
benchmarks	[SPARK-25492][TEST] Refactor WideSchemaBenchmark to use main method	2018-10-20 17:31:13 -07:00
src	[SPARK-25816][SQL] Fix attribute resolution in nested extractors	2018-10-28 17:51:35 -07:00
pom.xml	[SPARK-25592] Setting version to 3.0.0-SNAPSHOT	2018-10-02 08:48:24 -07:00