[jira] [Commented] (NIFI-3856) PutCloudWatchMetric support for StatisticSets and Dimensions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3856:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1775
  
@tequalsme thanks again for contributing this cool upgrade to 
PutCloudWatchMetric.  First, a couple of nickpicks:
* PropertyDescriptor `name` should be a data key, typically lowercase, like 
"minimum".  The `displayName` property should have a human-readable name 
"Minimum".  Although the names and displayNames might be very similar now, this 
helps provide flexibility for later changes.  I realize we didn't follow that 
convention creating PutCloudWatchMetric, and your changes are following the 
pattern established in the file.  In this case, we should be different.
* I found a Checkstyle warning for "Unused import - java.util.Comparator" 
(for TestPutCloudWatchMetric) running `mvn clean install -Pcontrib-check`.

The processor performed well under proper use.  So I moved on to improper 
use.  For the statistic set scenario, if I provided some but not all of 
Minimum, Maximum, Sum, and SampleCount, the processor did not raise a 
validation issue and later ran into a NullPointerException parsing a double 
from Minimum (in this case).  How about a validation clause to make sure you 
specified something for all four?

Other validations worked well.  Help/docs look good.  Code coverage from 
unit tests is great.  Code quality looks very high.


> PutCloudWatchMetric support for StatisticSets and Dimensions
> 
>
> Key: NIFI-3856
> URL: https://issues.apache.org/jira/browse/NIFI-3856
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> - Add support for StatisticSets as well as regular (double) values
> - Add support for Dimensions via dynamic properties



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1775: NIFI-3856 PutCloudWatchMetric support for StatisticSets an...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1775
  
@tequalsme thanks again for contributing this cool upgrade to 
PutCloudWatchMetric.  First, a couple of nickpicks:
* PropertyDescriptor `name` should be a data key, typically lowercase, like 
"minimum".  The `displayName` property should have a human-readable name 
"Minimum".  Although the names and displayNames might be very similar now, this 
helps provide flexibility for later changes.  I realize we didn't follow that 
convention creating PutCloudWatchMetric, and your changes are following the 
pattern established in the file.  In this case, we should be different.
* I found a Checkstyle warning for "Unused import - java.util.Comparator" 
(for TestPutCloudWatchMetric) running `mvn clean install -Pcontrib-check`.

The processor performed well under proper use.  So I moved on to improper 
use.  For the statistic set scenario, if I provided some but not all of 
Minimum, Maximum, Sum, and SampleCount, the processor did not raise a 
validation issue and later ran into a NullPointerException parsing a double 
from Minimum (in this case).  How about a validation clause to make sure you 
specified something for all four?

Other validations worked well.  Help/docs look good.  Code coverage from 
unit tests is great.  Code quality looks very high.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi pull request #84: MINIFI-255 Update to NiFi 1.2.0 | MINIFI-256 s...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi/pull/84


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

[Xsixteen]

Github user Xsixteen commented on the issue:

https://github.com/apache/nifi/pull/1747
  
Joe, I added functionality to list max/min/avg for .

Gray - I completely agree, I will add more testing if complexity increases.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3716) Utility to calculate MAX storage required for BackPressure on a Node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3716:
--

Github user Xsixteen commented on the issue:

https://github.com/apache/nifi/pull/1747
  
Joe, I added functionality to list max/min/avg for .

Gray - I completely agree, I will add more testing if complexity increases.


> Utility to calculate MAX storage required for BackPressure on a Node
> 
>
> Key: NIFI-3716
> URL: https://issues.apache.org/jira/browse/NIFI-3716
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Niemiec
>Assignee: Eric Ulicny
>Priority: Trivial
>
> Today there is no way to understand the max amount of data which can be 
> stored in backpressure for a given flow. Personally have had users configure 
> queues with impossible backpressure amounts that would definitely fill the 
> disk, having an operational tool to understand if anyone has done something 
> so dramatic would be helpful. 
> I see this produce a report by analyzing the FlowFile.xml.gz.
> * Total Storage for all queues Backpressure 
> * Average Storage of all queues  Backpressure
> * Min and Max of all queues  Backpressure over the entire flow. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-2752) Correct ReplaceText default pattern and unit tests

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2752:
--

Github user trkurc commented on the issue:

https://github.com/apache/nifi/pull/1732
  
Am I missing something, or did this pr get merged in, but is still open?


> Correct ReplaceText default pattern and unit tests
> --
>
> Key: NIFI-2752
> URL: https://issues.apache.org/jira/browse/NIFI-2752
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Joe Skora
>Assignee: Joe Skora
> Fix For: 1.1.0, 0.8.0
>
>
> [{{ReplaceText.DEFAULT_REGEX}}|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ReplaceText.java#L87]
>  is defined as "(?s:\^.\*$)", which is valid PCRE but must be expressed as 
> "(?s)(\^.\*$)" in Java.
> The Java [Pattern class|https://docs.oracle.com/javase/8/docs/api/index.html] 
> specifies that patterns like "(?idmsux-idmsux:X)" are _non-capturing_, so 
> anything but the default pattern and replacement value result in empty 
> output.  This isn't caught by unit tests because the code short circuits if 
> the default pattern and replacement are found in 
> [ReplaceText.onTrigger()|https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ReplaceText.java#L217].
>   This hides the capture group problem from the unit tests and the default 
> processor configuration, but causes the processor to produce empty output if 
> using non-trivial patterns and replacements.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1732: NIFI-2752 Correct ReplaceText default pattern and unit tes...

[trkurc]

Github user trkurc commented on the issue:

https://github.com/apache/nifi/pull/1732
  
Am I missing something, or did this pr get merged in, but is still open?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi pull request #84: MINIFI-255 Update to NiFi 1.2.0 | MINIFI-256 s...

[apiri]

GitHub user apiri opened a pull request:

https://github.com/apache/nifi-minifi/pull/84

MINIFI-255 Update to NiFi 1.2.0 | MINIFI-256 support site to site interface 
config 

MINIFI-255 Update codebase to incorporate NiFi 1.2.0 handling of NARs and 
required dependencies

MINIFI-256 Support Site to Site attaching to an interface in config


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apiri/nifi-minifi minifi-255-nifi1.2.0-deps

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-minifi/pull/84.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #84


commit 82a9a64acf1267b8a78e6e4f14845a2b9b45ab77
Author: Aldrin Piri 
Date:   2017-05-10T01:14:48Z

MINIFI-255 Update codebase to incorporate NiFi 1.2.0 handling of NARs and 
required dependencies
MINIFI-256 Support Site to Site attaching to an interface in config




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-1603) Remove deprecated content repo properties

[Olav Jordens (JIRA)]

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

Olav Jordens commented on NIFI-1603:


This is an important issue for flows that have large numbers of very small and 
large numbers of very large files. If the small files remain enqueued for a 
while, they may prevent large claims being garbage collected. This has caused 
storage disks to fill up to 100% with content that is no longer required. Back 
pressure is one way to handle it, but not always satisfactory for complex 
flows. If it is decided that these two nifi.content properties are to be 
removed, it would be useful to have a way to force one flowfile per claim.

> Remove deprecated content repo properties
> -
>
> Key: NIFI-1603
> URL: https://issues.apache.org/jira/browse/NIFI-1603
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Core Framework
>Affects Versions: 0.5.1
>Reporter: Aldrin Piri
>Priority: Trivial
>
> Both nifi.content.claim.max.appendable.size & 
> nifi.content.claim.max.flow.files no longer appear to be used with defaults 
> specified for the associated properties in FileSystemRepository's 
> maxAppendClaimLength and the configured writableClaimQueue length.
> These should either be removed from both the codebase and documentation or 
> configured to use the associated properties and have their documentation 
> updated to reflect current configuration defaults.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-391) Need ability to deprecate components

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-391:
-

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1718
  
@mcgilman - will adjust


> Need ability to deprecate components
> 
>
> Key: NIFI-391
> URL: https://issues.apache.org/jira/browse/NIFI-391
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework, Core UI, Extensions
>Reporter: Mark Payne
>Assignee: Andre F de Miranda
>
> The API should allow processors to be marked as deprecated such that the UI 
> then shows on the graph that the Processor is deprecated.
> Additionally, the UI should show in the Status Bar that there are deprecated 
> components (processors, reporting tasks, controller services) in the flow.
> This valuable because of improvements such as NIFI-377. In this case, we have 
> a community member making the Base64EncodeContent processor more generic so 
> that it can encode/decode base 16,32, and 64. At this point, 
> Base64EncodeContent doesn't make sense as a name, so there is a more generic 
> EncodeContent processor. We don't need both, so we want to deprecated the 
> Base64EncodeContent processor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1718: NIFI-391 - Introduce the ability to deprecate a component

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1718
  
@mcgilman - will adjust


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3856) PutCloudWatchMetric support for StatisticSets and Dimensions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3856:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1775
  
