Quantity normalization and Elasticsearch conf for JPA Server starter V8.6.0-1

[Xiaocheng Luan]

Hi,

This is about the application.yaml for the JPA server starter V 8.6.0-1. 

I noticed that this quantity normalization configuration is gone:

    normalized_quantity_search_level

Is it still supported?  Also, the Elasticsearch configuration (connection) section is gone, too, even though the rest of the file and readme doc seem to suggest that Elasticsearch is still supported.

Could you please help clarify/elaborate on HAPI's position on current and future support for these two items?

Thanks!

Xiaocheng 

[James Agnew]

Both of these things are definitely still supported by HAPI, fwiw... Not sure why they would have disappeared from the starter project YAML. Any idea when/which commit removed them?

--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hapi-fhir+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hapi-fhir/CAEsMcbtM1od_o_ar7dUKoQffLGTatxXXcH%2B%3DaoC2KsrVuq_a%2BQ%40mail.gmail.com.

[Xiaocheng Luan]

Thanks, James - here is another update:

The Elasticsearch conf entries were removed from application.yaml during the changes from v8.4.0-2 to v8.4.0-3. The common/ElasticsearchConfig.java has also been dropped, and added jpa/starter/elastic/, 

It appears that the configuration is now through the spring. I was able to make it connect to Elasticsearch by configuring it through spring.

However, I got a new error during HAPI FHIR (JPAServer with tomcat) that complained about max_ngram_diff (details enclosed below). I'm not seeing the max_ngram_diff exposed in the configurations. Any suggestions? 

Also, I have not been able to figure out what's the new way to configure "normalized_quantity_search_level", which is also dropped from application.yaml.

Thanks,

Xiaocheng

PS: The error message:

{
                        "type": "illegal_argument_exception",
                        "reason": "The difference between max_gram and min_gram in NGram Tokenizer must be less than or equal to: [1] but was [17]. This limit can be set by changing the [index.max_ngram_diff] index level setting."
}