Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-03-05 Thread via GitHub
markap14 merged PR #8407: URL: https://github.com/apache/nifi/pull/8407 -- 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:

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-03-05 Thread via GitHub
markap14 commented on PR #8407: URL: https://github.com/apache/nifi/pull/8407#issuecomment-1979701945 Thanks @exceptionfactory all seems to be working well now. This is a huge improvement! +1 will merge to main -- This is an automated message from the Apache Git Service. To respond to

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-03-05 Thread via GitHub
exceptionfactory commented on PR #8407: URL: https://github.com/apache/nifi/pull/8407#issuecomment-1978901124 Thanks for the feedback @markap14, I rebased to incorporate the recent Python framework improvements, and also addressed the comments regarding log writing and exception handling.

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-03-05 Thread via GitHub
exceptionfactory commented on code in PR #8407: URL: https://github.com/apache/nifi/pull/8407#discussion_r1512922173 ## nifi-nar-bundles/nifi-py4j-bundle/nifi-py4j-bridge/src/main/java/org/apache/nifi/py4j/PythonProcessLogReader.java: ## @@ -0,0 +1,163 @@ +/* + * Licensed to

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-02-28 Thread via GitHub
markap14 commented on code in PR #8407: URL: https://github.com/apache/nifi/pull/8407#discussion_r1506303249 ## nifi-nar-bundles/nifi-py4j-bundle/nifi-py4j-bridge/src/main/java/org/apache/nifi/py4j/PythonProcessLogReader.java: ## @@ -0,0 +1,163 @@ +/* + * Licensed to the Apache

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-02-28 Thread via GitHub
markap14 commented on code in PR #8407: URL: https://github.com/apache/nifi/pull/8407#discussion_r1506300182 ## nifi-nar-bundles/nifi-py4j-bundle/nifi-py4j-bridge/src/main/java/org/apache/nifi/py4j/PythonProcessLogReader.java: ## @@ -0,0 +1,163 @@ +/* + * Licensed to the Apache

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-02-20 Thread via GitHub
exceptionfactory commented on PR #8407: URL: https://github.com/apache/nifi/pull/8407#issuecomment-1955870544 Thanks for the initial feedback @markap14! Based on further discussion, I will be following up with additional changes to incorporate log level updates from Logback. -- This is

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-02-14 Thread via GitHub
exceptionfactory commented on code in PR #8407: URL: https://github.com/apache/nifi/pull/8407#discussion_r1490140332 ## nifi-nar-bundles/nifi-py4j-bundle/nifi-py4j-bridge/src/main/java/org/apache/nifi/py4j/PythonProcessLogReader.java: ## @@ -0,0 +1,140 @@ +/* + * Licensed to

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-02-14 Thread via GitHub
markap14 commented on code in PR #8407: URL: https://github.com/apache/nifi/pull/8407#discussion_r1490101070 ## nifi-nar-bundles/nifi-py4j-bundle/nifi-py4j-bridge/src/test/java/org/apache/nifi/py4j/PythonProcessLogReaderTest.java: ## @@ -0,0 +1,127 @@ +/* + * Licensed to the

Re: [PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-02-14 Thread via GitHub
markap14 commented on code in PR #8407: URL: https://github.com/apache/nifi/pull/8407#discussion_r1490098492 ## nifi-nar-bundles/nifi-py4j-bundle/nifi-py4j-bridge/src/main/java/org/apache/nifi/py4j/PythonProcessLogReader.java: ## @@ -0,0 +1,140 @@ +/* + * Licensed to the Apache

[PR] NIFI-11443 Route Python Framework Logging to SLF4J [nifi]

2024-02-14 Thread via GitHub
exceptionfactory opened a new pull request, #8407: URL: https://github.com/apache/nifi/pull/8407 # Summary [NIFI-11443](https://issues.apache.org/jira/browse/NIFI-11443) Updates Python Process log handling to route messages to SLF4J so that logging levels and appenders can be