Removing few lingering Elasticsearch strings in the repo (#6)

* Removing few lingering Elasticsearch strings in the repo

Signed-off-by: Sarat Vemulapalli <vemulapallisarat@gmail.com>

Author: saratvemulapalli

.eclipseformat.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <profiles version="17">
-    <profile kind="CodeFormatterProfile" name="Elasticsearch" version="17">
+    <profile kind="CodeFormatterProfile" name="OpenSearch" version="17">
         <setting id="org.eclipse.jdt.core.formatter.insert_space_after_ellipsis" value="insert"/>
         <setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations" value="insert"/>
         <setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_allocation_expression" value="do not insert"/>

.github/draft-release-notes-config.yml

@@ -1,6 +1,6 @@
 # The overall template of the release notes
 template: |
-  Compatible with Elasticsearch (**set version here**).
+  Compatible with OpenSearch (**set version here**).
   $CHANGES
 
 # Setting the formatting and sorting for the release notes body

.github/workflows/CI.yml

@@ -52,9 +52,9 @@ jobs:
 
             ## The ESRestTest Client uses http by default.
             ## Need to disable the security plugin to call the rest api over http.
-            echo "RUN if [ -d /usr/share/elasticsearch/plugins/opendistro-anomaly-detection ]; then /usr/share/elasticsearch/bin/elasticsearch-plugin remove opendistro-anomaly-detection; fi" >> Dockerfile
+            echo "RUN if [ -d /usr/share/opensearch/plugins/opendistro-anomaly-detection ]; then /usr/share/elasticsearch/bin/elasticsearch-plugin remove opendistro-anomaly-detection; fi" >> Dockerfile
             echo "ADD anomaly-detection/build/distributions/opendistro-anomaly-detection-$plugin_version.zip /tmp/" >> Dockerfile
-            echo "RUN /usr/share/elasticsearch/bin/elasticsearch-plugin install --batch file:/tmp/opendistro-anomaly-detection-$plugin_version.zip" >> Dockerfile
+            echo "RUN /usr/share/opensearch/bin/elasticsearch-plugin install --batch file:/tmp/opendistro-anomaly-detection-$plugin_version.zip" >> Dockerfile
 
             docker build -t odfe-ad:test .
             echo "imagePresent=true" >> $GITHUB_ENV

README.md

@@ -12,9 +12,9 @@ The Open Distro for Elasticsearch Anomaly Detection plugin enables you to levera
 
 Anomaly detection is using [Random Cut Forest (RCF) algorithm](https://github.com/aws/random-cut-forest-by-aws) for detecting anomalous data points.
 
-Anomaly detections run a scheduled job based on [job-scheduler](https://github.com/opendistro-for-elasticsearch/job-scheduler).
+Anomaly detections run a scheduled job based on [job-scheduler](https://github.com/opensearch-project/job-scheduler).
 
-You should use anomaly detection plugin with the same version of [Open Distro Alerting plugin](https://github.com/opendistro-for-elasticsearch/alerting). You can also create a monitor based on the anomaly detector. A scheduled monitor run checks the anomaly detection results regularly and collects anomalies to trigger alerts based on custom trigger conditions.
+You should use anomaly detection plugin with the same version of [OpenSearch Alerting plugin](https://github.com/opensearch-project/alerting). You can also create a monitor based on the anomaly detector. A scheduled monitor run checks the anomaly detection results regularly and collects anomalies to trigger alerts based on custom trigger conditions.
 
 ## Current Limitations
 * We will continuously add new unit test cases, but we don't have 100% unit test coverage for now. This is a great area for developers from the community to contribute and help improve test coverage.
@@ -82,7 +82,7 @@ The **test runner JVM** will start suspended and wait for a debugger to attach t
 
 ### Advanced: Launching multi node clusters locally
 
-Sometimes you need to launch a cluster with more than one Elasticsearch server process.
+Sometimes you need to launch a cluster with more than one OpenSearch server process.
 
 You can do this by running `./gradlew run -PnumNodes=<numberOfNodesYouWant>`
 

src/main/java/com/amazon/opendistroforelasticsearch/ad/transport/handler/AnomalyIndexHandler.java

@@ -70,7 +70,7 @@ public class AnomalyIndexHandler<T extends ToXContentObject> {
     /**
      * Abstract class for index operation.
      *
-     * @param client client to Elasticsearch query
+     * @param client client to OpenSearch query
      * @param settings accessor for node settings.
      * @param threadPool used to invoke specific threadpool to execute
      * @param indexName name of index to save to
@@ -184,15 +184,15 @@ void saveIteration(IndexRequest indexRequest, String detectorId, Iterator<TimeVa
                     .<IndexResponse>wrap(
                         response -> { LOG.debug(String.format(Locale.ROOT, SUCCESS_SAVING_MSG, detectorId)); },
                         exception -> {
-                            // Elasticsearch has a thread pool and a queue for write per node. A thread
+                            // OpenSearch has a thread pool and a queue for write per node. A thread
                             // pool will have N number of workers ready to handle the requests. When a
                             // request comes and if a worker is free , this is handled by the worker. Now by
                             // default the number of workers is equal to the number of cores on that CPU.
                             // When the workers are full and there are more write requests, the request
                             // will go to queue. The size of queue is also limited. If by default size is,
                             // say, 200 and if there happens more parallel requests than this, then those
                             // requests would be rejected as you can see OpenSearchRejectedExecutionException.
-                            // So OpenSearchRejectedExecutionException is the way that Elasticsearch tells us that
+                            // So OpenSearchRejectedExecutionException is the way that OpenSearch tells us that
                             // it cannot keep up with the current indexing rate.
                             // When it happens, we should pause indexing a bit before trying again, ideally
                             // with randomized exponential backoff.

src/main/java/com/amazon/opendistroforelasticsearch/ad/util/ClientUtil.java

@@ -247,7 +247,7 @@ public boolean hasRunningQuery(AnomalyDetector detector) {
 
     /**
      * Cancel long running query for given detectorId
-     * @param client Elasticsearch client
+     * @param client OpenSearch client
      * @param detectorId Anomaly Detector Id
      * @param LOG Logger
      */

src/main/java/com/amazon/opendistroforelasticsearch/ad/util/ExceptionUtil.java

@@ -29,10 +29,10 @@ public class ExceptionUtil {
         .getExceptionName(new ResourceNotFoundException("", ""));
 
     /**
-     * Elasticsearch restricts the kind of exceptions can be thrown over the wire
+     * OpenSearch restricts the kind of exceptions can be thrown over the wire
      * (See OpenSearchException.OpenSearchExceptionHandle). Since we cannot
      * add our own exception like ResourceNotFoundException without modifying
-     * Elasticsearch's code, we have to unwrap the remote transport exception and
+     * OpenSearch's code, we have to unwrap the remote transport exception and
      * check its root cause message.
      *
      * @param exception exception thrown locally or over the wire

src/main/resources/plugin-descriptor.properties

@@ -18,10 +18,10 @@ description=${project.description}
 
 version=${project.version}
 
-name=${elasticsearch.plugin.name}
+name=${opensearch.plugin.name}
 
-classname=${elasticsearch.plugin.classname}
+classname=${opensearch.plugin.classname}
 
 java.version=1.8
 
-elasticsearch.version=${elasticsearch.version}
+opensearch.version=${opensearch.version}