Wenchen Fan
Wenchen Fan
Hiding plans/expressions with a lambda function is evil. We should do the right thing even if it's not easy (need to fix commands one by one).
I don't believe this is the right fix. We should fix every place in the parser to not hide plans/expressions within a lambda function.
`SqlScriptingInterpreterSuite` fails
Let's create a JIRA ticket. This is not a minor change. Otherwise LGTM
thanks, merging to master/4.0!
There is a linter failure ``` Checkstyle checks failed at following occurrences: Error: src/main/java/org/apache/spark/sql/connector/read/SupportsPushDownJoin.java:[50] (sizes) LineLength: Line is longer than 100 characters (found 108). Error: src/main/java/org/apache/spark/sql/connector/read/SupportsPushDownJoin.java:[51] (sizes) LineLength: Line is...
thanks, merging to master!
@peter-toth Sorry for the late response. I've been struggling with this issue for a long time and can't make up my mind until recently that I find a design I'm...
thanks, merging to master!
@mihailoale-db can you say more about how your example query gets a different type coercion result with different rule order? Let's describe "not consistent" clearly here.