[GitHub] [nifi-minifi-cpp] lordgamez commented on a diff in pull request #1409: MINIFICPP-1911 Make concat_path variadic

[GitBox]

lordgamez commented on code in PR #1409:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1409#discussion_r964473490


##
libminifi/test/unit/FileUtilsTests.cpp:
##
@@ -52,43 +52,43 @@ TEST_CASE("TestFileUtils::concat_path", "[TestConcatPath]") 
{
 
 TEST_CASE("TestFileUtils::get_parent_path", "[TestGetParentPath]") {
 #ifdef WIN32
-  REQUIRE("foo\\" == FileUtils::get_parent_path("foo\\bar"));
-  REQUIRE("foo\\" == FileUtils::get_parent_path("foo\\bar\\"));
-  REQUIRE("C:\\foo\\" == FileUtils::get_parent_path("C:\\foo\\bar"));
-  REQUIRE("C:\\foo\\" == FileUtils::get_parent_path("C:\\foo\\bar\\"));
-  REQUIRE("C:\\" == FileUtils::get_parent_path("C:\\foo"));
-  REQUIRE("C:\\" == FileUtils::get_parent_path("C:\\foo\\"));
-  REQUIRE("" == FileUtils::get_parent_path("C:\\"));  // 
NOLINT(readability-container-size-empty)
-  REQUIRE("" == FileUtils::get_parent_path("C:"));  // 
NOLINT(readability-container-size-empty)
+  CHECK("foo" == FileUtils::get_parent_path("foo\\bar"));
+  CHECK("foo\\bar" == FileUtils::get_parent_path("foo\\bar\\"));

Review Comment:
   I see, if we don't want to deviate from the semantics of the standard 
library, could you add this explanation as a comment to these functions?



-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (NIFI-10452) Parameter Context [deleted values are restored when version imports or changes are done]

[Brendan (Jira)]

Brendan created NIFI-10452:
--

 Summary: Parameter Context [deleted values are restored when 
version imports or changes are done]
 Key: NIFI-10452
 URL: https://issues.apache.org/jira/browse/NIFI-10452
 Project: Apache NiFi
  Issue Type: Bug
 Environment: Apache NIFI v1.16.2
Reporter: Brendan


Experienced a behaviour on a implementation where some parameters in the 
parameter context that were deleted are re-imported/added when you do an import 
from registry

so for example lets say we have commited V90 to registry we did some work 
deleted properties and then commit V91 with some deleted parameters

You then go to another env and import this V91 all the deleted parameters 
import with new ones then you delete it on UAT and save that as V92 and you 
update dev to V92 from V91 all the deleted parameters in DEV are restored again 
and every time you change the version you need to re-delete all deleted 
parameters etc.

So when new ones are added then they are automatically added to environments 
you deploy to but deleted parameters dont stay deleted they just keep getting 
readded back again, it seems.

As an added test I download the Flow Definition and imported it into a clean 
instance of docker NiFi and it imported the entire history of parameters 
including deleted ones past.

The expected outcome is once deleted and commited to registry or flow 
definition download it will no longer have all the historical parameters in the 
parameter context once deleted

The result is on each import I would have to remove these redundant parameters 
to clean things up or just ignore them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [nifi] mathemare closed pull request #6269: NIFI-10236: ByteArrayContentRepository in nifi-framework-components

[GitBox]

mathemare closed pull request #6269: NIFI-10236: ByteArrayContentRepository in 
nifi-framework-components
URL: https://github.com/apache/nifi/pull/6269


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (NIFI-10451) Update QuestDB based status history repository's clean up query

[Simon Bence (Jira)]

Simon Bence created NIFI-10451:
--

 Summary: Update QuestDB based status history repository's clean up 
query
 Key: NIFI-10451
 URL: https://issues.apache.org/jira/browse/NIFI-10451
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework, Extensions
Reporter: Simon Bence
Assignee: Simon Bence


QuestDB 6.X uses a different syntax for dropping partitons (here: cleaning up 
old status history information) than 4.x. As the version number has been 
bumped, the query must be updated too. The currently expected syntax is the 
following:

{{ALTER TABLE measurements DROP PARTITION LIST '2019-05-18';}}

This is from the QuestDB 
[documentation|https://questdb.io/docs/reference/sql/alter-table-drop-partition]
 at the time of creating the ticket (might change in the future)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (NIFI-10438) PutGCSObject : Read timed out : Failure completing upload flowfile={} bucket={} key={} reason={}

[mayki (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601168#comment-17601168
 ] 

mayki commented on NIFI-10438:
--

Hello.

Could we use this feature : 
[https://cloud.google.com/storage/docs/performing-resumable-uploads] for bigger 
files ?

Thanks for help

> PutGCSObject : Read timed out : Failure completing upload flowfile={} 
> bucket={} key={} reason={}
> 
>
> Key: NIFI-10438
> URL: https://issues.apache.org/jira/browse/NIFI-10438
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.16.3
>Reporter: mayki
>Priority: Major
>  Labels: bucket, gcp, processor
>
> Hello,
> Usually we don't have this error in the nifi 1.11 and 1.13 but since we 
> upgraded to the nifi 1.16.3, we could see a lot of error concerning the 
> processor "PutGCSObject"
> Also, we use the proxy to communicate with GCP
>  
> {code:java}
> 2022-09-05 01:32:49,731 ERROR [Timer-Driven Process Thread-1] 
> o.a.n.p.gcp.storage.PutGCSObject [PutGCSObject[id=b0bb35fb-47b3-1], textfile, 
> bucket-name, RACOPE00.RAC08BIG.I0503311_20220905_033220, Read timed out] 
> Failure completing upload flowfile={} bucket={} key={} reason={}
> com.google.cloud.storage.StorageException: Read timed out
>         at 
> com.google.cloud.storage.spi.v1.HttpStorageRpc.translate(HttpStorageRpc.java:286)
>         at 
> com.google.cloud.storage.spi.v1.HttpStorageRpc.writeWithResponse(HttpStorageRpc.java:954)
>         at 
> com.google.cloud.storage.BlobWriteChannel.transmitChunk(BlobWriteChannel.java:67)
>         at 
> com.google.cloud.storage.BlobWriteChannel.access$1400(BlobWriteChannel.java:34)
>         at 
> com.google.cloud.storage.BlobWriteChannel$1.run(BlobWriteChannel.java:252)
>         at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>         at 
> com.google.api.gax.retrying.DirectRetryingExecutor.submit(DirectRetryingExecutor.java:103)
>         at com.google.cloud.RetryHelper.run(RetryHelper.java:76)
>         at com.google.cloud.RetryHelper.runWithRetries(RetryHelper.java:50)
>         at 
> com.google.cloud.storage.BlobWriteChannel.flushBuffer(BlobWriteChannel.java:183)
>         at com.google.cloud.BaseWriteChannel.flush(BaseWriteChannel.java:112)
>         at com.google.cloud.BaseWriteChannel.write(BaseWriteChannel.java:139)
>         at 
> com.google.cloud.storage.StorageImpl.uploadHelper(StorageImpl.java:254)
>         at 
> com.google.cloud.storage.StorageImpl.createFrom(StorageImpl.java:236)
>         at 
> com.google.cloud.storage.StorageImpl.createFrom(StorageImpl.java:225)
>         at 
> org.apache.nifi.processors.gcp.storage.PutGCSObject$1.process(PutGCSObject.java:407)
>         at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2675)
>         at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2643)
>         at 
> org.apache.nifi.processors.gcp.storage.PutGCSObject.onTrigger(PutGCSObject.java:343)
>         at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>         at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1283)
>         at 
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
>         at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
>         at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
>         at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>         at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
> Caused by: java.net.SocketTimeoutException: Read timed out
>         at java.net.SocketInputStream.socketRead0(Native Method)
>         at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
>         at java.net.SocketInputStream.read(SocketInputStream.java:171)
>         at java.net.SocketInputStream.read(SocketInputStream.java:141)
>         at 
> sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:475)
>         at 
> 

[GitHub] [nifi] Aerilym commented on pull request #6243: NIFI-10192 Cache schema request result for reuse

[GitBox]

Aerilym commented on PR #6243:
URL: https://github.com/apache/nifi/pull/6243#issuecomment-1239303648

   > Can this be closed if #6364 replaces it?
   
   Yes, this one can be closed, I have taken over the PR from @kent-nguyen and 
implemented a modified solution based on the given feedback.


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (NIFI-9989) sftp processors Received SSH_MSG_UNIMPLEMENTED

[David Handermann (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601292#comment-17601292
 ] 

David Handermann commented on NIFI-9989:


Thanks for the reply [~Kirhold], that is a good point about FetchSFTP.

I am planning on submitting a pull request to SSHJ, and I will link it to this 
issue when submitted.

> sftp processors Received SSH_MSG_UNIMPLEMENTED
> --
>
> Key: NIFI-9989
> URL: https://issues.apache.org/jira/browse/NIFI-9989
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.17.0, 1.16.1
> Environment: Ubuntu 20.04, openjdk version "1.8.0_312"
> OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07)
> OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)
>Reporter: Jens M Kofoed
>Assignee: David Handermann
>Priority: Major
> Attachments: image-2022-08-16-09-44-10-682.png
>
>
> After upgrading from single instance version 1.13.2 to a 3 node cluster 
> version 1.16.1 All sftp processors occasionally report errors:
> 2022-05-05 07:26:08,318 INFO [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.random.JCERandom Creating new SecureRandom.
> 2022-05-05 07:26:08,318 DEBUG [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.random.JCERandom Random creation took 0 ms
> 2022-05-05 07:26:08,318 DEBUG [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.DefaultConfig Available cipher factories: 
> [chacha20-poly1...@openssh.com, aes128-cbc, aes128-ctr, aes192-cbc, 
> aes192-ctr, aes256-cbc, aes256-ctr, aes128-...@openssh.com, 
> aes256-...@openssh.com, blowfish-cbc, blowfish-ctr, cast128-cbc, cast128-ctr, 
> idea-cbc, idea-ctr, serpent128-cbc, serpent128-ctr, serpent192-cbc, 
> serpent192-ctr, serpent256-cbc, serpent256-ctr, 3des-cbc, 3des-ctr, 
> twofish128-cbc, twofish128-ctr, twofish192-cbc, twofish192-ctr, 
> twofish256-cbc, twofish256-ctr, twofish-cbc, arcfour, arcfour128, arcfour256]
> 2022-05-05 07:26:08,319 INFO [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.TransportImpl Client identity string: 
> SSH-2.0-SSHJ_0.33.0
> 2022-05-05 07:26:08,334 INFO [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.TransportImpl Server identity string: 
> SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.4
> 2022-05-05 07:26:08,339 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Received SSH_MSG_KEXINIT
> 2022-05-05 07:26:08,340 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Sending SSH_MSG_KEXINIT
> 2022-05-05 07:26:08,340 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Negotiated algorithms: [ 
> kex=curve25519-sha256; sig=ssh-ed25519; 
> c2sCipher=chacha20-poly1...@openssh.com; 
> s2cCipher=chacha20-poly1...@openssh.com; c2sMAC=hmac-sha1; s2cMAC=hmac-sha1; 
> c2sComp=none; s2cComp=none;  ]
> 2022-05-05 07:26:08,340 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.kex.Curve25519SHA256 Sending SSH_MSG_KEXDH_INIT
> 2022-05-05 07:26:08,349 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Received kex followup data
> 2022-05-05 07:26:08,349 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.kex.Curve25519SHA256 Received SSH_MSG_KEXDH_REPLY
> 2022-05-05 07:26:08,349 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.common.KeyType Key algo: ssh-ed25519, Key curve: 25519, Key 
> Len: 32p: [52, 76, 38, 101, -74, -101, -94, -14, 109, -121, -87, -122, -50, 
> -103, -88, -87, -50, -64, -55, 41, -109, -93, 60, 84, -75, -85, 59, -48, -34, 
> 25, -77, -53]
> 2022-05-05 07:26:08,351 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Trying to verify host key with 
> net.schmizz.sshj.transport.verification.PromiscuousVerifier@45c3e734
> 2022-05-05 07:26:08,351 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Sending SSH_MSG_NEWKEYS
> 2022-05-05 07:26:08,351 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Received SSH_MSG_NEWKEYS
> 2022-05-05 07:26:08,351 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.TransportImpl Received SSH_MSG_EXT_INFO
> 2022-05-05 07:26:08,354 DEBUG [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.KeyExchanger Sending SSH_MSG_KEXINIT
> 2022-05-05 07:26:08,355 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.TransportImpl Received SSH_MSG_UNIMPLEMENTED #3
> 2022-05-05 07:26:08,355 ERROR [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.TransportImpl Dying because - Received 
> SSH_MSG_UNIMPLEMENTED while exchanging keys
> 

[GitHub] [nifi-minifi-cpp] szaszm commented on pull request #1409: MINIFICPP-1911 Make concat_path variadic

[GitBox]

szaszm commented on PR #1409:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1409#issuecomment-1239242437

   Instead of introducing "UrlUrils", I'd prefer to model URLs in their own
   class, similar to `std::filesystem::path`.
   
   On Tue, Sep 6, 2022, 18:30 Ferenc Gerlits ***@***.***> wrote:
   
   > ***@***. commented on this pull request.
   > --
   >
   > In extensions/sftp/processors/ListSFTP.cpp
   > 
   > :
   >
   > > @@ -186,7 +186,7 @@ ListSFTP::Child::Child(const std::string& 
parent_path_, std::tuple  }
   >
   >  std::string ListSFTP::Child::getPath() const {
   > -  return utils::file::FileUtils::concat_path(parent_path, filename, true 
/*force_posix*/);
   > +  return utils::StringUtils::join_pack(parent_path, "/", filename);
   >
   > This is not used for files, only for URLs, so I wouldn't put it in
   > FileUtils. I can add a makeUrl() function in StringUtils (or maybe a new
   > UrlUtils) which joins its argument with '/'s. I think that would be less
   > explicit, but it may be more readable.
   >
   > —
   > Reply to this email directly, view it on GitHub
   > 
,
   > or unsubscribe
   > 

   > .
   > You are receiving this because you commented.Message ID:
   > ***@***.***>
   >
   


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (NIFI-10453) Cannot set AnnotationData while processor is running

[hipotures (Jira)]

hipotures created NIFI-10453:


 Summary: Cannot set AnnotationData while processor is running
 Key: NIFI-10453
 URL: https://issues.apache.org/jira/browse/NIFI-10453
 Project: Apache NiFi
  Issue Type: Bug
  Components: Flow Versioning
Affects Versions: 1.17.0
 Environment: Linux debian
Reporter: hipotures


Action: Change version
Problem: Can't change to newer version of flow

Web UI error popup:
Change Version
Failed to perform update flow request due to Cannot set AnnotationData while 
processor is running

Description: Updated flow is in state STOPPED. Controller is active (this 
controller is shared between many other flows).

Workaround: Stop all flows and controllers.

Error Log:
2022-09-07 10:43:05,380 ERROR [Process Group Update Thread-1] 
o.apache.nifi.web.api.FlowUpdateResource Failed to perform update flow request 
java.lang.IllegalStateException: Cannot set AnnotationData while processor is 
running
at 
org.apache.nifi.controller.StandardProcessorNode.setAnnotationData(StandardProcessorNode.java:1370)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateProcessor(StandardVersionedComponentSynchronizer.java:2529)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeProcessors(StandardVersionedComponentSynchronizer.java:880)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:407)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:248)
at 
org.apache.nifi.controller.flow.AbstractFlowManager.withParameterContextResolution(AbstractFlowManager.java:464)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:246)
at 
org.apache.nifi.groups.StandardProcessGroup.synchronizeFlow(StandardProcessGroup.java:3825)
at 
org.apache.nifi.groups.StandardProcessGroup.updateFlow(StandardProcessGroup.java:3805)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO.updateProcessGroupFlow(StandardProcessGroupDAO.java:431)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO$$FastClassBySpringCGLIB$$10a99b47.invoke()
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
at 
org.apache.nifi.audit.ProcessGroupAuditor.updateProcessGroupFlowAdvice(ProcessGroupAuditor.java:313)
at sun.reflect.GeneratedMethodAccessor1323.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:634)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:624)
at 
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:72)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 

[GitHub] [nifi] turcsanyip closed pull request #6331: NIFI-10380 ListDropbox processor

[GitBox]

turcsanyip closed pull request #6331: NIFI-10380 ListDropbox processor
URL: https://github.com/apache/nifi/pull/6331


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] ravinarayansingh commented on a diff in pull request #6367: NIFI-10435: Masked sensitive properties while writing command arguments to the flow file …

[GitBox]

ravinarayansingh commented on code in PR #6367:
URL: https://github.com/apache/nifi/pull/6367#discussion_r964830153


##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteStreamCommand.java:
##
@@ -419,21 +422,27 @@ public void onTrigger(ProcessContext context, final 
ProcessSession session) thro
 }
 return 0;
 });
