pelias/api - api - CogtoSrc

Author	SHA1	Message	Date
Julian Simioni	b1107a0c8f	fix(autocomplete): detect the case where input text is unsubstantial It's possible for the `text` input to /v1/autocomplete to be of non-zero length after trimming whitespace and quotes, but still be insufficient to use for geocoding. One common case is that it contains only commas, slashes, or other delimiters. Our query logic currently does not handle this case, and will generate Elasticsearch queries that do not have a primary `must` clause and end up searching every document in the index. These queries are slow, take up cluster resources, and are not useful. By detecting unsubstantial inputs, we can prevent this.	6 years ago
Lily He	13a7b42de7	Standardize sanitizers to export setup function that returns sanitize and expected function	8 years ago
Stephen Hess	3763d0b503	renamed `sanitise` -> `sanitize`	8 years ago
Peter Johnson	52c35cb37d	allow single non-numeric chars, change boost_mode to 'replace' for function_score queries	9 years ago
missinglink	05240626fd	handle addressit case where parsed_text.street is produced and parsed_text.name is not	9 years ago
missinglink	ee73774c89	add tokenizer, refactor how we determine if a token is 'complete' or 'incomplete'	9 years ago