title: Hibernate search elasticsearch schema management NONE still connects to elasticsearch?
body: <p>I'm looking into moving our hibernate search implementation from file-based lucene indices to elasticsearch, but am confused about the documentation. Specifically, for the index schema management strategy NONE:</p>
  
  <blockquote>
    <p>The index, its mappings and the analyzer definitions will not be created, deleted nor altered. Hibernate Search will not even check that the index already exists.</p>
  </blockquote>
  
  <p>We want to remove the startup dependency of hibernate search (so it won't try and query elasticsearch at startup). Reading the schema management strategies indicates that NONE should do that.</p>
  
  <p>However, looking at the implementation of the code, I can see that it still explicitly checks if the index exists:</p>
  
  <pre class="lang-java prettyprint-override"><code>if (this.schemaManagementStrategy == IndexSchemaManagementStrategy.NONE) {
      this.schemaCreator.checkIndexExists(this.actualIndexName, this.schemaManagementExecutionOptions);
      return false;
  }
  </code></pre>
  
  <p>I would've expected that this didn't happen. When I entered a purposely incorrect host to connect to, server startup still fails with:</p>
  
  <pre><code> Request:
  ========
  Operation: IndicesExists
  URI: registryreference
  Data:
  null
  Response:
  =========
  null
      at org.hibernate.search.elasticsearch.client.impl.JestClient.executeRequest(JestClient.java:188) ~[hibernate-search-elasticsearch-5.6.5.Final.jar:5.6.5.Final]
  ... (omitted rest of stack) 
  Caused by: java.net.ConnectException: Connection refused: connect
  </code></pre>
  
  <p>We are using hibernate search 5.6.5 and elasticsearch 2.4.6.</p>