Member since
11-23-2022
11
Posts
1
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
340 | 07-01-2025 06:50 AM | |
1362 | 10-25-2023 05:35 AM |
07-01-2025
06:50 AM
Fixed by using toolkit 1.28.1 to access nifi 1.27.x
... View more
06-25-2025
07:31 AM
I attach a sample command with the output generated by the -verbose option Regards
... View more
06-25-2025
06:36 AM
Hello, I'm sending nifi tookit 1.27.0 nifi set-param commands to a nifi 1.27.0 cluster to add parameter key/values to an existing parameter context In an intermittent way, the nifi set-param commands properly set the key/value in the PC but end in error with message Error deleting parameter context update request: Could not find a Request with identifier xxx I sometimes, not systematically, get the same error message when manipulating the PC key/value pairs via th UI ( when applying the changes ). From a network point of view I see 404 not found errors when the problem occurs Is this a known issue ? Is there any way to avoid/solve this problem ? Regards
... View more
Labels:
- Labels:
-
Apache NiFi
04-25-2025
06:45 AM
Thanks for the reminder regarding the semantic of merge-param-context. I overlooked the contents of the help and my initial posting. Regards
... View more
04-25-2025
03:16 AM
A quick series of command I used to test the above scenario outlined in my reply just above where an existing key did not get its corresponding value updated #> nifi get-param-context -pcid 5d3d3ac8-0196-1000-ffff-ffffaf0565d4 # Name Value Sensitive Description - ---------- ------------ --------- ----------- 1 test-key-1 test-value-1 false 2 test-key-2 test-value-2 false #> nifi merge-param-context -pcid 5d3d3ac8-0196-1000-ffff-ffffaf0565d4 -i sample-pc.json Found parameter to add - 'test-key-3' Waiting for update request to complete... Waiting for update request to complete... Waiting for update request to complete... Waiting for update request to complete... #> nifi get-param-context -pcid 5d3d3ac8-0196-1000-ffff-ffffaf0565d4 # Name Value Sensitive Description - ---------- ------------------ --------- ----------- 1 test-key-1 test-value-1 false 2 test-key-2 test-value-2 false 3 test-key-3 test-added-value-3 false The new key test-key-3 is added with its value to the PC. But the value corresponding to test-key-1 is left unchanged --- The sample json contents used below { "name" : "test-param-ctx", "description" : "", "parameters" : [ { "parameter" : { "name" : "test-key-1", "description" : "", "sensitive" : false, "value" : "test-modified-value-1", "provided" : true, "inherited" : false } }, { "parameter" : { "name" : "test-key-3", "description" : "", "sensitive" : false, "value" : "test-added-value-3", "provided" : false, "inherited" : false } } ], "inheritedParameterContexts" : [ ] }
... View more
04-25-2025
03:08 AM
Hello, Thanks for the quick and detailed answer. I've tested the solution and managed to use it to insert new key / value pairs int he PC if the key is not already present But I could not update the value of a key already existing in the PC. Is this expected behaviour ? Or is there a way to just update the value of an existing key that I would have missed ? Regards
... View more
04-23-2025
07:40 AM
Hello, I'm investigating Nifi toolkit (1.16 if it matters) to add key/value pairs to a param-context programmatically ( I can't use existing PC providers ) Nifi toolkit documents the following action: #> nifi merge-param-context -help Adds any parameters that exist in the exported context that don't exist in the existing context. Overwrites any existing inherited parameter contexts with the provided list. ... -i,--input <arg> A local file to read as input contents, or a public URL to fetch I would like to know if the key/value pairs to add to the PC ( -pcid argument ) can come from the contents of the -i file If yes, what is expected format of this file please ? ( random testing and error messages didn't help much) Regards
... View more
Labels:
- Labels:
-
Apache NiFi
01-31-2025
04:29 AM
Based on the initial input in the question, slightly adapted the following seems to work for me (1.27.0) docker run --rm --name nifi -p 8080:8080 \ -e NIFI_WEB_HTTP_PORT=8080 \ -e NIFI_WEB_HTTPS_PORT= \ -e NIFI_WEB_HTTPS_HOST= \ -e NIFI_SECURITY_KEYSTORE= \ -e NIFI_SECURITY_KEYSTOREPASSWD= \ -e NIFI_SECURITY_KEYPASSWD= \ -e NIFI_SECURITY_TRUSTSTORE= \ -e NIFI_SECURITY_TRUSTSTOREPASSWD= \ apache/nifi:1.27.0 --- --- from container nifi@xxxxxxxxxxxx:/opt/nifi/nifi-toolkit-current/bin$ ./cli.sh _ ___ _ Apache (_) .' ..](_) , _ .--. __ _| |_ __ )\ [ `.-. | [ |'-| |-'[ | / \ | | | | | | | | | | ' ' [___||__][___][___] [___]', ,' `' CLI v1.27.0 Type 'help' to see a list of available commands, use tab to auto-complete. Session loaded from /home/nifi/.nifi-cli.config #> nifi get-root-id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
... View more
06-06-2024
04:37 AM
1 Kudo
Hello I'm running apache zookeeper 3.8.4. File zookeeper.log does not get created. Log files are empty except the following message: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder". SLF4J: Defaulting to no-operation MDCAdapter implementation. SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details. How can I configure zookeeper with logs working ? According to the links, this is due to slf4j not detecting logback. The process runs with the following options in the commandline (extract) The classpath does seem to include slf4j and logback jars, as well as the conf directory containing logback.xml /apps/dis/java/jdk/bin/java -Dzookeeper.log.dir=/apps/zookeeper/log -Dzookeeper.log.file=zookeeper.log -cp ... /apps/zookeeper/bin/zkcurrent/bin/../lib/slf4j-api-1.7.30.jar: ... /apps/zookeeper/bin/zkcurrent/bin/../lib/logback-core-1.2.13.jar: ... /apps/zookeeper/bin/zkcurrent/bin/../lib/logback-classic-1.2.13.jar: /apps/zookeeper/bin/zkcurrent/bin/../conf: ... org.apache.zookeeper.server.quorum.QuorumPeerMain /apps/zookeeper/bin/zkcurrent/bin/../conf/zoo.cfg The logback.xml file is in /apps/zookeeper/bin/zkcurrent/bin/../conf with rollingfile and console appenders activated: <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{ISO8601} [myid:%X{myid}] - %-5p [%t:%C{1}@%L] - %m%n</pattern> </encoder> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>${zookeeper.console.threshold}</level> </filter> </appender> ... <appender name="ROLLINGFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${zookeeper.log.dir}/${zookeeper.log.file}</File> <encoder> <pattern>%d{ISO8601} [myid:%X{myid}] - %-5p [%t:%C{1}@%L] - %m%n</pattern> </encoder> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>${zookeeper.log.threshold}</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <maxIndex>${zookeeper.log.maxbackupindex}</maxIndex> <FileNamePattern>${zookeeper.log.dir}/${zookeeper.log.file}.%i</FileNamePattern> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>${zookeeper.log.maxfilesize}</MaxFileSize> </triggeringPolicy> </appender> ... <root level="INFO"> <appender-ref ref="CONSOLE" /> <appender-ref ref="ROLLINGFILE" /> </root> All suggestions welcome. Regards
... View more
Labels:
- Labels:
-
Apache Zookeeper
10-25-2023
05:35 AM
The problem seemed to be caused by wrong access policies on PG under the root. With the wrong credentials the name attribute of certain PG was not returned in the response which caused pg-list to fail. Adding read policy for the credentials on the PGs solved the case. ?! Regards
... View more