There is a check in
Caused by: java.lang.UnsupportedOperationException: Boot class path mechanism
is not supported
at
java.management/sun.management.RuntimeImpl.getBootClassPath(RuntimeImpl.java:99)
at org.elasticsearch.monitor.jvm.JvmInfo.<clinit>(JvmInfo.java:77)
at
org.elasticsearch.node.internal.InternalNode.<init>(InternalNode.java:132)
at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:159)
at org.elasticsearch.node.NodeBuilder.node(NodeBuilder.java:166)
In the 2.0 because in the integration test it is creating an Elastic node to
submitted to. Embedding ES is not supported by Elastic so they have made this
difficult to do. We really do not need to do this anyway. You can spin up
an ES instance outside via a Maven Plugin. The unit tests code calls ES
directly so with that, you can upgrade the libraries and it works on the later
versions and Java 11.
I’ll clean up what I worked on and submitted it for consideration.
Michael
From: Furkan KAMACI <[email protected]>
Date: Saturday, April 18, 2020 at 9:04 AM
To: Michael Cizmar <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: Release schedule
Hi,
By the way, when I check the error here:
https://issues.apache.org/jira/secure/attachment/12997363/elastic-search-1.0.1-java11-build-error.log
Seems that it is not specific to Java 11:
https://stackoverflow.com/questions/46636954/elasticsearch-1-1-2-not-starting-properly
Upgrading ES to minimum Java 9 support version which is 6.2.x can be fine:
https://www.elastic.co/de/support/matrix#matrix_jvm
Kind Regards,
Furkan KAMACI
On Sat, Apr 18, 2020 at 4:49 PM Michael Cizmar
<[email protected]<mailto:[email protected]>> wrote:
I've got a fix for this. I switched to using a Maven plugin that spins up an
Elasticsearch instance. With this, you need only to remove the Node code in
the integration tests. Tested with 6.x client and 7.x elasticsearch.
There are more things we can do with this output plugin in the future like
moving to the SDK.
M
On 4/18/20, 8:32 AM, "Karl Wright"
<[email protected]<mailto:[email protected]>> wrote:
Thanks for the quick reply.
I agree we don't want to turn off the ES connector itself, but yes we will
need to shut down the tests. Cihad, would you like to propose a strategy
for that? I think for now just marking them with @Ignore should be OK,
since the tests don't have compile time dependencies on missing classes.
What do you think?
Upgrading to ES 6.x is obviously the right thing to do but who here has the
knowledge to do a good job with this? I am certain there are a number of
ES users lurking on this list. Please volunteer if so.
Karl
On Sat, Apr 18, 2020 at 9:15 AM Furkan KAMACI
<[email protected]<mailto:[email protected]>>
wrote:
> Hi,
>
> There is a compatibility matrix for Elasticsearch. We need to support at
> least Elasticsearch 6.5.x for Java 11 support. You can check it from here:
> https://www.elastic.co/de/support/matrix#matrix_jvm
>
> @Cihad
>
> As far as I know, current support is not 2.0.0. It is 5.5.2:
> https://github.com/apache/manifoldcf-integration-elasticsearch-5.5
>
> @Karl Wright <[email protected]<mailto:[email protected]>>
>
> So, such an upgrade from 5.5.2 to 6.5.x may not be so painful. Committers
> who use ES can comment on this.
>
> My comments:
>
> +1 to temporarily turning those tests off
> -1 to temporarily turning the connector off
>
> Kind Regards,
> Furkan KAMACI
>
> On Sat, Apr 18, 2020 at 3:27 PM Cihad Guzel
<[email protected]<mailto:[email protected]>> wrote:
>
>> Hi Karl,
>>
>> MFC ES Connector uses the Elastic Search 2.0.0 . It's an ancient version.
>> The latest version is 7.6.2 . So, I agree with you and I think we can
>> temporarily turn the connector off.
>>
>> +1
>>
>> Kind Regards,
>> Cihad Güzel
>>
>>
>> Karl Wright <[email protected]<mailto:[email protected]>>, 18 Nis 2020
Cmt, 11:41 tarihinde şunu
>> yazdı:
>>
>> > Hi all,
>> >
>> > We're due to release ManifoldCF 2.16 by April 30th. The major work for
>> > this release was adoption of Java 11, and that work is incomplete
>> because
>> > of ElasticSearch incompatibilities. I'm therefore tempted to hold the
>> > release until we at least have a plan for dealing with ES going
forward.
>> >
>> > It's not clear that our ES connector support is affected, but certainly
>> our
>> > integration tests are, because Java 11 isn't supported in any of the ES
>> > versions we run for those tests. So at the least we need to decide to
>> turn
>> > those off. And indeed, we really need to have someone with ES
>> experience
>> > map a strategy for getting our ES support back into compliance with
>> what's
>> > out in the world at large now. Cihad Guzel did much work on Java 11
but
>> > stumbled over the Elastic Search problem. Any of our committers who
>> know
>> > ES and are stuck inside at the moment, please speak up.
>> >
>> > Thanks in advance,
>> > Karl
>> >
>>
>
