[jira] [Resolved] (NIFI-1377) Upgrade to JsonPath 2.2.0
[ https://issues.apache.org/jira/browse/NIFI-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-1377. --- Resolution: Won't Fix > Upgrade to JsonPath 2.2.0 > - > > Key: NIFI-1377 > URL: https://issues.apache.org/jira/browse/NIFI-1377 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Aldrin Piri >Priority: Minor > > JsonPath (https://github.com/jayway/JsonPath) has a new release. > Given some of the optimizations that were made for the processors to provide > caching of and validation without exceptions of expressions, it is not a > clean upgrade due to those library internals being removed and/or changed. > Additionally, a new caching mechanism for expressions was also provided that > may be beneficial to make use of. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-1377) Upgrade to JsonPath 2.2.0
[ https://issues.apache.org/jira/browse/NIFI-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960697#comment-16960697 ] Aldrin Piri commented on NIFI-1377: --- [~janh] certainly can and good find > Upgrade to JsonPath 2.2.0 > - > > Key: NIFI-1377 > URL: https://issues.apache.org/jira/browse/NIFI-1377 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Aldrin Piri >Priority: Minor > > JsonPath (https://github.com/jayway/JsonPath) has a new release. > Given some of the optimizations that were made for the processors to provide > caching of and validation without exceptions of expressions, it is not a > clean upgrade due to those library internals being removed and/or changed. > Additionally, a new caching mechanism for expressions was also provided that > may be beneficial to make use of. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi] HorizonNet opened a new pull request #3851: NIFI-6816 Removed duplicated dependency declarations
HorizonNet opened a new pull request #3851: NIFI-6816 Removed duplicated
dependency declarations
URL: https://github.com/apache/nifi/pull/3851
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Removed the duplicated dependency declarations in Maven, which are inherited
via the main pom.
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? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### 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?
- [x] Have you verified that the full build is successful on both JDK 8 and
JDK 11?
- [ ] 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.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Created] (NIFI-6816) Remove duplicated dependency declarations
Jan Hentschel created NIFI-6816: --- Summary: Remove duplicated dependency declarations Key: NIFI-6816 URL: https://issues.apache.org/jira/browse/NIFI-6816 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Reporter: Jan Hentschel Some dependencies, which are inherited from the main pom, are declared again in sub-modules, resulting in warnings during the Maven build. These duplications should be removed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-1377) Upgrade to JsonPath 2.2.0
[ https://issues.apache.org/jira/browse/NIFI-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960648#comment-16960648 ] Jan Hentschel commented on NIFI-1377: - With NIFI-5169 already merged, is this one still necessary or can it be closed? > Upgrade to JsonPath 2.2.0 > - > > Key: NIFI-1377 > URL: https://issues.apache.org/jira/browse/NIFI-1377 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Reporter: Aldrin Piri >Priority: Minor > > JsonPath (https://github.com/jayway/JsonPath) has a new release. > Given some of the optimizations that were made for the processors to provide > caching of and validation without exceptions of expressions, it is not a > clean upgrade due to those library internals being removed and/or changed. > Additionally, a new caching mechanism for expressions was also provided that > may be beneficial to make use of. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi] HorizonNet opened a new pull request #3850: NIFI-6398 Added the 'replace first' and 'replace all' strategy to ReplaceText
HorizonNet opened a new pull request #3850: NIFI-6398 Added the 'replace first'
and 'replace all' strategy to ReplaceText
URL: https://github.com/apache/nifi/pull/3850
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Adds a 'replace first' and 'replace all' strategy to the ReplaceText
processor.
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? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### 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] Have you verified that the full build is successful on both JDK 8 and
JDK 11?
- [ ] 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.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Created] (NIFI-6815) NiFi status variables are not consistent with use of case
Jay Barra created NIFI-6815: --- Summary: NiFi status variables are not consistent with use of case Key: NIFI-6815 URL: https://issues.apache.org/jira/browse/NIFI-6815 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.9.2 Reporter: Jay Barra Responses for statuses can vary between "RUNNING" and "Running" for different calls. They should share casing -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6806) IllegalStateExceptionMapper, etc. should always log full stack trace
[ https://issues.apache.org/jira/browse/NIFI-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-6806: --- Resolution: Fixed Status: Resolved (was: Patch Available) > IllegalStateExceptionMapper, etc. should always log full stack trace > > > Key: NIFI-6806 > URL: https://issues.apache.org/jira/browse/NIFI-6806 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 1.11.0 > > > The IllegalStateExceptionMapper is used when any IllegalStateException makes > its way all the way back to the web tier. This happens, for instance, if a > Controller Service cannot be enabled. When this happens, the Exception Mapper > only logs the stack trace if DEBUG is enabled. This is an old pattern that > was followed during early releases to prevent such verbose logging, but this > Exception Mapper needs to be updated to always log the stack traces. > Otherwise, we have no way of knowing the underlying cause of the failure. > IllegalArgumentExceptionMapper and a few others also appear to follow this > same pattern and need to be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6806) IllegalStateExceptionMapper, etc. should always log full stack trace
[ https://issues.apache.org/jira/browse/NIFI-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Witt updated NIFI-6806: --- Fix Version/s: (was: 1.10.0) 1.11.0 > IllegalStateExceptionMapper, etc. should always log full stack trace > > > Key: NIFI-6806 > URL: https://issues.apache.org/jira/browse/NIFI-6806 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 1.11.0 > > > The IllegalStateExceptionMapper is used when any IllegalStateException makes > its way all the way back to the web tier. This happens, for instance, if a > Controller Service cannot be enabled. When this happens, the Exception Mapper > only logs the stack trace if DEBUG is enabled. This is an old pattern that > was followed during early releases to prevent such verbose logging, but this > Exception Mapper needs to be updated to always log the stack traces. > Otherwise, we have no way of knowing the underlying cause of the failure. > IllegalArgumentExceptionMapper and a few others also appear to follow this > same pattern and need to be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [nifi] aloneface commented on issue #3816: Nifi-6682 SplitJson does not work if the input is String "null"
aloneface commented on issue #3816: Nifi-6682 SplitJson does not work if the input is String "null" URL: https://github.com/apache/nifi/pull/3816#issuecomment-546695534 Why not catch all the throwables in SplitJson? If splitjson has other exceptions, the data will still not be put into failure route. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] aloneface edited a comment on issue #3816: Nifi-6682 SplitJson does not work if the input is String "null"
aloneface edited a comment on issue #3816: Nifi-6682 SplitJson does not work if the input is String "null" URL: https://github.com/apache/nifi/pull/3816#issuecomment-546695534 @MikeThomsen Why not catch all the throwables in SplitJson? If splitjson has other exceptions, the data will still not be put into failure route. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi] aloneface opened a new pull request #3816: Nifi-6682 SplitJson does not work if the input is String "null"
aloneface opened a new pull request #3816: Nifi-6682 SplitJson does not work if
the input is String "null"
URL: https://github.com/apache/nifi/pull/3816
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
_Enables X functionality; fixes bug 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? Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### 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?
- [ ] Have you verified that the full build is successful on both JDK 8 and
JDK 11?
- [-] 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.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Commented] (NIFI-6733) Create Apache NiFi 1.10.0 Release
[ https://issues.apache.org/jira/browse/NIFI-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960589#comment-16960589 ] ASF subversion and git services commented on NIFI-6733: --- Commit 9f14538bb14c141f4ca9d9b7dee3b5eb6115ddc1 in nifi's branch refs/heads/NIFI-6733-RC2 from Joe Witt [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9f14538 ] NIFI-6733-RC2 prepare release nifi-1.10.0-RC2 > Create Apache NiFi 1.10.0 Release > - > > Key: NIFI-6733 > URL: https://issues.apache.org/jira/browse/NIFI-6733 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Affects Versions: 1.10.0 >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-6733) Create Apache NiFi 1.10.0 Release
[ https://issues.apache.org/jira/browse/NIFI-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960590#comment-16960590 ] ASF subversion and git services commented on NIFI-6733: --- Commit 5e151359824dda51a33c58ad6dd7a37e299d5647 in nifi's branch refs/heads/NIFI-6733-RC2 from Joe Witt [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5e15135 ] NIFI-6733-RC2 prepare for next development iteration > Create Apache NiFi 1.10.0 Release > - > > Key: NIFI-6733 > URL: https://issues.apache.org/jira/browse/NIFI-6733 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Affects Versions: 1.10.0 >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6814) NiFi REST api returns incompatible date format for NiFi Client DTO
[
https://issues.apache.org/jira/browse/NIFI-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Barra updated NIFI-6814:
Description:
Using the Java client DTO library provided by
org.apache.nifi:nifi-client-dto:1.9.2
A JSON response returned from `GET /nifi-api/output-ports/\{id}` has the date
for a `statsLastRefreshed` field of a PortStatusDTO in an invalid format.
The DTO library should reflect the returned value or the response should match
the expected output format for deserialization.
{code:java}
com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize
value of type `java.util.Date` from String "12:20:32 UTC": not a valid
representation (error: Failed to parse Date value '12:20:32 UTC': Cannot parse
date "12:20:32 UTC": not compatible with any of standard forms
("-MM-dd'T'HH:mm:ss.SSSZ", "-MM-dd'T'HH:mm:ss.SSS", "EEE, dd MMM
HH:mm:ss zzz", "-MM-dd")) at [Source:
(String)"{"revision":{"version":0},"id":"06f7a59e-0169-1000-e2b6-5e89cb325bde","uri":"http://localhost:8080/nifi-api/output-ports/06f7a59e-0169-1000-e2b6-5e89cb325bde","position":{"x":1911.6532984123653,"y":127.11453136381226},"permissions":{"canRead":true,"canWrite":true},"bulletins":[],"component":{"id":"06f7a59e-0169-1000-e2b6-5e89cb325bde","parentGroupId":"bac43dfb-cafc-1fba-f7be-02cf8f20b6c6","position":{"x":1911.6532984123653,"y":127.11453136381226},"name":"ToRoute","comments":"","state":"STOPPED","[truncated
596 chars]; line: 1, column: 723] (through reference chain:
org.apache.nifi.web.api.entity.PortEntity["status"]->org.apache.nifi.web.api.dto.status.PortStatusDTO["statsLastRefreshed"])
at
com.fasterxml.jackson.databind.exc.InvalidFormatException.from(InvalidFormatException.java:67)
at
com.fasterxml.jackson.databind.DeserializationContext.weirdStringException(DeserializationContext.java:1549)
at
com.fasterxml.jackson.databind.DeserializationContext.handleWeirdStringValue(DeserializationContext.java:911)
at
com.fasterxml.jackson.databind.deser.std.StdDeserializer._parseDate(StdDeserializer.java:524)
at
com.fasterxml.jackson.databind.deser.std.StdDeserializer._parseDate(StdDeserializer.java:467)
at
com.fasterxml.jackson.databind.deser.std.DateDeserializers$DateBasedDeserializer._parseDate(DateDeserializers.java:195)
at
com.fasterxml.jackson.databind.deser.std.DateDeserializers$DateDeserializer.deserialize(DateDeserializers.java:285)
at
com.fasterxml.jackson.databind.deser.std.DateDeserializers$DateDeserializer.deserialize(DateDeserializers.java:268)
at
com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at
com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at
com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4014)
at
com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3005)
at
mil.dth.thapi.services.NifiServiceTest.canParseResponseValues(NifiServiceTest.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:532)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:115)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$6(TestMethodTestDescriptor.java:171)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:72)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:167)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:114)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:59)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$4(NodeTestTask.java:108)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:72)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:98)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:74)
at
[jira] [Updated] (NIFI-6814) NiFi REST api returns incompatible date format for NiFi Client DTO
[
https://issues.apache.org/jira/browse/NIFI-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Barra updated NIFI-6814:
Description:
Using the Java client DTO library provided by
org.apache.nifi:nifi-client-dto:1.9.2
A JSON response returned from `GET /nifi-api/output-ports/\{id}` has the date
for a `statsLastRefreshed` field of a PortStatusDTO in an invalid format.
The DTO library should reflect the returned value or the response should match
the expected output format for deserialization.
{code:java}
com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize
value of type `java.util.Date` from String "12:20:32 UTC": not a valid
representation (error: Failed to parse Date value '12:20:32 UTC': Cannot parse
date "12:20:32 UTC": not compatible with any of standard forms
("-MM-dd'T'HH:mm:ss.SSSZ", "-MM-dd'T'HH:mm:ss.SSS", "EEE, dd MMM
HH:mm:ss zzz", "-MM-dd")) at [Source:
(String)"{"revision":{"version":0},"id":"06f7a59e-0169-1000-e2b6-5e89cb325bde","uri":"http://localhost:8080/nifi-api/output-ports/06f7a59e-0169-1000-e2b6-5e89cb325bde","position":{"x":1911.6532984123653,"y":127.11453136381226},"permissions":{"canRead":true,"canWrite":true},"bulletins":[],"component":{"id":"06f7a59e-0169-1000-e2b6-5e89cb325bde","parentGroupId":"bac43dfb-cafc-1fba-f7be-02cf8f20b6c6","position":{"x":1911.6532984123653,"y":127.11453136381226},"name":"ToRoute","comments":"","state":"STOPPED","[truncated
596 chars]; line: 1, column: 723] (through reference chain:
org.apache.nifi.web.api.entity.PortEntity["status"]->org.apache.nifi.web.api.dto.status.PortStatusDTO["statsLastRefreshed"])
at
com.fasterxml.jackson.databind.exc.InvalidFormatException.from(InvalidFormatException.java:67)
at
com.fasterxml.jackson.databind.DeserializationContext.weirdStringException(DeserializationContext.java:1549)
at
com.fasterxml.jackson.databind.DeserializationContext.handleWeirdStringValue(DeserializationContext.java:911)
at
com.fasterxml.jackson.databind.deser.std.StdDeserializer._parseDate(StdDeserializer.java:524)
at
com.fasterxml.jackson.databind.deser.std.StdDeserializer._parseDate(StdDeserializer.java:467)
at
com.fasterxml.jackson.databind.deser.std.DateDeserializers$DateBasedDeserializer._parseDate(DateDeserializers.java:195)
at
com.fasterxml.jackson.databind.deser.std.DateDeserializers$DateDeserializer.deserialize(DateDeserializers.java:285)
at
com.fasterxml.jackson.databind.deser.std.DateDeserializers$DateDeserializer.deserialize(DateDeserializers.java:268)
at
com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at
com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288)
at
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at
com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4014)
at
com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3005)
at
mil.dth.thapi.services.NifiServiceTest.canParseResponseValues(NifiServiceTest.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:532)
at
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:115)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$6(TestMethodTestDescriptor.java:171)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:72)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:167)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:114)
at
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:59)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$4(NodeTestTask.java:108)
at
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:72)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:98)
at
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:74)
at
[jira] [Created] (NIFI-6814) NiFi REST api returns incompatible date format for NiFi Client DTO
Jay Barra created NIFI-6814:
---
Summary: NiFi REST api returns incompatible date format for NiFi
Client DTO
Key: NIFI-6814
URL: https://issues.apache.org/jira/browse/NIFI-6814
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 1.9.2
Reporter: Jay Barra
Using the Java client DTO library provided by
org.apache.nifi:nifi-client-dto:1.9.2
A JSON response returned from `GET /nifi-api/output-ports/\{id}` has the date
for a `statsLastRefreshed` field of a PortStatusDTO in an invalid format.
The DTO library should reflect the returned value or the response should match
the expected output format for deserialization.
{code:java}
/Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/bin/java -ea
-Didea.test.cyclic.buffer.size=1048576
"-javaagent:/Users/jaybarra/Library/Application
Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.6817.14/IntelliJ
IDEA.app/Contents/lib/idea_rt.jar=53526:/Users/jaybarra/Library/Application
Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.6817.14/IntelliJ
IDEA.app/Contents/bin" -Dfile.encoding=UTF-8 -classpath
"/Users/jaybarra/Library/Application
Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.6817.14/IntelliJ
IDEA.app/Contents/lib/idea_rt.jar:/Users/jaybarra/Library/Application
Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.6817.14/IntelliJ
IDEA.app/Contents/plugins/junit/lib/junit-rt.jar:/Users/jaybarra/Library/Application
Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/192.6817.14/IntelliJ
[GitHub] [nifi] aloneface closed pull request #3816: Nifi-6682 SplitJson does not work if the input is String "null"
aloneface closed pull request #3816: Nifi-6682 SplitJson does not work if the input is String "null" URL: https://github.com/apache/nifi/pull/3816 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
