Hi Peter, I don't see any magic solution with your current structure but it would be easier if you structure your data in the opposite way: - Index one document per user with all users information (firstname, lastname, uid, ...) - On each user object add the list of your document ID that the user owns in a 'documents' attribute
In that case, you are now in a standard usecase where you can use a prefix query or ngram and filter by document ID (prefix query and ngrams are well covered here: http://jontai.me/blog/2013/02/adding-autocomplete-to-an-elasticsearch-search-application/) Best Julien -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Facet-autocomplete-for-field-with-multiple-values-tp4046865p4046932.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1388660153419-4046932.post%40n3.nabble.com. For more options, visit https://groups.google.com/groups/opt_out.
