markobean commented on pull request #5192: URL: https://github.com/apache/nifi/pull/5192#issuecomment-875631065
Clarifying the outcome of the latest push. I followed your steps to reproduce, and the new PG properties maintained their values, as expected. 1. Starting from a blank canvas/flow, create a new PG at the root level called 'test1' 2. Right-click on the PG and change the values for default backpressure to 20000 and 2 GB. Click Apply 3. Go into the PG and create a new PG called 'child1' 4. Right-click and configure the child1 PG, verify the values were inherited from the test1 PG. Click Cancel 5. Move the child PG on the canvas 6. Right-click and configure the child1 PG, verify the values **are still 20000 and 2GB** The above verified custom default FlowFile expiration setting as well. Also, I tried copy/paste; it maintained values as expected. The Java 8 contrib-check passed, but I'm getting the following error for Java 11 contrib-check. Maybe it is strictly an environmental thing with my VM. Have you seen this before? `[ERROR] Failed to execute goal on project minifi-c2-integration-tests: Could not resolve dependencies for project org.apache.nifi.minifi:minifi-c2-integration-tests:jar:1.14.0-SNAPSHOT: Failed to collect dependencies at com.palantir.docker.compose:docker-compose-rule-junit4:jar:0.33.0: Failed to read artifact descriptor for com.palantir.docker.compose:docker-compose-rule-junit4:jar:0.33.0: Could not transfer artifact com.palantir.docker.compose:docker-compose-rule-junit4:pom:0.33.0 from/to palantir.bintray (https://dl.bintray.com/palantir/releases): authorization failed for https://dl.bintray.com/palantir/releases/com/palantir/docker/compose/docker-compose-rule-junit4/0.33.0/docker-compose-rule-junit4-0.33.0.pom, status: 403 Forbidden -> [Help 1]` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
