hello.
First of all, I apologize for sending spam emails.
But when I looked at the 1.23.2 source, it was the same. (ToT)
have a nice day
Hello.
I found that there is no problem when writing with pretty json.
I am currently guessing that there is no problem when loading with bytes
like the pretty json part.
parsed = json.loads(flowFile.getContentsAsBytes())
Can this part be included in the next bug fix if it is correct?
I will look
hello.
Thank you for taking the time to look into the issue.
I found that whether or not an error occurs changes depending on the
version of JsonTreeReader.
I will also look into the differences and let you know if I find any.
Thank you very much again.
hello.
I guess the source I attached above has nothing to do with it.
if (prettyPrint) {
generator.useDefaultPrettyPrinter();
} else if (OutputGrouping.OUTPUT_ONELINE.equals(outputGrouping)) {
// Use a minimal pretty printer with a newline object
separat
hello.
The data provided appears to be sufficient for testing as we have tested it
several times and sent the problematic data.
I think it's almost certain because we've tested it multiple times on Linux
and Mac and only the problematic data has been clearly extracted.
I'm almost 100% sure it do
k you again. have a good day.
Data Sample
{"timestamp":"2024-10-20T16:10:00.322+09:00","data":"[{\"name\":\"\uD83D*\"}]"}
PartitionRecord property
mmddhh : format(toDate( /timestamp, "-MM-dd'T'HH:mm:ss.SSSXXX
