mattcasters opened a new pull request, #8632:
URL: https://github.com/apache/hop/pull/8632

   An execution data profile can leave oversized String, JSON, Binary, and Avro 
values out of the sample rows it stores. A few wide values in those rows are 
enough to blow a Neo4j transaction or the Jackson string limit on a database 
location.
   
   The profile editor has a Large values group. Each of String, JSON, Binary, 
and Avro has its own size limit, and the limit applies to every sampler in the 
profile on the local, Beam, and Spark engines. An empty field keeps today's 
behavior. Zero stores none of that type. A longer String or JSON cell is 
replaced with `<not stored, N characters>`. Binary and Avro cells over the 
limit are left empty. Null counts and string lengths are still recorded. 
Minimum and maximum values are taken only from values that were stored.
   
   fixes #8617
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   - [ ] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [x] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
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