inde
> > > şunu
> > > > > yazdı:
> > > > >
> > > > > > 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
> > > > >
> > > > >
> > > > > On Sat, Apr 18, 2020 at 10:33 AM Michael Cizmar <
> > > > > michael.ciz...@mcplusa.com>
> > > > > wrote:
> > > > >
> > > > > > I believe so. I only modified the Pom in the es connector
>
10:33 AM Michael Cizmar <
> > > > michael.ciz...@mcplusa.com>
> > > > wrote:
> > > >
> > > > > I believe so. I only modified the Pom in the es connector project
> > and
> > > > > removed the Node references. I know t
> > > > 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<https://aka.ms/o0ukef>
> > > >
> > > > F
> Get Outlook for iOS<https://aka.ms/o0ukef>
> > >
> > > From: Karl Wright
> > > Sent: Saturday, April 18, 2020 9:15:15 AM
> > > To: dev
> > > Subject: Re: Release schedule
> > >
> > >
gt; >
> > Get Outlook for iOS<https://aka.ms/o0ukef>
> >
> > From: Karl Wright
> > Sent: Saturday, April 18, 2020 9:15:15 AM
> > To: dev
> > Subject: Re: Release schedule
> >
> > Hi Michael,
> > This has to run under
15 AM
> To: dev
> Subject: 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
: Karl Wright
Sent: Saturday, April 18, 2020 9:15:15 AM
To: dev
Subject: 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 t
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
versions and Java 11.
I’ll clean up what I worked on and submitted it for consideration.
Michael
From: Furkan KAMACI
Date: Saturday, April 18, 2020 at 9:04 AM
To: Michael Cizmar
Cc: "dev@manifoldcf.apache.org"
Subject: Re: Release schedule
Hi,
By the way, when I check the error he
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
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
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
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
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:
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,
>
>
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.
, Karl Wright wrote:
Hi All,
Our quarterly release schedule means that we'll need to code-freeze what is
in 1.3 in about 1 month.
There is currently a *lot* of outstanding activity that needs to solidify
between now and then, and I'm not likely to be able to get done with
everything currently assigned
18 matches
Mail list logo
