[jira] [Created] (NIFI-9621) Ignore reserved characters to FlattenJson Processor
Jaeyeong Baek created NIFI-9621: --- Summary: Ignore reserved characters to FlattenJson Processor Key: NIFI-9621 URL: https://issues.apache.org/jira/browse/NIFI-9621 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Jaeyeong Baek Improvement to FlattenJson Processor to support 'ignore reserved characters while flattening' -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] Noel-bk opened a new pull request #5704: NIFI-9621: Ignore reserved characters to FlattenJson Processor
Noel-bk opened a new pull request #5704:
URL: https://github.com/apache/nifi/pull/5704
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Ignore reserved characters to FlattenJson Processor
- upgrade to json-flattener 0.13.0
- add ignore_reserved_characters property
### 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 `main`)?
- [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 JDK 8?
- [x] Have you verified that the full build is successful on 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 GitHub Actions 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.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (NIFI-9622) There is currently no Cluster Coordinator. This often happens upon restart of NiFi when running an embedded ZooKeeper. Will register this node to become the active Cluster
Tarun Bali created NIFI-9622: Summary: There is currently no Cluster Coordinator. This often happens upon restart of NiFi when running an embedded ZooKeeper. Will register this node to become the active Cluster Coordinator and will attempt to connect to cluster again. Key: NIFI-9622 URL: https://issues.apache.org/jira/browse/NIFI-9622 Project: Apache NiFi Issue Type: Bug Reporter: Tarun Bali -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9622) There is currently no Cluster Coordinator. This often happens upon restart of NiFi when running an embedded ZooKeeper. Will register this node to become the active Cluster
[ https://issues.apache.org/jira/browse/NIFI-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tarun Bali updated NIFI-9622: - Component/s: Docker Description: Hi Community, I am trying to run nifi through docker compose but getting below WARN: There is currently no Cluster Coordinator. This often happens upon restart of NiFi when running an embedded ZooKeeper. Will register this node to become the active Cluster Coordinator and will attempt to connect to cluster again Attempted to register Leader Election for role 'Cluster Coordinator' but this role is already registered. The NiFI UI is in invalid state and saying that The Flow Controller is initializing the Data Flow. Below are my docker-compose config: zookeeper: hostname: zookeeper image: zookeeper:latest container_name: zookeeper ports: - "2181:2181" networks: net_pet: ipv4_address: 172.27.1.15 environment: - ZOOKEEPER_HOST_NAME=zookeeper - ZOOKEEPER_CONNECTION_TIMEOUT_MS=6000 - STREAMS_ZK_SESSION_TIMEOUT_SEC=60 - ALLOW_ANONYMOUS_LOGIN=yes nifi: image: apache/nifi:latest ports: - 8080 environment: - NIFI_WEB_HTTP_PORT=8080 - NIFI_CLUSTER_IS_NODE=true - NIFI_CLUSTER_NODE_PROTOCOL_PORT=8082 - NIFI_ZK_CONNECT_STRING=zookeeper:2181 - NIFI_ELECTION_MAX_WAIT=1 min - NIFI_SENSITIVE_PROPS_KEY=tarunbali > There is currently no Cluster Coordinator. This often happens upon restart of > NiFi when running an embedded ZooKeeper. Will register this node to become > the active Cluster Coordinator and will attempt to connect to cluster again. > -- > > Key: NIFI-9622 > URL: https://issues.apache.org/jira/browse/NIFI-9622 > Project: Apache NiFi > Issue Type: Bug > Components: Docker >Reporter: Tarun Bali >Priority: Major > > Hi Community, > I am trying to run nifi through docker compose but getting below WARN: > There is currently no Cluster Coordinator. This often happens upon restart of > NiFi when running an embedded ZooKeeper. Will register this node to become > the active Cluster Coordinator and will attempt to connect to cluster again > Attempted to register Leader Election for role 'Cluster Coordinator' but this > role is already registered. > > The NiFI UI is in invalid state and saying that The Flow Controller is > initializing the Data Flow. > Below are my docker-compose config: > > zookeeper: > hostname: zookeeper > image: zookeeper:latest > container_name: zookeeper > ports: > - "2181:2181" > networks: > net_pet: > ipv4_address: 172.27.1.15 > environment: > - ZOOKEEPER_HOST_NAME=zookeeper > - ZOOKEEPER_CONNECTION_TIMEOUT_MS=6000 > - STREAMS_ZK_SESSION_TIMEOUT_SEC=60 > - ALLOW_ANONYMOUS_LOGIN=yes > nifi: > image: apache/nifi:latest > ports: > - 8080 > environment: > - NIFI_WEB_HTTP_PORT=8080 > - NIFI_CLUSTER_IS_NODE=true > - NIFI_CLUSTER_NODE_PROTOCOL_PORT=8082 > - NIFI_ZK_CONNECT_STRING=zookeeper:2181 > - NIFI_ELECTION_MAX_WAIT=1 min > - NIFI_SENSITIVE_PROPS_KEY=tarunbali > > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [nifi] github-actions[bot] closed pull request #5377: NIFI-9165 Refactored nifi-standard-bundle to use JUnit 5.
github-actions[bot] closed pull request #5377: URL: https://github.com/apache/nifi/pull/5377 -- 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. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (NIFI-5899) json-smart of Hadoop dependency for 2.3-SNAPSHOT version
[
https://issues.apache.org/jira/browse/NIFI-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kemix Koo resolved NIFI-5899.
-
Resolution: Won't Do
> json-smart of Hadoop dependency for 2.3-SNAPSHOT version
>
>
> Key: NIFI-5899
> URL: https://issues.apache.org/jira/browse/NIFI-5899
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.8.0
>Reporter: Kemix Koo
>Assignee: Kemix Koo
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, because the hadoop processors with hadoop-client dependency. but
> it depend on the SNAPSHOT version of json-smart.
> Same problem with https://issues.apache.org/jira/browse/HBASE-20291
>
> {code:java}
> [ERROR] Failed to execute goal on project nifi-hadoop-utils: Could not
> resolve dependencies for project
> org.apache.nifi:nifi-hadoop-utils:jar:1.9.0-SNAPSHOT: Failed to collect
> dependencies at org.apache.hadoop:hadoop-common:jar:3.0.0 ->
> org.apache.hadoop:hadoop-auth:jar:3.0.0 ->
> com.nimbusds:nimbus-jose-jwt:jar:4.41.1 ->
> net.minidev:json-smart:jar:2.3-SNAPSHOT: Failed to read artifact descriptor
> for net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact
> net.minidev:json-smart:pom:2.3-SNAPSHOT from/to dynamodb-local-oregon
> (https://s3-us-west-2.amazonaws.com/dynamodb-local/release):
> s3-us-west-2.amazonaws.com: Unknown host s3-us-west-2.amazonaws.com
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [nifi] timeabarna commented on pull request #5582: NIFI-9455 Add aggregated predictions to Prometheus
timeabarna commented on pull request #5582: URL: https://github.com/apache/nifi/pull/5582#issuecomment-1019764197 Thanks @exceptionfactory for your help. This PR should be the final of the consolidated PRs, can you please help reviewing it? -- 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. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
