<div dir="ltr"><div dir="ltr">update:<div><br><div>Apparently ES 6.x does not support the data type "string" so we cannot use ES 6.x. Apiman 1.5.1 must use ES 5.x and lesser. May be we should add this note to release guide for future readers.</div></div><div><br></div><div><div>(ESRegistryCacheInvalidator) Exception in thread "ESRegistryCacheInvalidator" java.lang.RuntimeException: java.lang.Exception: Failed to create index: 'apiman_gateway' Reason: {"root_cause":</div><div>}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [client]: No handler for type [string] declared on field [organizationId]","caused_by":{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [organizationId]"}}</div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Sep 17, 2018 at 5:03 PM Balu S <<a href="mailto:sbalu27@gmail.com">sbalu27@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>I am upgrading to latest Apiman 1.5.1 release from 1.3.x version. I noticed the ES is now migrated to 5.x (thanks for this change). But If I look in to ES product, the latest version is 6.x since early 2018. Is there any reason that Apiman can support only 5.x version ? I can think of one reason that embedded Jest client jar is 5.x version which makes it supported by ES 5.x version only ? </div><div><br></div><div>Thanks</div><div>Balu</div></div>
</blockquote></div>