doc.put("intStr", "123");
        assertEquals(Integer.valueOf(123), DocumentUtil.getValue(doc, "intStr", Integer.class));

        doc.put("longStr", "123456789");
        assertEquals(Long.valueOf(123456789L), DocumentUtil.getValue(doc, "longStr", Long.class));

        doc.put("doubleStr", "123.45");
        assertEquals(Double.valueOf(123.45), DocumentUtil.getValue(doc, "doubleStr", Double.class));

Doing this provides the following specific benefits:
- **Reduce the API surface** - We no longer need to maintain two methods.
- **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
- **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages.

## Decision

      {
        "lang_tl": {
          "match": "*_tl",
          "mapping": {
            "type": "text",
            "analyzer": "empty_analyzer"
          }
        }
      },
      {
        "lang_tr": {
          "match": "*_tr",
          "mapping": {
            "type": "text",
            "analyzer": "turkish_analyzer"
          }
        }
      },
      {
        "lang_uk": {

      {
        "lang_tl": {
          "match": "*_tl",
          "mapping": {
            "type": "text",
            "analyzer": "empty_analyzer"
          }
        }
      },
      {
        "lang_tr": {
          "match": "*_tr",
          "mapping": {
            "type": "text",
            "analyzer": "turkish_analyzer"
          }
        }
      },
      {
        "lang_uk": {

      {
        "lang_tl": {
          "match": "*_tl",
          "mapping": {
            "type": "text",
            "analyzer": "empty_analyzer"
          }
        }
      },
      {
        "lang_tr": {
          "match": "*_tr",
          "mapping": {
            "type": "text",
            "analyzer": "turkish_analyzer"
          }
        }
      },
      {
        "lang_uk": {

        }
    }

    @Test
    public void test_startProcess_replaceExistingProcess() {
        String sessionId = "test_replace";
        // Use sleep commands that run longer so we can verify they're running
        List<String> cmdList1 = Arrays.asList("sleep", "10");
        List<String> cmdList2 = Arrays.asList("sleep", "10");
        Consumer<ProcessBuilder> pbCall = pb -> {

        assertNotNull(details);
        assertTrue(details.contains("Total: 1 event(s)"));
        assertTrue(details.contains("Something went wrong"));
        // Throwable is no longer included in summary-oriented format
        // Only log message is shown per event line
    }

    @Test
    public void test_formatDetails_emptyList() {

        indexUpdater.start();

        // Let it run briefly
        ThreadUtil.sleep(100);

        // Stop the indexer
        indexUpdater.setFinishCrawling(true);

        // Wait for completion with longer timeout
        indexUpdater.join(3000);

        assertFalse(errorOccurred.get());
        // Thread may still be alive in test environment, just check no errors

If they need to be renamed or removed (together or separately from the feature itself), they MUST go through a deprecation cycle and the actual property change MUST happen in a major release.
Since the naming of the properties no longer suggests they are experimental, we want to ensure users are aware if the current property stops having an effect.
Since the underlying feature is incubating, its actual behavior can still change or be removed in the minor releases.

labels.doc_score=Score:
labels.development_mode_warning=Fess is running in development mode. Please install OpenSearch separately in a production environment.
labels.eol_error=The system you are using is no longer supported. Please refer to the product support lifecycle page and upgrade.
labels.tooltip_search_view=Search Screen
labels.tooltip_run_crawler=Run Crawler
labels.tooltip_forum=Forum
labels.tooltip_onlinehelp=Help