import org.codelibs.fess.exception.FessSystemException;
import org.codelibs.fess.util.ComponentUtil;

/**
 * Helper class for controlling crawler execution intervals and timing.
 * This class manages crawler execution timing based on configurable rules
 * that can specify different delays for different time periods and days.
 */
public class IntervalControlHelper {

/**
 * FessIntervalController extends DefaultIntervalController to provide
 * Fess-specific interval control functionality for web crawling operations.
 * This controller manages delays and timing for various crawling states
 * including processing delays, queue waiting times, and new URL discovery.
 */
public class FessIntervalController extends DefaultIntervalController {

 *   <li>Thread pool management for crawler execution</li>
 *   <li>Session-based crawling with cleanup operations</li>
 *   <li>Old document deletion after successful crawling</li>
 *   <li>Crawling execution monitoring and timing</li>
 * </ul>
 */
public class DataIndexHelper {

    /** Logger instance for this class */
    private static final Logger logger = LogManager.getLogger(DataIndexHelper.class);

    }

    /**
     * Creates a QueryResponseList containing the search results and metadata.
     * Wraps the document list with additional information about the search operation
     * including record counts, timing, and pagination details.
     *
     * @param documentList the list of search result documents
     * @param allRecordCount the total number of records found

- Use proper authentication header:
  ```bash
  curl -u admin:admin ...
  # or
  curl -H "Authorization: Basic YWRtaW46YWRtaW4=" ...
  ```

#### Issue: Large bulk imports timing out

**Solution**:
- Split large files into smaller batches (e.g., 10,000 docs per file)
- Increase timeout in `system.properties`:
  ```properties
  crawler.document.request.timeout=600000
  ```

import java.util.stream.Stream;

import javax.naming.Context;
import javax.naming.NamingEnumeration;
import javax.naming.NamingException;
import javax.naming.directory.Attribute;
import javax.naming.directory.Attributes;
import javax.naming.directory.BasicAttribute;
import javax.naming.directory.BasicAttributes;
import javax.naming.directory.DirContext;
import javax.naming.directory.InitialDirContext;

- **Strategy**: Normalizer, ReadingConverter, ContentsParser
- **Deferred/Promise**: Async operations

### Index Alias Strategy

Zero-downtime index updates using dual aliases:

```
Index Naming: {baseIndex}.{timestamp}
Example:      my-suggest.20250123120000

Aliases:
├── Search Alias: {baseIndex}          (read operations)
└── Update Alias: {baseIndex}.update   (write operations)
```

4. **Edge Cases**: Null, empty, and boundary conditions are covered
5. **Resources**: Test resources are properly managed and cleaned up

## Contributing

When adding new tests:
1. Follow the existing naming convention: `test_<method>_<scenario>_<expectedResult>`
2. Add clear JavaDoc comments explaining the test purpose
3. Ensure tests are independent and can run in any order

                extractFile(ent.getKey(), embeddedFile, writer);
            }
        }
    }

    /**
     * Gets the embedded file from a file specification, trying different platform-specific variants.
     * @param fileSpec the file specification
     * @return the embedded file, or null if not found
     */

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
2. Understand root cause
3. Minimal changes
4. Verify no regressions

### When Refactoring

1. Preserve behavior
2. Keep tests green