nio.Paths and nio.Files package are used in StringHelper, but they are restricted in many infrastructure and platforms [LUCENE-7036]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
nio.Paths and nio.Files package are used in StringHelper, but they are restricted in many infrastructure and platforms like Google App Engine.
The use of Paths and Fiiles are not related to the main function of Lucene.
It's better to provide an interface to store system properties instead of using File API in String Helper directly.
---
Migrated from [LUCENE-7036](https://issues.apache.org/jira/browse/LUCENE-7036) by Forrest Sun
Contributor guide
Research direction
Locate StringHelper and inspect how nio.Paths and nio.Files are used there, along with the surrounding system-property handling. Compare those uses with the issue's stated platform restrictions; the work is complete when StringHelper no longer directly depends on the restricted File API and system properties can be provided through an interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100