Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Now, only minor `HINT_PREFIX` remains.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featur
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62196 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62196/consoleFull)**
for PR 14132 at commit
[`5c76e25`](https://github.com/apache/spark/commit/5
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
So far, I couldn't do the following two advices. I just inform you that I'm
still working these. :)
- `HINT_PREFIX`
- `| hintName=identifier '(' parameters+=identifier parameters+=
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
I'm back. I'll resolve them.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Thank you always, @hvanhovell . Annd, sorry for the delay. Since last
Saturday, I need to do some important personal stuff offline, so the time is
limited for me. :(
---
If your project is s
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
For the HINT_PREFIX, I tried at the first, but still have some problem. So,
I couldn't include the very previous commit.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62162/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62162 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62162/consoleFull)**
for PR 14132 at commit
[`edec2e4`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62162 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62162/consoleFull)**
for PR 14132 at commit
[`edec2e4`](https://github.com/apache/spark/commit/e
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Oops. Five errors, too. I'll fix these tomorrow.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have t
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62082/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62082 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62082/consoleFull)**
for PR 14132 at commit
[`6bd704e`](https://github.com/apache/spark/commit/
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Thank you for quick review! I'll let you know after updating.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project do
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14132
This looks pretty good!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wish
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
If the direction is right, I can move on adding `BROADCAST JOIN` syntax.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
cc @rxin and @hvanhovell .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled an
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62082 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62082/consoleFull)**
for PR 14132 at commit
[`6bd704e`](https://github.com/apache/spark/commit/6
19 matches
Mail list logo
