-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document agg pushdown on ORC file limitation [skip ci] #4957
Conversation
Signed-off-by: Ahmed Hussein (amahussein) <[email protected]>
docs/compatibility.md
Outdated
|
||
**Limitations With RAPIDS** | ||
|
||
[CUDF](https://github.com/rapidsai/cudf) still does not support writing the whole file statistcis into ORC file. The status of this feature request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we say that the RAPIDS Accelerator does not support. Because technically CUDF does, just not for chunked writes, which is what we are doing. Or perhaps just say that we are working with CUDF to support this feature and you can track it here...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made the changes.
BTW, There was another CUDF issue 10075 which reports that statistics are missing without being specific to the mode. I commented on the issues to verify whether they are dup or that Cudf does not support the file statistics at all.
Signed-off-by: Ahmed Hussein (amahussein) <[email protected]>
build |
6 similar comments
build |
build |
build |
build |
build |
build |
The PR has [skip ci] in the title. Why do you expect it to run ci? |
I could not build previous PRs couple of weeks ago. |
closes #4950
Signed-off-by: Ahmed Hussein (amahussein) [email protected]
document the expected failure caused by Spark-3.3.0 assumption that all ORC files must have file statistics.
document the usage of new spark-3.3.0 feature introduced in SPARK-34960