About Samya

vafs · ‎11-13-2025

Hello @Samya, Thanks for joining our community. That issue is happening because JSON_STORE format is VARCHAR(2), not VARIANT as required. Something you can try is to add a ConvertRecord processor before the PutDatabaseRecord. There, you can use a JsonTreeReader → JsonRecordSetWriter to reformat the content. In that way, the JSON_STORE field becomes a proper JSON object. Something like this👆

Samya · ‎06-20-2023

It just gave this information in DEBUG. "PutAzureDataLakeStorage DataLakeServiceClient is not found in the cache with the given credentials. Creating it."

Samya · ‎09-27-2022

Hi , we are consuming and publishing from MQ. Consumer is fast enough, the publisher is slow and it’s builds a lot of back pressure. we have a 4 node 20 core each * 4 total 80 cores. memory 16GB each 64GB total. publish is running at 200 concurrency. I did system diagnostics cores and memory are free, then what is causing the slow publish and build back pressure. I wanted to try and increase run duration to increase the throughput but this processor don’t seem to have the option to modify run duration. what other option there to increase throughput. let me know if you need more information . Regards

Samya · ‎09-23-2022

Hi Team, We have a 4 node cluster with 64 cores. but when we do system diagnostics we see only average usage of 5 cores. also the data is queuing up and processing slowly. regards, samyan

Online	Offline
Last Visited	‎11-15-2025 06:34 PM

Member Since	‎09-23-2022 02:59 PM
Last Visited	‎11-15-2025 06:34 PM
Posts	5

Cloudera Community

Re: PutDatabaseRecord into snowflake Variant field

Re: create ADLS directory using PutZaureDataLakeSt...

PublishJMS performance

Nifi CPU core utilization