Re: Release schedule
I can try this one out: https://david.pilato.fr/blog/2016/10/18/elasticsearch-real-integration-tests-updated-for-ga/ Based on a review, this would seem to accomplish that. There’s no remote shutdown afaik. You can download, unpack and then start elastic with the commands necessary via the command line. You then wait until it responds on 9200 and you write out the PID. Terminating it means killing the PID. On Thu, Apr 23, 2020 at 6:55 AM Karl Wright wrote: > The problem with running anything under Ant is that it's not set up for > this kind of flow: > > - start service > - run tests > - stop service > > Ant is about building and is not a sequential language, so starting this > under Ant is the wrong idea. > > Instead, we can invoke scripts at will from within the java test class > itself. But we need both Linux and Windows scripts for that, and we > download only one ES instance, and therefore we get only one kind of script > to go with it. > > I supposed I can platform-conditionalize the download itself so we get > different scripts for different platforms. Since ES doesn't include all > script variants in every download we're kind of stuck with this it seems. > > The other issue we have to address is waiting for ES to actually fully > start. I believe the code we had did this via a specific HTTP Get > request fired at the instance, so maybe we can reuse that code. There may > also be a way to shut ES down via a similar HTTP Get mechanism. > > Can you verify that waiting for ES to come up and shutting down ES can be > done with the same mechanism as is currently in the test code? > > Karl > > > On Thu, Apr 23, 2020 at 7:44 AM Michael Cizmar > wrote: > > > Karl, > > > > I found this: > > > > > https://gquintana.github.io/2016/11/30/Testing-a-Java-and-Elasticsearch-50-application.html > > > > Which should solve the issue of running elastic in the background via > Ant. > > > > I can also provide a simple setup script (sh) if that helps as well. > > > > Michael > > > > On Wed, Apr 22, 2020 at 12:35 PM Karl Wright wrote: > > > > > I looked into trying to get things working under Ant and created a > branch > > > CONNECTORS-1639 containing some changes relating to download of > > > elasticsearch artifacts. I did a little exploration as to whether we > > could > > > use the Elasticsearch Runner package to start a cluster, but that is > > really > > > painful because it has a ton of dependencies, so I think I'll just try > > > calling the main class that the ES startup script uses and see how we > do > > > that way. > > > > > > But I'm snowed under with work related tasks again so it will have to > > wait. > > > > > > Karl > > > > > > > > > On Sat, Apr 18, 2020 at 5:52 PM Michael Cizmar < > > mich...@michaelcizmar.com> > > > wrote: > > > > > > > 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 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 Wright , 18 Nis 2020 Cmt, 17:49 tarihinde > > > ş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 > > I > > > > > think. > > > > > > > > > > > > > > > > > > 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 > > project > > > > and > > > > > > > removed th
Re: Release schedule
The problem with running anything under Ant is that it's not set up for this kind of flow: - start service - run tests - stop service Ant is about building and is not a sequential language, so starting this under Ant is the wrong idea. Instead, we can invoke scripts at will from within the java test class itself. But we need both Linux and Windows scripts for that, and we download only one ES instance, and therefore we get only one kind of script to go with it. I supposed I can platform-conditionalize the download itself so we get different scripts for different platforms. Since ES doesn't include all script variants in every download we're kind of stuck with this it seems. The other issue we have to address is waiting for ES to actually fully start. I believe the code we had did this via a specific HTTP Get request fired at the instance, so maybe we can reuse that code. There may also be a way to shut ES down via a similar HTTP Get mechanism. Can you verify that waiting for ES to come up and shutting down ES can be done with the same mechanism as is currently in the test code? Karl On Thu, Apr 23, 2020 at 7:44 AM Michael Cizmar wrote: > Karl, > > I found this: > > https://gquintana.github.io/2016/11/30/Testing-a-Java-and-Elasticsearch-50-application.html > > Which should solve the issue of running elastic in the background via Ant. > > I can also provide a simple setup script (sh) if that helps as well. > > Michael > > On Wed, Apr 22, 2020 at 12:35 PM Karl Wright wrote: > > > I looked into trying to get things working under Ant and created a branch > > CONNECTORS-1639 containing some changes relating to download of > > elasticsearch artifacts. I did a little exploration as to whether we > could > > use the Elasticsearch Runner package to start a cluster, but that is > really > > painful because it has a ton of dependencies, so I think I'll just try > > calling the main class that the ES startup script uses and see how we do > > that way. > > > > But I'm snowed under with work related tasks again so it will have to > wait. > > > > Karl > > > > > > On Sat, Apr 18, 2020 at 5:52 PM Michael Cizmar < > mich...@michaelcizmar.com> > > wrote: > > > > > 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 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 Wright , 18 Nis 2020 Cmt, 17:49 tarihinde > > ş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 > I > > > > think. > > > > > > > > > > > > > > > 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 > 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<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 Ant as well. Any way to make that happen? > > > > > > > > > > > > Karl > > > > > > > > > > > > > > > > > > On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar < > > > > > michael.ciz...@mcplusa.com > > > > > > > > > > >
Re: Release schedule
Karl, I found this: https://gquintana.github.io/2016/11/30/Testing-a-Java-and-Elasticsearch-50-application.html Which should solve the issue of running elastic in the background via Ant. I can also provide a simple setup script (sh) if that helps as well. Michael On Wed, Apr 22, 2020 at 12:35 PM Karl Wright wrote: > I looked into trying to get things working under Ant and created a branch > CONNECTORS-1639 containing some changes relating to download of > elasticsearch artifacts. I did a little exploration as to whether we could > use the Elasticsearch Runner package to start a cluster, but that is really > painful because it has a ton of dependencies, so I think I'll just try > calling the main class that the ES startup script uses and see how we do > that way. > > But I'm snowed under with work related tasks again so it will have to wait. > > Karl > > > On Sat, Apr 18, 2020 at 5:52 PM Michael Cizmar > wrote: > > > 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 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 Wright , 18 Nis 2020 Cmt, 17:49 tarihinde > ş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 I > > > think. > > > > > > > > > > > > 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 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<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 Ant as well. Any way to make that happen? > > > > > > > > > > Karl > > > > > > > > > > > > > > > On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar < > > > > michael.ciz...@mcplusa.com > > > > > > > > > > > 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" 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? > > > > > > > > > > > >
Re: Release schedule
I looked into trying to get things working under Ant and created a branch CONNECTORS-1639 containing some changes relating to download of elasticsearch artifacts. I did a little exploration as to whether we could use the Elasticsearch Runner package to start a cluster, but that is really painful because it has a ton of dependencies, so I think I'll just try calling the main class that the ES startup script uses and see how we do that way. But I'm snowed under with work related tasks again so it will have to wait. Karl On Sat, Apr 18, 2020 at 5:52 PM Michael Cizmar wrote: > 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 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 Wright , 18 Nis 2020 Cmt, 17:49 tarihinde ş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 I > > think. > > > > > > > > > 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 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<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 Ant as well. Any way to make that happen? > > > > > > > > Karl > > > > > > > > > > > > On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar < > > > michael.ciz...@mcplusa.com > > > > > > > > > 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" 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 < > > > > furkankam...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > There is a compatibility matrix for Elasticsearch. We need to > > > > > support at > > > > > > least
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 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 Wright , 18 Nis 2020 Cmt, 17:49 tarihinde ş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 I > think. > > > > > > 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 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<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 Ant as well. Any way to make that happen? > > > > > > Karl > > > > > > > > > On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar < > > michael.ciz...@mcplusa.com > > > > > > > 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" 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 < > > > furkankam...@gmail.com> > > > > 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 > > > > > > > > > > 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, > > > > > F
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 Wright , 18 Nis 2020 Cmt, 17:49 tarihinde ş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 I think. > > > 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 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<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 Ant as well. Any way to make that happen? > > > > Karl > > > > > > On Sat, Apr 18, 2020 at 9:49 AM Michael Cizmar < > michael.ciz...@mcplusa.com > > > > > 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" 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 < > > furkankam...@gmail.com> > > > 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 > > > > > > > > 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 > > > 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 W
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 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> > > 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 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 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" 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 < > furkankam...@gmail.com> > > 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 > > > > > > 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 > > 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 , 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 > > >> > > > >> > > > > > > > >
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<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 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 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" 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 > 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 > > > > 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 > 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 , 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 > >> > > >> > > > >
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 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" 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 > 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 > > > > 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 > 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 , 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 > >> > > >> > > > >
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 org.elasticsearch.node.internal.InternalNode.(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 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 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 mailto:michael.ciz...@mcplusa.com>> 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" mailto:daddy...@gmail.com>> 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 mailto:furkankam...@gmail.com>> 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 mailto:daddy...@gmail.com>> > > 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 mailto:cguz...@gmail.com>> 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 mailto:daddy...@gmail.com>>, 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 >&
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 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" 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 > 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 > > > > 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 > 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 , 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 > >> > > >> > > > >
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 like moving to the SDK. M On 4/18/20, 8:32 AM, "Karl Wright" 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 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 > > 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 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 , 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 >> > >> >
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 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 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 > > 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 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 , 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 >> > >> >
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 tests are going to need to be written. The code is more or less fine for what I can see. On 4/18/20, 8:22 AM, "Furkan KAMACI" 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 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 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 , 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 > > >
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: https://github.com/apache/manifoldcf-integration-elasticsearch-5.5 @Karl Wright 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 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 , 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 > > >
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, > > 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 >
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. 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
Re: 1.3 release schedule
I'm sorry to inform that I haven't worked with the Hydra connector the last month. I have been busy with a major release of our search project at the university and my summer vaccation starts tomorrow. And I have also been busy with creating patches for Solr. Erlend On 6/24/13 5:13 PM, 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 to me. If you have the capacity to look at any of these tickets, please let me know. Thanks, Karl