-for ( final PropertyDescriptor descriptor : propertyDescriptors) {
+
+for (final PropertyDescriptor descriptor : propertyDescriptors) {
+if (descriptor.isSensitive()) {
+String maskedValue = IntStream.rangeClosed(0, 
MASKED_VALUE_LENGTH).mapToObj(i -> "*").collect(Collectors.joining());
+argumentAttributeValue.add(maskedValue);

Review Comment:
   okay i will change 



-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (NIFI-10419) Record does not have a value for the Required column 'dut_revision'

[Matt Burgess (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601305#comment-17601305
 ] 

Matt Burgess commented on NIFI-10419:
-

What is your table definition?

> Record does not have a value for the Required column 'dut_revision'
> ---
>
> Key: NIFI-10419
> URL: https://issues.apache.org/jira/browse/NIFI-10419
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Docker
>Affects Versions: 1.16.3
> Environment: docker 
>Reporter: lijunbao
>Priority: Major
>
> All of our fields have values, but this error is reported. I modify the field 
> not null to default null, and the error disappears
> ERROR [Timer-Driven Process Thread-10] o.a.n.p.standard.PutDatabaseRecord 
> PutDatabaseRecord[id=012f20f9-1089-1182-7dec-f7ff0f1bd17b] Failed to put 
> Records to database for 
> StandardFlowFileRecord[uuid=c8bbd9ef-1b48-4b32-9809-ba718d9319ad,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1662017931571-52877, 
> container=default, section=653], offset=1155, 
> length=1172],offset=0,name=ef006c68-d18e-4257-bc02-dd1de2b997a4,size=1172]. 
> Routing to failure.
> java.lang.IllegalArgumentException: Record does not have a value for the 
> Required column 'dut_revision'



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (NIFI-10419) Record does not have a value for the Required column 'dut_revision'

[Matt Burgess (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-10419:

Fix Version/s: (was: 1.16.3)

> Record does not have a value for the Required column 'dut_revision'
> ---
>
> Key: NIFI-10419
> URL: https://issues.apache.org/jira/browse/NIFI-10419
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Docker
>Affects Versions: 1.16.3
> Environment: docker 
>Reporter: lijunbao
>Priority: Major
>
> All of our fields have values, but this error is reported. I modify the field 
> not null to default null, and the error disappears
> ERROR [Timer-Driven Process Thread-10] o.a.n.p.standard.PutDatabaseRecord 
> PutDatabaseRecord[id=012f20f9-1089-1182-7dec-f7ff0f1bd17b] Failed to put 
> Records to database for 
> StandardFlowFileRecord[uuid=c8bbd9ef-1b48-4b32-9809-ba718d9319ad,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1662017931571-52877, 
> container=default, section=653], offset=1155, 
> length=1172],offset=0,name=ef006c68-d18e-4257-bc02-dd1de2b997a4,size=1172]. 
> Routing to failure.
> java.lang.IllegalArgumentException: Record does not have a value for the 
> Required column 'dut_revision'



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (NIFI-10454) flowfiles not progressing

[Jira]

[ 
https://issues.apache.org/jira/browse/NIFI-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601319#comment-17601319
 ] 

Nurullah Çalışkan commented on NIFI-10454:
--

Or as an alternative solution, for example, the number of active threads is 93 
(this was the number that appeared in my case), in this case, if you set the 
timer driven thread count to 100, the number of threads will quickly decrease 
to the actual number.

> flowfiles not progressing
> -
>
> Key: NIFI-10454
> URL: https://issues.apache.org/jira/browse/NIFI-10454
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Nurullah Çalışkan
>Priority: Major
>
> When the script body part of the execute script processor is set as set empty 
> string and added to the nifi UI from the registry, 1 thread is open. The more 
> processors there are, the more threads open. Because these threads are not 
> terminated, the processors cannot proceed to the next runtime. This prevents 
> flowfiles from progressing.
> I found a solution for this myself, so I'll share it. I found each processor 
> one by one and terminated it. Problem solved. Then my flowfiles started to 
> progress.
> This is the problem: I've seen nifi-1.15.x , nifi-1.16.0 and nifi-1.17.0, but 
> haven't tried the others. I am using openjdk java 11.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [nifi] turcsanyip commented on pull request #6331: NIFI-10380 ListDropbox processor

[GitBox]

turcsanyip commented on PR #6331:
URL: https://github.com/apache/nifi/pull/6331#issuecomment-123959

   Closed accidentally. Reopening...


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (NIFI-10440) JsonTreeReader - all strings Schema Access Strategy

[Matt Burgess (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601290#comment-17601290
 ] 

Matt Burgess commented on NIFI-10440:
-

Can you provide more details here? Perhaps share your flow or a reproduction 
flow? If you are using Infer Schema for JsonTreeReader, you could instead 
supply an explicit schema that treats each field as a string (although you 
would have to know all fields in the JSON document).

> JsonTreeReader - all strings Schema Access Strategy
> ---
>
> Key: NIFI-10440
> URL: https://issues.apache.org/jira/browse/NIFI-10440
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: DEOM Damien
>Priority: Critical
>
> Similary to CSVReader, JsonTreeReader should have an option to treat all 
> values as strings in Schema Access Strategy
>  
> It is mandatory in order to avoid cryptic errors like:
>  
> PutDatabaseRecord[id=99723f81-545a-13a7-9136-742bda23d870] Failed to put 
> Records to database for 
> StandardFlowFileRecord[uuid=6e4eae83-83d7-4c42-a3a2-1bf6d72ac121,claim=StandardContentClaim
>  [resourceClaim=StandardResourceClaim[id=1662386479395-157, 
> container=default, section=157], offset=730137, 
> length=231164],offset=0,name=ca3ede75-9b72-4dec-930a-420ae5267b8a,size=231164].
>  Routing to failure.: Cannot convert CHOICE, type must be explicit



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (NIFI-9989) sftp processors Received SSH_MSG_UNIMPLEMENTED

[Wiktor Kubicki (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601135#comment-17601135
 ] 

Wiktor Kubicki edited comment on NIFI-9989 at 9/7/22 12:51 PM:
---

[~exceptionfactory] thank you for your analys. I can disable Keep Alive in 
ListSFTP and it is probably good workaround. But I'm getting this error for 
FetchSFTP too, and there i can't disable Keep Alive because when i have it off, 
then:

{code:java}
FetchSFTP[id=0171108a-3596-188c-e3c6-0728aabc0bfd] Failed to close SFTPClient 
due to net.schmizz.sshj.connection.ConnectionException: Timeout expired: 
net.schmizz.sshj.connection.ConnectionException: Timeout expired - Caused by: 
java.util.concurrent.TimeoutException: Timeout expired 
{code}

This comes because our network killing not used connections - it is *not* nifi 
issue, but i need that option on.

I created seperated ticket for Send Alive support for ListSFTP (NIFI-10450). 
Can you created bug report in SSHJ? You are able to provide better tech 
description.
But.. it began in NiFi 1.16.1. The reason is sshj uprade or other changes in 
NiFi code? Maybe you can fix it here?




was (Author: kirhold):
[~exceptionfactory] thank you for your analys. I can disable Keep Alive in 
ListSFTP and it is probably good workaround. But I'm getting this error for 
FetchSFTP too, and there i can't disable Keep Alive because when i have it off, 
then:

{code:java}
FetchSFTP[id=0171108a-3596-188c-e3c6-0728aabc0bfd] Failed to close SFTPClient 
due to net.schmizz.sshj.connection.ConnectionException: Timeout expired: 
net.schmizz.sshj.connection.ConnectionException: Timeout expired - Caused by: 
java.util.concurrent.TimeoutException: Timeout expired 
{code}

This comes because our network killing not used connections - it is *not* nifi 
issue, but i need that option on.

I created seperated ticket for Send Alive support for LiveSFTP (NIFI-10450). 
Can you created bug report in SSHJ? You are able to provide better tech 
description.
But.. it began in NiFi 1.16.1. The reason is sshj uprade or other changes in 
NiFi code? Maybe you can fix it here?



> sftp processors Received SSH_MSG_UNIMPLEMENTED
> --
>
> Key: NIFI-9989
> URL: https://issues.apache.org/jira/browse/NIFI-9989
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.17.0, 1.16.1
> Environment: Ubuntu 20.04, openjdk version "1.8.0_312"
> OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07)
> OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)
>Reporter: Jens M Kofoed
>Assignee: David Handermann
>Priority: Major
> Attachments: image-2022-08-16-09-44-10-682.png
>
>
> After upgrading from single instance version 1.13.2 to a 3 node cluster 
> version 1.16.1 All sftp processors occasionally report errors:
> 2022-05-05 07:26:08,318 INFO [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.random.JCERandom Creating new SecureRandom.
> 2022-05-05 07:26:08,318 DEBUG [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.random.JCERandom Random creation took 0 ms
> 2022-05-05 07:26:08,318 DEBUG [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.DefaultConfig Available cipher factories: 
> [chacha20-poly1...@openssh.com, aes128-cbc, aes128-ctr, aes192-cbc, 
> aes192-ctr, aes256-cbc, aes256-ctr, aes128-...@openssh.com, 
> aes256-...@openssh.com, blowfish-cbc, blowfish-ctr, cast128-cbc, cast128-ctr, 
> idea-cbc, idea-ctr, serpent128-cbc, serpent128-ctr, serpent192-cbc, 
> serpent192-ctr, serpent256-cbc, serpent256-ctr, 3des-cbc, 3des-ctr, 
> twofish128-cbc, twofish128-ctr, twofish192-cbc, twofish192-ctr, 
> twofish256-cbc, twofish256-ctr, twofish-cbc, arcfour, arcfour128, arcfour256]
> 2022-05-05 07:26:08,319 INFO [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.TransportImpl Client identity string: 
> SSH-2.0-SSHJ_0.33.0
> 2022-05-05 07:26:08,334 INFO [Timer-Driven Process Thread-7] 
> net.schmizz.sshj.transport.TransportImpl Server identity string: 
> SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.4
> 2022-05-05 07:26:08,339 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Received SSH_MSG_KEXINIT
> 2022-05-05 07:26:08,340 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Sending SSH_MSG_KEXINIT
> 2022-05-05 07:26:08,340 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> net.schmizz.sshj.transport.KeyExchanger Negotiated algorithms: [ 
> kex=curve25519-sha256; sig=ssh-ed25519; 
> c2sCipher=chacha20-poly1...@openssh.com; 
> s2cCipher=chacha20-poly1...@openssh.com; c2sMAC=hmac-sha1; s2cMAC=hmac-sha1; 
> c2sComp=none; s2cComp=none;  ]
> 2022-05-05 07:26:08,340 DEBUG [sshj-Reader-hostname/192.168.1.3:22] 
> 

[jira] [Commented] (NIFI-10454) flowfiles not progressing

[Mark Payne (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601323#comment-17601323
 ] 

Mark Payne commented on NIFI-10454:
---

[~nurullahcaliskan] can you capture a thread dump (bin/nifi.sh dump 
threaad-dump.txt) when NiFi is in this state?

> flowfiles not progressing
> -
>
> Key: NIFI-10454
> URL: https://issues.apache.org/jira/browse/NIFI-10454
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Nurullah Çalışkan
>Priority: Major
>
> When the script body part of the execute script processor is set as set empty 
> string and added to the nifi UI from the registry, 1 thread is open. The more 
> processors there are, the more threads open. Because these threads are not 
> terminated, the processors cannot proceed to the next runtime. This prevents 
> flowfiles from progressing.
> I found a solution for this myself, so I'll share it. I found each processor 
> one by one and terminated it. Problem solved. Then my flowfiles started to 
> progress.
> This is the problem: I've seen nifi-1.15.x , nifi-1.16.0 and nifi-1.17.0, but 
> haven't tried the others. I am using openjdk java 11.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [nifi] ravinarayansingh commented on a diff in pull request #6367: NIFI-10435: Masked sensitive properties while writing command arguments to the flow file …

[GitBox]

ravinarayansingh commented on code in PR #6367:
URL: https://github.com/apache/nifi/pull/6367#discussion_r964831097


##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteStreamCommand.java:
##
@@ -419,21 +422,27 @@ public void onTrigger(ProcessContext context, final 
ProcessSession session) thro
 }
 return 0;
 });
-for ( final PropertyDescriptor descriptor : propertyDescriptors) {
+
+for (final PropertyDescriptor descriptor : propertyDescriptors) {
+if (descriptor.isSensitive()) {
+String maskedValue = IntStream.rangeClosed(0, 
MASKED_VALUE_LENGTH).mapToObj(i -> "*").collect(Collectors.joining());
+argumentAttributeValue.add(maskedValue);
+} else {
+
argumentAttributeValue.add(context.getProperty(descriptor.getName()).evaluateAttributeExpressions(inputFlowFile).getValue());
+}
 
args.add(context.getProperty(descriptor.getName()).evaluateAttributeExpressions(inputFlowFile).getValue());

Review Comment:
   sure i will assign value to variable and reuse 



-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (NIFI-10453) Cannot set AnnotationData while processor is running

[Matt Burgess (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601307#comment-17601307
 ] 

Matt Burgess commented on NIFI-10453:
-

How are you changing to a new version of the flow? Is it a child Process Group 
you're updating from a NiFi Registry?

> Cannot set AnnotationData while processor is running
> 
>
> Key: NIFI-10453
> URL: https://issues.apache.org/jira/browse/NIFI-10453
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Flow Versioning
>Affects Versions: 1.17.0, 1.16.3
> Environment: Linux debian
>Reporter: hipotures
>Priority: Major
>
> *Action*: Change version
> *Problem*: Can't change to newer version of flow
> *Web UI error popup*:
> Change Version
> Failed to perform update flow request due to Cannot set AnnotationData while 
> processor is running
> *Description*: Updated flow is in state STOPPED. Controller is active (this 
> controller is shared between many other flows).
> *Workaround*: Stop all flows and controllers.
> *Error Log*:
> {code:java}
> 2022-09-07 10:43:05,380 ERROR [Process Group Update Thread-1] 
> o.apache.nifi.web.api.FlowUpdateResource Failed to perform update flow 
> request 
> java.lang.IllegalStateException: Cannot set AnnotationData while processor is 
> running
>   at 
> org.apache.nifi.controller.StandardProcessorNode.setAnnotationData(StandardProcessorNode.java:1370)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateProcessor(StandardVersionedComponentSynchronizer.java:2529)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeProcessors(StandardVersionedComponentSynchronizer.java:880)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:407)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:248)
>   at 
> org.apache.nifi.controller.flow.AbstractFlowManager.withParameterContextResolution(AbstractFlowManager.java:464)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:246)
>   at 
> org.apache.nifi.groups.StandardProcessGroup.synchronizeFlow(StandardProcessGroup.java:3825)
>   at 
> org.apache.nifi.groups.StandardProcessGroup.updateFlow(StandardProcessGroup.java:3805)
>   at 
> org.apache.nifi.web.dao.impl.StandardProcessGroupDAO.updateProcessGroupFlow(StandardProcessGroupDAO.java:431)
>   at 
> org.apache.nifi.web.dao.impl.StandardProcessGroupDAO$$FastClassBySpringCGLIB$$10a99b47.invoke()
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
>   at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
>   at 
> org.apache.nifi.audit.ProcessGroupAuditor.updateProcessGroupFlowAdvice(ProcessGroupAuditor.java:313)
>   at sun.reflect.GeneratedMethodAccessor1323.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:634)
>   at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:624)
>   at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:72)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
>   at 
> 

[jira] [Updated] (NIFI-10453) Cannot set AnnotationData while processor is running

[hipotures (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

hipotures updated NIFI-10453:
-
Description: 
*Action*: Change version
*Problem*: Can't change to newer version of flow

*Web UI error popup*:
Change Version
Failed to perform update flow request due to Cannot set AnnotationData while 
processor is running

*Description*: Updated flow is in state STOPPED. Controller is active (this 
controller is shared between many other flows).

*Workaround*: Stop all flows and controllers.

*Error Log*:

{code:java}
2022-09-07 10:43:05,380 ERROR [Process Group Update Thread-1] 
o.apache.nifi.web.api.FlowUpdateResource Failed to perform update flow request 
java.lang.IllegalStateException: Cannot set AnnotationData while processor is 
running
at 
org.apache.nifi.controller.StandardProcessorNode.setAnnotationData(StandardProcessorNode.java:1370)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateProcessor(StandardVersionedComponentSynchronizer.java:2529)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeProcessors(StandardVersionedComponentSynchronizer.java:880)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:407)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:248)
at 
org.apache.nifi.controller.flow.AbstractFlowManager.withParameterContextResolution(AbstractFlowManager.java:464)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:246)
at 
org.apache.nifi.groups.StandardProcessGroup.synchronizeFlow(StandardProcessGroup.java:3825)
at 
org.apache.nifi.groups.StandardProcessGroup.updateFlow(StandardProcessGroup.java:3805)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO.updateProcessGroupFlow(StandardProcessGroupDAO.java:431)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO$$FastClassBySpringCGLIB$$10a99b47.invoke()
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
at 
org.apache.nifi.audit.ProcessGroupAuditor.updateProcessGroupFlowAdvice(ProcessGroupAuditor.java:313)
at sun.reflect.GeneratedMethodAccessor1323.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:634)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:624)
at 
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:72)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:708)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO$$EnhancerBySpringCGLIB$$f6deb592.updateProcessGroupFlow()
   

