Skip to content
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

[BUG] Spark UT framework: Propagate Hadoop configs from parquet options to underlying file system #11602

Open
Tracked by #11402
Feng-Jiang28 opened this issue Oct 14, 2024 · 0 comments
Labels
? - Needs Triage Need team to review and classify bug Something isn't working test Only impacts tests

Comments

@Feng-Jiang28
Copy link
Collaborator

Feng-Jiang28 commented Oct 14, 2024

In Spark UT framework, there is a test case ensuring the Hadoop configurations are correctly propagated from the data source options to the underlying file system. '

val conf = Map("ds_option" -> "value", "mergeSchema" -> mergeSchema.toString)
inputDataset
   .write
   .options(conf)
   .format(dataSourceFormat)
   .save(path)

The test code then checks if the underlying FileSystem' conf has been set correctly.
However, the ds_option seems be to missed in FileSystem.

If I modified the test code to set spark.sparkContext.hadoopConfiguration.set("ds_option", "value"), then the test case will passs.

So the gap between Rapids and Spark is that options(conf) method on the DataFrameWriter of plugin cannot modify the Hadoop configuration.

@Feng-Jiang28 Feng-Jiang28 added ? - Needs Triage Need team to review and classify test Only impacts tests bug Something isn't working labels Oct 14, 2024
@Feng-Jiang28 Feng-Jiang28 changed the title Propagate Hadoop configs from parquet options to underlying file system [BUG] Spark UT framework: Propagate Hadoop configs from parquet options to underlying file system Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
? - Needs Triage Need team to review and classify bug Something isn't working test Only impacts tests
Projects
None yet
Development

No branches or pull requests

1 participant