@SAMSAL  Jeez... I should not have prepared that flow at the end of 12 hour work... Of course, it works now, sorry for troubles and thanks for quick support ... View more

Hi, Can you provide sample of this data highlighting what the problem and how do you expect to solve? Also what kind of processor\service are you trying to use to parse this data? ... View more

@fisblack Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  Thanks. ... View more

Hi @Syed0000 , Sorry for the delay. You json is quite complex and very nested which make jolt very hard to write. You probably know your data very well and my recommendation before writing jolt for such Json is that you try to simplify it first by stripping un need blocks and\or flattening the structure where the transformation is not going to be on the same nested level. I honestly tried but when the jolt got so nested it got harder to reference the upper fields and upper array indexes to maintain the same array position and then maintain the required grouping of fields, and may be that is the draw back of using jolt spec in these scenarios (without prior simplification of course :). This leads me to the second option, which I think  I have mentioned to you in prior post regarding using JSLT Transformation instead.  JSLT is better option in these cases because you can traverse the structure much easier , and since you have some condition on how to set fields and values this also would be easier to achieve with some expression language like if-else  . For example if we take the transformation to create  catalogCondition strucutre which seems to the most complex, here is how the jstl  looks like: let paths ={ "paths":[for(.tiers) { for(.conditions) "catalogCondition": { "category": [for(.conditionsMerch) { "include": if(.excludeInd==0) "yes" else "no", "categoryList":[.webCategoryId] } if(.merchandiseLevel!=5 and not(.keyItemNum))] } + { "products" : [for(.conditionsMerch) { "include": if(.excludeInd==0) "yes" else "no", "productList":[.keyItemNum] } if(not(.webCategoryId))] } } ] } { "pricePaths": $paths } I know this might look a little intimidating at beginning but its not near as bad as when you try to do it with jolt. I understand that jstl is bit of learning curve but I believe it would save you tons of time long term specially when dealing with long, complex and nested Json transformation. I know this is not the answer you were looking for but hopefully this can help you when facing other json transformation challenges in the future. Good luck.     ... View more

For reference, I tried solution #1 where I added an UpdateAttribute processor and deleted any references to SQL attributes. That did it. Thanks! ... View more

Thank you @SAMSAL ,  we used Execute Process with a curl script file, when writing the script into the Execute Process itself, the body still did not go away. Your message helped solve the problem, 👏but unfortunately I don't have a button to mark it as a solution.😪 ... View more

     @drewski7 wrote: @AndreyDE  Is one flowfile going into the SplitText processor and outputting 10000 flowfiles? Yes - one flow file How big is the flowfile going into the SplitText processor? About 30 KB Or is the source of the pipeline recursively getting all objects in your S3 bucket?  Yes, it searches all objects recursively     ... View more

@SAMSAL thank you so much for your detailed answer, I really appreciated (and sorry for not able to reply earlier) ... View more