[jira] [Created] (NIFI-10454) flowfiles not progressing

[Jira]

Nurullah Çalışkan created NIFI-10454:


 Summary: flowfiles not progressing
 Key: NIFI-10454
 URL: https://issues.apache.org/jira/browse/NIFI-10454
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Nurullah Çalışkan


When the script body part of the execute script processor is set as set empty 
string and added to the nifi UI from the registry, 1 thread is open. The more 
processors there are, the more threads open. Because these threads are not 
terminated, the processors cannot proceed to the next runtime. This prevents 
flowfiles from progressing.

I found a solution for this myself, so I'll share it. I found each processor 
one by one and terminated it. Problem solved. Then my flowfiles started to 
progress.

This is the problem: I've seen nifi-1.15.x , nifi-1.16.0 and nifi-1.17.0, but 
haven't tried the others. I am using openjdk java 11.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (NIFI-10453) Cannot set AnnotationData while processor is running

[hipotures (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

hipotures updated NIFI-10453:
-
Description: 
Action: Change version
Problem: Can't change to newer version of flow

Web UI error popup:
Change Version
Failed to perform update flow request due to Cannot set AnnotationData while 
processor is running

Description: Updated flow is in state STOPPED. Controller is active (this 
controller is shared between many other flows).

Workaround: Stop all flows and controllers.

Error Log:

{code:java}
2022-09-07 10:43:05,380 ERROR [Process Group Update Thread-1] 
o.apache.nifi.web.api.FlowUpdateResource Failed to perform update flow request 
java.lang.IllegalStateException: Cannot set AnnotationData while processor is 
running
at 
org.apache.nifi.controller.StandardProcessorNode.setAnnotationData(StandardProcessorNode.java:1370)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateProcessor(StandardVersionedComponentSynchronizer.java:2529)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeProcessors(StandardVersionedComponentSynchronizer.java:880)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:407)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:248)
at 
org.apache.nifi.controller.flow.AbstractFlowManager.withParameterContextResolution(AbstractFlowManager.java:464)
at 
org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:246)
at 
org.apache.nifi.groups.StandardProcessGroup.synchronizeFlow(StandardProcessGroup.java:3825)
at 
org.apache.nifi.groups.StandardProcessGroup.updateFlow(StandardProcessGroup.java:3805)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO.updateProcessGroupFlow(StandardProcessGroupDAO.java:431)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO$$FastClassBySpringCGLIB$$10a99b47.invoke()
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
at 
org.apache.nifi.audit.ProcessGroupAuditor.updateProcessGroupFlowAdvice(ProcessGroupAuditor.java:313)
at sun.reflect.GeneratedMethodAccessor1323.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:634)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:624)
at 
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:72)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:708)
at 
org.apache.nifi.web.dao.impl.StandardProcessGroupDAO$$EnhancerBySpringCGLIB$$f6deb592.updateProcessGroupFlow()
at 

