Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1436F200B73 for ; Mon, 29 Aug 2016 23:25:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 12862160AB8; Mon, 29 Aug 2016 21:25:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 09404160A89 for ; Mon, 29 Aug 2016 23:25:36 +0200 (CEST) Received: (qmail 74106 invoked by uid 500); 29 Aug 2016 21:25:36 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 74078 invoked by uid 99); 29 Aug 2016 21:25:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Aug 2016 21:25:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BE2F0C252E for ; Mon, 29 Aug 2016 21:25:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Q0X0SRU3MPbO for ; Mon, 29 Aug 2016 21:25:33 +0000 (UTC) Received: from mail-it0-f44.google.com (mail-it0-f44.google.com [209.85.214.44]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 828AD5FAE0 for ; Mon, 29 Aug 2016 21:25:33 +0000 (UTC) Received: by mail-it0-f44.google.com with SMTP id g62so6766559ith.1 for ; Mon, 29 Aug 2016 14:25:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=GNqeSQ/UMzidKJv9b2OBFuGEcdZi457iZk67ecWBCSw=; b=ZCbuby3rAoWLGAt+x3aQhbhWEA+5IFSvzvD2SFvsWwFqvjAc8SQzyI7jWW9jRQ1pbE 1QckW5rF7+NlMia3STcHreq6ci1GhTQzvGsXsys0Dn6WidGjzYsUEAiu8+qKwN7WEpUX 7kjo85EbLs4A1uku20vfgiBfHMx51O5r4juuKgKh7Yd+eu+lc4101EjrmpIRNkasNaXs awDCIs6FFLLQP3YrLefvwswSfDMo0jWC0kI2smElNp2I0BoOnyK5MOfQeohP+BzK8HDZ Hn8NuZOMCP9wLJSCpuJU0t6oU1ibHkNJs/3hYmEhA8qZis7qGqRRmwsb0hOtp8UAjtBS vtOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=GNqeSQ/UMzidKJv9b2OBFuGEcdZi457iZk67ecWBCSw=; b=jApIYONBae3+JTG6UCKKdN77tYxXEdoD2dR5iL4/1RPLUNEQojamT0lbUcPL3dsFNR BR5YrCr+9+1O4I4ZXhh0yYxoSxlbh7tCj8Z4YaPK9VVJUHc5Rdoe1y4QYStLCaBdPR4n O1NPy3rA0U1TSKSXS0zU0lsEkTAcmM5YWC+WUTe6m5k6h8Rg2HQ+i/RKyYSv1rWd7OgL k2FwtrO+3SqBpgfFI3MsrWTwKACpqOlYBnisEiL9pYvzKWIyyVHj2C1ZAbuCMOiKGfUg NUgTDx9sDQQG5Cxegk7rAHEijXVIzGBnSSSQSg6lDg1tN1fzvlW3w/G+yYshbCZyvMeN jAlg== X-Gm-Message-State: AE9vXwN+B3fIs3wASL+V7Em1m/m//7wwyN7+NNi7/+0Fb+8dxpof10oNOaXvoJSJbOJOMYmglLiBLrG7PDWwAg== X-Received: by 10.36.39.67 with SMTP id g64mr18092742ita.93.1472505932932; Mon, 29 Aug 2016 14:25:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.18.31 with HTTP; Mon, 29 Aug 2016 14:25:32 -0700 (PDT) In-Reply-To: References: From: Karl Wright Date: Mon, 29 Aug 2016 17:25:32 -0400 Message-ID: Subject: Re: Has anyone successfully populated Elastic Search properties from custom SharePoint Meta data fields? To: "user@manifoldcf.apache.org" Content-Type: multipart/alternative; boundary=001a1147cc8e0feb1f053b3c8186 archived-at: Mon, 29 Aug 2016 21:25:38 -0000 --001a1147cc8e0feb1f053b3c8186 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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) < MHoltz@consultantemail.com> 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:daddywri@gmail.com] > *Sent:* Monday, August 29, 2016 5:20 PM > > *To:* user@manifoldcf.apache.org > *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 error= s. > > > > Karl > > > > > > On Mon, Aug 29, 2016 at 5:18 PM, Holtz, Michael (IT Consultant) < > MHoltz@consultantemail.com> wrote: > > Karl, > > > > Yes, it shows up. I include all meta-data. > > > > I=E2=80=99m no trying to use a MetaData adjuster like this > > > > Parameter > > field1 =E2=80=9C${Field 1}=E2=80=9D > > > > And now I see =E2=80=9Cfield1=E2=80=9D=3D=E2=80=9D=E2=80=9D in Elastic Se= arch. > > > > 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: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. > > > > Karl > > > > > > On Mon, Aug 29, 2016 at 5:01 PM, Holtz, Michael (IT Consultant) < > MHoltz@consultantemail.com> wrote: > > Hi, > > > > I have created a custom content type with a custom field =E2=80=9CField 1= =E2=80=9D. > > > > I have configured the job to include all meta data. > > > > I do not see =E2=80=9CField 1=E2=80=9D being populated in the Elastic Sea= rch index. > > > > > > Does anyone have any experience with this? > > > > Thanks in advance, > > Mike H > > > > > --001a1147cc8e0feb1f053b3c8186 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 t= hat is taking a long time to transfer/index.

Also,= you can generally see what MCF is up to using the "document status&qu= ot; and "queue status" reports.

Karl


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

Karl,

=C2=A0

I see no errors in the lo= g.

=C2=A0

I probably need to config= ure the logging I think.

=C2=A0

Thanks,

Mike H.

=C2=A0

From: Karl Wri= ght [mailto:daddywr= i@gmail.com]
Sent: Monday, August 29, 2016 5:20 PM


To: = user@manifoldcf.apache.org
Subject: Re: Has anyone successfully populated Elastic Search proper= ties from custom SharePoint Meta data fields?

<= /p>

=C2=A0

Hi Mike,

=C2=A0

Have a look in the log.=C2=A0 If there are errors th= ere please send them to us.=C2=A0 Generally, "hangs" are due to M= CF retrying documents that have errors.

=C2=A0

Karl

=C2=A0

=C2=A0

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

Karl,

=C2=A0

Yes, it shows up. I inclu= de all meta-data.

=C2=A0

I=E2=80=99m no trying to = use a MetaData adjuster like this

=C2=A0

Parameter

field1=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 =E2=80=9C${Field 1}=E2=80=9D

=C2=A0

And now I see =E2=80=9Cfi= eld1=E2=80=9D=3D=E2=80=9D=E2=80=9D in Elastic Search.<= /p>

=C2=A0

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.

=C2=A0

Thanks,<= /u>

Mike H.<= /u>

=C2=A0

From: Karl Wri= ght [mailto:daddywr= i@gmail.com]
Sent: Monday, August 29, 2016 5:13 PM
To: = user@manifoldcf.apache.org
Subject: Re: Has anyone successfully populated Elastic Search proper= ties from custom SharePoint Meta data fields?

=C2=A0

Hi Mike,

=C2=A0

If I were you I'd try to independently verify th= at the custom field shows up.=C2=A0 Do you see it appear in the pulldown fo= r selecting metadata?=C2=A0 If not, it probably is not accessible through the inspection methods that give us access into SharePoint fields.=

=C2=A0

If it appears there then we should look at what ES g= ets sent.=C2=A0 It's possible it appears but under a different field na= me.

=C2=A0

Karl

=C2=A0

=C2=A0

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

Hi,

=C2=A0

I have created a custom content type with a custom f= ield =E2=80=9CField 1=E2=80=9D.

=C2=A0

I have configured the job to include all meta data.<= u>

=C2=A0

I do not see =E2=80=9CField 1=E2=80=9D being populat= ed in the Elastic Search index.

=C2=A0

=C2=A0

Does anyone have any experience with this?=

=C2=A0

Thanks in advance,

Mike H

=C2=A0

=C2=A0


--001a1147cc8e0feb1f053b3c8186--