[ https://issues.jboss.org/browse/TEIID-3314?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3314: ----------------------------------- Van, after looking into this a little bit more I agree the REST would be a better approach than using the Java client. We put together a quick internal prototype using the Java client and there were a couple of downsides. * No way to do authentication. Most people seem to put ES behind Apache/Nginx to add basic auth, but this is not possible using the Java client (at least, not without using an addon like Shield). * The module was 40-50mb because it included Lucene. It's possible that this could be stripped down slightly. * Unclear if this approach would be portable between different server versions, since the Java client is essentially another server node in the cluster AFAICT. We used the mappings API for metadata. One issue we ran into here is that ES does not distinguish between scalar and array values, so handling these fields automatically is difficult. TEIID-3349 might help here, or perhaps taking an approach similar to the Accumulo translator (query first record and then parse metadata from that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)