ChrisSamo632 opened a new pull request, #9244:
URL: https://github.com/apache/nifi/pull/9244

   # Summary
   
   [NIFI-13719](https://issues.apache.org/jira/browse/NIFI-13719) allow 
Elasticsearch response to contain Long values for the took field
   
   While documented as an Integer, the Elasticsearch `took` field value can 
extend beyond the maximum allowed Integer value of Java, so NiFi should allow 
for Long values (or Integers) in the parsed response JSON of Search and _bulk 
API index operations.
   
   This affects use of Elasticsearch 8.15.0 - 
https://github.com/elastic/elasticsearch/issues/111854
   
   # Tracking
   
   Please complete the following tracking steps prior to pull request creation.
   
   ### Issue Tracking
   
   - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue 
created
   
   ### Pull Request Tracking
   
   - [x] Pull Request title starts with Apache NiFi Jira issue number, such as 
`NIFI-00000`
   - [x] Pull Request commit message starts with Apache NiFi Jira issue number, 
as such `NIFI-00000`
   
   ### Pull Request Formatting
   
   - [x] Pull Request based on current revision of the `main` branch
   - [x] Pull Request refers to a feature branch with one commit containing 
changes
   
   # Verification
   
   Please indicate the verification steps performed prior to pull request 
creation.
   
   ### Build
   
   - [x] Build completed using `mvn clean install -P contrib-check`
     - [x] JDK 21
   
   ### Licensing
   
   - ~~[ ] New dependencies are compatible with the [Apache License 
2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License 
Policy](https://www.apache.org/legal/resolved.html)~~
   - ~~[ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` 
files~~
   
   ### Documentation
   
   - ~~[ ] Documentation formatting appears as expected in rendered files~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to