Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
Hm, I am trying to make another clean version but it seems taking a bit of
time. I will close this and open again when I am ready. Please feel free to
take over this meanwhile.
---
If your
Github user wgtmac commented on the issue:
https://github.com/apache/spark/pull/14215
@HyukjinKwon no problem. Take your time.
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
@wgtmac Sorry, I will try to make this complete this within this week. I
was busy for some reasons.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
@wgtmac I hope this one is merged into 2.1 but I believe I am not supposed
to decide it. I will anyway take out of the vectorized one described in the PR
then.
---
If your project is set up
Github user wgtmac commented on the issue:
https://github.com/apache/spark/pull/14215
@HyukjinKwon yep, keep each PR as small as possible is a good idea. BTW,
may I know the target version of your non-vectorize fix? Our production job is
in need of this fix.
Separating
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
@wgtmac BTW, as you might already know, my plan and though is, to implement
each first and then unify them within a common parent at the end if possible
and it makes sense..
---
If your
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
@wgtmac Thanks for pinging. I think I can proceed this on this weekend. I
haven't looked into vectorized one closely yet. If you have already looked into
that, I think it'd also make sense not
Github user wgtmac commented on the issue:
https://github.com/apache/spark/pull/14215
@HyukjinKwon Do you have a timeline for this patch?
Also, what's your plan on vectorized parquet reader?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14215
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14215
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66177/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14215
**[Test build #66177 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66177/consoleFull)**
for PR 14215 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14215
**[Test build #66177 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66177/consoleFull)**
for PR 14215 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14215
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66086/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14215
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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14215
**[Test build #66086 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66086/consoleFull)**
for PR 14215 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14215
**[Test build #66086 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66086/consoleFull)**
for PR 14215 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
I am reopening this. Please refer the discussion in
https://github.com/apache/spark/pull/15264
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
I am closing this for now. I will reopen or suggest better way later.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
For handling messages, I will open a separate PR soon!
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
I see, yes I will think of a better way to fix the message. Yea it is still
happening across other data sources and this implementation is very specific to
Parquet.
I just wonder we
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14215
Currently, the error message is still confusing.
```
org.apache.parquet.io.ParquetDecodingException: Can not read value at 1 in
block 0
```
Could we first improve the error
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14215
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62365/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14215
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14215
**[Test build #62365 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62365/consoleFull)**
for PR 14215 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14215
**[Test build #62365 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62365/consoleFull)**
for PR 14215 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
Hi @gatorsmile @dongjoon-hyun @liancheng , currently this deals with only
`NumericType` except `DecimalType` for upcasting only for non-vectorized reader.
Before proceeding further, I
26 matches
Mail list logo
