Hi, Elasticsearch doesn't have a concept of joining or foreign keys, so the connection as you describe it isn't an option.
The best solution I've seen is to index the documents in a way where workerName and organizationName is in the same document, and a clever way of doing that would be to use workerID as the _id of the document in Elasticsearch. As additional information about the worker comes into the system, you will update document _id: 3940. Essentially, that merges new info with existing info. There may be field collisions, but it would only be a problem if the values are changing - then the integrity would be getting lost in the data.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.