Hello,
The Apache NiFi team would like to announce the release of Apache NiFi
0.5.1.
Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data. Apache NiFi was made for dataflow. It supports highly
configurable directed graphs of data routing, transformation, a
Github user trixpan commented on the pull request:
https://github.com/apache/nifi/pull/233#issuecomment-189735776
@bbende
The protocol is proprietary
https://answers.splunk.com/answers/12543/splunk-data-format.html
so unless they suddenly decided to documen
Github user mans2singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54336504
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/ItemKeys.java
---
@@ -0,0 +1,52 @@
Github user mans2singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54336495
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDB.java
---
@@ -0,0 +1,152
Github user mans2singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54336499
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/GetDynamoDB.java
---
@@ -0,0 +1,180 @@
Github user mans2singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54336478
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDB.java
---
@@ -0,0 +1,152
Github user mans2singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54336475
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBProcessor.java
---
@@ -
Github user mans2singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54336468
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBProcessor.java
---
@@ -
Github user mans4singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54335906
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBProcessor.java
---
@@ -
Github user mans4singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54335848
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/GetDynamoDB.java
---
@@ -0,0 +1,180 @@
Github user mans4singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54335853
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/ItemKeys.java
---
@@ -0,0 +1,52 @@
Github user mans4singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54335830
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDB.java
---
@@ -0,0 +1,152
Github user mans4singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54335802
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBProcessor.java
---
@@ -
Github user mans4singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54335808
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDB.java
---
@@ -0,0 +1,152
Github user mans4singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r54335804
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBProcessor.java
---
@@ -
GitHub user rpmiskin opened a pull request:
https://github.com/apache/nifi/pull/251
NIFI-1573 Allow programmatic access to a Processor's name
I've added a `getName()` method to `ProcessContext` which means that a
`Processor` can access the name that was configured in the UI.
You ca
I guess it will depend how much change is expected on the maintenance branches,
but if you want every change in the maintenance branch to go into the
main-line branch then there is little difference from a conflict point of view
between a series of cherry-picks and a merge.
Either way, it is just
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/233#issuecomment-189659132
@trixpan You are right that ListenSplunkForwarder is essentially a
ListenTCP. I started out thinking we might be able to do acknowledgements, but
was unable to find any doc
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/250
---
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 enable
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/250#issuecomment-189658351
Looks good, thanks for taking care of knocking this out! Will merge into
master shortly.
---
If your project is set up for it, you can reply to this email and have your
re
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/250#issuecomment-189656225
reviewing
---
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
On board with Tony's points. I think the realities of merging in practice
when that "breaking point" of sorts occurs will make the complexity and
overhead quite difficult and maybe even more error prone than the cherry
picking approach with some additional guidelines. When the codebase
drasticall
the reason I like applying patches to both lines is that once code begins
to diverge, cleanly merging into one codebase can be impossible. having
good practices for managing patches and where they apply is paramount for
success.
I expect that divergence to happen with 1.x. I wanted to get in a bat
I did the deployment with the standard name with not more success. I did also
change with upper and lower cases ,without any success.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/Installing-NIFI-through-ambari-tp7194p7680.html
Sent from the Apache NiF
Hi,
On a couple of work projects we found that the approach of cherry-picking
commits can lead to an unnecessarily complicated history where the same piece
of work appears as multiple separate commits on different branches. This can
then make it hard to be confident that a bug fix has been appl
GitHub user rpmiskin opened a pull request:
https://github.com/apache/nifi/pull/250
NIFI-963 Update admin guide to cover configuration of multiple lib
directories
Update to the admin guide to document the ability to configure multiple
library directories, which was added in NIFI-43
26 matches
Mail list logo
