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.


On Mon, Aug 29, 2016 at 5:18 PM, Holtz, Michael (IT Consultant) <MHoltz@consultantemail.com> wrote:



Yes, it shows up. I include all meta-data.


I’m no trying to use a MetaData adjuster like this



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.



Mike H.


From: Karl Wright [mailto:daddywri@gmail.com]
Sent: Monday, August 29, 2016 5:13 PM
To: user@manifoldcf.apache.org
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.





On Mon, Aug 29, 2016 at 5:01 PM, Holtz, Michael (IT Consultant) <MHoltz@consultantemail.com> wrote:



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