[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086704#comment-17086704 ] Cihad Guzel commented on CONNECTORS-1639: - I have tested the patch. Connector maven build is

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086693#comment-17086693 ] Karl Wright commented on CONNECTORS-1639: - The pom diff you included looks fine. Once

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086677#comment-17086677 ] Michael Cizmar commented on CONNECTORS-1639: Right.  If you upgrade/remove the library

[jira] [Commented] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086674#comment-17086674 ] Karl Wright commented on CONNECTORS-1639: - [~michaelcizmar] Cihad Guzel has made some

Re: Release schedule

I've updated the ticket with the changes: https://issues.apache.org/jira/projects/CONNECTORS/issues/CONNECTORS-1639 On Sat, Apr 18, 2020 at 3:59 PM Cihad Guzel wrote: > Thanks folks for your information. > > I reviewed the pom.xml of the ES connector. It uses an old elastic search > version

[jira] [Updated] (CONNECTORS-1639) Upgrade Elastic Search Version

[ https://issues.apache.org/jira/browse/CONNECTORS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Cizmar updated CONNECTORS-1639: --- Attachment: CONNECTORS-1639.diff > Upgrade Elastic Search Version >

Re: Release schedule

Thanks folks for your information. I reviewed the pom.xml of the ES connector. It uses an old elastic search version as dependency. It misled me. On the other hand, you are right. I agree with your thoughts on this matter. It is best if we can rearrange them. Kind regards, Cihad Guzel Karl

Re: Release schedule

I can help with Ant tasks but I need information as to how you're supposed to start the ES instance. An ant task snippet would be sufficient I think. On Sat, Apr 18, 2020 at 10:33 AM Michael Cizmar wrote: > I believe so. I only modified the Pom in the es connector project and > removed the

Re: Release schedule

I believe so. I only modified the Pom in the es connector project and removed the Node references. I know there is a way to do this in ant as well. I will look it up but may need some guidance on Ant. Get Outlook for iOS From: Karl

Re: Release schedule

Hi Michael, This has to run under Ant as well. Any way to make that happen? Karl On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar 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

Re: Release schedule

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.(JvmInfo.java:77) at

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

Re: Release schedule

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

Re: Release schedule

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

Re: Release schedule

Right. The issue is that the unit tests rely on embedding an elasticsearch instance which is officially deprecated: https://www.elastic.co/blog/elasticsearch-the-server There are integration methods using ESIntegTestCase. I'm looking if we can quickly refactor to utilize that or the unit

Re: Release schedule

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:

Re: Release schedule

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 , 18 Nis 2020 Cmt, 11:41 tarihinde şunu yazdı: > Hi all, > >

Release schedule

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.