<packaging.fess.group>fess</packaging.fess.group>
		<packaging.fess.pid.dir>/var/run/fess</packaging.fess.pid.dir>
		<packaging.fess.systemd.dir>/usr/lib/systemd/system</packaging.fess.systemd.dir>
		<packaging.fess.systemd.sysctl.dir>/usr/lib/sysctl.d</packaging.fess.systemd.sysctl.dir>
		<packaging.fess.tmpfilesd.dir>/usr/lib/tmpfiles.d</packaging.fess.tmpfilesd.dir>

- Added kubelet support for systemd watchdog integration. With this enabled, systemd can automatically recover a hung kubelet. ([#127566](https://github.com/kubernetes/kubernetes/pull/127566), [@zhifei92](https://github.com/zhifei92)) [SIG Cloud Provider, Node and Testing]

- The `SystemdWatchdog` feature gate has been locked to default and will be removed in future release. The systemd watchdog functionality in `kubelet` can be enabled via systemd without any feature gate configuration. See the [systemd watchdog documentation](https://kubernetes.io/docs/reference/node/systemd-watchdog/) for more information. ([#134691](https://github.com/kubernetes/kubernetes/pull/134691), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev))...

Shinsuke Sugaya <******@****.***> 1763013292 +0900

- **Apache Solr** - Document import via REST API
- **Database Systems** - Direct connection via DataStore plugins
- **File Systems** - SMB, FTP, local file crawling
- **Custom Systems** - REST API for bulk document indexing

---

## Pre-Migration Planning

### 1. Assessment Phase

Before starting migration, assess your current system:

- **Document Count**: Total number of indexed documents

labels.system_info_configuration=Informacje o systemie
labels.system_info_env_title=Właściwości zmiennych środowiskowych
labels.system_info_prop_title=Właściwości systemu
labels.system_info_fess_prop_title=Właściwości aplikacji
labels.system_info_bug_report_title=Właściwości raportu o błędach
labels.system_info_system_properties_does_not_exist=system.properties nie istnieje. Zostaną zastosowane wartości domyślne.

    version number is enough for some build systems (notably, Gradle) to select
    that empty artifact over the "real" listenablefuture-1.0 -- avoiding a
    conflict with the copy of ListenableFuture in guava itself. If users are
    using an older version of Guava or a build system other than Gradle, they
    may see class conflicts. If so, they can solve them by manually excluding

 * It manages the crawling lifecycle, including initialization, execution coordination,
 * monitoring, and cleanup operations.
 *
 * <p>The crawler can operate in different modes based on command-line options:
 * <ul>
 * <li>Web crawling - crawls web sites and web content</li>
 * <li>File system crawling - crawls file systems and documents</li>

    private static final Logger logger = LogManager.getLogger(CrawlJob.class);

    /**
     * The namespace identifier for the crawling session.
     * Used to organize and identify crawling activities in the system.
     * Defaults to the system crawling info name.
     */
    protected String namespace = Constants.CRAWLING_INFO_SYSTEM_NAME;

    /**
     * Array of web crawling configuration IDs to process.

labels.failure_url_file_config_name=Dosya Tarama Yapılandırması
labels.system_info_configuration=Sistem Bilgisi
labels.system_info_env_title=Ortam Değişkeni Özellikleri
labels.system_info_prop_title=Sistem Özellikleri
labels.system_info_fess_prop_title=Uygulama Özellikleri
labels.system_info_bug_report_title=Hata Raporu Özellikleri
labels.system_info_system_properties_does_not_exist=system.properties mevcut değil. Varsayılan değerler uygulanır.