Hi Jorg, I wanted a single ES document, i have a primary table that has unique id's and the names is a 1:N relation, and the address is a 1:N relation
reason being is we will need to search on names and addresses to try to find the unique ID for the individual so we can do further processing how could I search over several indicies and merge those results back together to give the one unique id that best matches? my initial test of splitting these apart into different indicies is showing addresses and entities littered in the same result set, i havent any idea how to get a commonality between them the addresses and names dont really have unique identifiers of their own, they are sequenced by the primary ID, example: if the primary table ID is '1001', and he has three addresses then the unqiue ID for those rows would be id='1001', sequence='1', id='1001', sequence='2', ... etc -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/JDBC-river-query-results-collapsing-to-JSON-issue-tp4054562p4054576.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1398192809993-4054576.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