Reviewing...


> PutCloudWatchMetric support for StatisticSets and Dimensions
> 
>
> Key: NIFI-3856
> URL: https://issues.apache.org/jira/browse/NIFI-3856
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> - Add support for StatisticSets as well as regular (double) values
> - Add support for Dimensions via dynamic properties



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1775: NIFI-3856 PutCloudWatchMetric support for StatisticSets an...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1775
  
Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3851) Add expression language support to AWS Endpoint Override URL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3851:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1769
  
@tequalsme Thanks for putting this together.  The commit passes the full 
build, and manually running it with an S3 processor worked great.

But I would prefer not to add `runner.setValidateExpressionUsage(false)` to 
the unit tests for DyanmoDB, Kinesis, etc.  They might use EL validation in the 
future, and I don't think it should be necessary based on precedents like 
ACCESS_KEY or PROXY_HOST that also use EL.

The problem appears to be a mismatch between those processors not 
configured to use the ENDPOINT_OVERRIDE property descriptor, but are 
nonetheless evaluating it when they call 
`AbstractAWSProcessor::initializeRegionAndEndpoint`.  That situation predates 
your change, but adding EL causes the exception for those tests.

Instead, what would you think about the treatment given to REGION in that 
same method ([AbstractAWSProcessor.java, ~line 
210](https://github.com/tequalsme/nifi/blob/c56e026f0677a3894063d7d044cef38b63cc0066/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/AbstractAWSProcessor.java#L210))?

protected void initializeRegionAndEndpoint(ProcessContext context) {
// if the processor supports REGION, get the configured region.
if (getSupportedPropertyDescriptors().contains(REGION)) {
final String region = context.getProperty(REGION).getValue();
if (region != null) {
this.region = Region.getRegion(Regions.fromName(region));
client.setRegion(this.region);
} else {
this.region = null;
}
}

// if the endpoint override has been configured, set the endpoint.
// (per Amazon docs this should only be configured at client 
creation)
final String urlstr = 
StringUtils.trimToEmpty(context.getProperty(ENDPOINT_OVERRIDE).evaluateAttributeExpressions().getValue());
if (!urlstr.isEmpty()) {
this.client.setEndpoint(urlstr);
}

}

The client is only modified when REGION is explicitly included on the 
concrete processor class.  We could add a second `if 
(getSupportedPropertyDescriptors().contains(ENDPOINT_OVERRIDE)) {...` 
protecting the expression language from being evaluated for ENDPOINT_OVERRIDE.  
There is a similar, but different, approach used for PROXY_HOST on line 193 `if 
(context.getProperty(PROXY_HOST).isSet()) {...`.

Now that I've made it this far, I'm not sure why there isn't such an if 
statement even without the expression language, like REGION.  Maybe I'm missing 
something?  Is this already familiar to you?


> Add expression language support to AWS Endpoint Override URL
> 
>
> Key: NIFI-3851
> URL: https://issues.apache.org/jira/browse/NIFI-3851
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> Add expression language support to AWS Endpoint Override URL property



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1769: NIFI-3851 Add expression language support to AWS Endpoint ...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1769
  
@tequalsme Thanks for putting this together.  The commit passes the full 
build, and manually running it with an S3 processor worked great.

But I would prefer not to add `runner.setValidateExpressionUsage(false)` to 
the unit tests for DyanmoDB, Kinesis, etc.  They might use EL validation in the 
future, and I don't think it should be necessary based on precedents like 
ACCESS_KEY or PROXY_HOST that also use EL.

The problem appears to be a mismatch between those processors not 
configured to use the ENDPOINT_OVERRIDE property descriptor, but are 
nonetheless evaluating it when they call 
`AbstractAWSProcessor::initializeRegionAndEndpoint`.  That situation predates 
your change, but adding EL causes the exception for those tests.

Instead, what would you think about the treatment given to REGION in that 
same method ([AbstractAWSProcessor.java, ~line 
210](https://github.com/tequalsme/nifi/blob/c56e026f0677a3894063d7d044cef38b63cc0066/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/AbstractAWSProcessor.java#L210))?

protected void initializeRegionAndEndpoint(ProcessContext context) {
// if the processor supports REGION, get the configured region.
if (getSupportedPropertyDescriptors().contains(REGION)) {
final String region = context.getProperty(REGION).getValue();
if (region != null) {
this.region = Region.getRegion(Regions.fromName(region));
client.setRegion(this.region);
} else {
this.region = null;
}
}

// if the endpoint override has been configured, set the endpoint.
// (per Amazon docs this should only be configured at client 
creation)
final String urlstr = 
StringUtils.trimToEmpty(context.getProperty(ENDPOINT_OVERRIDE).evaluateAttributeExpressions().getValue());
if (!urlstr.isEmpty()) {
this.client.setEndpoint(urlstr);
}

}

The client is only modified when REGION is explicitly included on the 
concrete processor class.  We could add a second `if 
(getSupportedPropertyDescriptors().contains(ENDPOINT_OVERRIDE)) {...` 
protecting the expression language from being evaluated for ENDPOINT_OVERRIDE.  
There is a similar, but different, approach used for PROXY_HOST on line 193 `if 
(context.getProperty(PROXY_HOST).isSet()) {...`.

Now that I've made it this far, I'm not sure why there isn't such an if 
statement even without the expression language, like REGION.  Maybe I'm missing 
something?  Is this already familiar to you?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-391) Need ability to deprecate components

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-391:
-

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1718
  
Ok sounds good. Let's proceed with this PR and then we can file another 
JIRA for the UI work.

I just started reviewing and noticed that the `DocumentTypeDTO` is missing 
the deprecation flag. Once the field has been added it will need to be set in 
the `DtoFactory`. This will be needed for the new [Processor|Controller 
Service|Reporting Task] dialogs.

Thanks


> Need ability to deprecate components
> 
>
> Key: NIFI-391
> URL: https://issues.apache.org/jira/browse/NIFI-391
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework, Core UI, Extensions
>Reporter: Mark Payne
>Assignee: Andre F de Miranda
>
> The API should allow processors to be marked as deprecated such that the UI 
> then shows on the graph that the Processor is deprecated.
> Additionally, the UI should show in the Status Bar that there are deprecated 
> components (processors, reporting tasks, controller services) in the flow.
> This valuable because of improvements such as NIFI-377. In this case, we have 
> a community member making the Base64EncodeContent processor more generic so 
> that it can encode/decode base 16,32, and 64. At this point, 
> Base64EncodeContent doesn't make sense as a name, so there is a more generic 
> EncodeContent processor. We don't need both, so we want to deprecated the 
> Base64EncodeContent processor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1718: NIFI-391 - Introduce the ability to deprecate a component

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1718
  
Ok sounds good. Let's proceed with this PR and then we can file another 
JIRA for the UI work.

I just started reviewing and noticed that the `DocumentTypeDTO` is missing 
the deprecation flag. Once the field has been added it will need to be set in 
the `DtoFactory`. This will be needed for the new [Processor|Controller 
Service|Reporting Task] dialogs.

Thanks


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3851) Add expression language support to AWS Endpoint Override URL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3851:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1769
  
Reviewing...


> Add expression language support to AWS Endpoint Override URL
> 
>
> Key: NIFI-3851
> URL: https://issues.apache.org/jira/browse/NIFI-3851
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> Add expression language support to AWS Endpoint Override URL property



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1769: NIFI-3851 Add expression language support to AWS Endpoint ...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1769
  
Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3860) Consider relaxing the constraint that ProcessSession enforces we give it the most recent version of a FlowFile

[Mark Payne (JIRA)]

Mark Payne created NIFI-3860:


 Summary: Consider relaxing the constraint that ProcessSession 
enforces we give it the most recent version of a FlowFile
 Key: NIFI-3860
 URL: https://issues.apache.org/jira/browse/NIFI-3860
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core Framework
Reporter: Mark Payne


Currently, when we call methods on ProcessSession to access or modify a 
FlowFile, the ProcessSession will roll itself back and throw a 
FlowFileHandlingException with the message " is not the most recent 
version of this FlowFile within this session". This was done to ensure that 
Processor developers ensure that they know what they are doing and always have 
the most recent version of a FlowFile. However, this comes with a few 
downsides: 

