[jira] [Resolved] (NIFI-2816) The great typo cleanup

[Andre (JIRA)]

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

Andre resolved NIFI-2816.
-
Resolution: Fixed

> The great typo cleanup
> --
>
> Key: NIFI-2816
> URL: https://issues.apache.org/jira/browse/NIFI-2816
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre
>Assignee: Andre
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2685) Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "

[Andre (JIRA)]

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

Andre updated NIFI-2685:

Fix Version/s: 0.8.0
   1.1.0
   Status: Patch Available  (was: Open)

> Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "
> 
>
> Key: NIFI-2685
> URL: https://issues.apache.org/jira/browse/NIFI-2685
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Andre
>Priority: Trivial
> Fix For: 1.1.0, 0.8.0
>
>
> When building NiFi on a machine with ssh X11 forwarding enabled, maven may 
> fail to build due to the following error:
> {code}
> testResize(org.apache.nifi.processors.image.TestResizeImage)  Time elapsed: 
> 2.22 sec  <<< FAILURE!
> java.lang.AssertionError: java.awt.AWTError: Can't connect to X11 window 
> server using 'localhost:12.0' as the value of the DISPLAY variable.
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:192)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:151)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:146)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:141)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:136)
> at 
> org.apache.nifi.processors.image.TestResizeImage.testResize(TestResizeImage.java:44)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2904) Create processor to decode netflow

[Andre (JIRA)]

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

Andre commented on NIFI-2904:
-

[~madhu1512]

> Create processor to decode netflow
> --
>
> Key: NIFI-2904
> URL: https://issues.apache.org/jira/browse/NIFI-2904
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.1.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.2.0
>
>
> Recently, users have asked if netflow collection is possible.
> http://apache-nifi.1125220.n5.nabble.com/Netflow-parser-tp11319p11322.html
> Given logstash replacement is a frequent NiFi use case and netflow is a 
> farily well documented protocol, it may be well worth implementing a netflow 
> decoder



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2903) GetKafka cannot handle null value in Kafka offset cause NullPointerException

[Kurt Hung (JIRA)]

Kurt Hung created NIFI-2903:
---

 Summary: GetKafka cannot handle null value in Kafka offset cause 
NullPointerException
 Key: NIFI-2903
 URL: https://issues.apache.org/jira/browse/NIFI-2903
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 0.7.0, 1.0.0
Reporter: Kurt Hung


The GetKafka processor does not handle the condition of null value that exists 
in Kafka offset, which would cause the processor hang on and generate a 
NullPointerException after 30 sec. It's easy to reproduce this issue; I use the 
kafka-python to insert a key-value pair ("abc", None), and create a GetKafka 
processor to consume the topic I've created. This issue would happen 
immediately, and moreover, the processor could't consume rest offsets.

Temporary I customize a GetKafka processor for a "Failure" relationship to 
handle null values exist in Kafka offset to prevent this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1815) Tesseract OCR Processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1815:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/397
  
@olegz @jdye64 is this PR still active / plan to review?

Cheers


> Tesseract OCR Processor
> ---
>
> Key: NIFI-1815
> URL: https://issues.apache.org/jira/browse/NIFI-1815
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
> Attachments: 0006-changes-to-the-OCR-processor.patch, 
> nifi_1815_1.x_patch.zip
>
>
> This ticket is a follow-up to NIFI-1718 minus the use of the Tika library
> Expose OCR capabilities through a new processor which uses the Tesseract 
> library. Use of this processor would require that Tesseract be installed on 
> the NiFi host. Since the processor will have a system dependency care must be 
> taken to ensure that the overall NiFi cluster continues to function properly 
> in the absence of the Tesseract system dependency even though the OCR 
> processor itself will be unable to perform its duties. In the event that the 
> system dependencies are not detected the processor should display a 
> validation warning rather than failing or preventing the NiFi instance from 
> booting properly.
> Properties expose to configure Tesseract
> tesseractPath - Path to tesseract installation folder, if not on system path.
> language - Language ID (e.g. "eng"); language dictionary to be used.
> pageSegMode - Tesseract page segmentation mode, defaults to 1.
> minFileSizeToOcr - Minimum file size to submit file to OCR, defaults to 0.
> maxFileSizeToOcr - Maximum file size to submit file to OCR, defaults to 
> Integer.MAX_VALUE.
> timeout - Maximum time (in seconds) to wait for the OCR process termination; 
> defaults to 120.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #397: NIFI-1815

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/397
  
