[
https://issues.apache.org/jira/browse/NIFI-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837101#comment-15837101
]
ASF GitHub Bot commented on NIFI-3354:
--
Github user olegz commented on the issue:
Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/1436
@joewitt Thanks Joe. That was indeed copy/paste issue from unrelated
internal effort. Will fix.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
[
https://issues.apache.org/jira/browse/NIFI-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837073#comment-15837073
]
ASF GitHub Bot commented on NIFI-3352:
--
Github user trixpan commented on the issue:
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1421
@joewitt
sure thing:
https://github.com/elastic/logstash-forwarder/blob/master/PROTOCOL.md#ack-frame-type
---
If your project is set up for it, you can reply to this email and
[
https://issues.apache.org/jira/browse/NIFI-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837068#comment-15837068
]
ASF GitHub Bot commented on NIFI-3352:
--
Github user joewitt commented on the issue:
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/1421
@trixpan is there anything we can reference for this change showing it
should be an int instead of a long? It is clearly a pretty simple change just
want to have some clear basis for it. thanks
[
https://issues.apache.org/jira/browse/NIFI-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837064#comment-15837064
]
ASF GitHub Bot commented on NIFI-3354:
--
Github user joewitt commented on the issue:
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/1436
some of the source files have headers referencing hortonworks copyright.
That is either a copy/paste issue and just needs to be fixed or it is not an
original work for apache nifi and will need to
[
https://issues.apache.org/jira/browse/NIFI-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837062#comment-15837062
]
ASF GitHub Bot commented on NIFI-3385:
--
Github user joewitt commented on the issue:
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/1440
its probably not a big deal or maybe even not a thing but technically this
might update too many things as it is including updates against some
dependencies we have. Such updates might not be true
[
https://issues.apache.org/jira/browse/NIFI-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto resolved NIFI-3391.
-
Resolution: Fixed
Fix Version/s: 1.2.0
> Cron documentation fixes
>
[
https://issues.apache.org/jira/browse/NIFI-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837050#comment-15837050
]
ASF subversion and git services commented on NIFI-3391:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837053#comment-15837053
]
ASF GitHub Bot commented on NIFI-3391:
--
Github user alopresto commented on the issue:
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/1442
---
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
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1442
Fixed a minor typo and merged. @thesolson thanks for getting this done so
quickly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
[
https://issues.apache.org/jira/browse/NIFI-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837052#comment-15837052
]
ASF GitHub Bot commented on NIFI-3391:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/NIFI-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836939#comment-15836939
]
ASF GitHub Bot commented on NIFI-3391:
--
GitHub user thesolson opened a pull request:
GitHub user thesolson opened a pull request:
https://github.com/apache/nifi/pull/1442
NIFI-3391: Update Chron Scheduling information in the Configuring a Pâ¦
â¦rocessor section of the User Guide
Thank you for submitting a contribution to Apache NiFi.
In order to
[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Wing updated NIFI-3251:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Users who do not have modify the
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/1399
@mcgilman I think this looks good, it worked well in my testing. The
integration tests are passing again. These changes didn't break any tests, but
none of the tests in nifi-web-api really exercise
[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836667#comment-15836667
]
ASF GitHub Bot commented on NIFI-3251:
--
Github user jvwing commented on the issue:
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/1399
---
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
[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836659#comment-15836659
]
ASF GitHub Bot commented on NIFI-3251:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836658#comment-15836658
]
ASF subversion and git services commented on NIFI-3251:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarah Olson reassigned NIFI-3391:
-
Assignee: Sarah Olson
> Cron documentation fixes
>
>
>
[
https://issues.apache.org/jira/browse/NIFI-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim reassigned NIFI-3392:
Assignee: Andrew Lim
> Enhance documentation for provenance event type definitions
>
[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836552#comment-15836552
]
ASF GitHub Bot commented on NIFI-3251:
--
Github user mcgilman commented on the issue:
Andy LoPresto created NIFI-3392:
---
Summary: Enhance documentation for provenance event type
definitions
Key: NIFI-3392
URL: https://issues.apache.org/jira/browse/NIFI-3392
Project: Apache NiFi
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1399
I've updated the PR with the changes suggested thus far. Thanks again
@jvwing!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1302
@skrewz Yes, please make the changes and then as @apiri mentioned just push
to the same branch and the PR will update automatically. Thanks for the quick
response to my comments. Sorry again for
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1399
Yep, I'm tracking. Looks like that will provide more consistent coverage
when checking if that behavior should be available.
---
If your project is set up for it, you can reply to this email and
[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836530#comment-15836530
]
ASF GitHub Bot commented on NIFI-3251:
--
Github user mcgilman commented on the issue:
[
https://issues.apache.org/jira/browse/NIFI-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836522#comment-15836522
]
ASF GitHub Bot commented on NIFI-2656:
--
Github user alopresto commented on the issue:
[
https://issues.apache.org/jira/browse/NIFI-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836520#comment-15836520
]
ASF GitHub Bot commented on NIFI-3251:
--
Github user jvwing commented on the issue:
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1399#discussion_r97633156
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-controller-services.js
---
@@ -497,6
[
https://issues.apache.org/jira/browse/NIFI-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Rosander reassigned NIFI-3389:
Assignee: Bryan Rosander
> FlowFileSchema writes attribute name and value as STRING instead
[
https://issues.apache.org/jira/browse/NIFI-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-3390:
-
Assignee: Pierre Villard
Status: Patch Available (was: Open)
> Add support for LDAP HA
>
[
https://issues.apache.org/jira/browse/NIFI-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836400#comment-15836400
]
ASF GitHub Bot commented on NIFI-3390:
--
GitHub user pvillard31 opened a pull request:
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/1441
NIFI-3390 Added support for LDAP HA
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/1399
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 and wishes so, or if the
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/1302
@skrewz You can just push to the same branch that this PR was made from and
GitHub has you covered from there.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user skrewz commented on the issue:
https://github.com/apache/nifi/pull/1302
So, ehm. Should I remedy the above, and ehm---haven't done GitHub pull
requests before---update the pull request or how does this work? :)
---
If your project is set up for it, you can reply to this
Github user skrewz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1302#discussion_r97520897
--- Diff:
nifi-bootstrap/src/main/java/org/apache/nifi/bootstrap/RunNiFi.java ---
@@ -1027,19 +1028,24 @@ public boolean accept(final File dir, final String
Github user skrewz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1302#discussion_r97520807
--- Diff:
nifi-bootstrap/src/main/java/org/apache/nifi/bootstrap/RunNiFi.java ---
@@ -1027,19 +1028,24 @@ public boolean accept(final File dir, final String
Github user HandOfGod94 commented on the issue:
https://github.com/apache/nifi/pull/1294
I am not in need of this processor. I just wanted to contribute so took it
up. I'll give it another go, but I have few question:
1. Should we modify original EncryptContent to achieve
45 matches
Mail list logo
