You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Chris Sampson (Jira)" <ji...@apache.org> on 2023/05/13 18:43:00 UTC
[jira] [Updated] (NIFI-11430) Elasticsearch Paginated Query processor empty hits and extraction issues
[ https://issues.apache.org/jira/browse/NIFI-11430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Sampson updated NIFI-11430:
---------------------------------
Fix Version/s: 2.0.0
1.22.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Elasticsearch Paginated Query processor empty hits and extraction issues
> ------------------------------------------------------------------------
>
> Key: NIFI-11430
> URL: https://issues.apache.org/jira/browse/NIFI-11430
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.20.0
> Reporter: Ryan
> Assignee: Ryan
> Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If you use the PaginatedJsonQueryProcessor with the following settings
> |el-rest-split-up-hits|PER_QUERY|
> |el-rest-pagination-type|POINT_IN_TIME !https://nifi.apache.org/docs/nifi-docs/html/images/iconInfo.png!|
> |el-rest-output-no-hits|true|
> If you run the processor and hits are returned it outputs 2 flow files, 1 with the query hits and the other that is empty which is incorrect, it should return only 1 flow file that contains hits.
>
> -------
>
> If you use the PaginatedJsonQueryProcessor with the following settings
> |el-rest-split-up-hits|PER_QUERY|
> |el-rest-pagination-type|POINT_IN_TIME |
> |el-rest-output-no-hits|true|
> |el-rest-format-hits|SOURCE_ONLY|
> or
> |el-rest-split-up-hits|PER_QUERY|
> |el-rest-pagination-type|POINT_IN_TIME |
> |el-rest-output-no-hits|true|
> |el-rest-format-hits|METADATA_ONLY|
> If you run the processor and hits are returned it does not extract either _source or _metadata
--
This message was sent by Atlassian Jira
(v8.20.10#820010)