Identifier Attribute is a little confusing and different, I struggled
to decide whether to have an "Identifier" property or an "Identifier
Attribute" property, and chose the latter because if you had an
Identifier property and didn't use expression language, then the
processor would immediately fail on the second Put because all
identifiers would be the same. Having an Identifier Attribute was
supposed to make it clear that the identifier should be unique and
associated with each document. I'm not sure it ended up being as clear
as I'd hoped :-P
Identifier Attribute refers to the name of the FlowFile attribute that
contains the identifier for the document. So in the above example you
will want to set it to "uuid", not "${uuid}". PutElasticsearch will
then get the value of the "uuid" attribute, and use that value as the
identifier for the document in ES.
Regards,
Matt
On Thu, Apr 28, 2016 at 12:54 PM, Bryan Bende <[email protected]> wrote:
> Hello,
>
> ElasticSearch requires id for each document that is added. The value of
> this property will be the id on the document being added.
>
> You would likely set the value of this property to expression language that
> references a FlowFile attribute, you could use ${uuid} to use the
> FlowFile's uuid as your ElasticSearch id.
>
> -Bryan
>
>
> On Thu, Apr 28, 2016 at 11:19 AM, idioma <[email protected]> wrote:
>
>> Hi,
>> I am trying to use the out-of-the-box PutElastiSearch with my local
>> ElasticSearch installation (I am on Windows), but I am rather puzzled about
>> the actual value to be included for the PropertyDescriptor: Identifier
>> Attribute. Can you provide an example?
>>
>> Thanks,
>>
>> I.
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-nifi-developer-list.39713.n7.nabble.com/Identifier-Attribute-for-PutElasticSearch-tp9683.html
>> Sent from the Apache NiFi Developer List mailing list archive at
>> Nabble.com.
>>