[jira] [Updated] (NIFI-10453) Cannot set AnnotationData while processor is running

[hipotures (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

hipotures updated NIFI-10453:
-
Affects Version/s: 1.16.3

> Cannot set AnnotationData while processor is running
> 
>
> Key: NIFI-10453
> URL: https://issues.apache.org/jira/browse/NIFI-10453
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Flow Versioning
>Affects Versions: 1.17.0, 1.16.3
> Environment: Linux debian
>Reporter: hipotures
>Priority: Major
>
> *Action*: Change version
> *Problem*: Can't change to newer version of flow
> *Web UI error popup*:
> Change Version
> Failed to perform update flow request due to Cannot set AnnotationData while 
> processor is running
> *Description*: Updated flow is in state STOPPED. Controller is active (this 
> controller is shared between many other flows).
> *Workaround*: Stop all flows and controllers.
> *Error Log*:
> {code:java}
> 2022-09-07 10:43:05,380 ERROR [Process Group Update Thread-1] 
> o.apache.nifi.web.api.FlowUpdateResource Failed to perform update flow 
> request 
> java.lang.IllegalStateException: Cannot set AnnotationData while processor is 
> running
>   at 
> org.apache.nifi.controller.StandardProcessorNode.setAnnotationData(StandardProcessorNode.java:1370)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.updateProcessor(StandardVersionedComponentSynchronizer.java:2529)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeProcessors(StandardVersionedComponentSynchronizer.java:880)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:407)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronizeChildGroups(StandardVersionedComponentSynchronizer.java:489)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:401)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.lambda$synchronize$0(StandardVersionedComponentSynchronizer.java:248)
>   at 
> org.apache.nifi.controller.flow.AbstractFlowManager.withParameterContextResolution(AbstractFlowManager.java:464)
>   at 
> org.apache.nifi.flow.synchronization.StandardVersionedComponentSynchronizer.synchronize(StandardVersionedComponentSynchronizer.java:246)
>   at 
> org.apache.nifi.groups.StandardProcessGroup.synchronizeFlow(StandardProcessGroup.java:3825)
>   at 
> org.apache.nifi.groups.StandardProcessGroup.updateFlow(StandardProcessGroup.java:3805)
>   at 
> org.apache.nifi.web.dao.impl.StandardProcessGroupDAO.updateProcessGroupFlow(StandardProcessGroupDAO.java:431)
>   at 
> org.apache.nifi.web.dao.impl.StandardProcessGroupDAO$$FastClassBySpringCGLIB$$10a99b47.invoke()
>   at 
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
>   at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:89)
>   at 
> org.apache.nifi.audit.ProcessGroupAuditor.updateProcessGroupFlowAdvice(ProcessGroupAuditor.java:313)
>   at sun.reflect.GeneratedMethodAccessor1323.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:634)
>   at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:624)
>   at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:72)
>   at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
>   at 
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763)
>   at 
> 

