[jira] [Updated] (NIFI-3467) Add EL support to more fields
[ https://issues.apache.org/jira/browse/NIFI-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Schultz updated NIFI-3467: -- Summary: Add EL support to more fields (was: Support EL Fields) > Add EL support to more fields > - > > Key: NIFI-3467 > URL: https://issues.apache.org/jira/browse/NIFI-3467 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Tom Schultz > > As per conversation with Matt Burgess, here are a list of fields we use that > don't support EL. We would like to have EL on these fields so we can automate > the deployment of our NiFis. The list actually turned out to be fairly small, > so kudos for having EL support on so many. > * Remote Process Group - Make it configurable in the first place. These > values will change per deploy > * GetFile - File filter > * GetKafka - Zookeeper connection string, topic name, client name, group ID > * ConsumeKafka - Group ID > * PutElasticSearch - Cluster name, hosts, username, password > * All processors - make scheduling configurable (with EL support) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3467) Support EL Fields
Tom Schultz created NIFI-3467: - Summary: Support EL Fields Key: NIFI-3467 URL: https://issues.apache.org/jira/browse/NIFI-3467 Project: Apache NiFi Issue Type: Improvement Reporter: Tom Schultz As per conversation with Matt Burgess, here are a list of fields we use that don't support EL. We would like to have EL on these fields so we can automate the deployment of our NiFis. The list actually turned out to be fairly small, so kudos for having EL support on so many. * Remote Process Group - Make it configurable in the first place. These values will change per deploy * GetFile - File filter * GetKafka - Zookeeper connection string, topic name, client name, group ID * ConsumeKafka - Group ID * PutElasticSearch - Cluster name, hosts, username, password * All processors - make scheduling configurable (with EL support) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3446) Make FlowConfigurationDAO Pluggable
[ https://issues.apache.org/jira/browse/NIFI-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862418#comment-15862418 ] ASF GitHub Bot commented on NIFI-3446: -- Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/1478#discussion_r100668964 --- Diff: nifi-commons/nifi-properties/src/main/java/org/apache/nifi/util/NiFiProperties.java --- @@ -48,6 +48,7 @@ // core properties public static final String PROPERTIES_FILE_PATH = "nifi.properties.file.path"; +public static final String FLOW_CONFIGURATION_IMPLEMENTATION = "nifi.flow.configuration.implementation"; --- End diff -- This needs to be added in nifi.properties file in nifi-resources. > Make FlowConfigurationDAO Pluggable > --- > > Key: NIFI-3446 > URL: https://issues.apache.org/jira/browse/NIFI-3446 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.2.0 >Reporter: Peter Wicks >Assignee: Peter Wicks > Fix For: 1.2.0 > > > FlowConfigurationDAO should be pluggable so that an alternate Flow > Configuration storage layer can be used. > This may be a multistep process, this ticket does the first step by moving > more of the functionality into FlowConfigurationDAO, allows users to override > (optional) properties in nifi.properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi pull request #1478: NIFI-3446 FlowConfigurationDAO Changes
Github user pvillard31 commented on a diff in the pull request: https://github.com/apache/nifi/pull/1478#discussion_r100668964 --- Diff: nifi-commons/nifi-properties/src/main/java/org/apache/nifi/util/NiFiProperties.java --- @@ -48,6 +48,7 @@ // core properties public static final String PROPERTIES_FILE_PATH = "nifi.properties.file.path"; +public static final String FLOW_CONFIGURATION_IMPLEMENTATION = "nifi.flow.configuration.implementation"; --- End diff -- This needs to be added in nifi.properties file in nifi-resources. --- 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] [Updated] (NIFI-3459) Weird blue highlighting of breadcrumbs
[ https://issues.apache.org/jira/browse/NIFI-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-3459: - Resolution: Fixed Fix Version/s: 1.2.0 Status: Resolved (was: Patch Available) > Weird blue highlighting of breadcrumbs > -- > > Key: NIFI-3459 > URL: https://issues.apache.org/jira/browse/NIFI-3459 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Trivial > Fix For: 1.2.0 > > > When clicking on the breadcrumbs to navigate to a group there seems to be > some weird blue highlighting. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3459) Weird blue highlighting of breadcrumbs
[ https://issues.apache.org/jira/browse/NIFI-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862410#comment-15862410 ] ASF subversion and git services commented on NIFI-3459: --- Commit febe6da4a2c85b8fdda7c80bd7626e8a3f54536f in nifi's branch refs/heads/master from [~scottyaslan] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=febe6da ] [NIFI-3459] remove blue higlighting from bread crumbs This closes #1500. > Weird blue highlighting of breadcrumbs > -- > > Key: NIFI-3459 > URL: https://issues.apache.org/jira/browse/NIFI-3459 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Trivial > > When clicking on the breadcrumbs to navigate to a group there seems to be > some weird blue highlighting. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3459) Weird blue highlighting of breadcrumbs
[ https://issues.apache.org/jira/browse/NIFI-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862409#comment-15862409 ] ASF GitHub Bot commented on NIFI-3459: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1500 Confirmed the observation when using Chrome (it does not seem to appear in Firefox), and checked the fix. Merging, thanks @scottyaslan. > Weird blue highlighting of breadcrumbs > -- > > Key: NIFI-3459 > URL: https://issues.apache.org/jira/browse/NIFI-3459 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Trivial > > When clicking on the breadcrumbs to navigate to a group there seems to be > some weird blue highlighting. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi pull request #1500: [NIFI-3459] remove blue highlighting from bread cru...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1500 --- 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 #1500: [NIFI-3459] remove blue highlighting from bread crumbs
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1500 Confirmed the observation when using Chrome (it does not seem to appear in Firefox), and checked the fix. Merging, thanks @scottyaslan. --- 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-3452) Add Wait processor Wait Mode property
[
https://issues.apache.org/jira/browse/NIFI-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862406#comment-15862406
]
ASF GitHub Bot commented on NIFI-3452:
--
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/1490
Hi @ijokarumawak, thanks for this improvement, that's really nice. And
thanks for the template, it was really useful to review this PR! I just have a
minor styling issue and since this processor is not released yet: could you
just update the properties to use both ``.name()`` and ``.displayName()``?
Otherwise LGTM and I'll merge as soon as you let me know.
> Add Wait processor Wait Mode property
> -
>
> Key: NIFI-3452
> URL: https://issues.apache.org/jira/browse/NIFI-3452
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.2.0
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
> Attachments: wait-for-a-par-of-flow-to-finish.png
>
>
> NiFi back pressure is handled per relationship and as long as a relationship
> has room to receive more flow files, source processor is scheduled to run.
> However, this behavior is not ideal in some cases. For example, when there is
> very computationally expensive task and user wants to limit the number of
> FlowFiles can be processed at a given time, it's not always possible to limit
> the rate by existing RateControl nor back-pressure mechanism.
> As a more practical example, in the following flow, it's expected the GetSQS
> is triggered only when the previous FlowFile has been processed completely.
> Node 1 is parsing a flow file (indicated by the X in the connection between
> FetchS3Object and Parse). Both connections have a back-pressure threshold of
> 1, but because the object is already fetched, the first connection is empty
> and can thus be filled. This means that, if a new item becomes available in
> the queue, both of the following cases can happen with equal probability:
> {code}
> Case 1:
> -- - -
> Node 1: | GetSQS | -X-> | FetchS3Object | -X-> | Parse |
> -- - -
> -- - -
> Node 2: | GetSQS | ---> | FetchS3Object | ---> | Parse |
> -- - -
> Case 2:
> -- - -
> Node 1: | GetSQS | ---> | FetchS3Object | -X-> | Parse |
> -- - -
> -- - -
> Node 2: | GetSQS | -X-> | FetchS3Object | ---> | Parse |
> -- - -
> {code}
> To achieve that, we could improve Wait processor as follows.
> NiFi scheduler checks downstream relationship availability, when it's full,
> the processor won't be scheduled to run. In case a source processor has
> multiple outgoing relationships, and if ANY of those is full, the processor
> won't be scheduled.
> (This is how processor scheduling works with back-pressure, but can
> alter with @TriggerWhenAnyDestinationAvailable annotation. DistributeLoad is
> the only processor annotated with this)
> We could use this mechanism to keep the source processor waiting to be
> scheduled, by following flow:
> {code}
> GetSQS
> -- success --> FetchS3Object --> Parse --> Notify
> -- success --> Wait
> {code}
> To make it work as expected, we need to improve Wait so that user can choose
> how waiting FlowFile is handled, from either:
> "Route to 'wait' relationship" or "Keep in the Upstream connection".
> Currently it has only option to route to 'wait'.
> Use "Keep in the Upstream connection" Wait mode with the flow above,
> the incoming flow file in GetSQS -> Wait connection stays there until actual
> data processing finishes and Notify sends a notification signal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] nifi issue #1490: NIFI-3452: Add Wait processor Wait Mode property
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1490 Hi @ijokarumawak, thanks for this improvement, that's really nice. And thanks for the template, it was really useful to review this PR! I just have a minor styling issue and since this processor is not released yet: could you just update the properties to use both ``.name()`` and ``.displayName()``? Otherwise LGTM and I'll merge as soon as you let me know. --- 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] [Updated] (NIFI-1657) Provide support for various locales in CI builds
[ https://issues.apache.org/jira/browse/NIFI-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-1657: - Resolution: Fixed Fix Version/s: 1.2.0 Status: Resolved (was: Patch Available) > Provide support for various locales in CI builds > > > Key: NIFI-1657 > URL: https://issues.apache.org/jira/browse/NIFI-1657 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Andre >Priority: Minor > Fix For: 1.2.0 > > > There were issues stemming from locale and building on more than the default > would help us catch similar issues moving forward. > From https://github.com/apache/nifi/pull/292, this can be accomplished via > something like: > -Duser.language=fr -Duser.region=FR -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-1657) Provide support for various locales in CI builds
[ https://issues.apache.org/jira/browse/NIFI-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862403#comment-15862403 ] ASF subversion and git services commented on NIFI-1657: --- Commit 1e5570d9b09d80a47eab45a4901eca8c092a21a5 in nifi's branch refs/heads/master from Andre F de Miranda [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1e5570d ] NIFI-1657 - Configure travis-ci to run mvn verify in ja_JP, fr_FR, and pt_BR This closes #1480. > Provide support for various locales in CI builds > > > Key: NIFI-1657 > URL: https://issues.apache.org/jira/browse/NIFI-1657 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Andre >Priority: Minor > > There were issues stemming from locale and building on more than the default > would help us catch similar issues moving forward. > From https://github.com/apache/nifi/pull/292, this can be accomplished via > something like: > -Duser.language=fr -Duser.region=FR -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-1657) Provide support for various locales in CI builds
[ https://issues.apache.org/jira/browse/NIFI-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862404#comment-15862404 ] ASF GitHub Bot commented on NIFI-1657: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1480 > Provide support for various locales in CI builds > > > Key: NIFI-1657 > URL: https://issues.apache.org/jira/browse/NIFI-1657 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Andre >Priority: Minor > > There were issues stemming from locale and building on more than the default > would help us catch similar issues moving forward. > From https://github.com/apache/nifi/pull/292, this can be accomplished via > something like: > -Duser.language=fr -Duser.region=FR -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi pull request #1480: NIFI-1657 - Configure travis-ci to run mvn verify i...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1480 --- 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-1657) Provide support for various locales in CI builds
[ https://issues.apache.org/jira/browse/NIFI-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862402#comment-15862402 ] ASF GitHub Bot commented on NIFI-1657: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1480 Thanks a lot @trixpan, I know it has been a real nightmare to get things working with Travis... Will merge ;) > Provide support for various locales in CI builds > > > Key: NIFI-1657 > URL: https://issues.apache.org/jira/browse/NIFI-1657 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Andre >Priority: Minor > > There were issues stemming from locale and building on more than the default > would help us catch similar issues moving forward. > From https://github.com/apache/nifi/pull/292, this can be accomplished via > something like: > -Duser.language=fr -Duser.region=FR -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi issue #1480: NIFI-1657 - Configure travis-ci to run mvn verify in jp an...
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1480 ð Thanks a lot @trixpan, I know it has been a real nightmare to get things working with Travis... Will merge ;) --- 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-3455) GenerateTableFetch fails for very large row counts
[ https://issues.apache.org/jira/browse/NIFI-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862401#comment-15862401 ] ASF GitHub Bot commented on NIFI-3455: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1499 Hey @patricker, It looks good to me, thanks for the PR. Could you fix the checkstyle violations? [WARNING] src/test/java/org/apache/nifi/processors/standard/TestGenerateTableFetch.java[40:8] (imports) UnusedImports: Unused import - java.sql.JDBCType. [WARNING] src/test/java/org/apache/nifi/processors/standard/TestGenerateTableFetch.java[41:8] (imports) UnusedImports: Unused import - java.sql.PreparedStatement. [WARNING] src/test/java/org/apache/nifi/processors/standard/TestGenerateTableFetch.java[57] (imports) AvoidStarImport: Using the '.*' form of import should be avoided - org.mockito.Mockito.*. Thanks. > GenerateTableFetch fails for very large row counts > -- > > Key: NIFI-3455 > URL: https://issues.apache.org/jira/browse/NIFI-3455 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.2.0 >Reporter: Peter Wicks >Assignee: Peter Wicks >Priority: Minor > Fix For: 1.2.0 > > > When retrieving the row count for the total number of rows to page over > GenerateTableFetch gets the row count as an integer. In some cases the value > returned is greater then the maximum value of Int32 causing a looping of the > value, resulting in a negative number. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi issue #1499: NIFI-3455 Large row count paging
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1499 Hey @patricker, It looks good to me, thanks for the PR. Could you fix the checkstyle violations? [WARNING] src/test/java/org/apache/nifi/processors/standard/TestGenerateTableFetch.java[40:8] (imports) UnusedImports: Unused import - java.sql.JDBCType. [WARNING] src/test/java/org/apache/nifi/processors/standard/TestGenerateTableFetch.java[41:8] (imports) UnusedImports: Unused import - java.sql.PreparedStatement. [WARNING] src/test/java/org/apache/nifi/processors/standard/TestGenerateTableFetch.java[57] (imports) AvoidStarImport: Using the '.*' form of import should be avoided - org.mockito.Mockito.*. 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-3466) ParseCEF tests fail when run with ja_JP locale
[ https://issues.apache.org/jira/browse/NIFI-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862363#comment-15862363 ] Andre commented on NIFI-3466: - The issue seems to be caused by the rt field containing MMM formatted month. I have reached out to HPE to confirm if CEF's MMM notation should be locale independent or not and will update code accordingly. > ParseCEF tests fail when run with ja_JP locale > -- > > Key: NIFI-3466 > URL: https://issues.apache.org/jira/browse/NIFI-3466 > Project: Apache NiFi > Issue Type: Bug >Reporter: Andre >Assignee: Andre > > testSuccessfulParseToContentUTC(org.apache.nifi.processors.standard.TestParseCEF) > Time elapsed: 0.005 sec <<< FAILURE! > java.lang.AssertionError: Expected all Transferred FlowFiles to go to success > but 1 were routed to failure > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) > at > org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToContentUTC(TestParseCEF.java:217) > testSuccessfulParseToAttributes(org.apache.nifi.processors.standard.TestParseCEF) > Time elapsed: 0.001 sec <<< FAILURE! > java.lang.AssertionError: Expected all Transferred FlowFiles to go to success > but 1 were routed to failure > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) > at > org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToAttributes(TestParseCEF.java:85) > testSuccessfulParseToAttributesWithUTC(org.apache.nifi.processors.standard.TestParseCEF) > Time elapsed: 0.002 sec <<< FAILURE! > java.lang.AssertionError: Expected all Transferred FlowFiles to go to success > but 1 were routed to failure > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) > at > org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToAttributesWithUTC(TestParseCEF.java:125) > testSuccessfulParseToContent(org.apache.nifi.processors.standard.TestParseCEF) > Time elapsed: 0.002 sec <<< FAILURE! > java.lang.AssertionError: Expected all Transferred FlowFiles to go to success > but 1 were routed to failure > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) > at > org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToContent(TestParseCEF.java:148) > testSuccessfulParseToContentWhenCEFContainsJSON(org.apache.nifi.processors.standard.TestParseCEF) > Time elapsed: 0.001 sec <<< FAILURE! > java.lang.AssertionError: Expected all Transferred FlowFiles to go to success > but 1 were routed to failure > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) > at > org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) > at > org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToContentWhenCEFContainsJSON(TestParseCEF.java:180) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3466) ParseCEF tests fail when run with ja_JP locale
Andre created NIFI-3466: --- Summary: ParseCEF tests fail when run with ja_JP locale Key: NIFI-3466 URL: https://issues.apache.org/jira/browse/NIFI-3466 Project: Apache NiFi Issue Type: Bug Reporter: Andre Assignee: Andre testSuccessfulParseToContentUTC(org.apache.nifi.processors.standard.TestParseCEF) Time elapsed: 0.005 sec <<< FAILURE! java.lang.AssertionError: Expected all Transferred FlowFiles to go to success but 1 were routed to failure at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) at org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToContentUTC(TestParseCEF.java:217) testSuccessfulParseToAttributes(org.apache.nifi.processors.standard.TestParseCEF) Time elapsed: 0.001 sec <<< FAILURE! java.lang.AssertionError: Expected all Transferred FlowFiles to go to success but 1 were routed to failure at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) at org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToAttributes(TestParseCEF.java:85) testSuccessfulParseToAttributesWithUTC(org.apache.nifi.processors.standard.TestParseCEF) Time elapsed: 0.002 sec <<< FAILURE! java.lang.AssertionError: Expected all Transferred FlowFiles to go to success but 1 were routed to failure at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) at org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToAttributesWithUTC(TestParseCEF.java:125) testSuccessfulParseToContent(org.apache.nifi.processors.standard.TestParseCEF) Time elapsed: 0.002 sec <<< FAILURE! java.lang.AssertionError: Expected all Transferred FlowFiles to go to success but 1 were routed to failure at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) at org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToContent(TestParseCEF.java:148) testSuccessfulParseToContentWhenCEFContainsJSON(org.apache.nifi.processors.standard.TestParseCEF) Time elapsed: 0.001 sec <<< FAILURE! java.lang.AssertionError: Expected all Transferred FlowFiles to go to success but 1 were routed to failure at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.MockProcessSession.assertAllFlowFilesTransferred(MockProcessSession.java:1152) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:267) at org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:313) at org.apache.nifi.processors.standard.TestParseCEF.testSuccessfulParseToContentWhenCEFContainsJSON(TestParseCEF.java:180) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-1657) Provide support for various locales in CI builds
[ https://issues.apache.org/jira/browse/NIFI-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862323#comment-15862323 ] ASF GitHub Bot commented on NIFI-1657: -- Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1480 @pvillard31 - after a few hundred builds and options build seems to be having as expected: https://travis-ci.org/trixpan/nifi/builds/200568234 when environment is set to en_US or "default", build succeeds while the french build fails as expected. https://travis-ci.org/trixpan/nifi/jobs/200568237#L2899 > Provide support for various locales in CI builds > > > Key: NIFI-1657 > URL: https://issues.apache.org/jira/browse/NIFI-1657 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Andre >Priority: Minor > > There were issues stemming from locale and building on more than the default > would help us catch similar issues moving forward. > From https://github.com/apache/nifi/pull/292, this can be accomplished via > something like: > -Duser.language=fr -Duser.region=FR -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi issue #1480: NIFI-1657 - Configure travis-ci to run mvn verify in jp an...
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1480 @pvillard31 - after a few hundred builds and options build seems to be having as expected: https://travis-ci.org/trixpan/nifi/builds/200568234 when environment is set to en_US or "default", build succeeds while the french build fails as expected. https://travis-ci.org/trixpan/nifi/jobs/200568237#L2899 --- 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. ---