* It can result in code being complex in error-handling cases when we need to 
ensure that no matter what we hold the most recent version of a FlowFile
* It's easy to call session.putAttribute and forget to store the most recent 
version of the FlowFile, which gets returned - this is most problematic when 
dealing with a Collection.
* We have a method for ProcessSession.read(FlowFile) that returns an 
InputStream. However, we don't have a corresponding write() method. This is due 
to the fact that once we finish writing to the FlowFile, we would have to 
return the most up-to-date version of the FlowFile and there's no way to do 
that if returning an OutputStream.

We should consider relaxing this constraint and instead just always make use of 
the most recent version of the FlowFile, even if an older version of the 
FlowFile is passed in.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3850:
--

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1771
  
Thanks @andrewmlim this has been merged to master.


> Error in Admin Guide web property nifi.web.jetty.working.directory
> --
>
> Key: NIFI-3850
> URL: https://issues.apache.org/jira/browse/NIFI-3850
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.2.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Documentation is missing "i".
> nif.web.jetty.working.directory
> should be
> nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[Scott Aslan (JIRA)]

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

Scott Aslan resolved NIFI-3850.
---
Resolution: Fixed

> Error in Admin Guide web property nifi.web.jetty.working.directory
> --
>
> Key: NIFI-3850
> URL: https://issues.apache.org/jira/browse/NIFI-3850
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.2.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Documentation is missing "i".
> nif.web.jetty.working.directory
> should be
> nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1771: NIFI-3850 Corrected errors in Admin Guide and made propert...

[scottyaslan]

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1771
  
Thanks @andrewmlim this has been merged to master.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-3850:
---

Commit b6bdc4a0a81b43eba11f99c864f613788e1cf15a in nifi's branch 
refs/heads/master from [~andrewmlim]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b6bdc4a ]

NIFI-3850 Corrected errors in Admin Guide and made property formatting 
consistent

Signed-off-by: Scott Aslan 

This closes #1771


> Error in Admin Guide web property nifi.web.jetty.working.directory
> --
>
> Key: NIFI-3850
> URL: https://issues.apache.org/jira/browse/NIFI-3850
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.2.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Documentation is missing "i".
> nif.web.jetty.working.directory
> should be
> nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1771: NIFI-3850 Corrected errors in Admin Guide and made ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1771


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3850:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1771


> Error in Admin Guide web property nifi.web.jetty.working.directory
> --
>
> Key: NIFI-3850
> URL: https://issues.apache.org/jira/browse/NIFI-3850
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.2.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Documentation is missing "i".
> nif.web.jetty.working.directory
> should be
> nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3859) Provide filtering options in S2SProvenanceReportingTask

[Pierre Villard (JIRA)]

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

Pierre Villard updated NIFI-3859:
-
Status: Patch Available  (was: Open)

> Provide filtering options in S2SProvenanceReportingTask
> ---
>
> Key: NIFI-3859
> URL: https://issues.apache.org/jira/browse/NIFI-3859
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Minor
>
> Based on what will be used the S2SProvenanceReportingTask for, it could be 
> nice to provide some filtering options to the user in order to generate flow 
> files only for a subset of the last provenance events.
> Filters could be:
> - Event type
> - Component type
> - Component ID



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3859) Provide filtering options in S2SProvenanceReportingTask

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3859:
--

GitHub user pvillard31 opened a pull request:

https://github.com/apache/nifi/pull/1777

NIFI-3859 - Provide filtering options in S2SProvenanceReportingTask

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [X] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [X] Is your initial contribution a single, squashed commit?

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [X] Have you written or updated unit tests to verify your changes?
- [X] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### 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.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pvillard31/nifi NIFI-3859

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1777.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1777


commit 37a0e407cd166c24cd1d143d406319cd00c9ceb2
Author: Pierre Villard 
Date:   2017-05-09T18:44:43Z

NIFI-3859 - Provide filtering options in S2SProvenanceReportingTask




> Provide filtering options in S2SProvenanceReportingTask
> ---
>
> Key: NIFI-3859
> URL: https://issues.apache.org/jira/browse/NIFI-3859
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Minor
>
> Based on what will be used the S2SProvenanceReportingTask for, it could be 
> nice to provide some filtering options to the user in order to generate flow 
> files only for a subset of the last provenance events.
> Filters could be:
> - Event type
> - Component type
> - Component ID



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1777: NIFI-3859 - Provide filtering options in S2SProvena...

[pvillard31]

GitHub user pvillard31 opened a pull request:

https://github.com/apache/nifi/pull/1777

NIFI-3859 - Provide filtering options in S2SProvenanceReportingTask

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [X] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [X] Is your initial contribution a single, squashed commit?

### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [X] Have you written or updated unit tests to verify your changes?
- [X] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### 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.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pvillard31/nifi NIFI-3859

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1777.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1777


commit 37a0e407cd166c24cd1d143d406319cd00c9ceb2
Author: Pierre Villard 
Date:   2017-05-09T18:44:43Z

NIFI-3859 - Provide filtering options in S2SProvenanceReportingTask




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3859) Provide filtering options in S2SProvenanceReportingTask

[Pierre Villard (JIRA)]

Pierre Villard created NIFI-3859:


 Summary: Provide filtering options in S2SProvenanceReportingTask
 Key: NIFI-3859
 URL: https://issues.apache.org/jira/browse/NIFI-3859
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Reporter: Pierre Villard
Assignee: Pierre Villard
Priority: Minor


Based on what will be used the S2SProvenanceReportingTask for, it could be nice 
to provide some filtering options to the user in order to generate flow files 
only for a subset of the last provenance events.

Filters could be:
- Event type
- Component type
- Component ID



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3858) PostHTTP support for custom headers

[Tim Reardon (JIRA)]

Tim Reardon created NIFI-3858:
-

 Summary: PostHTTP support for custom headers
 Key: NIFI-3858
 URL: https://issues.apache.org/jira/browse/NIFI-3858
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Tim Reardon
Priority: Minor


Add support for custom headers to be sent with the request, specified through 
dynamic properties.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3857) Create PartitionRecord processor

[Mark Payne (JIRA)]

Mark Payne created NIFI-3857:


 Summary: Create PartitionRecord processor
 Key: NIFI-3857
 URL: https://issues.apache.org/jira/browse/NIFI-3857
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Extensions
Reporter: Mark Payne
Assignee: Mark Payne


With the record readers and writers, it will be useful to be able to bring in a 
stream of records as a FlowFile and output N different FlowFiles, where all 
records in the output are "alike." Users should be able to define what it means 
for two records to be "like records" by entering one or more RecordPaths.

Since we know that all records in an outgoing FlowFile will have the same value 
for a given field, we should also add an attribute to the FlowFile for each of 
these, so that routing can easily be done and we can also track that attribute 
via Provenance, etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3832) AvroRecordSetWriter initial validation fails with NullPointerException

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3832:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1768
  
@ijokarumawak thanks for the PR, and for catching the bug. Verified that 
NiFi was exhibiting the behavior that you described before and that after the 
PR the behavior was as-expected. +1 merged to master!