[jira] [Commented] (NIFI-10377) Multiple executesqlrecord using the same jdbc connection pool causes the query to report an error

[Matt Burgess (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601306#comment-17601306
 ] 

Matt Burgess commented on NIFI-10377:
-

Can you share the error from the log and the configuration of the Connection 
Pool?

> Multiple executesqlrecord using the same jdbc connection pool causes the 
> query to report an error
> -
>
> Key: NIFI-10377
> URL: https://issues.apache.org/jira/browse/NIFI-10377
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.16.1
> Environment: Nifi 1.6.1 version 
>Reporter: sunhao
>Priority: Major
>
> Nifi 1.6.1 version uses pijdbc to read data, and there is no problem with one 
> connection pool corresponding to one executesqlrecord，Multiple 
> executesqlrecord using the same jdbc connection pool causes the query to 
> report an error，My intention is to access the pi database in parallel to read 
> data



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (NIFI-10454) flowfiles not progressing

[Jira]

[ 
https://issues.apache.org/jira/browse/NIFI-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601331#comment-17601331
 ] 

Nurullah Çalışkan commented on NIFI-10454:
--

[~markap14]  Sure, but the nifis we are having this problem with, I will take a 
clone in production environment and pull it to my local and send the dump.

> flowfiles not progressing
> -
>
> Key: NIFI-10454
> URL: https://issues.apache.org/jira/browse/NIFI-10454
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Nurullah Çalışkan
>Priority: Major
>
> When the script body part of the execute script processor is set as set empty 
> string and added to the nifi UI from the registry, 1 thread is open. The more 
> processors there are, the more threads open. Because these threads are not 
> terminated, the processors cannot proceed to the next runtime. This prevents 
> flowfiles from progressing.
> I found a solution for this myself, so I'll share it. I found each processor 
> one by one and terminated it. Problem solved. Then my flowfiles started to 
> progress.
> This is the problem: I've seen nifi-1.15.x , nifi-1.16.0 and nifi-1.17.0, but 
> haven't tried the others. I am using openjdk java 11.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (NIFI-10454) flowfiles not progressing

[Matt Burgess (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601351#comment-17601351
 ] 

Matt Burgess commented on NIFI-10454:
-

How did you get any of the ExecuteScript processors with an empty string for 
Script Body to run? I tried importing a flow from the registry with 16 
ExecuteScript instances with an empty string for Script Body and all of them 
were instantly invalid.

> flowfiles not progressing
> -
>
> Key: NIFI-10454
> URL: https://issues.apache.org/jira/browse/NIFI-10454
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Nurullah Çalışkan
>Priority: Major
>
> When the script body part of the execute script processor is set as set empty 
> string and added to the nifi UI from the registry, 1 thread is open. The more 
> processors there are, the more threads open. Because these threads are not 
> terminated, the processors cannot proceed to the next runtime. This prevents 
> flowfiles from progressing.
> I found a solution for this myself, so I'll share it. I found each processor 
> one by one and terminated it. Problem solved. Then my flowfiles started to 
> progress.
> This is the problem: I've seen nifi-1.15.x , nifi-1.16.0 and nifi-1.17.0, but 
> haven't tried the others. I am using openjdk java 11.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [nifi] kevdoran closed pull request #6329: NIFI-10360 VOLUME declaration prevents updating flow from CI

[GitBox]

kevdoran closed pull request #6329: NIFI-10360 VOLUME declaration prevents 
updating flow from CI
URL: https://github.com/apache/nifi/pull/6329


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] kevdoran commented on pull request #6329: NIFI-10360 VOLUME declaration prevents updating flow from CI

[GitBox]

kevdoran commented on PR #6329:
URL: https://github.com/apache/nifi/pull/6329#issuecomment-1239566918

   Closing per discussion. Will revisit as part of [larger 
changes](https://cwiki.apache.org/confluence/display/NIFI/NiFi+Docker+Container+Improvements),
 planned tentatively for sometime in the next couple of months.


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] mathemare opened a new pull request, #6372: NIFI-10236: ByteArrayContentRepository in nifi-framework-components

[GitBox]

mathemare opened a new pull request, #6372:
URL: https://github.com/apache/nifi/pull/6372

   Improved ByteArrayContentRepository for nifi-framework-components, to be 
used in the classical nifi engine and the stateless engine
   
   - added implementation of the ByteArrayContentRepository with an optional 
max size
   - changed the interface ContentClaim for ContentClaims to implement if 
needed a setLength method used in the StandardContentClaimWriteCache
   - added tests inspired from the previous VolatileContentRepository and new 
use cases
   - added ByteArrayContentRepository to the administration guide
   
   Signed-off-by: mathemare 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   # Summary
   
   [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0)
   
   # Tracking
   
   Please complete the following tracking steps prior to pull request creation.
   
   ### Issue Tracking
   
   - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue 
created
   
   ### Pull Request Tracking
   
   - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as 
`NIFI-0`
   - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, 
as such `NIFI-0`
   
   ### Pull Request Formatting
   
   - [ ] Pull Request based on current revision of the `main` branch
   - [ ] Pull Request refers to a feature branch with one commit containing 
changes
   
   # Verification
   
   Please indicate the verification steps performed prior to pull request 
creation.
   
   ### Build
   
   - [ ] Build completed using `mvn clean install -P contrib-check`
 - [ ] JDK 8
 - [ ] JDK 11
 - [ ] JDK 17
   
   ### Licensing
   
   - [ ] New dependencies are compatible with the [Apache License 
2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License 
Policy](https://www.apache.org/legal/resolved.html)
   - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` 
files
   
   ### Documentation
   
   - [ ] Documentation formatting appears as expected in rendered files
   


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] nandorsoma opened a new pull request, #6373: NIFI-10411 Add record processing feature to PublishMQTT processor

[GitBox]

nandorsoma opened a new pull request, #6373:
URL: https://github.com/apache/nifi/pull/6373

   
   
   
   
   
   
   
   
   
   
   
   
   
   # Summary
   
   [NIFI-10411](https://issues.apache.org/jira/browse/NIFI-10411)
   
   This pr adds record processing feature to PublishMQTT processor. I also made 
a little bit of cleanup around the tests because the current structure is no 
longer useful (in the past multiple Test extended the Common one) and now it 
just makes the code difficult to understand. 
   
   # Tracking
   
   Please complete the following tracking steps prior to pull request creation.
   
   ### Issue Tracking
   
   - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue 
created
   
   ### Pull Request Tracking
   
   - [x] Pull Request title starts with Apache NiFi Jira issue number, such as 
`NIFI-0`
   - [x] Pull Request commit message starts with Apache NiFi Jira issue number, 
as such `NIFI-0`
   
   ### Pull Request Formatting
   
   - [x] Pull Request based on current revision of the `main` branch
   - [x] Pull Request refers to a feature branch with one commit containing 
changes
   
   # Verification
   
   Please indicate the verification steps performed prior to pull request 
creation.
   
   ### Build
   
   - [x] Build completed using `mvn clean install -P contrib-check`
 - [x] JDK 8
 - [ ] JDK 11
 - [ ] JDK 17
   
   ### Licensing
   
   - [ ] New dependencies are compatible with the [Apache License 
2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License 
Policy](https://www.apache.org/legal/resolved.html)
   - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` 
files
   
   ### Documentation
   
   - [ ] Documentation formatting appears as expected in rendered files
   


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Updated] (NIFI-10411) Add record processing feature to PublishMQTT processor

[Nandor Soma Abonyi (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nandor Soma Abonyi updated NIFI-10411:
--
Status: Patch Available  (was: Open)

> Add record processing feature to PublishMQTT processor
> --
>
> Key: NIFI-10411
> URL: https://issues.apache.org/jira/browse/NIFI-10411
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Nandor Soma Abonyi
>Assignee: Nandor Soma Abonyi
>Priority: Major
>  Labels: MQTT
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add record processing feature to PublishMQTT processor



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [nifi] ravinarayansingh commented on pull request #6367: NIFI-10435: Masked sensitive properties while writing command arguments to the flow file …

[GitBox]

ravinarayansingh commented on PR #6367:
URL: https://github.com/apache/nifi/pull/6367#issuecomment-1239794631

   > Thanks for the updates @ravinarayansingh, can you correct the Checkstyle 
warnings? Specifically, star imports should be avoided.
   > 
   > ```
   > AvoidStarImport: Using the '.*' form of import should be avoided
   > ```
   
   done


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] kevdoran commented on pull request #6329: NIFI-10360 VOLUME declaration prevents updating flow from CI

[GitBox]

kevdoran commented on PR #6329:
URL: https://github.com/apache/nifi/pull/6329#issuecomment-1239554932

   @vitalyzhakov If you are ok with revisiting this as part of a larger 
refactoring to our approach to Docker images, we can go ahead and close this PR.


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] vitalyzhakov commented on pull request #6329: NIFI-10360 VOLUME declaration prevents updating flow from CI

[GitBox]

vitalyzhakov commented on PR #6329:
URL: https://github.com/apache/nifi/pull/6329#issuecomment-1239561682

   @kevdoran , hello!
   I'm OK, thank you!


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] tpalfy commented on a diff in pull request #6331: NIFI-10380 ListDropbox processor

