[jira] [Commented] (NIFI-3971) UpdateAttribute metric for output 'size' is larger than it should be when cloning

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3971: This closes #1854. Fixed bug in calculating content size that was 
transferred when cloning a relationship

Signed-off-by: joewitt 


> UpdateAttribute metric for output 'size' is larger than it should be when 
> cloning
> -
>
> Key: NIFI-3971
> URL: https://issues.apache.org/jira/browse/NIFI-3971
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> When I configure UpdateAttribute so that the 'success' relationship goes to 
> multiple destinations, the output count is double what it should be. For 
> instance, if i send in 1 GB of data, the output size should be 2 GB (since 
> it's cloned to a second connection) but it shows 4 GB.



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

[jira] [Commented] (NIFI-3971) UpdateAttribute metric for output 'size' is larger than it should be when cloning

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3971:
--

Github user asfgit closed the pull request at:

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


> UpdateAttribute metric for output 'size' is larger than it should be when 
> cloning
> -
>
> Key: NIFI-3971
> URL: https://issues.apache.org/jira/browse/NIFI-3971
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> When I configure UpdateAttribute so that the 'success' relationship goes to 
> multiple destinations, the output count is double what it should be. For 
> instance, if i send in 1 GB of data, the output size should be 2 GB (since 
> it's cloned to a second connection) but it shows 4 GB.



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

[jira] [Commented] (NIFI-3971) UpdateAttribute metric for output 'size' is larger than it should be when cloning

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3971:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/1854
  
+1 will merge to master.  thanks


> UpdateAttribute metric for output 'size' is larger than it should be when 
> cloning
> -
>
> Key: NIFI-3971
> URL: https://issues.apache.org/jira/browse/NIFI-3971
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> When I configure UpdateAttribute so that the 'success' relationship goes to 
> multiple destinations, the output count is double what it should be. For 
> instance, if i send in 1 GB of data, the output size should be 2 GB (since 
> it's cloned to a second connection) but it shows 4 GB.



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

[jira] [Commented] (NIFI-3971) UpdateAttribute metric for output 'size' is larger than it should be when cloning

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3971:
---

under review

> UpdateAttribute metric for output 'size' is larger than it should be when 
> cloning
> -
>
> Key: NIFI-3971
> URL: https://issues.apache.org/jira/browse/NIFI-3971
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> When I configure UpdateAttribute so that the 'success' relationship goes to 
> multiple destinations, the output count is double what it should be. For 
> instance, if i send in 1 GB of data, the output size should be 2 GB (since 
> it's cloned to a second connection) but it shows 4 GB.



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

[jira] [Commented] (NIFI-3971) UpdateAttribute metric for output 'size' is larger than it should be when cloning

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3971:
--

GitHub user markap14 opened a pull request:

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

NIFI-3971: Fixed bug in calculating content size that was transferred…

… when cloning a relationship

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-3971

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

https://github.com/apache/nifi/pull/1854.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 #1854


commit 8d4bc8a2301535c6ca6041bda3c0ab35ee7531ea
Author: Mark Payne 
Date:   2017-05-24T19:31:33Z

NIFI-3971: Fixed bug in calculating content size that was transferred when 
cloning a relationship




> UpdateAttribute metric for output 'size' is larger than it should be when 
> cloning
> -
>
> Key: NIFI-3971
> URL: https://issues.apache.org/jira/browse/NIFI-3971
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>
> When I configure UpdateAttribute so that the 'success' relationship goes to 
> multiple destinations, the output count is double what it should be. For 
> instance, if i send in 1 GB of data, the output size should be 2 GB (since 
> it's cloned to a second connection) but it shows 4 GB.



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