@olegz @jdye64 is this PR still active / plan to review?

Cheers


---
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-2900) DateTime API Endpoints don't respect RFC 3339

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2900:
--

Github user simplesteph commented on the issue:

https://github.com/apache/nifi/pull/1136
  
I think then we need to add `dataType = "string"` in the annotation to 
every field `DateTime` that uses any `TimeAdapter` or `DateTimeAdapter`. 
Hopefully this way the format won't be shown as "date-time". Somehow my maven 
is acting up and I can't test it...

Let me know your thoughts


> DateTime API Endpoints don't respect RFC 3339
> -
>
> Key: NIFI-2900
> URL: https://issues.apache.org/jira/browse/NIFI-2900
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Stephane Maarek
>
> Hi,
> the endpoint /flow/process-group/id is supposed to return lastRefreshed as 
> part of ProcessGroupFlowDTO as a DateTime, as indicated here:
> lastRefreshed string (date-time)  optionalThe time the flow for 
> the process group was last refreshed.
> as it currently stands, what I am getting doesn't look like a timestamp:
> "lastRefreshed":"14:02:46 AEDT"
> I'm not sure how much of the overall API is affected
> Edit:
> Actually, it seems every date a "date-time" is created we expect the format 
> "HH:mm:ss z".
> As per the OpenAPI specs, if a field is annotated "date-time", it should 
> respect the RFC 3339 convention 
> (https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types).
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1136: [NIFI-2900] fixes timestamps to be ISO 8601 compliant, as ...

[simplesteph]

Github user simplesteph commented on the issue:

https://github.com/apache/nifi/pull/1136
  
I think then we need to add `dataType = "string"` in the annotation to 
every field `DateTime` that uses any `TimeAdapter` or `DateTimeAdapter`. 
Hopefully this way the format won't be shown as "date-time". Somehow my maven 
is acting up and I can't test it...

Let me know your thoughts


---
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] [Resolved] (NIFI-314) Detailed dataflow statistics/info needed for back pressure and expiration.

[Pierre Villard (JIRA)]

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

Pierre Villard resolved NIFI-314.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

> Detailed dataflow statistics/info needed for back pressure and expiration.
> --
>
> Key: NIFI-314
> URL: https://issues.apache.org/jira/browse/NIFI-314
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matthew Clarke
> Fix For: 1.1.0
>
>
> Currently connections that have "File Expiration" set show this information 
> through an icon displayed on the connection box on the graph.  This icon 
> should be expanded to show what back pressure object and back pressure data 
> size thresholds have been set. 
> There are two pieces to this expanded information that are missing that would 
> make this information more useful to the end user.
> 1. There should be some indication to the end user when one of the above set 
> values is occurring.   (Are files actually expiring?  Is back pressure 
> currently being applied?)
> 2. Expose this information in the summary table connections tab. While it is 
> great that this information is exposed on the graph. On large dataflows it 
> can be hard to find or go unnoticed.  The summary table serves as a great 
> resources for identifying where issues exist within the dataflow.  Bulletins 
> displayed on the graph also show here.  end users need to be able to 
> find/identify from the summary table when things like file expiration and 
> back pressure are occurring.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2896) Perform Release Management Functions for 0.7.1

[ASF subversion and git services (JIRA)]

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

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

Commit e97d1a86094c45dd53af66e8c628b5cb5750c2a6 in nifi's branch 
refs/heads/NIFI-2896-RC1 from [~jskora]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e97d1a8 ]

NIFI-2896-RC1 prepare for next development iteration


> Perform Release Management Functions for 0.7.1
> --
>
> Key: NIFI-2896
> URL: https://issues.apache.org/jira/browse/NIFI-2896
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Joe Skora
>Assignee: Joe Skora
>  Labels: release
> Fix For: 0.7.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2896) Perform Release Management Functions for 0.7.1

[ASF subversion and git services (JIRA)]

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

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

Commit 421d5e61553e5fa160af9e0cc9fdc237af46906d in nifi's branch 
refs/heads/NIFI-2896-RC1 from [~jskora]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=421d5e6 ]

NIFI-2896-RC1 prepare release nifi-0.7.1-RC1


> Perform Release Management Functions for 0.7.1
> --
>
> Key: NIFI-2896
> URL: https://issues.apache.org/jira/browse/NIFI-2896
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Joe Skora
>Assignee: Joe Skora
>  Labels: release
> Fix For: 0.7.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #984: Nifi 2624

[ToivoAdams]

