Nuno Santos created OAK-9862:
--------------------------------
Summary: Some tests in oak-search are not cleaning up Elastic
Search indexes after the test
Key: OAK-9862
URL: https://issues.apache.org/jira/browse/OAK-9862
Project: Jackrabbit Oak
Issue Type: Improvement
Components: indexing
Reporter: Nuno Santos
Several of the Elastic tests that are based on the common tests in
{{oak-search}} are not cleaning up the indexes they create. They should clean
up the indexes.
When the tests are run with a disposable Elastic container started by the
tests, this is not much of an issue because these will all be cleaned at the
end of the test run when the container is terminated. But when running with an
external Elastic instance, the indexes accumulate and eventually have to be
deleted manually.
Running with an external instance is convenient for development, as it speeds
up the tests significantly (no waiting for ES container to start) and it allows
to inspect the indexes directly using Kibana. So having to periodically delete
all these stale indexes left by the tests are a bit of a nuisance.
And even when running with a disposable container, leaving indexes from
previous tests is not a good practice and can cause issues (maybe it can lead
to slowdowns if there are too many indexes).
As far as I checked, all the {{*CommonTests}} in package
{{org.apache.jackrabbit.oak.plugins.index}} do not delete the Elastic indexes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
