[
https://issues.apache.org/jira/browse/NIFI-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099505#comment-16099505
]
ASF GitHub Bot commented on NIFI-4212:
--
Github user jvwing commented on the issue:
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/2030
Overall, this looks good - tests pass, integration tests pass, refactoring
of integration test credentials is nice, code looks good. In my basic testing,
it deleted objects from RethinkDB just fine.
[
https://issues.apache.org/jira/browse/NIFI-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099406#comment-16099406
]
ASF GitHub Bot commented on NIFI-4212:
--
Github user jvwing commented on the issue:
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/2030
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
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099363#comment-16099363
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user alopresto commented on the issue:
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1986
I am trying to walk the line between "make everything configurable" and
"sometimes people who don't understand this configure it". If you have a client
that only supports `SSLv3`, it won't work
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099359#comment-16099359
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user trkurc commented on the issue:
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099358#comment-16099358
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user trkurc commented on the issue:
Github user trkurc commented on the issue:
https://github.com/apache/nifi/pull/1986
@m-hogue - do you have ideas on how to improve the user experience given
the above feedback?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user trkurc commented on the issue:
https://github.com/apache/nifi/pull/1986
From a "just works" perspective, if I happened to have a client that only
worked with SSLv3 for whatever reason and attempted to configure it as such, I
think no user feedback and an unexpected
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099354#comment-16099354
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user alopresto commented on the issue:
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1986
What was the previous behavior if an unavailable protocol version was
selected? My understanding is that it will silently use a more secure available
protocol. This is debatable about which is
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099343#comment-16099343
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user trkurc commented on the issue:
Github user trkurc commented on the issue:
https://github.com/apache/nifi/pull/1986
@alopresto - fair points, however, I do think this is a step in the right
direction in terms of user experience - previously, when selecting an
StandardSSLContextService and protocol, the choice was
[
https://issues.apache.org/jira/browse/NIFI-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099338#comment-16099338
]
ASF GitHub Bot commented on NIFI-2529:
--
Github user alopresto commented on the issue:
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1985
I have similar concerns with this as with [PR
1986](https://github.com/apache/nifi/pull/1986) about throwing exceptions on
71% of the available options in the protocol version dropdown.
---
If
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099334#comment-16099334
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user alopresto commented on the issue:
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1986
@trkurc My initial reaction was to earlier comments that I interpreted to
open the idea of manually overriding the current state, which does not allow
`SSLv3` to be used. I should have cleaned that
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099330#comment-16099330
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user trkurc commented on the issue:
Github user trkurc commented on the issue:
https://github.com/apache/nifi/pull/1986
@alopresto - I'm not sure I understand your concerns. The current
implementation won't support SSLv3, and will throw an error if someone selects
that protocol in their StandardSSLContextService and
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099307#comment-16099307
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user alopresto commented on the issue:
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1986
I realize that performing this logic (controller service used for listening
vs. outgoing connections) dynamically may be challenging or not possible (CS
can be used by multiple referencing
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099301#comment-16099301
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user alopresto commented on the issue:
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1986
I'm sorry I'm late on this, but why are we trying to allow `SSLv3` for
anything? I understand the original reason for this work was to be in line with
the `PostHTTP` processor, but this makes
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099298#comment-16099298
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user alopresto commented on a diff in the pull request:
Github user alopresto commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1986#discussion_r129185483
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListenHTTP.java
---
@@ -227,7
Andy LoPresto created NIFI-4222:
---
Summary: TLS Toolkit should provide SAN by default
Key: NIFI-4222
URL: https://issues.apache.org/jira/browse/NIFI-4222
Project: Apache NiFi
Issue Type:
Andy LoPresto created NIFI-4221:
---
Summary: Print app startup in human-readable time
Key: NIFI-4221
URL: https://issues.apache.org/jira/browse/NIFI-4221
Project: Apache NiFi
Issue Type:
[
https://issues.apache.org/jira/browse/NIFI-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto updated NIFI-4221:
Labels: logs time (was: )
> Print app startup in human-readable time
>
Andy LoPresto created NIFI-4220:
---
Summary: Cmd + R does not refresh page from Insufficient
Permissions error page
Key: NIFI-4220
URL: https://issues.apache.org/jira/browse/NIFI-4220
Project: Apache
[
https://issues.apache.org/jira/browse/NIFI-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099124#comment-16099124
]
Joseph Witt commented on NIFI-3376:
---
I also meant to comment on your recent proposal specifically. The
[
https://issues.apache.org/jira/browse/NIFI-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099102#comment-16099102
]
Joseph Witt commented on NIFI-3376:
---
I think you do have a group of people that want to help find a
[
https://issues.apache.org/jira/browse/NIFI-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099056#comment-16099056
]
ASF GitHub Bot commented on NIFI-4219:
--
GitHub user yuri1969 opened a pull request:
[
https://issues.apache.org/jira/browse/NIFI-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099055#comment-16099055
]
Michael Moser commented on NIFI-3376:
-
I don't think the degree of difficulty should stop us from
GitHub user yuri1969 opened a pull request:
https://github.com/apache/nifi-site/pull/21
NIFI-4219 - Describe partial builds in Quickstart
... guide
Suggestions are welcome.
You can merge this pull request into a Git repository by running:
$ git pull
Yuri created NIFI-4219:
--
Summary: Describe partial builds in Quickstart guide
Key: NIFI-4219
URL: https://issues.apache.org/jira/browse/NIFI-4219
Project: Apache NiFi
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/NIFI-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099048#comment-16099048
]
ASF GitHub Bot commented on NIFI-4032:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/NIFI-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099046#comment-16099046
]
ASF subversion and git services commented on NIFI-4032:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099047#comment-16099047
]
ASF subversion and git services commented on NIFI-4032:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16099013#comment-16099013
]
ASF GitHub Bot commented on NIFI-4032:
--
Github user YolandaMDavis commented on the issue:
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/2019
@mcgilman with the latest commit I was able to add a new node and see the
users.xml file populated. The node started successfully and I was able to
access the cluster without issue.
[
https://issues.apache.org/jira/browse/NIFI-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-4217:
---
Status: Patch Available (was: In Progress)
> CaptureChangeMySQL DDL lowercases table names
>
[
https://issues.apache.org/jira/browse/NIFI-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098557#comment-16098557
]
ASF GitHub Bot commented on NIFI-4217:
--
GitHub user mattyb149 opened a pull request:
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/2036
NIFI-4217: Retain original DDL in CaptureChangeMySQL
The DDL contents were being "normalized" to check for certain keywords like
"alter table". However this normalized version was being passed on,
[
https://issues.apache.org/jira/browse/NIFI-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess reassigned NIFI-4217:
--
Assignee: Matt Burgess
> CaptureChangeMySQL DDL lowercases table names
>
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098546#comment-16098546
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user m-hogue commented on the issue:
[
https://issues.apache.org/jira/browse/NIFI-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098544#comment-16098544
]
ASF GitHub Bot commented on NIFI-2529:
--
Github user m-hogue commented on the issue:
Github user m-hogue commented on the issue:
https://github.com/apache/nifi/pull/1986
@trkurc : Pushed changes. Please let me know if you'd like any additional
changes.
---
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 m-hogue commented on the issue:
https://github.com/apache/nifi/pull/1985
@trkurc : pushed same SSL protocol checks as added in #1985. Let me know if
you'd like any additional changes.
---
If your project is set up for it, you can reply to this email and have your
reply
Matt Burgess created NIFI-4218:
--
Summary: ElasticsearchHttp processors should support dynamic
properties as query parameters
Key: NIFI-4218
URL: https://issues.apache.org/jira/browse/NIFI-4218
Project:
Matt Burgess created NIFI-4217:
--
Summary: CaptureChangeMySQL DDL lowercases table names
Key: NIFI-4217
URL: https://issues.apache.org/jira/browse/NIFI-4217
Project: Apache NiFi
Issue Type: Bug
[
https://issues.apache.org/jira/browse/NIFI-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098489#comment-16098489
]
ASF GitHub Bot commented on NIFI-2529:
--
Github user trkurc commented on a diff in the pull request:
[
https://issues.apache.org/jira/browse/NIFI-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098486#comment-16098486
]
ASF GitHub Bot commented on NIFI-2528:
--
Github user trkurc commented on the issue:
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1985#discussion_r129051538
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpRequest.java
---
@@
Github user trkurc commented on the issue:
https://github.com/apache/nifi/pull/1986
the approach looks good.
---
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
[
https://issues.apache.org/jira/browse/NIFI-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16098317#comment-16098317
]
ASF GitHub Bot commented on NIFI-4032:
--
Github user mcgilman commented on the issue:
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2019
Great find @YolandaMDavis! Will address this and update. Thanks!
---
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
Joseph Witt created NIFI-4216:
-
Summary: NiFi Maven plugin for Nars needs to be marked ThreadSafe
Key: NIFI-4216
URL: https://issues.apache.org/jira/browse/NIFI-4216
Project: Apache NiFi
Issue
58 matches
Mail list logo