> AvroRecordSetWriter initial validation fails with NullPointerException
> --
>
> Key: NIFI-3832
> URL: https://issues.apache.org/jira/browse/NIFI-3832
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.2.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
>
> AvroRecordSetWriter overrides default value for SCHEMA_WRITE_STRATEGY to 
> AVRO_EMBEDDED. However getRequiredSchemaFields uses SCHEMA_WRITE_STRATEGY 
> constant defined in its super class to get value, which has 
> SCHAMA_NAME_ATTRIBUTE as its default value.
> So, at the initial validation (before user hit apply button), following code 
> go through the if statement and results in NPE:
> {code}
> @Override
> protected Set getRequiredSchemaFields(final 
> ValidationContext validationContext) {
> final String writeStrategyValue = 
> validationContext.getProperty(SCHEMA_WRITE_STRATEGY).getValue();
> if (writeStrategyValue.equalsIgnoreCase(AVRO_EMBEDDED.getValue())) {
> return requiredSchemaFields;
> }
> return super.getRequiredSchemaFields(validationContext);
> }
> {code}
> Here is the stacktrace:
> {code}
> 2017-05-08 19:19:22,749 ERROR [NiFi Web Server-158] 
> o.a.n.c.AbstractConfiguredComponent Failed to perform validation of 
> AvroRecordSetWriter[id=e78aac25-015b-1000-f931-33bf517d5e42]
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.getRequiredSchemaFields(SchemaRegistryRecordSetWriter.java:138)
> at 
> org.apache.nifi.avro.AvroRecordSetWriter.getRequiredSchemaFields(AvroRecordSetWriter.java:138)
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.customValidate(SchemaRegistryRecordSetWriter.java:147)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:460)
> at 
> org.apache.nifi.controller.service.StandardControllerServiceNode.getValidationErrors(StandardControllerServiceNode.java:506)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:448)
> at 
> org.apache.nifi.web.api.dto.DtoFactory.createControllerServiceDto(DtoFactory.java:1381)
> at 
> org.apache.nifi.web.StandardNiFiServiceFacade.createControllerServiceEntity(StandardNiFiServiceFacade.java:30
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3832) AvroRecordSetWriter initial validation fails with NullPointerException

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-3832:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> AvroRecordSetWriter initial validation fails with NullPointerException
> --
>
> Key: NIFI-3832
> URL: https://issues.apache.org/jira/browse/NIFI-3832
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.2.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
>
> AvroRecordSetWriter overrides default value for SCHEMA_WRITE_STRATEGY to 
> AVRO_EMBEDDED. However getRequiredSchemaFields uses SCHEMA_WRITE_STRATEGY 
> constant defined in its super class to get value, which has 
> SCHAMA_NAME_ATTRIBUTE as its default value.
> So, at the initial validation (before user hit apply button), following code 
> go through the if statement and results in NPE:
> {code}
> @Override
> protected Set getRequiredSchemaFields(final 
> ValidationContext validationContext) {
> final String writeStrategyValue = 
> validationContext.getProperty(SCHEMA_WRITE_STRATEGY).getValue();
> if (writeStrategyValue.equalsIgnoreCase(AVRO_EMBEDDED.getValue())) {
> return requiredSchemaFields;
> }
> return super.getRequiredSchemaFields(validationContext);
> }
> {code}
> Here is the stacktrace:
> {code}
> 2017-05-08 19:19:22,749 ERROR [NiFi Web Server-158] 
> o.a.n.c.AbstractConfiguredComponent Failed to perform validation of 
> AvroRecordSetWriter[id=e78aac25-015b-1000-f931-33bf517d5e42]
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.getRequiredSchemaFields(SchemaRegistryRecordSetWriter.java:138)
> at 
> org.apache.nifi.avro.AvroRecordSetWriter.getRequiredSchemaFields(AvroRecordSetWriter.java:138)
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.customValidate(SchemaRegistryRecordSetWriter.java:147)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:460)
> at 
> org.apache.nifi.controller.service.StandardControllerServiceNode.getValidationErrors(StandardControllerServiceNode.java:506)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:448)
> at 
> org.apache.nifi.web.api.dto.DtoFactory.createControllerServiceDto(DtoFactory.java:1381)
> at 
> org.apache.nifi.web.StandardNiFiServiceFacade.createControllerServiceEntity(StandardNiFiServiceFacade.java:30
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3832) AvroRecordSetWriter initial validation fails with NullPointerException

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-3832:
---

Commit 744ecc3d83a203db67cc8e99aa97bf1985e16470 in nifi's branch 
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=744ecc3 ]

NIFI-3832: Fixed AvroRecordSetWriter validation NPE.

This closes #1768.


> AvroRecordSetWriter initial validation fails with NullPointerException
> --
>
> Key: NIFI-3832
> URL: https://issues.apache.org/jira/browse/NIFI-3832
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.2.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
>
> AvroRecordSetWriter overrides default value for SCHEMA_WRITE_STRATEGY to 
> AVRO_EMBEDDED. However getRequiredSchemaFields uses SCHEMA_WRITE_STRATEGY 
> constant defined in its super class to get value, which has 
> SCHAMA_NAME_ATTRIBUTE as its default value.
> So, at the initial validation (before user hit apply button), following code 
> go through the if statement and results in NPE:
> {code}
> @Override
> protected Set getRequiredSchemaFields(final 
> ValidationContext validationContext) {
> final String writeStrategyValue = 
> validationContext.getProperty(SCHEMA_WRITE_STRATEGY).getValue();
> if (writeStrategyValue.equalsIgnoreCase(AVRO_EMBEDDED.getValue())) {
> return requiredSchemaFields;
> }
> return super.getRequiredSchemaFields(validationContext);
> }
> {code}
> Here is the stacktrace:
> {code}
> 2017-05-08 19:19:22,749 ERROR [NiFi Web Server-158] 
> o.a.n.c.AbstractConfiguredComponent Failed to perform validation of 
> AvroRecordSetWriter[id=e78aac25-015b-1000-f931-33bf517d5e42]
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.getRequiredSchemaFields(SchemaRegistryRecordSetWriter.java:138)
> at 
> org.apache.nifi.avro.AvroRecordSetWriter.getRequiredSchemaFields(AvroRecordSetWriter.java:138)
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.customValidate(SchemaRegistryRecordSetWriter.java:147)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:460)
> at 
> org.apache.nifi.controller.service.StandardControllerServiceNode.getValidationErrors(StandardControllerServiceNode.java:506)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:448)
> at 
> org.apache.nifi.web.api.dto.DtoFactory.createControllerServiceDto(DtoFactory.java:1381)
> at 
> org.apache.nifi.web.StandardNiFiServiceFacade.createControllerServiceEntity(StandardNiFiServiceFacade.java:30
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3832) AvroRecordSetWriter initial validation fails with NullPointerException

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3832:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1768


> AvroRecordSetWriter initial validation fails with NullPointerException
> --
>
> Key: NIFI-3832
> URL: https://issues.apache.org/jira/browse/NIFI-3832
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.2.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
>
> AvroRecordSetWriter overrides default value for SCHEMA_WRITE_STRATEGY to 
> AVRO_EMBEDDED. However getRequiredSchemaFields uses SCHEMA_WRITE_STRATEGY 
> constant defined in its super class to get value, which has 
> SCHAMA_NAME_ATTRIBUTE as its default value.
> So, at the initial validation (before user hit apply button), following code 
> go through the if statement and results in NPE:
> {code}
> @Override
> protected Set getRequiredSchemaFields(final 
> ValidationContext validationContext) {
> final String writeStrategyValue = 
> validationContext.getProperty(SCHEMA_WRITE_STRATEGY).getValue();
> if (writeStrategyValue.equalsIgnoreCase(AVRO_EMBEDDED.getValue())) {
> return requiredSchemaFields;
> }
> return super.getRequiredSchemaFields(validationContext);
> }
> {code}
> Here is the stacktrace:
> {code}
> 2017-05-08 19:19:22,749 ERROR [NiFi Web Server-158] 
> o.a.n.c.AbstractConfiguredComponent Failed to perform validation of 
> AvroRecordSetWriter[id=e78aac25-015b-1000-f931-33bf517d5e42]
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.getRequiredSchemaFields(SchemaRegistryRecordSetWriter.java:138)
> at 
> org.apache.nifi.avro.AvroRecordSetWriter.getRequiredSchemaFields(AvroRecordSetWriter.java:138)
> at 
> org.apache.nifi.serialization.SchemaRegistryRecordSetWriter.customValidate(SchemaRegistryRecordSetWriter.java:147)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:460)
> at 
> org.apache.nifi.controller.service.StandardControllerServiceNode.getValidationErrors(StandardControllerServiceNode.java:506)
> at 
> org.apache.nifi.controller.AbstractConfiguredComponent.getValidationErrors(AbstractConfiguredComponent.java:448)
> at 
> org.apache.nifi.web.api.dto.DtoFactory.createControllerServiceDto(DtoFactory.java:1381)
> at 
> org.apache.nifi.web.StandardNiFiServiceFacade.createControllerServiceEntity(StandardNiFiServiceFacade.java:30
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1768: NIFI-3832: Fixed AvroRecordSetWriter validation NPE...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/1768


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3856) PutCloudWatchMetric support for StatisticSets and Dimensions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3856:
--

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1775

NIFI-3856 PutCloudWatchMetric support for StatisticSets and Dimensions

- Add support for StatisticSets as well as regular (double) values
- Add support for Dimensions via dynamic properties

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3856

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1775.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1775






> PutCloudWatchMetric support for StatisticSets and Dimensions
> 
>
> Key: NIFI-3856
> URL: https://issues.apache.org/jira/browse/NIFI-3856
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> - Add support for StatisticSets as well as regular (double) values
> - Add support for Dimensions via dynamic properties



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1775: NIFI-3856 PutCloudWatchMetric support for Statistic...

[tequalsme]

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1775

NIFI-3856 PutCloudWatchMetric support for StatisticSets and Dimensions

- Add support for StatisticSets as well as regular (double) values
- Add support for Dimensions via dynamic properties

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3856

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1775.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1775






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3856) PutCloudWatchMetric support for StatisticSets and Dimensions