Github user ToivoAdams commented on the issue:

https://github.com/apache/nifi/pull/984
  
I created new pull request #1142
Could not reopen this PR


---
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-2624) JDBC-to-Avro processors handle BigDecimals as Strings

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2624:
--

GitHub user ToivoAdams opened a pull request:

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

NIFI-2624 JdbcCommon treats BigDecimals now as Avro Logical type usin…

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.

…g bytes to hold data (not String as is was before).

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

$ git pull https://github.com/ToivoAdams/nifi nifi-2624b

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

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


commit 4d6de9663087ebb30041341c8d55de01c4af3875
Author: Toivo Adams 
Date:   2016-10-16T17:15:33Z

NIFI-2624 JdbcCommon treats BigDecimals now as Avro Logical type using 
bytes to hold data (not String as is was before).




> JDBC-to-Avro processors handle BigDecimals as Strings
> -
>
> Key: NIFI-2624
> URL: https://issues.apache.org/jira/browse/NIFI-2624
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Toivo Adams
>
> The original SQL processors implemented BigDecimal values as Strings for 
> Avro, as the version of Avro it used (1.7.6) did not support DECIMAL type.
> As of Avro 1.7.7 (AVRO-1402), this type is supported and so the SQL/HiveQL 
> processors should be updated to handle BigDecimals correctly if possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1142: NIFI-2624 JdbcCommon treats BigDecimals now as Avro...

[ToivoAdams]

GitHub user ToivoAdams opened a pull request:

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

NIFI-2624 JdbcCommon treats BigDecimals now as Avro Logical type usin…

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.

…g bytes to hold data (not String as is was before).

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

$ git pull https://github.com/ToivoAdams/nifi nifi-2624b

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

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


commit 4d6de9663087ebb30041341c8d55de01c4af3875
Author: Toivo Adams 
Date:   2016-10-16T17:15:33Z

NIFI-2624 JdbcCommon treats BigDecimals now as Avro Logical type using 
bytes to hold data (not String as is was before).




---
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-2685) Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2685:
--

GitHub user trixpan opened a pull request:

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

NIFI-2685 - Configure surefire to use JAVA Headless mode



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

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

$ git pull https://github.com/trixpan/nifi NIFI-2685v0.x

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

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


commit 607cf8fb92bc399216f2ec383814f9ce13159a7b
Author: Andre F de Miranda 
Date:   2016-10-16T09:54:14Z

NIFI-2685 - Configure surefire to use JAVA Headless mode




> Builds fails due to "java.awt.AWTError: Can't connect to X11 window server "
> 
>
> Key: NIFI-2685
> URL: https://issues.apache.org/jira/browse/NIFI-2685
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Andre
>Assignee: Andre
>Priority: Trivial
>
> When building NiFi on a machine with ssh X11 forwarding enabled, maven may 
> fail to build due to the following error:
> {code}
> testResize(org.apache.nifi.processors.image.TestResizeImage)  Time elapsed: 
> 2.22 sec  <<< FAILURE!
> java.lang.AssertionError: java.awt.AWTError: Can't connect to X11 window 
> server using 'localhost:12.0' as the value of the DISPLAY variable.
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:192)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:151)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:146)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:141)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:136)
> at 
> org.apache.nifi.processors.image.TestResizeImage.testResize(TestResizeImage.java:44)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1141: NIFI-2685 - Configure surefire to use JAVA Headless...

[trixpan]

GitHub user trixpan opened a pull request:

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

NIFI-2685 - Configure surefire to use JAVA Headless mode



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

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

$ git pull https://github.com/trixpan/nifi NIFI-2685v0.x

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

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


commit 607cf8fb92bc399216f2ec383814f9ce13159a7b
Author: Andre F de Miranda 
Date:   2016-10-16T09:54:14Z

NIFI-2685 - Configure surefire to use JAVA Headless mode




---
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] [Resolved] (NIFI-1154) testResizeImage fails under certain conditions

[Andre (JIRA)]

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

Andre resolved NIFI-1154.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

