**Key Test Areas**:
- Parameter handling (null, empty, missing)
- Special character handling
- Input stream validation (not consumption)
- Edge cases (long filenames, paths, whitespace)

**Test Count**: 10 tests

**Key Scenarios**:
- ✅ Valid filename extraction
- ✅ Null parameters handling
- ✅ Empty/missing resource name
- ✅ Special characters in filename (Japanese, paths)

        assertNotNull(pairs, "Decoded pairs should not be null");
        assertEquals(0, pairs.size(), "Should have no pairs");
    }

    /**
     * Test decode with missing EOL
     */
    @Test
    @DisplayName("Decode should throw exception when EOL is missing")
    void testDecodeMissingEOL() {
        byte[] flagData = new byte[4];
        SMBUtil.writeInt4(0x12345678, flagData, 0);

        client.admin().indices().prepareDelete(indexName).execute().actionGet();
        suggester.shutdown();
    }

    /**
     * Test getIndicesForAlias method with non-existing alias.
     * Verifies that the method returns an empty list for non-existing alias.
     */
    @Test
    @SuppressWarnings("unchecked")
    public void testGetIndicesForAlias_nonExistingAlias() throws Exception {

- [ ] Test pagination and sorting
- [ ] Validate security and access control

### Testing

- [ ] Functional testing of search queries
- [ ] Performance testing (response time, throughput)
- [ ] Security testing (authentication, authorization)
- [ ] Integration testing with client applications
- [ ] User acceptance testing
- [ ] Load testing for production capacity

### Go-Live

- [ ] Schedule maintenance window

    public String toString() {
        return "FacetInfo [field=" + Arrays.toString(field) + ", query=" + Arrays.toString(query) + ", size=" + size + ", minDocCount="
                + minDocCount + ", sort=" + sort + ", missing=" + missing + "]";
    }

    // Process
}  // Temp files auto-deleted
```

---

## Best Practices for AI Assistants

### When Adding Features

1. Read existing code first (use symbol overview tools)
2. Follow existing patterns
3. Add tests
4. Handle resources properly (try-with-resources)
5. Consider thread safety
6. Update JavaDoc

### When Fixing Bugs

1. Write failing test first

        System.err.println("Error: " + throwable.getMessage());
    });
```

## Advanced Usage

### Index from Existing Documents

```java
import org.codelibs.fess.suggest.index.contents.document.ESSourceReader;

// Index suggestions from existing Elasticsearch documents
DocumentReader reader = new ESSourceReader(
    client,
    suggester.settings(),

**Technology Stack:**
- Java 21+, Maven
- OpenSearch (provided dependency)
- Apache Lucene (query parsing, text analysis)
- ICU4J (Unicode text processing)
- JUnit 4 (testing)

**Repository:** https://github.com/codelibs/fess-suggest

---

## Architecture

### Package Structure

```
org.codelibs.fess.suggest/
├── Suggester.java              # Main entry point (Facade)

            final PathPattern pattern = new PathPattern(path);
            // Check if pattern already exists
            boolean exists = false;
            for (final PathPattern existing : allowedPaths) {
                if (existing.getPattern().equals(path)) {
                    exists = true;
                    break;
                }
            }
            if (!exists) {

    // A concrete implementation of the abstract NtlmServlet for testing purposes.
    private static class TestNtlmServlet extends NtlmServlet {
        private static final long serialVersionUID = 1L;

        @Override
        protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws ServletException, IOException {
            // Do nothing - just for testing
        }

        @Override