[Java] Ensure Flight with native Netty transport is actually being tested
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
There's only one test that exercises the domain socket path and it appears it's getting skipped on CI
```
[INFO] Running org.apache.arrow.flight.TestServerOptions
Warning: Tests run: 5, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.024 s - in org.apache.arrow.flight.TestServerOptions
```
We should make sure this test works and figure out whatever Maven magic we need to get the right dependencies on the right platforms
**Reporter**: [David Li](https://issues.apache.org/jira/browse/ARROW-17024) / @lidavidm
**Note**: *This issue was originally created as [ARROW-17024](https://issues.apache.org/jira/browse/ARROW-17024). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
Start by running org.apache.arrow.flight.TestServerOptions and checking why the domain socket test is skipped in CI. Inspect the Maven configuration and platform-specific dependencies for native Netty transport. Done means the test executes successfully, rather than being skipped, on the applicable CI platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100