Github user patricker commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2231#discussion_r159027392
--- Diff:
nifi-nar-bundles/nifi-cdc/nifi-cdc-mssql-bundle/nifi-cdc-mssql-processors/src/main/java/org/apache/nifi/cdc/mssql/MSSQLCDCUtils.java
---
@@ -0,0
[
https://issues.apache.org/jira/browse/NIFI-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306007#comment-16306007
]
ASF GitHub Bot commented on NIFI-4521:
--
Github user patricker commented on a diff in the pull request:
[
https://issues.apache.org/jira/browse/NIFI-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305969#comment-16305969
]
ASF GitHub Bot commented on NIFI-4521:
--
Github user GJPVN commented on a diff in the pull request:
Github user GJPVN commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2231#discussion_r159024001
--- Diff:
nifi-nar-bundles/nifi-cdc/nifi-cdc-mssql-bundle/nifi-cdc-mssql-processors/src/main/java/org/apache/nifi/cdc/mssql/MSSQLCDCUtils.java
---
@@ -0,0
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2219
It probably makes sense to consider a versioned flow dirty if new variables
are added which are already referenced (by name) in an EL statement in the
flow. So long as Variable Registry values are
[
https://issues.apache.org/jira/browse/NIFI-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-4717:
---
Status: Patch Available (was: Open)
> Minor bugs and performance improvements to record-oriented
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/2219
@pvillard31 I see what you are saying.. so the flow referenced variables
which didn't really exist yet so in v1 of the flow it didn't capture any
variables, then you want to add them but adding them
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/2219
@bbende - let's say I create a PG with a processor ListHDFS and I set
``${principal}`` and ``${keytab}`` for Kerberos properties. If I start
versioning and then add the variables, there is no
[
https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305633#comment-16305633
]
ASF GitHub Bot commented on NIFI-4428:
--
Github user vakshorton commented on the issue:
Github user vakshorton commented on the issue:
https://github.com/apache/nifi/pull/2310
@MikeThomsen There is an indexing service that works with Kafka. However,
for high volume use cases, this requires a lot of Kafka resources just to
ingest data into Druid. Presumably, all that
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/2219
@pvillard31 if the variable is added and not referenced by anything then i
believe that is expected behavior, there would be no reason to include that
variable in the versioned flow sent to the
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/2219
@mcgilman - when adding a variable to a versioned PG, it does not show
changes to be committed. Is it expected?
---
[
https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305560#comment-16305560
]
ASF GitHub Bot commented on NIFI-4428:
--
Github user MikeThomsen commented on the issue:
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2310
@mattyb149 @pvillard31 FWIW, I read on the Druid site that you can use
Kafka to load data into Druid instead of Tranquility. I don't know anything
about Tranquility, but working up a flow that
[
https://issues.apache.org/jira/browse/NIFI-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-4505:
Resolution: Fixed
Fix Version/s: 1.5.0
Status: Resolved (was: Patch Available)
>
[
https://issues.apache.org/jira/browse/NIFI-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-4504:
Resolution: Fixed
Fix Version/s: 1.5.0
Status: Resolved (was: Patch Available)
>
[
https://issues.apache.org/jira/browse/NIFI-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305530#comment-16305530
]
ASF subversion and git services commented on NIFI-4504:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305532#comment-16305532
]
ASF GitHub Bot commented on NIFI-4504:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/NIFI-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305531#comment-16305531
]
ASF subversion and git services commented on NIFI-4505:
---
Commit
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/2284
---
[
https://issues.apache.org/jira/browse/NIFI-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305528#comment-16305528
]
ASF GitHub Bot commented on NIFI-4504:
--
Github user ijokarumawak commented on the issue:
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/2284
@mosermw @devriesb Thanks for sharing your opinions. I think we have enough
discussion and since there are multiple audience willing to have these method.
I am going to merge this. Thanks again
[
https://issues.apache.org/jira/browse/NIFIREG-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305494#comment-16305494
]
ASF GitHub Bot commented on NIFIREG-87:
---
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/nifi-registry/pull/73
---
Github user kevdoran commented on a diff in the pull request:
https://github.com/apache/nifi-registry/pull/73#discussion_r158952014
--- Diff: nifi-registry-assembly/README.md ---
@@ -18,12 +18,27 @@ Registryâa subproject of Apache NiFiâis a
complementary application that pro
[
https://issues.apache.org/jira/browse/NIFIREG-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305485#comment-16305485
]
ASF GitHub Bot commented on NIFIREG-87:
---
Github user kevdoran commented on a diff in the pull
[
https://issues.apache.org/jira/browse/NIFIREG-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305483#comment-16305483
]
ASF GitHub Bot commented on NIFIREG-87:
---
GitHub user bbende opened a pull request:
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/73
NIFIREG-87 Updating assembly README for release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry update-readme
[
https://issues.apache.org/jira/browse/NIFIREG-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende resolved NIFIREG-84.
Resolution: Fixed
> Add screenshots to User Guide
> -
>
>
[
https://issues.apache.org/jira/browse/NIFI-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305451#comment-16305451
]
ASF GitHub Bot commented on NIFI-4504:
--
Github user devriesb commented on the issue:
Github user devriesb commented on the issue:
https://github.com/apache/nifi/pull/2284
Koji,
"Are all of these three methods, removeAndGet, removeByPatternAndGet and
keySet required by the folks you know of?" - Yes.
"atomicity is not that important in these method
31 matches
Mail list logo
