A 2.10 version was released middle of April. Karl
On Wed, May 16, 2018, 3:01 AM Shashank Saurabh LNU < sln...@worldbankgroup.org> wrote: > Hi Karl, > Thanks for the quick reply and update. > > I'm facing this issue in the ManifoldCF version 2.9.1 which I'm using and > think is the latest version. > > Please suggest the latest version to go with or the version you are > referring to in which this issue of ElasticSearch was fixed. > > Would be a great help. > > Regards, > Shashank Saurabh > > Sent from Gmail with Android for Worka2 > > On May 15, 2018 8:38 PM, Karl Wright <daddy...@gmail.com> wrote: > I believe a fix was made to the ElasticSearch connector a release or two > ago that addresses this problem. ElasticSearch once again changed their > API without notice and this was necessary. Please consider updating to the > latest release of MCF. > > Karl > > > On Tue, May 15, 2018 at 9:48 AM Shashank Saurabh LNU < > sln...@worldbankgroup.org> wrote: > >> Hi All, >> >> >> >> I’m using the Documentum Repository Connector and ElasticSearch Output >> Connector with the specified Docbase and Webtop credentials to crawl the >> contents from Documentum and index it into ElasticSearch. I’m using the >> local server for indexing into ElasticSearch i.e*. >> http://localhost:9200/ <http://localhost:9200/>.* >> >> >> >> Created the job, by giving required connections as Documentum in >> Repository and ElasticSearch in Output. >> >> >> >> When I run the job, the History Status shows the fetch status as OK from >> the Documentum but shows as error during the indexing to ElasticSearch. >> >> The error logged is*: **"error":"Content-Type header >> [application/x-www-form-urlencoded] is not supported.* >> >> >> >> Please do assist on this. >> >> >> >> - Using the setup in Windows Environment. >> >> >> >> >> >> Attaching the screenshot for the reference. >> >> >> >> >> >> Regards, >> >> >> >> Shashank Saurabh >> >> >> >
