Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

how to validate PutElasticsearchHttpRecord processor load

avatar
New Member

Hi

I was loaded Josn data to Elastic search by using PutElasticsearchHttpRecord record processor . How to validate number of records loaded in elastic search using nifi processor after the load.

I was try to use Queryelasticsearch procesor but not get any proper results .Appreciate for your help on this issue

1 ACCEPTED SOLUTION

avatar
Master Guru

Record-based processors should be writing the "record.count" attribute to outgoing flow files, but PutElasticsearchHttpRecord does not currently. I have written NIFI-5356 to cover this improvement. In the meantime, if you are using other record-based processors upstream, you may find you already have a record.count attribute, and since PutElasticsearchHttpRecord transfers the entire flow file to either success or failure, then if the attribute is there and the flow file is transferred to success, then "record.count" correctly indicates the number of records loaded into ES by that processor (for that flow file).

View solution in original post

1 REPLY 1

avatar
Master Guru

Record-based processors should be writing the "record.count" attribute to outgoing flow files, but PutElasticsearchHttpRecord does not currently. I have written NIFI-5356 to cover this improvement. In the meantime, if you are using other record-based processors upstream, you may find you already have a record.count attribute, and since PutElasticsearchHttpRecord transfers the entire flow file to either success or failure, then if the attribute is there and the flow file is transferred to success, then "record.count" correctly indicates the number of records loaded into ES by that processor (for that flow file).