You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Am-ilcar (via GitHub)" <gi...@apache.org> on 2025/09/06 18:01:11 UTC

[PR] NIFI-14838 Adding a new processor and controller service to connect and listen to Ethereum Beacon Chain events. [nifi]

Am-ilcar opened a new pull request, #10280:
URL: https://github.com/apache/nifi/pull/10280

   
   <!-- Licensed to the Apache Software Foundation (ASF) under one or more -->
   <!-- contributor license agreements.  See the NOTICE file distributed with -->
   <!-- this work for additional information regarding copyright ownership. -->
   <!-- The ASF licenses this file to You under the Apache License, Version 2.0 -->
   <!-- (the "License"); you may not use this file except in compliance with -->
   <!-- the License.  You may obtain a copy of the License at -->
   <!--     http://www.apache.org/licenses/LICENSE-2.0 -->
   <!-- Unless required by applicable law or agreed to in writing, software -->
   <!-- distributed under the License is distributed on an "AS IS" BASIS, -->
   <!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -->
   <!-- See the License for the specific language governing permissions and -->
   <!-- limitations under the License. -->
   
   # Summary
   
   [NIFI-14838](https://issues.apache.org/jira/browse/NIFI-14838)
   
   # Tracking
   
   Please complete the following tracking steps prior to pull request creation.
   
   ### Issue Tracking
   
   - [ x ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created
   
   ### Pull Request Tracking
   
   - [ x ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000`
   - [ x ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000`
   
   ### Pull Request Formatting
   
   - [ x ] Pull Request based on current revision of the `main` branch
   - [ x ] Pull Request refers to a feature branch with one commit containing changes
   
   # Verification
   
   Please indicate the verification steps performed prior to pull request creation.
   
   ### Build
   
   - [ x ] Build completed using `./mvnw clean install -P contrib-check`
     - [ x ] JDK 21
   
   ### Licensing
   
   - [ x ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html)
   - [ x ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files
   
   ### Documentation
   
   - [ x ] Documentation formatting appears as expected in rendered files
   


-- 
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-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] NIFI-14838 Adding a new processor and controller service to connect and listen to Ethereum Beacon Chain events. [nifi]

Posted by "exceptionfactory (via GitHub)" <gi...@apache.org>.
exceptionfactory commented on PR #10280:
URL: https://github.com/apache/nifi/pull/10280#issuecomment-3263321994

   You're welcome @Am-ilcar, thanks for the reply!


-- 
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-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] NIFI-14838 Adding a new processor and controller service to connect and listen to Ethereum Beacon Chain events. [nifi]

Posted by "Am-ilcar (via GitHub)" <gi...@apache.org>.
Am-ilcar closed pull request #10280: NIFI-14838 Adding a new processor and controller service to connect and listen to Ethereum Beacon Chain events.
URL: https://github.com/apache/nifi/pull/10280


-- 
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-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] NIFI-14838 Adding a new processor and controller service to connect and listen to Ethereum Beacon Chain events. [nifi]

Posted by "taxmeifyoucan (via GitHub)" <gi...@apache.org>.
taxmeifyoucan commented on PR #10280:
URL: https://github.com/apache/nifi/pull/10280#issuecomment-3632377405

   I just wanted to vouch for this addition, it's a useful tool for Ethereum core developers, although I understand it is somewhat niche for the scope of this repo. 


-- 
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-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] NIFI-14838 Adding a new processor and controller service to connect and listen to Ethereum Beacon Chain events. [nifi]

Posted by "Am-ilcar (via GitHub)" <gi...@apache.org>.
Am-ilcar commented on PR #10280:
URL: https://github.com/apache/nifi/pull/10280#issuecomment-3263245448

   > Thanks for proposing these new components @Am-ilcar.
   > 
   > On initial consideration, integration with Ethereum Beacon Events seems too specialized for general adoption and maintenance within the Apache NiFi distribution.
   > 
   > In past years, the project accepted a small number of components that served particular purposes, but NiFi 2 incorporated the deprecation and removal of many components for various reasons, including components that did not have broad maintenance or common use.
   > 
   > Although NiFi provides an open framework, not every type of extension component is suitable for inclusion within the project, because it requires ongoing maintenance.
   > 
   > I recommend publishing the components as NAR bundles to the Maven Central repository, which would make them available for general use. If this leads to notable adoption, inclusion within the project could be reconsidered.
   
   Thank you David, I'll take your recommendation of uploading the components to the Maven Central repository. In any case, I hope this utility will help other developers who are working in web3.
   
   Best regards


-- 
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-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org