Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@manifoldcf.apache.org
Received-SPF: error (athena.apache.org: encountered temporary error during SPF
 processing of domain of Richard.Nichols@tellabs.com)
Received-SPF: neutral (mail103-va3: 204.154.129.192 is neither permitted nor
 denied by domain of tellabs.com) client-ip=204.154.129.192;
 envelope-from=Richard.Nichols@tellabs.com;
 helo=usnvwwmspedge01.tellabs-west.tellabsinc.net ;llabsinc.net ;
From: "Nichols, Richard" <Richard.Nichols@tellabs.com>
To: "user@manifoldcf.apache.org" <user@manifoldcf.apache.org>, Hermo
	<hermo.terblanche@euroling.se>
Date: Fri, 12 Jul 2013 16:12:51 -0500
Subject: RE: ElasticSearch Mappings Question
Thread-Topic: ElasticSearch Mappings Question
Thread-Index: Ac5/C8JSReSuDTmTRAuoF0kkAtDu7wAN83Ow
Message-ID: 
 <6355997B50A79B48B60F55953D30E3B601A5E71A8CA9@EX-WEST.tellabs-west.tellabsinc.net>
References: <4534274893465930731@unknownmsgid>
In-Reply-To: <4534274893465930731@unknownmsgid>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hermo,

Be aware that changes for CONNECTORS-690 (which I believe will be in the ne=
xt release) will expect that you have already set up a specific default map=
ping.  I realize this doesn't actually address your issue, but you should b=
e aware of it.

Rick

-----Original Message-----
From: Karl Wright [mailto:daddywri@gmail.com]
Sent: Friday, July 12, 2013 9:26 AM
To: Hermo; user@manifoldcf.apache.org
Subject: RE: ElasticSearch Mappings Question

Hi Hermo,
The mapping is determined by the elasticsearch connector. As of this
time, there is no way to change it other than to change the connector
code.

If you want such a feature, please create a jira ticket describing what
you think the connector should be able to do.

Thanks,
Karl

Sent from my Windows Phone
From: Hermo
Sent: 7/12/2013 9:30 AM
To: user@manifoldcf.apache.org
Subject: ElasticSearch Mappings Question
Hi,

I have the following scenario:

I configured a Job with a Windows Share repository connector, and an
ElasticSearch output connector.

It seems that, when a file in the share is crawled, it is ingested in
ElasticSearch with a very specific mapping as follows:
"myindex" is the name of the index and "docs" is the type.

{
 "myindex" : {
   "docs" : {
     "properties" : {
       "_content_type" : {
         "type" : "string"
       },
       "_name" : {
         "type" : "string"
       },
       "allow_token_document" : {
         "type" : "string"
       },
       "allow_token_share" : {
         "type" : "string"
       },
       "deny_token_document" : {
         "type" : "string"
       },
       "deny_token_share" : {
         "type" : "string"
       },
       "file" : {
         "type" : "string"
       },
       "lastModified" : {
         "type" : "string"
       },
       "type" : {
         "type" : "string"
       }
     }
   }
 }
}

I have the following questions:
1) What determines this mapping: The repository connector (in above
scenario the windows share connector), or the ElasticSearch connector?
2) Is there a way that I could specify my own mapping, for example I
would like to map the _name property to something different like
_productname. Where would be the correct place to do this?

Looking forward to any help and suggestions.

Regards,
Hermo Terblanche


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D