You should be looking at the ManifoldCF.log file, and the examples have logging for errors at least as being the default.
The only other possibility is that you have a very large document that is taking a long time to transfer/index. Also, you can generally see what MCF is up to using the "document status" and "queue status" reports. Karl On Mon, Aug 29, 2016 at 5:22 PM, Holtz, Michael (IT Consultant) < [email protected]> wrote: > Karl, > > > > I see no errors in the log. > > > > I probably need to configure the logging I think. > > > > Thanks, > > Mike H. > > > > *From:* Karl Wright [mailto:[email protected]] > *Sent:* Monday, August 29, 2016 5:20 PM > > *To:* [email protected] > *Subject:* Re: Has anyone successfully populated Elastic Search > properties from custom SharePoint Meta data fields? > > > > Hi Mike, > > > > Have a look in the log. If there are errors there please send them to > us. Generally, "hangs" are due to MCF retrying documents that have errors. > > > > Karl > > > > > > On Mon, Aug 29, 2016 at 5:18 PM, Holtz, Michael (IT Consultant) < > [email protected]> wrote: > > Karl, > > > > Yes, it shows up. I include all meta-data. > > > > I’m no trying to use a MetaData adjuster like this > > > > Parameter > > field1 “${Field 1}” > > > > And now I see “field1”=”” in Elastic Search. > > > > Also it seems each time I make a change the job will hang and I need to > restart everything including ElasticSearch to get it to complete. > > > > Thanks, > > Mike H. > > > > *From:* Karl Wright [mailto:[email protected]] > *Sent:* Monday, August 29, 2016 5:13 PM > *To:* [email protected] > *Subject:* Re: Has anyone successfully populated Elastic Search > properties from custom SharePoint Meta data fields? > > > > Hi Mike, > > > > If I were you I'd try to independently verify that the custom field shows > up. Do you see it appear in the pulldown for selecting metadata? If not, > it probably is not accessible through the inspection methods that give us > access into SharePoint fields. > > > > If it appears there then we should look at what ES gets sent. It's > possible it appears but under a different field name. > > > > Karl > > > > > > On Mon, Aug 29, 2016 at 5:01 PM, Holtz, Michael (IT Consultant) < > [email protected]> wrote: > > Hi, > > > > I have created a custom content type with a custom field “Field 1”. > > > > I have configured the job to include all meta data. > > > > I do not see “Field 1” being populated in the Elastic Search index. > > > > > > Does anyone have any experience with this? > > > > Thanks in advance, > > Mike H > > > > >