[GitBox]

tpalfy commented on code in PR #6331:
URL: https://github.com/apache/nifi/pull/6331#discussion_r964924295


##
nifi-nar-bundles/nifi-dropbox-bundle/nifi-dropbox-processors/src/main/java/org/apache/nifi/processors/dropbox/ListDropbox.java:
##
@@ -0,0 +1,295 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.dropbox;
+
+import static java.lang.String.format;
+
+import com.dropbox.core.DbxException;
+import com.dropbox.core.DbxRequestConfig;
+import com.dropbox.core.oauth.DbxCredential;
+import com.dropbox.core.v2.DbxClientV2;
+import com.dropbox.core.v2.files.FileMetadata;
+import com.dropbox.core.v2.files.ListFolderBuilder;
+import com.dropbox.core.v2.files.ListFolderResult;
+import com.dropbox.core.v2.files.Metadata;
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Optional;
+import java.util.concurrent.TimeUnit;
+import java.util.function.Predicate;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.PrimaryNodeOnly;
+import org.apache.nifi.annotation.behavior.Stateful;
+import org.apache.nifi.annotation.behavior.TriggerSerially;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.state.Scope;
+import org.apache.nifi.context.PropertyContext;
+import org.apache.nifi.dropbox.credentials.service.DropboxCredentialDetails;
+import org.apache.nifi.dropbox.credentials.service.DropboxCredentialService;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.processor.util.list.AbstractListProcessor;
+import org.apache.nifi.processor.util.list.ListedEntityTracker;
+import org.apache.nifi.serialization.record.RecordSchema;
+
+@PrimaryNodeOnly
+@TriggerSerially
+@Tags({"dropbox", "storage"})
+@CapabilityDescription("Retrieves a listing of files from Dropbox (shortcuts 
are ignored)." +
+" Each listed file may result in one FlowFile, the metadata being 
written as Flowfile attributes." +
+" When the 'Record Writer' property is set, the entire result is 
written as records to a single FlowFile." +
+" This Processor is designed to run on Primary Node only in a cluster. 
If the primary node changes, the new Primary Node will pick up where the" +
+" previous node left off without duplicating all of the data.")
+@InputRequirement(Requirement.INPUT_FORBIDDEN)
+@WritesAttributes({@WritesAttribute(attribute = DropboxFileInfo.ID, 
description = "The Dropbox identifier of the file"),
+@WritesAttribute(attribute = DropboxFileInfo.PATH, description = "The 
folder path where the file is located"),
+@WritesAttribute(attribute = DropboxFileInfo.FILENAME, description = 
"The name of the file"),
+@WritesAttribute(attribute = DropboxFileInfo.SIZE, description = "The 
size of the file"),
+@WritesAttribute(attribute = DropboxFileInfo.TIMESTAMP, description = 
"The server modified time, when the file was uploaded to Dropbox"),
+@WritesAttribute(attribute = DropboxFileInfo.REVISION, description = 
"Revision of the file")})
+@Stateful(scopes = {Scope.CLUSTER}, description = "The processor stores 
necessary data to be able to keep track what files have been listed already. " +
+"What exactly needs to be stored depends on the 'Listing Strategy'.")
+public class ListDropbox extends AbstractListProcessor  {
+
+public static final PropertyDescriptor FOLDER = new 
PropertyDescriptor.Builder()
+.name("folder")
+  

[jira] [Commented] (NIFI-10236) ByteArrayContentRepository in core framework

[Jira]

[ 
https://issues.apache.org/jira/browse/NIFI-10236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601383#comment-17601383
 ] 

Matthieu RÉ commented on NIFI-10236:


Hello David, hello Mark,
Thank you very much for your answers ! I needed the whole summer to compute 
your response and to produce something that passes my tests, sorry for the long 
time without answer. Now that I have a version that works we can maybe discuss 
it a little bit more.

My main point is that I struggled to have a wrapped version containing the 
length for it to be used in the ContentClaimCache, because I wasn't sure about 
where to set this wrapper for any other component to be able to call the 
ContentClaim.getLength() or "ContentClaimSomething".getLength(), without this 
cache available. It seemed more natural to me (and to be honest I didn't 
managed to make a proper wrapped version work correctly) to store this "length" 
information directly in the ContentClaim. So this version 
(https://github.com/apache/nifi/pull/6372) proposes to have the "length", its 
getter and setter directly in the ContentClaim interface. But then I am not 
sure about its name, since this "length" is not the actual length taken by the 
claim in the repository (on my understanding it is more related to an offset 
?), and is assigned by another object (the ContentClaimCache for instance)... 
Should I try another name ? Or maybe do you see a better implementation with a 
wrapper for the StandardContentClaimWriteCache ?

Thank you for you advices

> ByteArrayContentRepository in core framework
> 
>
> Key: NIFI-10236
> URL: https://issues.apache.org/jira/browse/NIFI-10236
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Affects Versions: 1.17.0
>Reporter: Matthieu RÉ
>Assignee: Matthieu RÉ
>Priority: Major
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> As discussed in NIFI-8760 and by mail, the use case of using an in-memory 
> based implementation of the ContentRepository is not completed after 1.17.0 
> and the removal of the old VolatileContentRepository (NIFI-9823) when the 
> ExecuteStateless is not a solution.
> As proposed by mail, the ByteArrayContentRepository could be duplicated from 
> the nifi-stateless framework to the core one, but maybe with more 
> functionalities, for instance the follow-up of the space taken in memory, and 
> the limitation of its total usage.
> Don't hesitate to comment, add or discuss requirements or the implementation 
> I will propose.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [nifi-minifi-cpp] lordgamez commented on a diff in pull request #1409: MINIFICPP-1911 Make concat_path variadic

[GitBox]

lordgamez commented on code in PR #1409:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1409#discussion_r964470948


##
extensions/sftp/processors/ListSFTP.cpp:
##
@@ -186,7 +186,7 @@ ListSFTP::Child::Child(const std::string& parent_path_, 
std::tuple

[GitHub] [nifi] simonbence opened a new pull request, #6374: NIFI-10451 Updating QuestDB based status history rollover mechanism to fit the new major version

[GitBox]

simonbence opened a new pull request, #6374:
URL: https://github.com/apache/nifi/pull/6374

   [NIFI-10451](https://issues.apache.org/jira/browse/NIFI-10451)
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   # Summary
   
   [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0)
   
   # Tracking
   
   Please complete the following tracking steps prior to pull request creation.
   
   ### Issue Tracking
   
   - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue 
created
   
   ### Pull Request Tracking
   
   - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as 
`NIFI-0`
   - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, 
as such `NIFI-0`
   
   ### Pull Request Formatting
   
   - [ ] Pull Request based on current revision of the `main` branch
   - [ ] Pull Request refers to a feature branch with one commit containing 
changes
   
   # Verification
   
   Please indicate the verification steps performed prior to pull request 
creation.
   
   ### Build
   
   - [ ] Build completed using `mvn clean install -P contrib-check`
 - [ ] JDK 8
 - [ ] JDK 11
 - [ ] JDK 17
   
   ### Licensing
   
   - [ ] New dependencies are compatible with the [Apache License 
2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License 
Policy](https://www.apache.org/legal/resolved.html)
   - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` 
files
   
   ### Documentation
   
   - [ ] Documentation formatting appears as expected in rendered files
   


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] turcsanyip commented on a diff in pull request #6368: NIFI-10442: Create PutIceberg processor

[GitBox]

turcsanyip commented on code in PR #6368:
URL: https://github.com/apache/nifi/pull/6368#discussion_r965057634


##
nifi-nar-bundles/nifi-iceberg-bundle/nifi-iceberg-services/src/main/java/org/apache/nifi/services/iceberg/HadoopCatalogService.java:
##
@@ -0,0 +1,68 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.services.iceberg;
+
+import org.apache.hadoop.conf.Configuration;
+import org.apache.iceberg.catalog.Catalog;
+import org.apache.iceberg.hadoop.HadoopCatalog;
+import org.apache.nifi.annotation.lifecycle.OnEnabled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.controller.AbstractControllerService;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.Collections;
+import java.util.List;
+
+/**
+ * Catalog service implementation that can use HDFS or similar file systems 
that support atomic rename.
+ */
+public class HadoopCatalogService extends AbstractControllerService implements 
IcebergCatalogService {
+
+static final PropertyDescriptor WAREHOUSE_PATH = new 
PropertyDescriptor.Builder()
+.name("warehouse-path")
+.displayName("Warehouse path")

Review Comment:
   Please use title case:
   ```suggestion
   .displayName("Warehouse Path")
   ```



##
nifi-nar-bundles/nifi-iceberg-bundle/nifi-iceberg-services-api/src/main/java/org/apache/nifi/services/iceberg/IcebergCatalogService.java:
##
@@ -0,0 +1,30 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.services.iceberg;
+
+import org.apache.iceberg.catalog.Catalog;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.controller.ControllerService;
+
+@Tags({"iceberg", "catalog", "service"})
+@CapabilityDescription("Provides a basic connector to Iceberg catalog 
services.")

Review Comment:
   These annotations must be specified on the CS implementation class, not on 
the CS interface.



##
nifi-nar-bundles/nifi-iceberg-bundle/nifi-iceberg-processors/src/main/java/org/apache/nifi/processors/iceberg/PutIceberg.java:
##
@@ -0,0 +1,224 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.iceberg;
+
+import org.apache.iceberg.BaseTable;
+import org.apache.iceberg.Table;
+import org.apache.iceberg.catalog.Catalog;
+import org.apache.iceberg.catalog.Namespace;
+import org.apache.iceberg.catalog.TableIdentifier;
+import org.apache.iceberg.io.TaskWriter;
+import org.apache.iceberg.io.WriteResult;
+import 

[GitHub] [nifi] nandorsoma commented on a diff in pull request #6373: NIFI-10411 Add record processing feature to PublishMQTT processor

[GitBox]

nandorsoma commented on code in PR #6373:
URL: https://github.com/apache/nifi/pull/6373#discussion_r965341740


##
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java:
##
@@ -232,6 +235,22 @@ private static String getSupportedSchemeList() {
 .addValidator(StandardValidators.POSITIVE_INTEGER_VALIDATOR)
 .build();
 
+public static final PropertyDescriptor RECORD_READER = new 
PropertyDescriptor.Builder()
+.name("record-reader")
+.displayName("Record Reader")
+.description("The Record Reader to use for received messages")

Review Comment:
   Thats a good idea, will do it!



-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] turcsanyip commented on a diff in pull request #6373: NIFI-10411 Add record processing feature to PublishMQTT processor

[GitBox]

turcsanyip commented on code in PR #6373:
URL: https://github.com/apache/nifi/pull/6373#discussion_r965334984


##
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java:
##
@@ -232,6 +235,22 @@ private static String getSupportedSchemeList() {
 .addValidator(StandardValidators.POSITIVE_INTEGER_VALIDATOR)
 .build();
 
+public static final PropertyDescriptor RECORD_READER = new 
PropertyDescriptor.Builder()
+.name("record-reader")
+.displayName("Record Reader")
+.description("The Record Reader to use for received messages")

Review Comment:
   The descriptions for the Record Reader/Writer were inherited from the 
Consume processor but they are not exactly applicable to the Publish processor 
because it does not receive messages and does not write FlowFiles but the 
opposite (reads FF and writes message).
   
   I would avoid changing it to a common but generic (and meaningless) message 
and would rather suggest the following:
   - do not specify description in the abstract class
   - redeclare the PropertyDescriptor in Consume and Publish using `new 
PropertyDescriptor.Builder().fromPropertyDescriptor()` and add the specific 
descriptions there



##
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/pom.xml:
##
@@ -93,5 +93,11 @@
 nifi-schema-registry-service-api
 test
 
+
+org.glassfish
+javax.json
+1.0.4
+test
+

Review Comment:
   We more commonly use Jackson for Json processing in the NiFi code base. 
Would it be possible to use this library here too?



-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [nifi] exceptionfactory closed pull request #6367: NIFI-10435: Masked sensitive properties while writing command arguments to the flow file …

[GitBox]

exceptionfactory closed pull request #6367: NIFI-10435: Masked sensitive 
properties while writing command arguments to the flow file …
URL: https://github.com/apache/nifi/pull/6367


-- 
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: issues-unsubscr...@nifi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (NIFI-10435) Mask sensitive argument in the attribute execution.command.args of ExecuteStreamCommand

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601590#comment-17601590
 ] 

ASF subversion and git services commented on NIFI-10435:


Commit 97b8f0e205d282516990a08f4574ebfa8bbe5f9a in nifi's branch 
refs/heads/main from ravinarayansingh
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=97b8f0e205 ]

NIFI-10435 Masked sensitive arguments in ExecuteStreamCommand

This closes #6367

Signed-off-by: David Handermann 


> Mask sensitive argument in the attribute execution.command.args  of 
> ExecuteStreamCommand  
> --
>
> Key: NIFI-10435
> URL: https://issues.apache.org/jira/browse/NIFI-10435
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.17.0
>Reporter: RAVINARAYAN SINGH
>Priority: Major
>  Labels: ExecuteStreamCommand
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> I this processor  when sensitive arguments added by dynamic property then 
> those sensitive attribute written back to the  "execution.command.args" 
> attribute as plane text.  
> It should be masked before writing to the attribute 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (NIFI-10435) Mask sensitive argument in the attribute execution.command.args of ExecuteStreamCommand

[David Handermann (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Handermann updated NIFI-10435:

Component/s: Extensions
 (was: Core Framework)

> Mask sensitive argument in the attribute execution.command.args  of 
> ExecuteStreamCommand  
> --
>
> Key: NIFI-10435
> URL: https://issues.apache.org/jira/browse/NIFI-10435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.17.0
>Reporter: RAVINARAYAN SINGH
>Priority: Major
>  Labels: ExecuteStreamCommand
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> I this processor  when sensitive arguments added by dynamic property then 
> those sensitive attribute written back to the  "execution.command.args" 
> attribute as plane text.  
> It should be masked before writing to the attribute 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (NIFI-10435) Mask sensitive argument in the attribute execution.command.args of ExecuteStreamCommand

[David Handermann (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Handermann updated NIFI-10435:

Issue Type: Bug  (was: Improvement)

> Mask sensitive argument in the attribute execution.command.args  of 
> ExecuteStreamCommand  
> --
>
> Key: NIFI-10435
> URL: https://issues.apache.org/jira/browse/NIFI-10435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.17.0
>Reporter: RAVINARAYAN SINGH
>Priority: Major
>  Labels: ExecuteStreamCommand
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> I this processor  when sensitive arguments added by dynamic property then 
> those sensitive attribute written back to the  "execution.command.args" 
> attribute as plane text.  
> It should be masked before writing to the attribute 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (NIFI-10435) Mask sensitive argument in the attribute execution.command.args of ExecuteStreamCommand

[David Handermann (Jira)]

 [ 
https://issues.apache.org/jira/browse/NIFI-10435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Handermann resolved NIFI-10435.
-
Fix Version/s: 1.18.0
 Assignee: RAVINARAYAN SINGH
   Resolution: Fixed

> Mask sensitive argument in the attribute execution.command.args  of 
> ExecuteStreamCommand  
> --
>
> Key: NIFI-10435
> URL: https://issues.apache.org/jira/browse/NIFI-10435
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.17.0
>Reporter: RAVINARAYAN SINGH
>Assignee: RAVINARAYAN SINGH
>Priority: Major
>  Labels: ExecuteStreamCommand
> Fix For: 1.18.0
>
>  Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> I this processor  when sensitive arguments added by dynamic property then 
> those sensitive attribute written back to the  "execution.command.args" 
> attribute as plane text.  
> It should be masked before writing to the attribute 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)