Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/21403
I updated the PR according to the previous discussion.
@hvanhovell @juliuszsompolski may you please take a look at it now? Thanks.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92084/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/21403
**[Test build #92084 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/92084/testReport)**
for PR 21403 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92085/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Merged build finished. Test FAILed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/21403
**[Test build #92085 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/92085/testReport)**
for PR 21403 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/21403
**[Test build #92085 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/92085/testReport)**
for PR 21403 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4210/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/316/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21403
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/21403
**[Test build #92084 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/92084/testReport)**
for PR 21403 at commit
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/21403
I am encountering big issues in enforcing the behavior we mentioned. The
problem is that we cannot really distinguish the cases:
- `... (a, b) in (select ...)`
- `... from (select (a, b)
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/21403
@juliuszsompolski yes, you're right, sorry, SPARK-24395 uses literal and
not subqueries, sorry.
---
-
To unsubscribe, e-mail:
Github user juliuszsompolski commented on the issue:
https://github.com/apache/spark/pull/21403
@mgaido91 BTW: In SPARK-24395 I would consider the cases to still be valid,
because I believe there is no other syntactic way to do a multi-column IN/NOT
IN with list of literals.
The
Github user juliuszsompolski commented on the issue:
https://github.com/apache/spark/pull/21403
@mgaido91 This also works, +1.
What about `a in (select (b, c) from ...)` when `a` is a struct? - I guess
allow it, but a potential gotcha during implementation
---
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/21403
@juliuszsompolski I see your point and I can say it is an acceptable
solution. Though it has some problems I think. If we follow this path, we are
saying that: `(a, b) IN (select c, d from ...)`
Github user juliuszsompolski commented on the issue:
https://github.com/apache/spark/pull/21403
I think that the way the columns are defined in the subquery should define
the semantics.
E.g.:
`(a, b) IN (select c, d from ...)` - unpack (a, b) and treat it as a multi
column
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/21403
thanks @hvanhovell, sorry for the error. I changed to the right one.
---
-
To unsubscribe, e-mail:
20 matches
Mail list logo