[Tim Reardon (JIRA)]

Tim Reardon created NIFI-3856:
-

 Summary: PutCloudWatchMetric support for StatisticSets and 
Dimensions
 Key: NIFI-3856
 URL: https://issues.apache.org/jira/browse/NIFI-3856
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Tim Reardon
Priority: Minor


- Add support for StatisticSets as well as regular (double) values
- Add support for Dimensions via dynamic properties



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3838) Create UpdateRecord processor and provide a RecordPath DSL to specify fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3838:
--

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r11861
  
--- Diff: 
nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/ArrayIndexFieldValue.java
 ---
@@ -0,0 +1,57 @@
+/*
+ * 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.record.path;
+
+import java.util.Objects;
+
+import org.apache.nifi.serialization.record.RecordField;
+import org.apache.nifi.serialization.record.RecordFieldType;
+
+public class ArrayIndexFieldValue extends StandardFieldValue {
+private final int index;
+
+public ArrayIndexFieldValue(final Object value, final RecordField 
field, final FieldValue parent, final int index) {
+super(value, field, validateParent(parent));
+this.index = index;
+}
+
+private static FieldValue validateParent(final FieldValue parent) {
+Objects.requireNonNull(parent, "Cannot create an 
ArrayIndexFieldValue without a parent");
+if (RecordFieldType.ARRAY != 
parent.getField().getDataType().getFieldType()) {
+// TODO: Add Unit test that does something like 
//myArray[../name = 'myName'][0] and ensure that
--- End diff --

Check your TODOs please to see which should stay and which can go :)


> Create UpdateRecord processor and provide a RecordPath DSL to specify fields
> 
>
> Key: NIFI-3838
> URL: https://issues.apache.org/jira/browse/NIFI-3838
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> With the addition of the RecordReader and RecordWriter controller services, 
> it would be nice to have a Processor that is capable of updating specific 
> fields of a record, based on user-defined values or based on the value of 
> another field in the Record.
> To do so, we need some sort of DSL that would allow us to access a specific 
> field in a record - something akin to JsonPath but that will work on any 
> Record object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1772: NIFI-3838: Initial implementation of RecordPath and...

[mattyb149]

Github user mattyb149 commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r11861
  
--- Diff: 
nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/ArrayIndexFieldValue.java
 ---
@@ -0,0 +1,57 @@
+/*
+ * 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.record.path;
+
+import java.util.Objects;
+
+import org.apache.nifi.serialization.record.RecordField;
+import org.apache.nifi.serialization.record.RecordFieldType;
+
+public class ArrayIndexFieldValue extends StandardFieldValue {
+private final int index;
+
+public ArrayIndexFieldValue(final Object value, final RecordField 
field, final FieldValue parent, final int index) {
+super(value, field, validateParent(parent));
+this.index = index;
+}
+
+private static FieldValue validateParent(final FieldValue parent) {
+Objects.requireNonNull(parent, "Cannot create an 
ArrayIndexFieldValue without a parent");
+if (RecordFieldType.ARRAY != 
parent.getField().getDataType().getFieldType()) {
+// TODO: Add Unit test that does something like 
//myArray[../name = 'myName'][0] and ensure that
--- End diff --

Check your TODOs please to see which should stay and which can go :)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #1774: Nifi-3855 Add attachment support to PutSlack

[tequalsme]

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1774

Nifi-3855 Add attachment support to PutSlack

Support including attachments array in message payload, as outlined at 
https://api.slack.com/docs/message-attachments

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3855

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1774.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1774


commit a1b167d16a30b28252cde737d816570be5b853f1
Author: Tim Reardon 
Date:   2017-05-09T17:42:42Z

NIFI-3855 Support PutSlack attachments as dynamic properties

commit f2617ebc3a09f822e8373ce4e90d3f8dda1e8b85
Author: Tim Reardon 
Date:   2017-05-09T17:45:25Z

NIFI-3855 Refactor deprecated API




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3855) Add attachment support to PutSlack

[Tim Reardon (JIRA)]

Tim Reardon created NIFI-3855:
-

 Summary: Add attachment support to PutSlack
 Key: NIFI-3855
 URL: https://issues.apache.org/jira/browse/NIFI-3855
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Tim Reardon
Priority: Minor


Support including attachments array in message payload, as outlined at 
https://api.slack.com/docs/message-attachments



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3853) Escape configurations prior to writing flow.xml

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-3853:
--
Description: 
If invalid characters are entered through the UI, they can corrupt the 
flow.xml.gz making it unparsable on future restarts. Once in this state, the 
flow.xml.gz needs to be hand-edited to remove the invalid characters. 
Characters outside the following ranges may cause issues:

{code}
#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
{code}

  was:
If invalid characters are entered through the UI, they can corrupt the 
flow.xml.gz making it unparsable on future restarts. Once in this state, the 
flow.xml.gz needs to be hand-edited to remove the invalid characters. The 
following characters may cause issues:

{code}
#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
{code}


> Escape configurations prior to writing flow.xml
> ---
>
> Key: NIFI-3853
> URL: https://issues.apache.org/jira/browse/NIFI-3853
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Critical
>
> If invalid characters are entered through the UI, they can corrupt the 
> flow.xml.gz making it unparsable on future restarts. Once in this state, the 
> flow.xml.gz needs to be hand-edited to remove the invalid characters. 
> Characters outside the following ranges may cause issues:
> {code}
> #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3853) Escape configurations prior to writing flow.xml

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-3853:
--
Description: 
If invalid characters are entered through the UI, they can corrupt the 
flow.xml.gz making it unparsable on future restarts. Once in this state, the 
flow.xml.gz needs to be hand-edited to remove the invalid characters. The 
following characters may cause issues:

{code}
#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
{code}

  was:
If invalid characters are entered through the UI, they can corrupt the 
flow.xml.gz making it unparsable on future restarts. Once in this state, the 
flow.xml.gz needs to be hand-edited to remove the invalid characters. The 
following characters may cause issues:

{code}
#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
{code}
{code}
[#x7F-#x84] | [#x86-#x9F]
{code}


> Escape configurations prior to writing flow.xml
> ---
>
> Key: NIFI-3853
> URL: https://issues.apache.org/jira/browse/NIFI-3853
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Critical
>
> If invalid characters are entered through the UI, they can corrupt the 
> flow.xml.gz making it unparsable on future restarts. Once in this state, the 
> flow.xml.gz needs to be hand-edited to remove the invalid characters. The 
> following characters may cause issues:
> {code}
> #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3838) Create UpdateRecord processor and provide a RecordPath DSL to specify fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3838:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1772
  
@joewitt good catch. Addressed the versioning info.


> Create UpdateRecord processor and provide a RecordPath DSL to specify fields
> 
>
> Key: NIFI-3838
> URL: https://issues.apache.org/jira/browse/NIFI-3838
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> With the addition of the RecordReader and RecordWriter controller services, 
> it would be nice to have a Processor that is capable of updating specific 
> fields of a record, based on user-defined values or based on the value of 
> another field in the Record.
> To do so, we need some sort of DSL that would allow us to access a specific 
> field in a record - something akin to JsonPath but that will work on any 
> Record object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1772: NIFI-3838: Initial implementation of RecordPath and Update...

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1772
  
@joewitt good catch. Addressed the versioning info.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3838) Create UpdateRecord processor and provide a RecordPath DSL to specify fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3838:
--

Github user joewitt commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r115547647
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
@@ -233,6 +237,12 @@
 test
 
 
+org.apache.nifi
+nifi-record-serialization-services
+1.2.0-SNAPSHOT
--- End diff --

@markap14  this should be 1.3.0-SNAPSHOT


> Create UpdateRecord processor and provide a RecordPath DSL to specify fields
> 
>
> Key: NIFI-3838
> URL: https://issues.apache.org/jira/browse/NIFI-3838
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> With the addition of the RecordReader and RecordWriter controller services, 
> it would be nice to have a Processor that is capable of updating specific 
> fields of a record, based on user-defined values or based on the value of 
> another field in the Record.
> To do so, we need some sort of DSL that would allow us to access a specific 
> field in a record - something akin to JsonPath but that will work on any 
> Record object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-871) Site-to-Site does not report the actual hostname that it was trying to connect to when it fails to connect

[Mark Payne (JIRA)]

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

Mark Payne commented on NIFI-871:
-

[~trixpan] - no, this does not appear to be resolved. I just tested against 
master. To recreate, create a standalone NiFi instance and in 
conf/nifi.properties set the "nifi.remote.input.host" property to "otherhost" 
and set the "nifi.remote.input.port" property to whatever port you'd like. Then 
start NiFi and create a RemoteProcessGroup that points to 
http://localhost:8080/nifi (or whatever your URL is). It will establish the 
connection and discover input ports correctly. However, when you attempt to 
push the data, it will error with the following message:

{code}
2017-05-09 13:12:53,523 ERROR [Timer-Driven Process Thread-3] 
o.a.nifi.remote.StandardRemoteGroupPort 
RemoteGroupPort[name=in,targets=http://localhost:8080/nifi] failed to 
communicate with http://localhost:8080/nifi due to java.net.UnknownHostException
{code}

This is incorrect because it appears that localhost is the Unknown Host. In 
reality, it was attempting to communicate with 'otherhost' and that is the 
unknown host.

> Site-to-Site does not report the actual hostname that it was trying to 
> connect to when it fails to connect
> --
>
> Key: NIFI-871
> URL: https://issues.apache.org/jira/browse/NIFI-871
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Andre F de Miranda
>
> In testing the patch provided for NIFI-868, I set the nifi properties to 
> advertise the hostname as "otherhost". Site-to-Site, of course, failed to 
> connect, but rather indicating that it could not connect to otherhost, it 
> simply indicated that it was the RemoteProcessGroup connected to 
> http://localhost:8080/nifi. This is misleading because it leads the user to 
> believe that the Remote Process Group is having trouble connecting to 
> localhost, when in reality it is attempting to connect to "otherhost". We 
> should indicate which host we are connecting to when providing an error like 
> this.
> 2015-08-19 13:03:46,083 WARN [Timer-Driven Process Thread-10] 
> o.a.n.c.t.ContinuallyRunConnectableTask 
> RemoteGroupPort[name=in,target=http://localhost:8080/nifi] Administratively 
> Pausing for 10 seconds due to processing failure: java.lang.RuntimeException: 
> java.nio.channels.UnresolvedAddressException
> java.lang.RuntimeException: java.nio.channels.UnresolvedAddressException
>   at 
> org.apache.nifi.controller.AbstractPort.onTrigger(AbstractPort.java:234) 
> ~[nifi-framework-core-api-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:80)
>  [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:40)
>  [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:119)
>  [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_51]
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_51]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_51]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_51]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_51]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_51]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
> Caused by: java.nio.channels.UnresolvedAddressException: null
>   at sun.nio.ch.Net.checkAddress(Net.java:123) ~[na:1.8.0_51]
>   at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622) 
> ~[na:1.8.0_51]
>   at java.nio.channels.SocketChannel.open(SocketChannel.java:189) 
> ~[na:1.8.0_51]
>   at 
> org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:708)
>  ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:682)
>  ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT]
>   at 
> 

[jira] [Commented] (NIFI-3838) Create UpdateRecord processor and provide a RecordPath DSL to specify fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3838:
--

Github user joewitt commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r115547596
  
--- Diff: nifi-commons/nifi-record-path/pom.xml ---
@@ -0,0 +1,73 @@
+
+http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd; 
xmlns="http://maven.apache.org/POM/4.0.0;
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
+
+
+  4.0.0
+  
+org.apache.nifi
+nifi-commons
+1.2.0-SNAPSHOT
--- End diff --

@markap14  this should be 1.3.0-SNAPSHOT


> Create UpdateRecord processor and provide a RecordPath DSL to specify fields
> 
>
> Key: NIFI-3838
> URL: https://issues.apache.org/jira/browse/NIFI-3838
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> With the addition of the RecordReader and RecordWriter controller services, 
> it would be nice to have a Processor that is capable of updating specific 
> fields of a record, based on user-defined values or based on the value of 
> another field in the Record.
> To do so, we need some sort of DSL that would allow us to access a specific 
> field in a record - something akin to JsonPath but that will work on any 
> Record object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1772: NIFI-3838: Initial implementation of RecordPath and...

[joewitt]

Github user joewitt commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r115547647
  
--- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml ---
@@ -233,6 +237,12 @@
 test
 
 
+org.apache.nifi
+nifi-record-serialization-services
+1.2.0-SNAPSHOT
--- End diff --

@markap14  this should be 1.3.0-SNAPSHOT


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #1772: NIFI-3838: Initial implementation of RecordPath and...

[joewitt]

Github user joewitt commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r115547596
  
--- Diff: nifi-commons/nifi-record-path/pom.xml ---
@@ -0,0 +1,73 @@
+
+http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd; 
xmlns="http://maven.apache.org/POM/4.0.0;
+xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
+
+
+  4.0.0
+  
+org.apache.nifi
+nifi-commons
+1.2.0-SNAPSHOT
--- End diff --

@markap14  this should be 1.3.0-SNAPSHOT


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3838) Create UpdateRecord processor and provide a RecordPath DSL to specify fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3838:
--

Github user joewitt commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r115547517
  
--- Diff: pom.xml ---
@@ -1459,6 +1459,11 @@
 
 
 org.apache.nifi
+nifi-record-path
+1.2.0-SNAPSHOT
--- End diff --

@markap14  this should be 1.3.0-SNAPSHOT


> Create UpdateRecord processor and provide a RecordPath DSL to specify fields
> 
>
> Key: NIFI-3838
> URL: https://issues.apache.org/jira/browse/NIFI-3838
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> With the addition of the RecordReader and RecordWriter controller services, 
> it would be nice to have a Processor that is capable of updating specific 
> fields of a record, based on user-defined values or based on the value of 
> another field in the Record.
> To do so, we need some sort of DSL that would allow us to access a specific 
> field in a record - something akin to JsonPath but that will work on any 
> Record object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1772: NIFI-3838: Initial implementation of RecordPath and...

[joewitt]

Github user joewitt commented on a diff in the pull request:

https://github.com/apache/nifi/pull/1772#discussion_r115547517
  
--- Diff: pom.xml ---
@@ -1459,6 +1459,11 @@
 
 
 org.apache.nifi
+nifi-record-path
+1.2.0-SNAPSHOT
--- End diff --

@markap14  this should be 1.3.0-SNAPSHOT


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1771: NIFI-3850 Corrected errors in Admin Guide and made propert...

[scottyaslan]

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1771
  
Will review...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Comment Edited] (NIFI-3853) Escape configurations prior to writing flow.xml

[Matt Gilman (JIRA)]

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

Matt Gilman edited comment on NIFI-3853 at 5/9/17 5:07 PM:
---

Some characters actually need to be filtered out as even after escaping they 
cannot be represented in XML [1].

[1] 
https://commons.apache.org/proper/commons-lang/apidocs/org/apache/commons/lang3/StringEscapeUtils.html#escapeXml10-java.lang.String-


was (Author: mcgilman):
Some characters actually need to be filtered out as even after escaping they 
cannot be represented in XML.

> Escape configurations prior to writing flow.xml
> ---
>
> Key: NIFI-3853
> URL: https://issues.apache.org/jira/browse/NIFI-3853
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Critical
>
> If invalid characters are entered through the UI, they can corrupt the 
> flow.xml.gz making it unparsable on future restarts. Once in this state, the 
> flow.xml.gz needs to be hand-edited to remove the invalid characters. The 
> following characters may cause issues:
> {code}
> #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
> {code}
> {code}
> [#x7F-#x84] | [#x86-#x9F]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1773: NIFI-3854 Expand expression language support for Ka...

[tequalsme]

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1773

NIFI-3854 Expand expression language support for Kafka processors

Expand expression language support for Kafka processors:

- brokers / zookeepers
- topic



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3854

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1773.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1773






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3853) Escape configurations prior to writing flow.xml

[Matt Gilman (JIRA)]

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

Matt Gilman commented on NIFI-3853:
---

Some characters actually need to be filtered out as even after escaping they 
cannot be represented in XML.

> Escape configurations prior to writing flow.xml
> ---
>
> Key: NIFI-3853
> URL: https://issues.apache.org/jira/browse/NIFI-3853
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Critical
>
> If invalid characters are entered through the UI, they can corrupt the 
> flow.xml.gz making it unparsable on future restarts. Once in this state, the 
> flow.xml.gz needs to be hand-edited to remove the invalid characters. The 
> following characters may cause issues:
> {code}
> #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
> {code}
> {code}
> [#x7F-#x84] | [#x86-#x9F]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3854) Expand expression language support for Kafka processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3854:
--

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1773

NIFI-3854 Expand expression language support for Kafka processors

Expand expression language support for Kafka processors:

- brokers / zookeepers
- topic



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3854

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1773.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1773






> Expand expression language support for Kafka processors
> ---
>
> Key: NIFI-3854
> URL: https://issues.apache.org/jira/browse/NIFI-3854
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> Expand expression language support for Kafka processors:
> - brokers / zookeepers
> - topic



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3854) Expand expression language support for Kafka processors

[Tim Reardon (JIRA)]

Tim Reardon created NIFI-3854:
-

 Summary: Expand expression language support for Kafka processors
 Key: NIFI-3854
 URL: https://issues.apache.org/jira/browse/NIFI-3854
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Tim Reardon
Priority: Minor


Expand expression language support for Kafka processors:

- brokers / zookeepers
- topic




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3838) Create UpdateRecord processor and provide a RecordPath DSL to specify fields

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-3838:
-
Assignee: Mark Payne
  Status: Patch Available  (was: Open)

> Create UpdateRecord processor and provide a RecordPath DSL to specify fields
> 
>
> Key: NIFI-3838
> URL: https://issues.apache.org/jira/browse/NIFI-3838
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> With the addition of the RecordReader and RecordWriter controller services, 
> it would be nice to have a Processor that is capable of updating specific 
> fields of a record, based on user-defined values or based on the value of 
> another field in the Record.
> To do so, we need some sort of DSL that would allow us to access a specific 
> field in a record - something akin to JsonPath but that will work on any 
> Record object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3838) Create UpdateRecord processor and provide a RecordPath DSL to specify fields

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3838:
--

GitHub user markap14 opened a pull request:

https://github.com/apache/nifi/pull/1772

NIFI-3838: Initial implementation of RecordPath and UpdateRecord proc…

…essor

Thank you for submitting a contribution to Apache 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?

### 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?
- [ ] 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.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/markap14/nifi NIFI-3838

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1772.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1772






> Create UpdateRecord processor and provide a RecordPath DSL to specify fields
> 
>
> Key: NIFI-3838
> URL: https://issues.apache.org/jira/browse/NIFI-3838
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mark Payne
>
> With the addition of the RecordReader and RecordWriter controller services, 
> it would be nice to have a Processor that is capable of updating specific 
> fields of a record, based on user-defined values or based on the value of 
> another field in the Record.
> To do so, we need some sort of DSL that would allow us to access a specific 
> field in a record - something akin to JsonPath but that will work on any 
> Record object.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1772: NIFI-3838: Initial implementation of RecordPath and...

[markap14]

GitHub user markap14 opened a pull request:

https://github.com/apache/nifi/pull/1772

NIFI-3838: Initial implementation of RecordPath and UpdateRecord proc…

…essor

Thank you for submitting a contribution to Apache 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?

### 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?
- [ ] 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.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/markap14/nifi NIFI-3838

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1772.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1772






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3853) Escape configurations prior to writing flow.xml

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-3853:
-

 Summary: Escape configurations prior to writing flow.xml
 Key: NIFI-3853
 URL: https://issues.apache.org/jira/browse/NIFI-3853
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Matt Gilman
Assignee: Matt Gilman
Priority: Critical


If invalid characters are entered through the UI, they can corrupt the 
flow.xml.gz making it unparsable on future restarts. Once in this state, the 
flow.xml.gz needs to be hand-edited to remove the invalid characters. The 
following characters may cause issues:

{code}
#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x1-#x10]
{code}
{code}
[#x7F-#x84] | [#x86-#x9F]
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3850:
--

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi/pull/1771

NIFI-3850 Corrected errors in Admin Guide and made property formattin…

…g consistent

Main fixes:
- corrected nifi.web.jetty.working.directory typo
- corrected cut-off nifi.state.management.embedded.zookeeper.properties 
description
- made formatting in property tables consistent with use of `` for 
references to properties and default values for properties
-fixed typo

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrewmlim/nifi NIFI-3850

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1771.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1771


commit cf2aa43999da42ebfe059dfb7d0d9b9131e0e27c
Author: Andrew Lim 
Date:   2017-05-09T16:41:02Z

NIFI-3850 Corrected errors in Admin Guide and made property formatting 
consistent




> Error in Admin Guide web property nifi.web.jetty.working.directory
> --
>
> Key: NIFI-3850
> URL: https://issues.apache.org/jira/browse/NIFI-3850
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.2.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Documentation is missing "i".
> nif.web.jetty.working.directory
> should be
> nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1771: NIFI-3850 Corrected errors in Admin Guide and made ...

[andrewmlim]

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi/pull/1771

NIFI-3850 Corrected errors in Admin Guide and made property formattin…

…g consistent

Main fixes:
- corrected nifi.web.jetty.working.directory typo
- corrected cut-off nifi.state.management.embedded.zookeeper.properties 
description
- made formatting in property tables consistent with use of `` for 
references to properties and default values for properties
-fixed typo

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/andrewmlim/nifi NIFI-3850

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1771.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1771


commit cf2aa43999da42ebfe059dfb7d0d9b9131e0e27c
Author: Andrew Lim 
Date:   2017-05-09T16:41:02Z

NIFI-3850 Corrected errors in Admin Guide and made property formatting 
consistent




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3852) Add expression language support to Cassandra processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3852:
--

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1770

NIFI-3852 Add expression language support to Cassandra processors

NIFI-3852 Add expression language support to Cassandra contact points and 
keyspace properties

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3852

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1770.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1770


commit d128ad778061f76eb9b2dc62445b89c4baba2cc2
Author: Tim Reardon 
Date:   2017-05-09T16:39:18Z

NIFI-3852 Add expression language support to Cassandra processors




> Add expression language support to Cassandra processors
> ---
>
> Key: NIFI-3852
> URL: https://issues.apache.org/jira/browse/NIFI-3852
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> Add expression language support to Cassandra contact points and keyspace 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1770: NIFI-3852 Add expression language support to Cassan...

[tequalsme]

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1770

NIFI-3852 Add expression language support to Cassandra processors

NIFI-3852 Add expression language support to Cassandra contact points and 
keyspace properties

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3852

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1770.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1770


commit d128ad778061f76eb9b2dc62445b89c4baba2cc2
Author: Tim Reardon 
Date:   2017-05-09T16:39:18Z

NIFI-3852 Add expression language support to Cassandra processors




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3852) Add expression language support to Cassandra processors

[Tim Reardon (JIRA)]

Tim Reardon created NIFI-3852:
-

 Summary: Add expression language support to Cassandra processors
 Key: NIFI-3852
 URL: https://issues.apache.org/jira/browse/NIFI-3852
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Tim Reardon
Priority: Minor


Add expression language support to Cassandra contact points and keyspace 
properties



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3851) Add expression language support to AWS Endpoint Override URL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3851:
--

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1769

NIFI-3851 Add expression language support to AWS Endpoint Override UR…

NIFI-3851 Add expression language support to AWS Endpoint Override URL 
property




You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3851

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1769.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1769


commit c56e026f0677a3894063d7d044cef38b63cc0066
Author: Tim Reardon 
Date:   2017-05-09T16:05:46Z

NIFI-3851 Add expression language support to AWS Endpoint Override URL 
property




> Add expression language support to AWS Endpoint Override URL
> 
>
> Key: NIFI-3851
> URL: https://issues.apache.org/jira/browse/NIFI-3851
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Tim Reardon
>Priority: Minor
>
> Add expression language support to AWS Endpoint Override URL property



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1769: NIFI-3851 Add expression language support to AWS En...

[tequalsme]

GitHub user tequalsme opened a pull request:

https://github.com/apache/nifi/pull/1769

NIFI-3851 Add expression language support to AWS Endpoint Override UR…

NIFI-3851 Add expression language support to AWS Endpoint Override URL 
property




You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tequalsme/nifi nifi-3851

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/1769.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1769


commit c56e026f0677a3894063d7d044cef38b63cc0066
Author: Tim Reardon 
Date:   2017-05-09T16:05:46Z

NIFI-3851 Add expression language support to AWS Endpoint Override URL 
property




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3851) Add expression language support to AWS Endpoint Override URL

[Tim Reardon (JIRA)]

Tim Reardon created NIFI-3851:
-

 Summary: Add expression language support to AWS Endpoint Override 
URL
 Key: NIFI-3851
 URL: https://issues.apache.org/jira/browse/NIFI-3851
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Tim Reardon
Priority: Minor


Add expression language support to AWS Endpoint Override URL property



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi-minifi-cpp pull request #96: MINIFI-304: Update testing strategy

[phrocker]

GitHub user phrocker opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/96

MINIFI-304: Update testing strategy

MINIFI-306: Move Docs and Docker cmake code into a separate module.
this will clean-up the end of the file. We will continue to do cleanup
but this has a great impact to improve the readability of the root
cmake

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 MINIFI- 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.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/phrocker/nifi-minifi-cpp MINIFI-304

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-minifi-cpp/pull/96.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #96


commit d4947cda45ee5eeb204148759121a3919224e017
Author: Marc Parisi 
Date:   2017-05-08T23:13:00Z

MINIFI-304: Update testing strategy

MINIFI-306: Move Docs and Docker cmake code into a separate module.
this will clean-up the end of the file. We will continue to do cleanup
but this has a great impact to improve the readability of the root
cmake




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

[GrayGwizdz]

Github user GrayGwizdz commented on the issue:

https://github.com/apache/nifi/pull/1747
  
Reading through the code everything looks good, I always err on the side of 
the more test cases the better but I think you have your bases covered.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3688) Create extended groovy scripting processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3688:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1662
  
Appveyor always fails, no worries. I will take a look at your latest


> Create extended groovy scripting processor
> --
>
> Key: NIFI-3688
> URL: https://issues.apache.org/jira/browse/NIFI-3688
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Dmitry Lukyanov
>Priority: Minor
>
> The idea is to simplify groovy scripting.
> Main targets:
> - to be compatible with existing groovy scripting
> - simplify read/write attributes
> - simplify read/write content
> - avoid closure casting to nifi types like `StreamCallback`
> - simplify and provide visibility when accessing to controller services from 
> script



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1662: NIFI-3688 Extended Groovy Nifi Processor

[mattyb149]

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1662
  
Appveyor always fails, no worries. I will take a look at your latest


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3716) Utility to calculate MAX storage required for BackPressure on a Node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3716:
--

Github user GrayGwizdz commented on the issue:

https://github.com/apache/nifi/pull/1747
  
Reading through the code everything looks good, I always err on the side of 
the more test cases the better but I think you have your bases covered.


> Utility to calculate MAX storage required for BackPressure on a Node
> 
>
> Key: NIFI-3716
> URL: https://issues.apache.org/jira/browse/NIFI-3716
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Niemiec
>Assignee: Eric Ulicny
>Priority: Trivial
>
> Today there is no way to understand the max amount of data which can be 
> stored in backpressure for a given flow. Personally have had users configure 
> queues with impossible backpressure amounts that would definitely fill the 
> disk, having an operational tool to understand if anyone has done something 
> so dramatic would be helpful. 
> I see this produce a report by analyzing the FlowFile.xml.gz.
> * Total Storage for all queues Backpressure 
> * Average Storage of all queues  Backpressure
> * Min and Max of all queues  Backpressure over the entire flow. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-3850:
--

Also noticed an error with nifi.state.management.embedded.zookeeper.properties. 
 Description is cut-off:

Specifies a properties file that contains the configuration for the embedded 
ZooKeeper Server that is started (if the `

Should be:

Specifies a properties file that contains the configuration for the embedded 
ZooKeeper Server that is started (if the 
`nifi.state.management.embedded.zookeeper.start` property is set to true).

> Error in Admin Guide web property nifi.web.jetty.working.directory
> --
>
> Key: NIFI-3850
> URL: https://issues.apache.org/jira/browse/NIFI-3850
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.2.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Documentation is missing "i".
> nif.web.jetty.working.directory
> should be
> nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3716) Utility to calculate MAX storage required for BackPressure on a Node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3716:
--

Github user josephxsxn commented on the issue:

https://github.com/apache/nifi/pull/1747
  
You need to update the root nifi project pom file, and the toolkit-assembly 
pom to include this  otherwise it does not get packed into the toolkit 
assembly. When this happens your script exists but it cant find the libs 
because they didnt get properly packed into the assembly. 

when running the below we can probably change the message -
```
>sh flow-analyzer.sh
Usage: java -cp  
org.apache.nifi.toolkit.flowanalyzer.FlowAnalyzerDriver 
``


> Utility to calculate MAX storage required for BackPressure on a Node
> 
>
> Key: NIFI-3716
> URL: https://issues.apache.org/jira/browse/NIFI-3716
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Niemiec
>Assignee: Eric Ulicny
>Priority: Trivial
>
> Today there is no way to understand the max amount of data which can be 
> stored in backpressure for a given flow. Personally have had users configure 
> queues with impossible backpressure amounts that would definitely fill the 
> disk, having an operational tool to understand if anyone has done something 
> so dramatic would be helpful. 
> I see this produce a report by analyzing the FlowFile.xml.gz.
> * Total Storage for all queues Backpressure 
> * Average Storage of all queues  Backpressure
> * Min and Max of all queues  Backpressure over the entire flow. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (NIFI-3829) Processor has visual defect and shows canvas

[Scott Aslan (JIRA)]

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

Scott Aslan resolved NIFI-3829.
---
Resolution: Invalid

> Processor has visual defect and shows canvas
> 
>
> Key: NIFI-3829
> URL: https://issues.apache.org/jira/browse/NIFI-3829
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.2.0
> Environment: Debian Stretch
> Firefox 45.1.1
>Reporter: Aldrin Piri
>Priority: Trivial
> Attachments: transparent processor info.png
>
>
> In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and 
> Windows), a processor after being placed on the canvas and then subsequently 
> moved, causes the background behind the processor name, version, NAR 
> disappears and allows the canvas to show through. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (NIFI-3770) Perform Release Manager duties for 1.2.0 Release

[Bryan Bende (JIRA)]

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

Bryan Bende resolved NIFI-3770.
---
Resolution: Fixed

> Perform Release Manager duties for 1.2.0 Release
> 
>
> Key: NIFI-3770
> URL: https://issues.apache.org/jira/browse/NIFI-3770
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[Andrew Lim (JIRA)]

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

Andrew Lim reassigned NIFI-3850:


Assignee: Andrew Lim

> Error in Admin Guide web property nifi.web.jetty.working.directory
> --
>
> Key: NIFI-3850
> URL: https://issues.apache.org/jira/browse/NIFI-3850
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.2.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> Documentation is missing "i".
> nif.web.jetty.working.directory
> should be
> nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3770) Perform Release Manager duties for 1.2.0 Release

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-3770:
---

Commit 3af53419afe415cb02743a60e4d3cc5fa8ca068d in nifi's branch 
refs/heads/master from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=3af5341 ]

NIFI-3770-RC2 prepare for next development iteration


> Perform Release Manager duties for 1.2.0 Release
> 
>
> Key: NIFI-3770
> URL: https://issues.apache.org/jira/browse/NIFI-3770
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3850) Error in Admin Guide web property nifi.web.jetty.working.directory

[Andrew Lim (JIRA)]

Andrew Lim created NIFI-3850:


 Summary: Error in Admin Guide web property 
nifi.web.jetty.working.directory
 Key: NIFI-3850
 URL: https://issues.apache.org/jira/browse/NIFI-3850
 Project: Apache NiFi
  Issue Type: Bug
  Components: Documentation & Website
Affects Versions: 1.2.0
Reporter: Andrew Lim
Priority: Minor


Documentation is missing "i".

nif.web.jetty.working.directory

should be

nifi.web.jetty.working.directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3716) Utility to calculate MAX storage required for BackPressure on a Node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3716:
--

Github user josephxsxn commented on the issue:

https://github.com/apache/nifi/pull/1747
  
works great now on multiple differing flow.xml.gz's... I am thinking that 
perhaps we should include the min/max/avg flow files per queue as well just in 
case some users decides to set it to 1billion for a 60 byte file... 


> Utility to calculate MAX storage required for BackPressure on a Node
> 
>
> Key: NIFI-3716
> URL: https://issues.apache.org/jira/browse/NIFI-3716
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Niemiec
>Assignee: Eric Ulicny
>Priority: Trivial
>
> Today there is no way to understand the max amount of data which can be 
> stored in backpressure for a given flow. Personally have had users configure 
> queues with impossible backpressure amounts that would definitely fill the 
> disk, having an operational tool to understand if anyone has done something 
> so dramatic would be helpful. 
> I see this produce a report by analyzing the FlowFile.xml.gz.
> * Total Storage for all queues Backpressure 
> * Average Storage of all queues  Backpressure
> * Min and Max of all queues  Backpressure over the entire flow. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

[josephxsxn]

Github user josephxsxn commented on the issue:

https://github.com/apache/nifi/pull/1747
  
works great now on multiple differing flow.xml.gz's... I am thinking that 
perhaps we should include the min/max/avg flow files per queue as well just in 
case some users decides to set it to 1billion for a 60 byte file... 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---