Issue 331 performance es refresh

See #331.

The elasticsearch index is set to no refresh while indexing. When indexing is finished, the index is set to refresh and optimize.
Strange - I just pushed (not forced) another commit where I remove this
reassignment and can't see your comment now any longer!?

Fabian Steeg wrote on 30.07.2014 16:50 :

>> +					.put("client.transport.ping_timeout", 20, TimeUnit.SECONDS)
>> +					.put("index.refresh_interval", -1);
>> +			Client client =
>> +					new TransportClient(settingsBuilder)
>> +							.addTransportAddress(new InetSocketTransportAddress(args[2], 9300));
>> +			CloseIndexRequestBuilder cirb =
>> +					client.admin().indices().prepareClose("_all");
>> +			CloseIndexResponse closeIndexResponse = cirb.execute().actionGet();
>> +			if (!closeIndexResponse.isAcknowledged())
>> +				LOG.warn("Could not close index[es].");
>> +			// then, make an update setting request to set off refresh intervall
>> +			final UpdateSettingsRequest updateSettingsRequest =
>> +					new UpdateSettingsRequest().settings(settingsBuilder);
>> +			client =
>> +					new TransportClient(settingsBuilder)
>> +							.addTransportAddress(new InetSocketTransportAddress(args[2], 9300));
> 
> Why the reassignment of `client` here? Seems to be exactly the same as 10 lines above.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/lobid/lodmill/pull/519/files#r15588102
>