# Problems with Java\_transport client tribe **URL:** \ **Category:** Elasticsearch\ **Created:** [September 9, 2016, 6:28pm UTC](https://discuss.elastic.co/t/problems-with-java-transport-client-tribe/60190 "2016-09-09T18:28:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![MarkOStewart](https://avatars.discourse-cdn.com/v4/letter/m/898d66/32.png) [@MarkOStewart](https://discuss.elastic.co/u/MarkOStewart)\ **Post date:** [September 9, 2016, 6:28pm UTC](https://discuss.elastic.co/t/problems-with-java-transport-client-tribe/60190/1 "2016-09-09T18:28:39Z")
I have a situation after updating to Elasticsearch to 2.3.5 (from 2.1) We have two clusters federated via tribe. To make things clear, one cluster we will call the tablet\_cluster and the other we will call site\_cluster. Before the update we had no issues with a java\_transport client getting documents using wildcards. (from either cluster via tribe transport node.) The java\_transport client jobs run out of talend and there are several java\_transport client calls to indices that run w/o error. There are six jobs that run nightly 1 process, the java\_transport client was successfully pulling documents from multiple indices using slp\_site\_sm\_\* wildcard call (from the site\_cluster) on 5 other processes, the java\_transport client was also pulling docs from the other tablet\_cluster using aliases and wildcard calls. (sv\_payment\_info, an alias and sv\_purchase\_\* a wildcard etc) After the update: The 5 jobs that run w/o error are all pointed to the tablet\_cluster using both aliases and wildcards. (sv\_payment\_info and sv\_purchase\_\*) The 1 job that errors out is a java\_transport client job that is pointed to slp\_site\_sm\_\* coming from the site\_cluster and is using a wildcard. If I change the call to an actual index name slp\_site\_sm\_06603\_2016218 it will pull data but obviously only from that index. We need a wildcard to pull data from all slp\_site\_sm\_\* matches. If I use sense and the http rest call I can get all documents using the wildcard call slp\_site\_sm\_\*. This is only an issue on transport for indices on the site\_cluster side using wildcard calls. It appears aliases work and so do real index names. I dont want to make a permenent bandaid by creating a alias for a bunch of indices. I really would like the \* wildcard in the transport to work as the http calls do. One more thing: I do get a message from Talend stating that the \_type tablets is not found. However using sense/REST commands on http I can retrieve over 6000 documents where type=tablets. Not sure if the error returned via talend (type tablets not found) is because it couldn't find the index or it finds the index and then cannot find that type. Hints and suggestions would be appreciated. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [September 11, 2016, 10:58am UTC](https://discuss.elastic.co/t/problems-with-java-transport-client-tribe/60190/2 "2016-09-11T10:58:56Z")
Is talend doing the integration? Was it updated along with your ES? ---
**Author:** ![MarkOStewart](https://avatars.discourse-cdn.com/v4/letter/m/898d66/32.png) [@MarkOStewart](https://discuss.elastic.co/u/MarkOStewart)\ **Post date:** [September 11, 2016, 4:03pm UTC](https://discuss.elastic.co/t/problems-with-java-transport-client-tribe/60190/3 "2016-09-11T16:03:10Z")
No talend change were made as far as I know. The JRE on the talend machine was updated to 1.8.0 as was the ELK cluster. There are many other jobs running out of Talend just this one process to get documents against the slp\_site\_sm\_\* wildcard is broken. ---
**Author:** ![MarkOStewart](https://avatars.discourse-cdn.com/v4/letter/m/898d66/32.png) [@MarkOStewart](https://discuss.elastic.co/u/MarkOStewart)\ **Post date:** [September 23, 2016, 2:59pm UTC](https://discuss.elastic.co/t/problems-with-java-transport-client-tribe/60190/4 "2016-09-23T14:59:36Z")
Figured this one out on my own. We had a project to change naming convention of a series of indices in order to make the alias and index names different. (so if people reindex and forget to remove the old index it doesn't get included w/o an alias. ) example we had indices with names similar to slp\_site\_sm\_06603\_2016218 and were in the process of reindexing/renaming them to sysmdl\_site\_06603\_2016218 with an alias of slp\_site\_sm\_06603 when talend called the wildcard slp\_site\_sm\_\* it not only matched the old index names we hadn't finished migrating to the new naming convention it also matched the new index's alias name slp\_site\_sm\_06603. I think this created a circular reference. I also found one index with a different schema and so one field had a data type mismatch. I re-aliased the indices I wanted talend to see with talend\_slp\_site\_sm\_06603 (or what numbers matched the other indices) to break up the match of wildcard slp\_site\_sm\_\* from the alias names. This seems to have fixed my issues. Clear as mud ? Mark ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:17pm UTC](https://discuss.elastic.co/t/problems-with-java-transport-client-tribe/60190/5 "2017-07-05T22:17:41Z")