[jira] [Commented] (NIFI-7301) Open Web Browser After Successful Startup
[ https://issues.apache.org/jira/browse/NIFI-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072291#comment-17072291 ] Otto Fowler commented on NIFI-7301: --- I agree with andy, also the implementation would have to "loop" for some period of time, calling the api with curl or wget until the site is up and will actually open. > Open Web Browser After Successful Startup > - > > Key: NIFI-7301 > URL: https://issues.apache.org/jira/browse/NIFI-7301 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Troy Melhase >Priority: Trivial > > 1. Select or develop method of determining OS > 2. Select or develop method of determining NiFi URL > 3. When URL is localhost and OS supports GUI browsers, open browser with > NiFi URL after startup > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi-minifi-cpp] bakaid opened a new pull request #747: MINIFICPP-1036 - libarchive extension improvements
bakaid opened a new pull request #747: MINIFICPP-1036 - libarchive extension improvements URL: https://github.com/apache/nifi-minifi-cpp/pull/747 This commit - transfers the libarchive compilation to an ExternalProject - adds bundled liblzma and bzip2 - makes the libarchive extension compile on Windows - adds the "Encapsulate in TAR" Property to CompressContent - adds raw GZIP compression support to CompressContent Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (NIFI-7305) TLS Toolkit should generate client certificate keystore without escaped characters
Andy LoPresto created NIFI-7305:
---
Summary: TLS Toolkit should generate client certificate keystore
without escaped characters
Key: NIFI-7305
URL: https://issues.apache.org/jira/browse/NIFI-7305
Project: Apache NiFi
Issue Type: Bug
Components: Tools and Build
Affects Versions: 1.11.4
Reporter: Andy LoPresto
The TLS Toolkit generates keystores by default which map to the DN provided,
which contains characters which must be escaped when interacting with the files
on the command-line. The DN should be transformed with a deterministic
character mapping to avoid these characters.
{code}
Generated filename: CN=alopresto OU=NiFi.p12
To run a command: keytool -list -v -storetype PKCS12 -keystore CN\=alopresto\
OU\=NiFi.p12
Suggested filename: CN_alopresto_OU_NiFi.p12
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (NIFI-7304) Default value for content length filter blocks Site to Site communication
[
https://issues.apache.org/jira/browse/NIFI-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072188#comment-17072188
]
Andy LoPresto commented on NIFI-7304:
-
Agreed and priority modified to *Blocker*.
> Default value for content length filter blocks Site to Site communication
> -
>
> Key: NIFI-7304
> URL: https://issues.apache.org/jira/browse/NIFI-7304
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.12.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Blocker
> Labels: cluster, filter, http, replication, security,
> site-to-site
>
> When the content-length filter was introduced in NIFI-7153, it did not
> separate Site to Site (S2S) or cluster request replication requests from
> user-generated requests. With the default value of 20 MB, it is very likely
> that legitimate requests of this nature will be unexpectedly blocked.
> The immediate fix is to change the default value in {{nifi.properties}} to
> empty and only enable this functionality when a value is provided.
> A subtask will be opened to investigate if these requests should be excluded
> from the length limiting filter (either by convention or via an
> admin-enumerated exclusion list/setting).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-7304) Default value for content length filter blocks Site to Site communication
[
https://issues.apache.org/jira/browse/NIFI-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto updated NIFI-7304:
Priority: Blocker (was: Major)
> Default value for content length filter blocks Site to Site communication
> -
>
> Key: NIFI-7304
> URL: https://issues.apache.org/jira/browse/NIFI-7304
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.12.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Blocker
> Labels: cluster, filter, http, replication, security,
> site-to-site
>
> When the content-length filter was introduced in NIFI-7153, it did not
> separate Site to Site (S2S) or cluster request replication requests from
> user-generated requests. With the default value of 20 MB, it is very likely
> that legitimate requests of this nature will be unexpectedly blocked.
> The immediate fix is to change the default value in {{nifi.properties}} to
> empty and only enable this functionality when a value is provided.
> A subtask will be opened to investigate if these requests should be excluded
> from the length limiting filter (either by convention or via an
> admin-enumerated exclusion list/setting).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (NIFI-7304) Default value for content length filter blocks Site to Site communication
[
https://issues.apache.org/jira/browse/NIFI-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072187#comment-17072187
]
Joe Witt commented on NIFI-7304:
I think maybe we should consider this a blocker since the new default entered
would change behavior. Folks should opt-in to a limit
> Default value for content length filter blocks Site to Site communication
> -
>
> Key: NIFI-7304
> URL: https://issues.apache.org/jira/browse/NIFI-7304
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.12.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Major
> Labels: cluster, filter, http, replication, security,
> site-to-site
>
> When the content-length filter was introduced in NIFI-7153, it did not
> separate Site to Site (S2S) or cluster request replication requests from
> user-generated requests. With the default value of 20 MB, it is very likely
> that legitimate requests of this nature will be unexpectedly blocked.
> The immediate fix is to change the default value in {{nifi.properties}} to
> empty and only enable this functionality when a value is provided.
> A subtask will be opened to investigate if these requests should be excluded
> from the length limiting filter (either by convention or via an
> admin-enumerated exclusion list/setting).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (NIFI-7304) Default value for content length filter blocks Site to Site communication
Andy LoPresto created NIFI-7304:
---
Summary: Default value for content length filter blocks Site to
Site communication
Key: NIFI-7304
URL: https://issues.apache.org/jira/browse/NIFI-7304
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.12.0
Reporter: Andy LoPresto
Assignee: Andy LoPresto
When the content-length filter was introduced in NIFI-7153, it did not separate
Site to Site (S2S) or cluster request replication requests from user-generated
requests. With the default value of 20 MB, it is very likely that legitimate
requests of this nature will be unexpectedly blocked.
The immediate fix is to change the default value in {{nifi.properties}} to
empty and only enable this functionality when a value is provided.
A subtask will be opened to investigate if these requests should be excluded
from the length limiting filter (either by convention or via an
admin-enumerated exclusion list/setting).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [nifi] natural commented on a change in pull request #4077: NIFI-5346 Introduces new PGP controller service and PGP processors.
natural commented on a change in pull request #4077: NIFI-5346 Introduces new PGP controller service and PGP processors. URL: https://github.com/apache/nifi/pull/4077#discussion_r401179314 ## File path: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/pgp/PGPControllerService.java ## @@ -0,0 +1,893 @@ +/* + * 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.standard.pgp; + +import org.apache.nifi.annotation.documentation.CapabilityDescription; +import org.apache.nifi.annotation.documentation.Tags; +import org.apache.nifi.components.PropertyDescriptor; +import org.apache.nifi.components.ValidationContext; +import org.apache.nifi.components.ValidationResult; +import org.apache.nifi.context.PropertyContext; +import org.apache.nifi.controller.AbstractControllerService; +import org.apache.nifi.controller.ControllerServiceInitializationContext; +import org.apache.nifi.expression.ExpressionLanguageScope; +import org.apache.nifi.processor.util.StandardValidators; +import org.apache.nifi.processors.standard.util.PGPUtil; +import org.apache.nifi.reporting.InitializationException; +import org.bouncycastle.bcpg.ArmoredOutputStream; +import org.bouncycastle.jce.provider.BouncyCastleProvider; +import org.bouncycastle.openpgp.PGPCompressedData; +import org.bouncycastle.openpgp.PGPCompressedDataGenerator; +import org.bouncycastle.openpgp.PGPEncryptedData; +import org.bouncycastle.openpgp.PGPEncryptedDataGenerator; +import org.bouncycastle.openpgp.PGPEncryptedDataList; +import org.bouncycastle.openpgp.PGPException; +import org.bouncycastle.openpgp.PGPLiteralData; +import org.bouncycastle.openpgp.PGPLiteralDataGenerator; +import org.bouncycastle.openpgp.PGPObjectFactory; +import org.bouncycastle.openpgp.PGPPBEEncryptedData; +import org.bouncycastle.openpgp.PGPPrivateKey; +import org.bouncycastle.openpgp.PGPPublicKey; +import org.bouncycastle.openpgp.PGPPublicKeyEncryptedData; +import org.bouncycastle.openpgp.PGPPublicKeyRing; +import org.bouncycastle.openpgp.PGPSecretKey; +import org.bouncycastle.openpgp.PGPSecretKeyRing; +import org.bouncycastle.openpgp.PGPSecretKeyRingCollection; +import org.bouncycastle.openpgp.PGPSignature; +import org.bouncycastle.openpgp.PGPSignatureGenerator; +import org.bouncycastle.openpgp.PGPSignatureList; +import org.bouncycastle.openpgp.jcajce.JcaPGPObjectFactory; +import org.bouncycastle.openpgp.jcajce.JcaPGPPublicKeyRingCollection; +import org.bouncycastle.openpgp.operator.KeyFingerPrintCalculator; +import org.bouncycastle.openpgp.operator.PBEDataDecryptorFactory; +import org.bouncycastle.openpgp.operator.PBESecretKeyDecryptor; +import org.bouncycastle.openpgp.operator.PGPDigestCalculatorProvider; +import org.bouncycastle.openpgp.operator.PublicKeyDataDecryptorFactory; +import org.bouncycastle.openpgp.operator.bc.BcKeyFingerprintCalculator; +import org.bouncycastle.openpgp.operator.bc.BcPGPDigestCalculatorProvider; +import org.bouncycastle.openpgp.operator.jcajce.JcaPGPContentSignerBuilder; +import org.bouncycastle.openpgp.operator.jcajce.JcaPGPContentVerifierBuilderProvider; +import org.bouncycastle.openpgp.operator.jcajce.JcaPGPDigestCalculatorProviderBuilder; +import org.bouncycastle.openpgp.operator.jcajce.JcePBEDataDecryptorFactoryBuilder; +import org.bouncycastle.openpgp.operator.jcajce.JcePBEKeyEncryptionMethodGenerator; +import org.bouncycastle.openpgp.operator.jcajce.JcePBESecretKeyDecryptorBuilder; +import org.bouncycastle.openpgp.operator.jcajce.JcePGPDataEncryptorBuilder; +import org.bouncycastle.openpgp.operator.jcajce.JcePublicKeyDataDecryptorFactoryBuilder; +import org.bouncycastle.openpgp.operator.jcajce.JcePublicKeyKeyEncryptionMethodGenerator; +import org.bouncycastle.util.io.Streams; + +import java.io.ByteArrayInputStream; +import java.io.File; +import java.io.FileInputStream; +import java.io.FileNotFoundException; +import java.io.IOException; +import java.io.InputStream; +import java.io.OutputStream; +import java.nio.charset.StandardCharsets; +import java.security.Security; +import java.util.ArrayList; +import java.util.Collection; +import java.util.Collections; +import java.util.Date; +import
[jira] [Created] (NIFI-7303) Start/Stop operations should map to Enable/Disable transmission on RPG
Andy LoPresto created NIFI-7303: --- Summary: Start/Stop operations should map to Enable/Disable transmission on RPG Key: NIFI-7303 URL: https://issues.apache.org/jira/browse/NIFI-7303 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.11.4 Reporter: Andy LoPresto The _Start_ and _Stop_ operations are enabled (i.e. clickable in the _Operate_ palette) for remote process groups (RPG) but these actions have no impact. Rather, the valid operations for RPGs are _Enable transmission_ and _Disable transmission_, which must be selected from the context menu on the component. The _Start_/_Stop_ actions should invoke the respective operation on the RPG so that selecting a segment containing both processors and RPG and choosing _Start_/_Stop_ from the Operate palette has the intended outcome (i.e. starting or stopping all selected components, including enabling/disabling transmission for the RPG(s)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7302) Using ValidateRecord it invalidates a field if it is an decimal ( 5.5 ) but schema has it as a float
[ https://issues.apache.org/jira/browse/NIFI-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan C. Sequeiros updated NIFI-7302: Attachment: ValidateRecord_test.xml > Using ValidateRecord it invalidates a field if it is an decimal ( 5.5 ) but > schema has it as a float > > > Key: NIFI-7302 > URL: https://issues.apache.org/jira/browse/NIFI-7302 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Juan C. Sequeiros >Priority: Major > Attachments: ValidateRecord_test.xml > > > If we pass a float number for instance 5.5 to ValidateRecord and schema is > defined as a float type it fails but if we change schema to a double it > passes. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7302) Using ValidateRecord it invalidates a field if it is an decimal ( 5.5 ) but schema has it as a float
Juan C. Sequeiros created NIFI-7302: --- Summary: Using ValidateRecord it invalidates a field if it is an decimal ( 5.5 ) but schema has it as a float Key: NIFI-7302 URL: https://issues.apache.org/jira/browse/NIFI-7302 Project: Apache NiFi Issue Type: Bug Components: Extensions Reporter: Juan C. Sequeiros If we pass a float number for instance 5.5 to ValidateRecord and schema is defined as a float type it fails but if we change schema to a double it passes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7301) Open Web Browser After Successful Startup
[
https://issues.apache.org/jira/browse/NIFI-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072087#comment-17072087
]
Andy LoPresto commented on NIFI-7301:
-
I think this is a useful feature in some environments but there should be a
manual flag on the startup script (e.g. {{nifi.sh start --browser}}) to
explicitly indicate the desire to open the web browser.
> Open Web Browser After Successful Startup
> -
>
> Key: NIFI-7301
> URL: https://issues.apache.org/jira/browse/NIFI-7301
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Troy Melhase
>Priority: Trivial
>
> 1. Select or develop method of determining OS
> 2. Select or develop method of determining NiFi URL
> 3. When URL is localhost and OS supports GUI browsers, open browser with
> NiFi URL after startup
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (NIFI-7301) Open Web Browser After Successful Startup
Troy Melhase created NIFI-7301: -- Summary: Open Web Browser After Successful Startup Key: NIFI-7301 URL: https://issues.apache.org/jira/browse/NIFI-7301 Project: Apache NiFi Issue Type: Improvement Reporter: Troy Melhase 1. Select or develop method of determining OS 2. Select or develop method of determining NiFi URL 3. When URL is localhost and OS supports GUI browsers, open browser with NiFi URL after startup -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (NIFI-7292) ListFile should apply filters before checking permissions.
[ https://issues.apache.org/jira/browse/NIFI-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072016#comment-17072016 ] Waleed Al Aibani edited comment on NIFI-7292 at 3/31/20, 5:48 PM: -- [~msclarke], I tried to simulate the case, but I could not get any error. The processor excludes the private directory successfully. Could you please provide the exact error message you got or a pic? Thank you was (Author: waibani): [~msclarke], I tried to simulate the case, but I could not get any error. The processor excludes the private directory successfully. Could you please provide the exact error message you got or the pic? Thank you > ListFile should apply filters before checking permissions. > -- > > Key: NIFI-7292 > URL: https://issues.apache.org/jira/browse/NIFI-7292 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.9.2 >Reporter: Matthew Clarke >Priority: Major > > I noticed that NiFi's ListFile processor (and probably other list based > processors) will check permissions on sub-directories before it evaluates the > path filter. > Let's assume we have a mounted directory (/NiFi/mount) that contains sub > directories (A, B, C, D, and private). The NiFi Service user has permissions > to access all directories A,B,C, and D, but not the "private" directory. > I then add a path filter in my ListFile to exclude the "private" directory > (for example: (?!(private)).* ) > When I start the ListFile it errors because the NiFi service user does not > have permissions to "private" directory even though I have no intention of > listing anything from that directory. Since it Errors it does not listed > files from any directory including those which have the needed permissions. > If I give the NiFi service user access to that "private" dir then the listing > works ignoring the "private" dir files. > I feel as though the processor should apply the path and/or file filters > before checking permissions? > Users may not have ability to edit permissions on some sub directories. And > with other sub-directories having being dynamically created or having a very > large number of sub-directories, creating a separate ListFile for each > sub-directory is not a desirable solution either. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7292) ListFile should apply filters before checking permissions.
[ https://issues.apache.org/jira/browse/NIFI-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072016#comment-17072016 ] Waleed Al Aibani commented on NIFI-7292: [~msclarke], I tried to simulate the case, but I could not get any error. The processor excludes the private directory successfully. Could you please provide the exact error message you got or the pic? Thank you > ListFile should apply filters before checking permissions. > -- > > Key: NIFI-7292 > URL: https://issues.apache.org/jira/browse/NIFI-7292 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.9.2 >Reporter: Matthew Clarke >Priority: Major > > I noticed that NiFi's ListFile processor (and probably other list based > processors) will check permissions on sub-directories before it evaluates the > path filter. > Let's assume we have a mounted directory (/NiFi/mount) that contains sub > directories (A, B, C, D, and private). The NiFi Service user has permissions > to access all directories A,B,C, and D, but not the "private" directory. > I then add a path filter in my ListFile to exclude the "private" directory > (for example: (?!(private)).* ) > When I start the ListFile it errors because the NiFi service user does not > have permissions to "private" directory even though I have no intention of > listing anything from that directory. Since it Errors it does not listed > files from any directory including those which have the needed permissions. > If I give the NiFi service user access to that "private" dir then the listing > works ignoring the "private" dir files. > I feel as though the processor should apply the path and/or file filters > before checking permissions? > Users may not have ability to edit permissions on some sub directories. And > with other sub-directories having being dynamically created or having a very > large number of sub-directories, creating a separate ListFile for each > sub-directory is not a desirable solution either. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-370) StandardRevisableEntityService returns wrong version on update
[ https://issues.apache.org/jira/browse/NIFIREG-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-370: --- Fix Version/s: (was: 1.0.0) > StandardRevisableEntityService returns wrong version on update > -- > > Key: NIFIREG-370 > URL: https://issues.apache.org/jira/browse/NIFIREG-370 > Project: NiFi Registry > Issue Type: Bug >Affects Versions: 0.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The StandardRevisableEntityService converges create and update into a shared > method that returns a revision where the version is the incremented version > from the request. In some cases this is fine, but in the case where the > update was allowed because the client id was the same, it won't return > correct version which could be different. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-369) Permissions in lib should be 0644
[ https://issues.apache.org/jira/browse/NIFIREG-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-369: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Permissions in lib should be 0644 > - > > Key: NIFIREG-369 > URL: https://issues.apache.org/jira/browse/NIFIREG-369 > Project: NiFi Registry > Issue Type: Bug >Affects Versions: 0.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The jars in lib and other sub-directories of lib are being set to 0660 by the > assembly plugin, which makes them unreadable outside the user/group that > created the assembly. They should be set to 0644. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-373) Make the timeout in ShellUserGroupProvider configurable
[ https://issues.apache.org/jira/browse/NIFIREG-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-373: --- Fix Version/s: (was: 1.0.0) > Make the timeout in ShellUserGroupProvider configurable > --- > > Key: NIFIREG-373 > URL: https://issues.apache.org/jira/browse/NIFIREG-373 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 0.6.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Currently there is a hard-coded timeout of 60 seconds in the > ShellUserGroupProvider commands. We should make this configurable through > authorizers.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-366) update NiFi Registry's parent pom version
[
https://issues.apache.org/jira/browse/NIFIREG-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpad Boda updated NIFIREG-366:
---
Fix Version/s: (was: 1.0.0)
> update NiFi Registry's parent pom version
> -
>
> Key: NIFIREG-366
> URL: https://issues.apache.org/jira/browse/NIFIREG-366
> Project: NiFi Registry
> Issue Type: Task
>Reporter: Endre Kovacs
>Assignee: Endre Kovacs
>Priority: Minor
> Fix For: 0.6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> currently Apache NiFi uses version *23* of its parent pom.
> {code}
>
> org.apache
> apache
> 23
>
>
> {code}
> let's update it in NiFi Registry as well!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFIREG-372) Downgrade H2 version due to error on upgrade
[ https://issues.apache.org/jira/browse/NIFIREG-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-372: --- Fix Version/s: (was: 1.0.0) > Downgrade H2 version due to error on upgrade > > > Key: NIFIREG-372 > URL: https://issues.apache.org/jira/browse/NIFIREG-372 > Project: NiFi Registry > Issue Type: Bug >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > On master we bumped the H2 version from 1.4.197 to 1.4.200, but this issue > can occur when there is an existing database from before 1.4.200: > [https://github.com/h2database/h2database/issues/2078] > Downgrade to 1.4.199 for now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-355) Include profiles for hadoop libs in ranger plugin
[ https://issues.apache.org/jira/browse/NIFIREG-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-355: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Include profiles for hadoop libs in ranger plugin > - > > Key: NIFIREG-355 > URL: https://issues.apache.org/jira/browse/NIFIREG-355 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In NiFi we added profiles to a few places like ranger authorizer to control > inclusion of AWS, Azure, and cloud libs. We should have the same profiles for > the ranger plugin in registry. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-362) Upgrade out of date dependencies
[ https://issues.apache.org/jira/browse/NIFIREG-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-362: --- Fix Version/s: (was: 1.0.0) > Upgrade out of date dependencies > > > Key: NIFIREG-362 > URL: https://issues.apache.org/jira/browse/NIFIREG-362 > Project: NiFi Registry > Issue Type: Task >Reporter: Nathan Gough >Assignee: Andy LoPresto >Priority: Major > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Upgrade out of date dependencies: > * jackson-databind > * h2 database > * spring security > * spring boot > * jgit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-356) Classpath element of Authorizer is not used
[ https://issues.apache.org/jira/browse/NIFIREG-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-356: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Classpath element of Authorizer is not used > --- > > Key: NIFIREG-356 > URL: https://issues.apache.org/jira/browse/NIFIREG-356 > Project: NiFi Registry > Issue Type: Bug >Affects Versions: 0.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The authorizers.xml of nifi registry has the same schema as nifi and the > authorizer element has a classpath element where the value is a comma > separated list of resources to add to the authorizer's classpath. > In nifi registry this value is ignored and never used in the create method: > https://github.com/apache/nifi-registry/blob/master/nifi-registry-core/nifi-registry-framework/src/main/java/org/apache/nifi/registry/security/authorization/AuthorizerFactory.java#L340 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-361) Improve logout handling
[ https://issues.apache.org/jira/browse/NIFIREG-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-361: --- Fix Version/s: (was: 1.0.0) > Improve logout handling > --- > > Key: NIFIREG-361 > URL: https://issues.apache.org/jira/browse/NIFIREG-361 > Project: NiFi Registry > Issue Type: Task >Affects Versions: 0.5.0 >Reporter: Nathan Gough >Assignee: Nathan Gough >Priority: Major > Fix For: 0.6.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-358) Proxy authorization not working with groups
[ https://issues.apache.org/jira/browse/NIFIREG-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-358: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Proxy authorization not working with groups > --- > > Key: NIFIREG-358 > URL: https://issues.apache.org/jira/browse/NIFIREG-358 > Project: NiFi Registry > Issue Type: Bug >Affects Versions: 0.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 0.6.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In NIFIREG-206 we added support for public access to buckets. As part of > this, we moved the authorization of proxies from > X509IdentityAuthenticationProvider, into the new FrameworkAuthorizer. In the > new code, the NiFiUser object for the proxy user is not created the same way > and does not end up having it's potential groups, so any policies granting > /proxy to a group will not take effect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-348) Update NiFi logo and ico file
[ https://issues.apache.org/jira/browse/NIFIREG-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-348: --- Fix Version/s: (was: 1.0.0) > Update NiFi logo and ico file > - > > Key: NIFIREG-348 > URL: https://issues.apache.org/jira/browse/NIFIREG-348 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Trivial > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Similar issue was addressed in NiFi and NiFi website. > For Registry, the two files in question exist here: > [https://github.com/andrewmlim/nifi-registry/tree/master/nifi-registry-core/nifi-registry-web-api/src/main/resources/images] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-345) Bump ranger client version from 1.x to 2.x
[ https://issues.apache.org/jira/browse/NIFIREG-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-345: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Bump ranger client version from 1.x to 2.x > -- > > Key: NIFIREG-345 > URL: https://issues.apache.org/jira/browse/NIFIREG-345 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Bump ranger client version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-354) Update VersionedFlowSnapshot to work without VersionedFlowSnapshotMetadata
[ https://issues.apache.org/jira/browse/NIFIREG-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-354: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Update VersionedFlowSnapshot to work without VersionedFlowSnapshotMetadata > -- > > Key: NIFIREG-354 > URL: https://issues.apache.org/jira/browse/NIFIREG-354 > Project: NiFi Registry > Issue Type: Task >Reporter: Joe Ferner >Assignee: Joe Ferner >Priority: Major > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > VersionedFlowSnapshot currently expects to always have snapshot metadata, > which makes sense for use within the NiFi Registry context. But some upcoming > changes in NiFi allow a VersionedFlowSnapshot to be used in an unversioned > context where no snapshot metadata is present. Make updates to gracefully > handle this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFIREG-352) Update frontend dependencies
[ https://issues.apache.org/jira/browse/NIFIREG-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda resolved NIFIREG-352. Fix Version/s: 0.6.0 Resolution: Fixed > Update frontend dependencies > > > Key: NIFIREG-352 > URL: https://issues.apache.org/jira/browse/NIFIREG-352 > Project: NiFi Registry > Issue Type: Bug >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-353) Add ShellUserGroupProvider
[ https://issues.apache.org/jira/browse/NIFIREG-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-353: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Add ShellUserGroupProvider > -- > > Key: NIFIREG-353 > URL: https://issues.apache.org/jira/browse/NIFIREG-353 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add the same ShellUserGroupProvider that NiFi has: > https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-shell-authorizer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-336) Enable Integration Tests by Default
[ https://issues.apache.org/jira/browse/NIFIREG-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-336: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Enable Integration Tests by Default > --- > > Key: NIFIREG-336 > URL: https://issues.apache.org/jira/browse/NIFIREG-336 > Project: NiFi Registry > Issue Type: Test >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Trivial > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The NiFi Registry backend rest api component has a nice set of integration > tests that currently must be explicitly enabled via a mvn profile to run. > This ticket proposes switching the build to run the integration tests by > default unless explicitly disabled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-339) Remove errors in root pom
[
https://issues.apache.org/jira/browse/NIFIREG-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpad Boda updated NIFIREG-339:
---
Fix Version/s: (was: 1.0.0)
0.6.0
> Remove errors in root pom
> -
>
> Key: NIFIREG-339
> URL: https://issues.apache.org/jira/browse/NIFIREG-339
> Project: NiFi Registry
> Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 0.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Some IDEs like IntelliJ show a few errors in the root pom. They are not
> really errors that impact the build, but it makes it annoying in your IDE to
> think there is an issue in the project.
> * Checkstyles
> * doclint in javadoc plugin
> * Use of @\{project.artifactId}- in the tagFormatName
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFIREG-337) Support postgres 10
[ https://issues.apache.org/jira/browse/NIFIREG-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-337: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Support postgres 10 > --- > > Key: NIFIREG-337 > URL: https://issues.apache.org/jira/browse/NIFIREG-337 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We currently have automated testing for only Postgres 9.x. The application > should run fine against 10.x, but in order to say we fully support 10.x, we > should have automated testing in place. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-334) Support building and running on Java 11
[ https://issues.apache.org/jira/browse/NIFIREG-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-334: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Support building and running on Java 11 > --- > > Key: NIFIREG-334 > URL: https://issues.apache.org/jira/browse/NIFIREG-334 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 0.6.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-338) fixing nifi registrty version in dockerfile
[ https://issues.apache.org/jira/browse/NIFIREG-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-338: --- Fix Version/s: (was: 1.0.0) 0.6.0 > fixing nifi registrty version in dockerfile > --- > > Key: NIFIREG-338 > URL: https://issues.apache.org/jira/browse/NIFIREG-338 > Project: NiFi Registry > Issue Type: Bug >Reporter: Endre Kovacs >Assignee: Endre Kovacs >Priority: Trivial > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > after the 0.5.0 release, the community agreed on jumping to the next major > version: *1.0.0* > the dockerfile however was not updated to reflect this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-341) Update README to make use of ASF url for community slack channel
[ https://issues.apache.org/jira/browse/NIFIREG-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-341: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Update README to make use of ASF url for community slack channel > > > Key: NIFIREG-341 > URL: https://issues.apache.org/jira/browse/NIFIREG-341 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Trivial > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We can use the shortened URL https://s.apache.org/nifi-community-slack to > point to the community slack invite link should it need to be refreshed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-325) support specifying group for 'NiFi Identity' to grant permission to proxy user requests
[
https://issues.apache.org/jira/browse/NIFIREG-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpad Boda updated NIFIREG-325:
---
Fix Version/s: (was: 1.0.0)
0.6.0
> support specifying group for 'NiFi Identity' to grant permission to proxy
> user requests
> ---
>
> Key: NIFIREG-325
> URL: https://issues.apache.org/jira/browse/NIFIREG-325
> Project: NiFi Registry
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Endre Kovacs
>Assignee: Endre Kovacs
>Priority: Major
> Fix For: 0.6.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> As documented in
> [https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#fileaccesspolicyprovider]
> one can specify NiFi node identities to grant permission to proxy user
> requests and bucket read permission.
>
> What I'd like to propose is to be able to provider a group name there.:
> {code:xml}
>
> file-access-policy-provider
> org.a.n.r.s.authorization.file.FileAccessPolicyProvider
> ./conf/authorizations.xml
> ...
> ...
> my-group
>
> {code}
> which in turn would bless that group with the same permissions as described
> in the admin guide for {code}NiFi Identity{code} (proxying user request and
> bucket read).
> This feature would be very similar to what
> https://issues.apache.org/jira/browse/NIFI-5542 does.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFIREG-329) Add build profile to test with all supported DBs
[ https://issues.apache.org/jira/browse/NIFIREG-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-329: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Add build profile to test with all supported DBs > > > Key: NIFIREG-329 > URL: https://issues.apache.org/jira/browse/NIFIREG-329 > Project: NiFi Registry > Issue Type: Test >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Trivial > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The automated tests against different DBs enabled by TestContainers is really > helpful. Now the most tedious part of that process is running multiple mvn > builds while specifying each target profile (mariadb, mysql, postgres, etc). > This task is to add a build profile that performs mutltiple executions of > surefire for the integration tests, while cylcing through the profiles that > toggle different DB containers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-327) Add a section to docs covering recommended antivirus exclusions
[ https://issues.apache.org/jira/browse/NIFIREG-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-327: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Add a section to docs covering recommended antivirus exclusions > --- > > Key: NIFIREG-327 > URL: https://issues.apache.org/jira/browse/NIFIREG-327 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add similar section regarding antivirus exclusions to Registry Admin Guide > that was added to NiFi Admin Guide via NIFI-6553 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-318) Only allow bootstrap port to be set during initial startup
[ https://issues.apache.org/jira/browse/NIFIREG-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-318: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Only allow bootstrap port to be set during initial startup > -- > > Key: NIFIREG-318 > URL: https://issues.apache.org/jira/browse/NIFIREG-318 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-319) Remove code coverage instrumentation from nifi-fds js modules
[ https://issues.apache.org/jira/browse/NIFIREG-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-319: --- Fix Version/s: 0.6.0 > Remove code coverage instrumentation from nifi-fds js modules > - > > Key: NIFIREG-319 > URL: https://issues.apache.org/jira/browse/NIFIREG-319 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Labels: UI > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-323) CLONE - Updated bootstrap port handling causes restarts to fail
[
https://issues.apache.org/jira/browse/NIFIREG-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpad Boda updated NIFIREG-323:
---
Fix Version/s: (was: 1.0.0)
0.6.0
> CLONE - Updated bootstrap port handling causes restarts to fail
> ---
>
> Key: NIFIREG-323
> URL: https://issues.apache.org/jira/browse/NIFIREG-323
> Project: NiFi Registry
> Issue Type: Bug
>Reporter: Aldrin Piri
>Assignee: Bryan Bende
>Priority: Blocker
> Fix For: 0.6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> NIFI-6653 introduced a way to avoid the port being changed to prevent a
> possible hijacking of that port to provide other commands than those
> explicitly between bootstrap and the nifi process. This causes issues when
> the NiFi process dies and precludes restart (the default functionality
> enabled out of the box).
> To recreate, build/run NiFi off of current master and kill the NiFi process.
> This will result in the following (when an additional nifi.sh status is
> carried out).
> {quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
> Apache NiFi appears to have died. Restarting...
> 2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 2088
> 2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Successfully started Apache NiFi with PID 2088
> 2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
> org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command
> port and secret after they have already been initialized. requestedPort=37871
> 2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
> Successfully loaded the following 0 services: []
> 2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STARTED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STOPPED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_DIED
> 2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
> NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFIREG-320) Add standard HTTP security headers
[ https://issues.apache.org/jira/browse/NIFIREG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-320: --- Fix Version/s: (was: 1.0.0) > Add standard HTTP security headers > -- > > Key: NIFIREG-320 > URL: https://issues.apache.org/jira/browse/NIFIREG-320 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Nathan Gough >Assignee: Nathan Gough >Priority: Major > Fix For: 0.6.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Add HTTP security headers that are commonly used in most brower-based > applications. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-324) UI - include hammerJS with unit tests
[ https://issues.apache.org/jira/browse/NIFIREG-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-324: --- Fix Version/s: (was: 1.0.0) 0.6.0 > UI - include hammerJS with unit tests > - > > Key: NIFIREG-324 > URL: https://issues.apache.org/jira/browse/NIFIREG-324 > Project: NiFi Registry > Issue Type: Bug >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Labels: ui > Fix For: 0.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We see > WARN LOG: 'The "longpress" event cannot be bound because Hammer.JS is not > loaded and no custom loader has been specified.' > in the logs when running JS unit tests. Including hammerJS will clean up > these warnings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-297) Upgrade to latest LTS release of Node (and npm)
[ https://issues.apache.org/jira/browse/NIFIREG-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-297: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Upgrade to latest LTS release of Node (and npm) > --- > > Key: NIFIREG-297 > URL: https://issues.apache.org/jira/browse/NIFIREG-297 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Rob Fellows >Assignee: Scott Aslan >Priority: Major > Fix For: 0.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > nifi-registry currently requires node 8.10.0 and npm 5.6.0. The current LTS > for node is v10 and based on the scheduled release, v12 will be in October of > 2019. > One driving factor behind this is to get to a version of npm that includes > npm audit. npm v6+ includes it (which is packaged with Node v10). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-293) Highlight in Getting Started guide that only process groups can be versioned.
[ https://issues.apache.org/jira/browse/NIFIREG-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-293: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Highlight in Getting Started guide that only process groups can be versioned. > - > > Key: NIFIREG-293 > URL: https://issues.apache.org/jira/browse/NIFIREG-293 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Trivial > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Received some feedback from new users that it wasn't clear in NiFi docs that > only Process Groups can be versioned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-314) Remove references to HipChat from README
[ https://issues.apache.org/jira/browse/NIFIREG-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-314: --- Fix Version/s: (was: 1.0.0) 0.6.0 > Remove references to HipChat from README > > > Key: NIFIREG-314 > URL: https://issues.apache.org/jira/browse/NIFIREG-314 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Denes Arvay >Assignee: Andrew M. Lim >Priority: Trivial > Fix For: 0.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > and update it similarly as it was done in NiFi (NIFI-6460) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFIREG-317) Improve logging of exceptions when creating providers
[
https://issues.apache.org/jira/browse/NIFIREG-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpad Boda updated NIFIREG-317:
---
Fix Version/s: (was: 1.0.0)
0.6.0
> Improve logging of exceptions when creating providers
> -
>
> Key: NIFIREG-317
> URL: https://issues.apache.org/jira/browse/NIFIREG-317
> Project: NiFi Registry
> Issue Type: Improvement
>Affects Versions: 0.5.0
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 0.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If we fail to create a provider, we throw an exception with the parent cause,
> but Spring doesn't log the cause so we end up with something like:
> {code:java}
> Error creating FlowPersistenceProvider with class name:
> org.apache.nifi.registry.provider.flow.GitFlowPersistenceProvider {code}
> but we can't see the cause.
> We should improve this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (NIFIREG-252) Add docker-maven image and build profile
[ https://issues.apache.org/jira/browse/NIFIREG-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda resolved NIFIREG-252. Fix Version/s: 0.6.0 Resolution: Fixed > Add docker-maven image and build profile > > > Key: NIFIREG-252 > URL: https://issues.apache.org/jira/browse/NIFIREG-252 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Kevin Doran >Assignee: Endre Kovacs >Priority: Major > Fix For: 0.6.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > For NiFi Registry, it would be nice to have the option to build a docker > image as part of the maven source code build, similar to NiFi. The > docker-maven plugin supports this. The basic idea would be to copy the build > artifacts into the docker image when building the image, and tag it in a way > that distinguishes it from the apache/nifi-registry dockerhub image. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi] walmut commented on a change in pull request #4167: NIFI-7263 Add [No Tracking] Listing Strategy to ListFile/ListFTP proc…
walmut commented on a change in pull request #4167: NIFI-7263 Add [No Tracking]
Listing Strategy to ListFile/ListFTP proc…
URL: https://github.com/apache/nifi/pull/4167#discussion_r401076346
##
File path:
nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/list/AbstractListProcessor.java
##
@@ -192,12 +192,16 @@
" However additional DistributedMapCache controller
service is required and more JVM heap memory is used." +
" See the description of 'Entity Tracking Time Window'
property for further details on how it works.");
+public static final AllowableValue NO_TRACKING = new
AllowableValue("none", "No Tracking",
+"This strategy lists an entity without any tracking. Any property
that related to persist state" +
+" will be disregarded.");
Review comment:
@pvillard31 How about this: "This strategy lists an entity without any
tracking. The same entity will be listed each time on executing this processor.
It is recommended to change the default run schedule value. Any property that
related to the persisting state will be disregarded."
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [nifi-minifi-cpp] arpadboda closed pull request #746: MINIFICPP-1185 - Remove moodycamel::concurrentqueue from threadpool
arpadboda closed pull request #746: MINIFICPP-1185 - Remove moodycamel::concurrentqueue from threadpool URL: https://github.com/apache/nifi-minifi-cpp/pull/746 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (NIFI-7300) Using ValidateRecord it invalidates a field if it is an int but schema has it as a long
[ https://issues.apache.org/jira/browse/NIFI-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-7300: - Component/s: (was: Core Framework) Extensions > Using ValidateRecord it invalidates a field if it is an int but schema has it > as a long > --- > > Key: NIFI-7300 > URL: https://issues.apache.org/jira/browse/NIFI-7300 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Environment: Nifi 1.9 but probably other versions >Reporter: Juan C. Sequeiros >Priority: Major > Labels: Record > Attachments: ValidateRecord_Weirdness.xml > > > In ValidateRecord with Strict Type Checking = true it invalidates a record > if a field schema is defined as a long for instance and the field is an int > less than or equal to 2147483647. > If I define a long I would expect it to validate even if the number is less > than 2147483647 > > Attached is template to reproduce the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi-minifi-cpp] arpadboda closed pull request #731: MINIFICPP-1096 fix BackTrace, OOB indexing, tests, appveyor reporting
arpadboda closed pull request #731: MINIFICPP-1096 fix BackTrace, OOB indexing, tests, appveyor reporting URL: https://github.com/apache/nifi-minifi-cpp/pull/731 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] joewitt commented on issue #4174: Nifi-7176 update okHttpClient version and added support to change ConnectionTimeout every single request
joewitt commented on issue #4174: Nifi-7176 update okHttpClient version and added support to change ConnectionTimeout every single request URL: https://github.com/apache/nifi/pull/4174#issuecomment-606734615 Thank you for contributing. However, this PR appears to be not based off the latest master and does not appear to pass basic build functions. Please resubmit the PR once it is confirmed to be ready for a review or for additional engagement from a community member. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] joewitt closed pull request #4174: Nifi-7176 update okHttpClient version and added support to change ConnectionTimeout every single request
joewitt closed pull request #4174: Nifi-7176 update okHttpClient version and added support to change ConnectionTimeout every single request URL: https://github.com/apache/nifi/pull/4174 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (NIFI-7300) Using ValidateRecord it invalidates a field if it is an int but schema has it as a long
Juan C. Sequeiros created NIFI-7300: --- Summary: Using ValidateRecord it invalidates a field if it is an int but schema has it as a long Key: NIFI-7300 URL: https://issues.apache.org/jira/browse/NIFI-7300 Project: Apache NiFi Issue Type: Bug Components: Core Framework Environment: Nifi 1.9 but probably other versions Reporter: Juan C. Sequeiros Attachments: ValidateRecord_Weirdness.xml In ValidateRecord with Strict Type Checking = true it invalidates a record if a field schema is defined as a long for instance and the field is an int less than or equal to 2147483647. If I define a long I would expect it to validate even if the number is less than 2147483647 Attached is template to reproduce the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7300) Using ValidateRecord it invalidates a field if it is an int but schema has it as a long
[ https://issues.apache.org/jira/browse/NIFI-7300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan C. Sequeiros updated NIFI-7300: Attachment: ValidateRecord_Weirdness.xml > Using ValidateRecord it invalidates a field if it is an int but schema has it > as a long > --- > > Key: NIFI-7300 > URL: https://issues.apache.org/jira/browse/NIFI-7300 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Environment: Nifi 1.9 but probably other versions >Reporter: Juan C. Sequeiros >Priority: Major > Labels: Record > Attachments: ValidateRecord_Weirdness.xml > > > In ValidateRecord with Strict Type Checking = true it invalidates a record > if a field schema is defined as a long for instance and the field is an int > less than or equal to 2147483647. > If I define a long I would expect it to validate even if the number is less > than 2147483647 > > Attached is template to reproduce the issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi] guvencenanguvenal opened a new pull request #4174: Nifi-7176 update okHttpClient version and added support to change ConnectionTimeout every single request
guvencenanguvenal opened a new pull request #4174: Nifi-7176 update okHttpClient version and added support to change ConnectionTimeout every single request URL: https://github.com/apache/nifi/pull/4174 I update okHttpClient dependency versşon because to use interceptor. Connection timeout parameter support different timeout value every single request. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] MikeThomsen opened a new pull request #4173: NIFI-7299 Add basic OAuth2 token provider controller service
MikeThomsen opened a new pull request #4173: NIFI-7299 Add basic OAuth2 token
provider controller service
URL: https://github.com/apache/nifi/pull/4173
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
_Enables X functionality; fixes bug NIFI-._
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with **NIFI-** where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `master`)?
- [ ] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] Have you verified that the full build is successful on both JDK 8 and
JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Updated] (NIFIREG-320) Add standard HTTP security headers
[ https://issues.apache.org/jira/browse/NIFIREG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpad Boda updated NIFIREG-320: --- Fix Version/s: 0.6.0 > Add standard HTTP security headers > -- > > Key: NIFIREG-320 > URL: https://issues.apache.org/jira/browse/NIFIREG-320 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Nathan Gough >Assignee: Nathan Gough >Priority: Major > Fix For: 1.0.0, 0.6.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Add HTTP security headers that are commonly used in most brower-based > applications. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7299) Create OAuth2TokenProvider controller service
Mike Thomsen created NIFI-7299: -- Summary: Create OAuth2TokenProvider controller service Key: NIFI-7299 URL: https://issues.apache.org/jira/browse/NIFI-7299 Project: Apache NiFi Issue Type: Improvement Reporter: Mike Thomsen Assignee: Mike Thomsen This is a placeholder for some code written for my client that implements client_credentials and password grant flows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400965152 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. + +=== Filters + +Filters provided in order to decrease the number of findings in a search based on positional information, like currently active Process Group. All filters consists of a key and a value, separated by a colon, like "_key:value_". The filters must present at the beginning of the search string and are not part of the search term. Unknown filters or known filters with unknown value are ignored. If the same filter appears multiple time, the first will be used. The order of different filters has no effect on the result. + +*scope*: This filter narrows the scope of the search based on the user's currently active Process Group. The only valid value is "_here_". The usage of this filter looks like "_scope:here_". Any other value is considered as invalid, thus the filter will be ignored during search. Review comment: ```suggestion *scope*: This filter narrows the scope of the search based on the user's currently active Process Group. The only valid value is "here". The usage of this filter looks like "scope:here". Any other value is considered as invalid, thus the filter will be ignored during search. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400945077 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. + +=== Filters + +Filters provided in order to decrease the number of findings in a search based on positional information, like currently active Process Group. All filters consists of a key and a value, separated by a colon, like "_key:value_". The filters must present at the beginning of the search string and are not part of the search term. Unknown filters or known filters with unknown value are ignored. If the same filter appears multiple time, the first will be used. The order of different filters has no effect on the result. + +*scope*: This filter narrows the scope of the search based on the user's currently active Process Group. The only valid value is "_here_". The usage of this filter looks like "_scope:here_". Any other value is considered as invalid, thus the filter will be ignored during search. + +*group*: This filter narrows the scope of the search based on the provided Process Group name or id. If provided, the only groups will be searched are the ones containing the filter value in their name or id. This is transitive, so if any parent Process Group is fit, than the contained Process Groups are subject of the search. In case on non-existing group, the filter will be used but the result list will be empty. Review comment: ```suggestion *group*: This filter narrows the scope of the search based on the provided Process Group name or id. Search will be restricted to groups (and their components - including subgroups and their components) the names or ids of which match the filter value. If no group matches the filter the result list will be empty. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400930004 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. Review comment: ```suggestion *validating*: Adds Processors to the result list that are validating at the time. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400929270 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. Review comment: ```suggestion *transmitting*: Adds Remote Process Groups to the result list that are transmitting data at the time. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400947528 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. + +=== Filters + +Filters provided in order to decrease the number of findings in a search based on positional information, like currently active Process Group. All filters consists of a key and a value, separated by a colon, like "_key:value_". The filters must present at the beginning of the search string and are not part of the search term. Unknown filters or known filters with unknown value are ignored. If the same filter appears multiple time, the first will be used. The order of different filters has no effect on the result. + +*scope*: This filter narrows the scope of the search based on the user's currently active Process Group. The only valid value is "_here_". The usage of this filter looks like "_scope:here_". Any other value is considered as invalid, thus the filter will be ignored during search. + +*group*: This filter narrows the scope of the search based on the provided Process Group name or id. If provided, the only groups will be searched are the ones containing the filter value in their name or id. This is transitive, so if any parent Process Group is fit, than the contained Process Groups are subject of the search. In case on non-existing group, the filter will be used but the result list will be empty. + +*properties*: In case of valid value, this filter excludes the findings would be added based on property. The valid values are: "_no_", "_none_", "_false_", "_exclude_" and "_0_". Every other value is invalid, resulting that the search will ignore the filter. Review comment: ```suggestion *properties*: With this, users can prevent property matches to appear in the search result. Valid values are: "no", "none", "false", "exclude" and "0". ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400954001 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. + +=== Filters + +Filters provided in order to decrease the number of findings in a search based on positional information, like currently active Process Group. All filters consists of a key and a value, separated by a colon, like "_key:value_". The filters must present at the beginning of the search string and are not part of the search term. Unknown filters or known filters with unknown value are ignored. If the same filter appears multiple time, the first will be used. The order of different filters has no effect on the result. + +*scope*: This filter narrows the scope of the search based on the user's currently active Process Group. The only valid value is "_here_". The usage of this filter looks like "_scope:here_". Any other value is considered as invalid, thus the filter will be ignored during search. + +*group*: This filter narrows the scope of the search based on the provided Process Group name or id. If provided, the only groups will be searched are the ones containing the filter value in their name or id. This is transitive, so if any parent Process Group is fit, than the contained Process Groups are subject of the search. In case on non-existing group, the filter will be used but the result list will be empty. + +*properties*: In case of valid value, this filter excludes the findings would be added based on property. The valid values are: "_no_", "_none_", "_false_", "_exclude_" and "_0_". Every other value is invalid, resulting that the search will ignore the filter. + +=== Search examples + + Example 1 + +`group:myGroup processor1` + +The search query will result a list of components are containing `processor1` in their relevant attributes. The search will be executed under Process Groups (directly or via contained Process Groups) containing the string "myGroup" in their name or id. + + Example 2 + +`scope:here properties:exclude import` + +The example search query above returns with every component is contained (directly or via contained Process Groups) by the currently active Process Group, where the component's relevant attributes (name, comment, etc.) contain the word _import_ but excludes the findings based on property attributes. Review comment: ```suggestion Search will be restricted to the currently active process group (and process groups within that). The result will contain components that match for "import" but property matches will be excluded. ``` 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. For queries
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400928274 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) Review comment: ```suggestion *primary:* Adds Processors to the result list that are set to run on the primary node only (whether the Processor is currently running or not). ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400925645 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". Review comment: ```suggestion *event*: Adds Processors to the result list where the Scheduling Strategy is "Event Driven". ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400948943 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. + +=== Filters + +Filters provided in order to decrease the number of findings in a search based on positional information, like currently active Process Group. All filters consists of a key and a value, separated by a colon, like "_key:value_". The filters must present at the beginning of the search string and are not part of the search term. Unknown filters or known filters with unknown value are ignored. If the same filter appears multiple time, the first will be used. The order of different filters has no effect on the result. + +*scope*: This filter narrows the scope of the search based on the user's currently active Process Group. The only valid value is "_here_". The usage of this filter looks like "_scope:here_". Any other value is considered as invalid, thus the filter will be ignored during search. + +*group*: This filter narrows the scope of the search based on the provided Process Group name or id. If provided, the only groups will be searched are the ones containing the filter value in their name or id. This is transitive, so if any parent Process Group is fit, than the contained Process Groups are subject of the search. In case on non-existing group, the filter will be used but the result list will be empty. + +*properties*: In case of valid value, this filter excludes the findings would be added based on property. The valid values are: "_no_", "_none_", "_false_", "_exclude_" and "_0_". Every other value is invalid, resulting that the search will ignore the filter. + +=== Search examples + + Example 1 + +`group:myGroup processor1` + +The search query will result a list of components are containing `processor1` in their relevant attributes. The search will be executed under Process Groups (directly or via contained Process Groups) containing the string "myGroup" in their name or id. Review comment: ```suggestion The search will be executed under Process Groups (directly or via contained Process Groups) containing the string "myGroup" in their name or id. The result will contain components that match for "processor1". ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400923296 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. Review comment: ```suggestion *back pressure*: Adds Connections to the result list that are applying back pressure at the time. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400926142 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. Review comment: ```suggestion *not transmitting*: Adds Remote Process Groups to the result list that are not transmitting data at the time. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400928982 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". Review comment: ```suggestion *timer*: Adds Processors to the result list where the Scheduling Strategy is "Event Timer". ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400921543 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: Review comment: I think these document sections should be worded as simply as possible. `literal` for example in the sense it is used here is a computer science specific expression and meant to be used for fixed values in the _source code_. In general it should read naturally for basically any user, here's a suggestion: ``` Users can use pre-defined (case-insensitive) keywords in the search box that will check certain conditions (instead of trying to match labels and values etc.). Keywords can be used with filters (see below) but not with other search terms (otherwise they won't be treated as keywords) and only one keyword can be used at a time. Note however that keywords will also be treated as general search terms at the same time. The supported keywords are the following: ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400964323 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. + +=== Filters + +Filters provided in order to decrease the number of findings in a search based on positional information, like currently active Process Group. All filters consists of a key and a value, separated by a colon, like "_key:value_". The filters must present at the beginning of the search string and are not part of the search term. Unknown filters or known filters with unknown value are ignored. If the same filter appears multiple time, the first will be used. The order of different filters has no effect on the result. Review comment: ```suggestion Filters can be added to the seatch box as key-value pairs where the keys are predifined and check certain conditions based on the given value. The syntax is "key:value". Filters can be used together with other search terms and multiple filters can be used. The only constraint is that the search must start with the filters. Unknown filters or known filters with unknown values are ignored. If the same filter key appears multiple times, the first will be used. The order of different filters has no effect on the result. ``` 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400924050 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. Review comment: ```suggestion *expiration*: Adds Connections to the result list that contain expired Flow 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors
tpalfy commented on a change in pull request #4123: NIFI-7188: Adding filter capabilities into search & prerequisite refactors URL: https://github.com/apache/nifi/pull/4123#discussion_r400958822 ## File path: nifi-docs/src/main/asciidoc/user-guide.adoc ## @@ -167,6 +167,74 @@ contains options that allow you to manipulate existing components on the canvas: image::global-menu.png[NiFi Global Menu] +=== Keywords in searching + +NiFi UI's search functionality supports a number of "keywords". These are literals used to execute search based on non-textual information. A keyword is used only in case of the search term consists of a section of the keyword or matches with it. In case the keyword is only the subset of the search term, the keyword is not picked for usage. The keywords are case-insensitive. The supported keywords are the following: + +*back pressure*: Adds the Connections to the result list which are applying back pressure in the time of search. + +*disabled*: Adds disabled Ports and Processors to the result list. + +*expiration*: Adds the Connections to the result list in which there are expired Flow Files. + +*expires*: See "expiration". + +*event*: Adds every Processor to the result list where the Scheduling Strategy is "Event Driven". + +*invalid*: Adds Ports and Processors to the result list where the component is invalid. + +*not transmitting*: Adds Remote Process Groups to the result list which are not transmitting data at the time of searching. + +*pressure*: See "back pressure". + +*primary:* Adds Processors into the result list which are set to running on the primary node only. (Regardless if the Processor is currently running or not) + +*running*: Adds running Ports and Processors to the result list. + +*stopped*: Adds stopped Ports and Processors to the result list. + +*timer*: Adds every Processor to the result list where the Scheduling Strategy is "Event Timer". + +*transmitting*: Adds Remote Process Groups to the result list which are transmitting data at the time of searching. + +*transmission disabled*: See "not transmitting". + +*transmitting enabled*: See "transmitting". + +*validating*: Adds Processors to the result list which are validating at the time of executing the search. + +=== Filters + +Filters provided in order to decrease the number of findings in a search based on positional information, like currently active Process Group. All filters consists of a key and a value, separated by a colon, like "_key:value_". The filters must present at the beginning of the search string and are not part of the search term. Unknown filters or known filters with unknown value are ignored. If the same filter appears multiple time, the first will be used. The order of different filters has no effect on the result. + +*scope*: This filter narrows the scope of the search based on the user's currently active Process Group. The only valid value is "_here_". The usage of this filter looks like "_scope:here_". Any other value is considered as invalid, thus the filter will be ignored during search. + +*group*: This filter narrows the scope of the search based on the provided Process Group name or id. If provided, the only groups will be searched are the ones containing the filter value in their name or id. This is transitive, so if any parent Process Group is fit, than the contained Process Groups are subject of the search. In case on non-existing group, the filter will be used but the result list will be empty. + +*properties*: In case of valid value, this filter excludes the findings would be added based on property. The valid values are: "_no_", "_none_", "_false_", "_exclude_" and "_0_". Every other value is invalid, resulting that the search will ignore the filter. + +=== Search examples + + Example 1 + +`group:myGroup processor1` + +The search query will result a list of components are containing `processor1` in their relevant attributes. The search will be executed under Process Groups (directly or via contained Process Groups) containing the string "myGroup" in their name or id. + + Example 2 + +`scope:here properties:exclude import` + +The example search query above returns with every component is contained (directly or via contained Process Groups) by the currently active Process Group, where the component's relevant attributes (name, comment, etc.) contain the word _import_ but excludes the findings based on property attributes. + + Example 3 + +`scope:here invalid` + +Executing this search will result the list of invalid Processors and Ports contained by the current group. The search execution will also use "invalid" as search term with the same scope. Review comment: ```suggestion Search will be restricted to the currently selected process group (and its sub process groups). "invalid" here (as it is alone after the filter) will be treated both as a keyword and a regular search term. The
[GitHub] [nifi] davyam commented on issue #4065: NIFI-4239 - Adding CaptureChangePostgreSQL processor to capture data changes (INSERT/UPDATE/DELETE) in PostgreSQL tables via Logical Replication.
davyam commented on issue #4065: NIFI-4239 - Adding CaptureChangePostgreSQL processor to capture data changes (INSERT/UPDATE/DELETE) in PostgreSQL tables via Logical Replication. URL: https://github.com/apache/nifi/pull/4065#issuecomment-606605529 Hey guys, All requested changes have been made, but the reviews remain pending for some time. So, how can we help to ensure that this PR will be in the next NiFi version? Best regards 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (NIFI-7298) Add tests for PutAzureDataLakeStorage
[ https://issues.apache.org/jira/browse/NIFI-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated NIFI-7298: -- Labels: azure (was: ) > Add tests for PutAzureDataLakeStorage > - > > Key: NIFI-7298 > URL: https://issues.apache.org/jira/browse/NIFI-7298 > Project: Apache NiFi > Issue Type: Test > Components: Extensions >Reporter: Peter Turcsanyi >Priority: Major > Labels: azure > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7298) Add tests for PutAzureDataLakeStorage
Peter Turcsanyi created NIFI-7298: - Summary: Add tests for PutAzureDataLakeStorage Key: NIFI-7298 URL: https://issues.apache.org/jira/browse/NIFI-7298 Project: Apache NiFi Issue Type: Test Components: Extensions Reporter: Peter Turcsanyi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-7103) PutAzureDataLakeStorageGen2 processor to provide native support for Azure Data lake Storage Gen 2 Storage
[ https://issues.apache.org/jira/browse/NIFI-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard resolved NIFI-7103. -- Fix Version/s: 1.12.0 Resolution: Fixed > PutAzureDataLakeStorageGen2 processor to provide native support for Azure > Data lake Storage Gen 2 Storage > - > > Key: NIFI-7103 > URL: https://issues.apache.org/jira/browse/NIFI-7103 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.12.0 >Reporter: Muazma Zahid >Assignee: Muazma Zahid >Priority: Major > Labels: azure > Fix For: 1.12.0 > > Time Spent: 5.5h > Remaining Estimate: 0h > > [Azure Data Lake Storage > Gen2|[https://docs.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction]] > makes Azure Storage the foundation for building enterprise data lakes on > Azure. Nifi supports Azure Blob storage but has no native support for ADLS > Gen 2 > This processor will be followed by Get/List/Delete to provide native support > for ADLS Gen 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7103) PutAzureDataLakeStorageGen2 processor to provide native support for Azure Data lake Storage Gen 2 Storage
[ https://issues.apache.org/jira/browse/NIFI-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071720#comment-17071720 ] ASF subversion and git services commented on NIFI-7103: --- Commit daddf400a2628c8768c452d6f835613916ae8139 in nifi's branch refs/heads/master from muazmaz [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=daddf40 ] NIFI-7103 Adding PutDataLakeStorage Processor to provide native support for Azure Data Lake Storage Gen 2 Storage. added data-lake dependency NIFI-7103 fixed indentation Update to add IllegalArgumentException Fixed indentation and logging nifi-7103 review changes nifi-7103 root directory and exception change This closes #4126. Signed-off-by: Peter Turcsanyi > PutAzureDataLakeStorageGen2 processor to provide native support for Azure > Data lake Storage Gen 2 Storage > - > > Key: NIFI-7103 > URL: https://issues.apache.org/jira/browse/NIFI-7103 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.12.0 >Reporter: Muazma Zahid >Assignee: Muazma Zahid >Priority: Major > Labels: azure > Time Spent: 5h 20m > Remaining Estimate: 0h > > [Azure Data Lake Storage > Gen2|[https://docs.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction]] > makes Azure Storage the foundation for building enterprise data lakes on > Azure. Nifi supports Azure Blob storage but has no native support for ADLS > Gen 2 > This processor will be followed by Get/List/Delete to provide native support > for ADLS Gen 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7103) PutAzureDataLakeStorageGen2 processor to provide native support for Azure Data lake Storage Gen 2 Storage
[ https://issues.apache.org/jira/browse/NIFI-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071721#comment-17071721 ] ASF subversion and git services commented on NIFI-7103: --- Commit daddf400a2628c8768c452d6f835613916ae8139 in nifi's branch refs/heads/master from muazmaz [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=daddf40 ] NIFI-7103 Adding PutDataLakeStorage Processor to provide native support for Azure Data Lake Storage Gen 2 Storage. added data-lake dependency NIFI-7103 fixed indentation Update to add IllegalArgumentException Fixed indentation and logging nifi-7103 review changes nifi-7103 root directory and exception change This closes #4126. Signed-off-by: Peter Turcsanyi > PutAzureDataLakeStorageGen2 processor to provide native support for Azure > Data lake Storage Gen 2 Storage > - > > Key: NIFI-7103 > URL: https://issues.apache.org/jira/browse/NIFI-7103 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.12.0 >Reporter: Muazma Zahid >Assignee: Muazma Zahid >Priority: Major > Labels: azure > Time Spent: 5h 20m > Remaining Estimate: 0h > > [Azure Data Lake Storage > Gen2|[https://docs.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-introduction]] > makes Azure Storage the foundation for building enterprise data lakes on > Azure. Nifi supports Azure Blob storage but has no native support for ADLS > Gen 2 > This processor will be followed by Get/List/Delete to provide native support > for ADLS Gen 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi] asfgit closed pull request #4126: NIFI-7103 Adding PutAzureDataLakeStorage Processor to provide native support for Azure Data Lake Storage Gen 2
asfgit closed pull request #4126: NIFI-7103 Adding PutAzureDataLakeStorage Processor to provide native support for Azure Data Lake Storage Gen 2 URL: https://github.com/apache/nifi/pull/4126 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi-registry] arpadboda closed pull request #271: NIFIREG-376 - Upgrading jackson-databind to 2.9.10.3
arpadboda closed pull request #271: NIFIREG-376 - Upgrading jackson-databind to 2.9.10.3 URL: https://github.com/apache/nifi-registry/pull/271 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi-registry] arpadboda closed pull request #270: NIFIREG-364 - Upgrade maven checkstyle version
arpadboda closed pull request #270: NIFIREG-364 - Upgrade maven checkstyle version URL: https://github.com/apache/nifi-registry/pull/270 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] pvillard31 commented on a change in pull request #4167: NIFI-7263 Add [No Tracking] Listing Strategy to ListFile/ListFTP proc…
pvillard31 commented on a change in pull request #4167: NIFI-7263 Add [No
Tracking] Listing Strategy to ListFile/ListFTP proc…
URL: https://github.com/apache/nifi/pull/4167#discussion_r400713968
##
File path:
nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/list/AbstractListProcessor.java
##
@@ -192,12 +192,16 @@
" However additional DistributedMapCache controller
service is required and more JVM heap memory is used." +
" See the description of 'Entity Tracking Time Window'
property for further details on how it works.");
+public static final AllowableValue NO_TRACKING = new
AllowableValue("none", "No Tracking",
+"This strategy lists an entity without any tracking. Any property
that related to persist state" +
+" will be disregarded.");
Review comment:
I'd probably try to be even more descriptive here... I think it's worth
saying that the same files will be listed at each execution of this processor,
and that it's recommended to change the default run schedule value.
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Resolved] (NIFI-7297) Mock bundle: inputStream created py MockProcessSession doesn't count avalable() bytes
[
https://issues.apache.org/jira/browse/NIFI-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-7297.
--
Fix Version/s: 1.12.0
Resolution: Fixed
> Mock bundle: inputStream created py MockProcessSession doesn't count
> avalable() bytes
> -
>
> Key: NIFI-7297
> URL: https://issues.apache.org/jira/browse/NIFI-7297
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Ilya Kovalev
>Priority: Minor
> Fix For: 1.12.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> MockProcessSession.read(FlowFile file) return `InputStream` doesn't count
> available bytes.
> due testing custom processor that read flowfile by following example
> BufferedReader reader = new BufferedReader(new
> InputStreamReader(inputStream)) ;
> while (reader.ready()){
> tests will fail because available() return constantly 0 and reader's buffer
> is empty
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (NIFI-7297) Mock bundle: inputStream created py MockProcessSession doesn't count avalable() bytes
[
https://issues.apache.org/jira/browse/NIFI-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071553#comment-17071553
]
ASF subversion and git services commented on NIFI-7297:
---
Commit f4a7aafe4a243e6eea43781ce0a3bd3f42714617 in nifi's branch
refs/heads/master from KovalevIV
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f4a7aaf ]
NIFI-7297 add available()
Signed-off-by: Pierre Villard
This closes #4172.
> Mock bundle: inputStream created py MockProcessSession doesn't count
> avalable() bytes
> -
>
> Key: NIFI-7297
> URL: https://issues.apache.org/jira/browse/NIFI-7297
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Ilya Kovalev
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> MockProcessSession.read(FlowFile file) return `InputStream` doesn't count
> available bytes.
> due testing custom processor that read flowfile by following example
> BufferedReader reader = new BufferedReader(new
> InputStreamReader(inputStream)) ;
> while (reader.ready()){
> tests will fail because available() return constantly 0 and reader's buffer
> is empty
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [nifi] asfgit closed pull request #4172: NIFI-7297 add available()
asfgit closed pull request #4172: NIFI-7297 add available() URL: https://github.com/apache/nifi/pull/4172 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] pvillard31 commented on issue #4172: NIFI-7297 add available()
pvillard31 commented on issue #4172: NIFI-7297 add available() URL: https://github.com/apache/nifi/pull/4172#issuecomment-606459586 Merged to master, thanks @IlyaKovalev 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (NIFIREG-377) Sub buckets / Ability to move flow in another bucket
DEOM Damien created NIFIREG-377: --- Summary: Sub buckets / Ability to move flow in another bucket Key: NIFIREG-377 URL: https://issues.apache.org/jira/browse/NIFIREG-377 Project: NiFi Registry Issue Type: Improvement Reporter: DEOM Damien As the number of flows grows in the registry, it would be very convenient to add an option to move a dataflow in another bucket / sub bucket. Nice to have: add a parent attribute to buckets, and display all buckets in hierarchical form -- This message was sent by Atlassian Jira (v8.3.4#803005)
