Skip to content

Conversation

@msfroh
Copy link
Contributor

@msfroh msfroh commented Oct 22, 2025

Description

Instead of using java.io.File, we can use java.nio.Path for a cleaner, more modern Java I/O experience.

Related Issues

N/A

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@msfroh msfroh requested a review from a team as a code owner October 22, 2025 20:02
@github-actions
Copy link
Contributor

✅ Gradle check result for 56c722b: SUCCESS

@codecov
Copy link

codecov bot commented Oct 22, 2025

Codecov Report

❌ Patch coverage is 90.90909% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 73.04%. Comparing base (c6236c3) to head (56c722b).

Files with missing lines Patch % Lines
...rch/plugin/ingestion/fs/FilePartitionConsumer.java 90.90% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main   #19736      +/-   ##
============================================
- Coverage     73.14%   73.04%   -0.11%     
+ Complexity    70797    70796       -1     
============================================
  Files          5732     5732              
  Lines        324258   324258              
  Branches      46925    46925              
============================================
- Hits         237186   236858     -328     
- Misses        67897    68325     +428     
+ Partials      19175    19075     -100     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

andrross
andrross previously approved these changes Oct 22, 2025
@varunbharadwaj
Copy link
Contributor

This does not work due to permission issues. We are checking for a different approach.

@andrross andrross dismissed their stale review October 22, 2025 22:48

See Varun's comment

Copy link
Contributor

@varunbharadwaj varunbharadwaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks for this change!

@msfroh
Copy link
Contributor Author

msfroh commented Oct 22, 2025

This does not work due to permission issues. We are checking for a different approach.

Discussed w/ @varunbharadwaj and updated the README to explain how to explicitly grant permissions to a directory (using the same approach as repository-fs and repository-url). Confirmed that it works 👍

Granting permission explicitly is a better/safer posture even for a plugin intended for tests/experiments. The fact that the older approach let you open files anywhere was a little sketchy.

@github-actions
Copy link
Contributor

❌ Gradle check result for b55ffb7: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

❌ Gradle check result for b55ffb7: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

@github-actions
Copy link
Contributor

❌ Gradle check result for b55ffb7: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Instead of using java.io.File, we can use java.nio.Path for a cleaner,
more modern Java I/O experience.

Signed-off-by: Michael Froh <msfroh@apache.org>
Signed-off-by: Michael Froh <msfroh@apache.org>
@msfroh msfroh force-pushed the use_nio_file_apis branch from b55ffb7 to 22ded2f Compare October 23, 2025 23:28
@github-actions
Copy link
Contributor

❌ Gradle check result for 22ded2f: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants