update:
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.
(ESRegistryCacheInvalidator) Exception in thread
"ESRegistryCacheInvalidator" java.lang.RuntimeException:
java.lang.Exception: Failed to create index: 'apiman_gateway' Reason:
{"root_cause":
}],"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]"}}
On Mon, Sep 17, 2018 at 5:03 PM Balu S <sbalu27(a)gmail.com> wrote:
Hello,
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 ?
Thanks
Balu