> testResizeImage fails under certain conditions 
> ---
>
> Key: NIFI-1154
> URL: https://issues.apache.org/jira/browse/NIFI-1154
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
> Environment: windows client. ssh'ed into linux box. DISPLAY set, but 
> no X Server
>Reporter: Tony Kurc
>Priority: Minor
> Fix For: 1.1.0
>
>
> {noformat}
> Running org.apache.nifi.processors.image.TestResizeImage
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.202 sec <<< 
> FAILURE! - in org.apache.nifi.processors.image.TestResizeImage
> testResize(org.apache.nifi.processors.image.TestResizeImage)  Time elapsed: 
> 2.202 sec  <<< FAILURE!
> java.lang.AssertionError: java.awt.AWTError: Can't connect to X11 window 
> server using 'localhost:10.0' as the value of the DISPLAY variable.
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:227)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:186)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:181)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:176)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:171)
> at 
> org.apache.nifi.processors.image.TestResizeImage.testResize(TestResizeImage.java:44)
> Caused by: java.awt.AWTError: Can't connect to X11 window server using 
> 'localhost:10.0' as the value of the DISPLAY variable.
> at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
> at 
> sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
> at 
> sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:115)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:74)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:102)
> at 
> java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:81)
> at sun.awt.X11.XToolkit.(XToolkit.java:126)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at java.awt.Toolkit$2.run(Toolkit.java:860)
> at java.awt.Toolkit$2.run(Toolkit.java:855)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:854)
> at java.awt.Image.getScaledInstance(Image.java:178)
> at 
> org.apache.nifi.processors.image.ResizeImage$1.process(ResizeImage.java:171)
> at 
> org.apache.nifi.util.MockProcessSession.write(MockProcessSession.java:667)
> at 
> org.apache.nifi.util.MockProcessSession.write(MockProcessSession.java:59)
> at 
> org.apache.nifi.processors.image.ResizeImage.onTrigger(ResizeImage.java:152)
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner$RunProcessor.call(StandardProcessorTestRunner.java:277)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner$RunProcessor.call(StandardProcessorTestRunner.java:271)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Results :
> Failed tests:
>   TestResizeImage.testResize:44 java.awt.AWTError: Can't connect to X11 
> window server using 'localhost:10.0' as the value of the DISPLAY variable.
> {noformat}
> test succeeds after an unset of DISPLAY



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-1154) testResizeImage fails under certain conditions

[Andre (JIRA)]

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

Andre updated NIFI-1154:

Fix Version/s: 0.7.1

> testResizeImage fails under certain conditions 
> ---
>
> Key: NIFI-1154
> URL: https://issues.apache.org/jira/browse/NIFI-1154
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
> Environment: windows client. ssh'ed into linux box. DISPLAY set, but 
> no X Server
>Reporter: Tony Kurc
>Priority: Minor
> Fix For: 1.1.0, 0.7.1
>
>
> {noformat}
> Running org.apache.nifi.processors.image.TestResizeImage
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.202 sec <<< 
> FAILURE! - in org.apache.nifi.processors.image.TestResizeImage
> testResize(org.apache.nifi.processors.image.TestResizeImage)  Time elapsed: 
> 2.202 sec  <<< FAILURE!
> java.lang.AssertionError: java.awt.AWTError: Can't connect to X11 window 
> server using 'localhost:10.0' as the value of the DISPLAY variable.
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:227)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:186)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:181)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:176)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:171)
> at 
> org.apache.nifi.processors.image.TestResizeImage.testResize(TestResizeImage.java:44)
> Caused by: java.awt.AWTError: Can't connect to X11 window server using 
> 'localhost:10.0' as the value of the DISPLAY variable.
> at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
> at 
> sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
> at 
> sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:115)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:74)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:102)
> at 
> java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:81)
> at sun.awt.X11.XToolkit.(XToolkit.java:126)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at java.awt.Toolkit$2.run(Toolkit.java:860)
> at java.awt.Toolkit$2.run(Toolkit.java:855)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:854)
> at java.awt.Image.getScaledInstance(Image.java:178)
> at 
> org.apache.nifi.processors.image.ResizeImage$1.process(ResizeImage.java:171)
> at 
> org.apache.nifi.util.MockProcessSession.write(MockProcessSession.java:667)
> at 
> org.apache.nifi.util.MockProcessSession.write(MockProcessSession.java:59)
> at 
> org.apache.nifi.processors.image.ResizeImage.onTrigger(ResizeImage.java:152)
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner$RunProcessor.call(StandardProcessorTestRunner.java:277)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner$RunProcessor.call(StandardProcessorTestRunner.java:271)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Results :
> Failed tests:
>   TestResizeImage.testResize:44 java.awt.AWTError: Can't connect to X11 
> window server using 'localhost:10.0' as the value of the DISPLAY variable.
> {noformat}
> test succeeds after an unset of DISPLAY



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)