[GitHub] nifi issue #655: DataDog support added
Github user Ramizjon commented on the issue: https://github.com/apache/nifi/pull/655 @JPercivall Thank you for your comments. About two last notes: in order to report to DataDog the DropWizard metrics "Gauges" are used (A gauge is an instantaneous measurement of a value). They work in such way, that you register some metric and specify where to take the value of every metric from (line with `ConcurrentHashMap metricsMap`). After that, DropWizard framework gets metric values from that structure with specified period of time. > Also doesn't DataDog use API keys in order to communicate? Shouldn't that be configured in the ReportingTask? In order do deliver metrics to DataDog, the DataDog agent is used. It is the best way do to so. It collects metrics and events and reports them to DataDog. This approach doesn't require any of API keys, but only agent installed. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #655: DataDog support added
Github user Ramizjon commented on a diff in the pull request: https://github.com/apache/nifi/pull/655#discussion_r71120239 --- Diff: nifi-nar-bundles/nifi-datadog-bundle/nifi-datadog-reporting-task/src/main/resources/docs/org.apache.nifi.reporting.ambari.AmbariReportingTask/additionalDetails.html --- @@ -0,0 +1,56 @@ + + + + + +DataDogReportingTask + + + + +DataDogReportingTask + +This ReportingTask sends the following metrics to DataDog: --- End diff -- User will add to his DataDog dashboard only that metrics that he is interested in. Other will not be shown, but they will exist, and he'll be able to include every of them at any moment. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #655: DataDog support added
Github user Ramizjon commented on a diff in the pull request: https://github.com/apache/nifi/pull/655#discussion_r71120372 --- Diff: nifi-nar-bundles/nifi-datadog-bundle/nifi-datadog-reporting-task/pom.xml --- @@ -0,0 +1,86 @@ + +http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> + +4.0.0 + +org.apache.nifi +nifi-datadog-bundle +0.6.1 + + +nifi-datadog-reporting-task +Publishes NiFi metrics to datadog + + + +org.glassfish.jersey.core +jersey-client + + +org.glassfish +javax.json +1.0.4 + + +javax.json +javax.json-api +1.0 + + +com.yammer.metrics +metrics-core + + +org.apache.nifi +nifi-api + + +org.apache.nifi +nifi-processor-utils + + +org.apache.nifi +nifi-utils + + + +org.apache.nifi +nifi-mock +test + + +org.mockito +mockito-all +test + + +io.dropwizard.metrics +metrics-core +3.1.0 + + +org.coursera +metrics-datadog +1.1.5 + + +com.google.guava +guava +19.0 + --- End diff -- Not all of them are "test". Will fix it. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #655: DataDog support added
Github user Ramizjon commented on a diff in the pull request:
https://github.com/apache/nifi/pull/655#discussion_r71120757
--- Diff:
nifi-nar-bundles/nifi-datadog-bundle/nifi-datadog-reporting-task/src/main/java/org/apache/nifi/reporting/datadog/DDMetricRegistryBuilder.java
---
@@ -0,0 +1,71 @@
+package org.apache.nifi.reporting.datadog;
+
+import com.codahale.metrics.MetricRegistry;
+import org.apache.commons.lang3.RandomStringUtils;
+import org.coursera.metrics.datadog.DatadogReporter;
+import org.coursera.metrics.datadog.transport.UdpTransport;
+
+import java.io.IOException;
+import java.net.InetAddress;
+import java.util.Arrays;
+import java.util.List;
+import java.util.concurrent.TimeUnit;
+
+/**
+ * Class configures MetricRegistry (passed outside or created from
scratch) with Datadog support
+ */
+public class DDMetricRegistryBuilder {
+
+private long interval = 10;
+
+private MetricRegistry metricRegistry = null;
+
+private String name = null;
+
+private List tags = Arrays.asList();
+
+public DDMetricRegistryBuilder setInterval(long interval) {
+this.interval = interval;
+return this;
+}
+
+public DDMetricRegistryBuilder setMetricRegistry(MetricRegistry
metricRegistry) {
+this.metricRegistry = metricRegistry;
+return this;
+}
+
+public DDMetricRegistryBuilder setName(String name) {
+this.name = name;
+return this;
+}
+
+public DDMetricRegistryBuilder setTags(List tags) {
+this.tags = tags;
+return this;
+}
+
+public MetricRegistry build() throws IOException {
+if(metricRegistry == null)
+metricRegistry = new MetricRegistry();
+
+if(name==null) {
+name = RandomStringUtils.randomAlphanumeric(8);
+}
+DatadogReporter datadogReporter =
createDatadogReporter(this.metricRegistry);
+datadogReporter.start(this.interval, TimeUnit.SECONDS);
+
+return this.metricRegistry;
+}
+
+//create DataDog reporter
+private DatadogReporter createDatadogReporter(MetricRegistry
metricRegistry) throws IOException {
+UdpTransport udpTransport = new UdpTransport.Builder().build();
+DatadogReporter reporter =
+DatadogReporter.forRegistry(metricRegistry)
+.withHost(InetAddress.getLocalHost().getHostName())
--- End diff --
It's a predefined tag that is called "host". Again, we report metrics to
DataDog agent, that is installed locally, and it reports these metrics to
DataDog
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi pull request #655: DataDog support added
Github user Ramizjon commented on a diff in the pull request:
https://github.com/apache/nifi/pull/655#discussion_r71120786
--- Diff:
nifi-nar-bundles/nifi-datadog-bundle/nifi-datadog-reporting-task/src/main/java/org/apache/nifi/reporting/datadog/DataDogReportingTask.java
---
@@ -0,0 +1,185 @@
+package org.apache.nifi.reporting.datadog;
+
+
+import com.codahale.metrics.Gauge;
+import com.codahale.metrics.MetricRegistry;
+import com.google.common.base.Optional;
+import com.google.common.util.concurrent.AtomicDouble;
+import com.yammer.metrics.core.VirtualMachineMetrics;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.controller.status.ProcessGroupStatus;
+import org.apache.nifi.controller.status.ProcessorStatus;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.reporting.AbstractReportingTask;
+import org.apache.nifi.reporting.ReportingContext;
+import org.apache.nifi.reporting.datadog.metrics.MetricsService;
+import org.coursera.metrics.datadog.DynamicTagsCallback;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import java.util.Map;
+import java.util.concurrent.ConcurrentHashMap;
+
+@Tags({"reporting", "datadog", "metrics"})
+@CapabilityDescription("Publishes metrics from NiFi to datadog")
+public class DataDogReportingTask extends AbstractReportingTask {
+
+//the amount of time between polls
+static final PropertyDescriptor REPORTING_PERIOD = new
PropertyDescriptor.Builder()
+.name("DataDog reporting period")
+.description("The amount of time in seconds between polls")
+.required(true)
+.expressionLanguageSupported(false)
+.defaultValue("10")
+.addValidator(StandardValidators.LONG_VALIDATOR)
+.build();
+
+static final PropertyDescriptor METRICS_PREFIX = new
PropertyDescriptor.Builder()
+.name("Metrics prefix")
+.description("Prefix to be added before every metric")
+.required(true)
+.expressionLanguageSupported(false)
+.defaultValue("nifi")
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.build();
+
+static final PropertyDescriptor ENVIRONMENT = new
PropertyDescriptor.Builder()
+.name("Environment")
+.description("Environment, dataflow is running in. " +
+"This property will be included as metrics tag.")
+.required(true)
+.expressionLanguageSupported(false)
+.defaultValue("dev")
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.build();
+
+private MetricsService metricsService;
+private DDMetricRegistryBuilder ddMetricRegistryBuilder;
+private MetricRegistry metricRegistry;
+private String metricsPrefix;
+private String environment;
+private String statusId;
+private ConcurrentHashMap metricsMap;
+private volatile VirtualMachineMetrics virtualMachineMetrics;
+private Logger logger = LoggerFactory.getLogger(getClass().getName());
--- End diff --
Ok, will fix that.
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi pull request #655: DataDog support added
Github user Ramizjon commented on a diff in the pull request:
https://github.com/apache/nifi/pull/655#discussion_r71120811
--- Diff:
nifi-nar-bundles/nifi-datadog-bundle/nifi-datadog-reporting-task/src/main/java/org/apache/nifi/reporting/datadog/DataDogReportingTask.java
---
@@ -0,0 +1,185 @@
+package org.apache.nifi.reporting.datadog;
+
+
+import com.codahale.metrics.Gauge;
+import com.codahale.metrics.MetricRegistry;
+import com.google.common.base.Optional;
+import com.google.common.util.concurrent.AtomicDouble;
+import com.yammer.metrics.core.VirtualMachineMetrics;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.controller.ConfigurationContext;
+import org.apache.nifi.controller.status.ProcessGroupStatus;
+import org.apache.nifi.controller.status.ProcessorStatus;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.reporting.AbstractReportingTask;
+import org.apache.nifi.reporting.ReportingContext;
+import org.apache.nifi.reporting.datadog.metrics.MetricsService;
+import org.coursera.metrics.datadog.DynamicTagsCallback;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.List;
+import java.util.Map;
+import java.util.concurrent.ConcurrentHashMap;
+
+@Tags({"reporting", "datadog", "metrics"})
+@CapabilityDescription("Publishes metrics from NiFi to datadog")
+public class DataDogReportingTask extends AbstractReportingTask {
+
+//the amount of time between polls
+static final PropertyDescriptor REPORTING_PERIOD = new
PropertyDescriptor.Builder()
+.name("DataDog reporting period")
+.description("The amount of time in seconds between polls")
+.required(true)
+.expressionLanguageSupported(false)
+.defaultValue("10")
+.addValidator(StandardValidators.LONG_VALIDATOR)
+.build();
+
+static final PropertyDescriptor METRICS_PREFIX = new
PropertyDescriptor.Builder()
+.name("Metrics prefix")
+.description("Prefix to be added before every metric")
+.required(true)
+.expressionLanguageSupported(false)
+.defaultValue("nifi")
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.build();
+
+static final PropertyDescriptor ENVIRONMENT = new
PropertyDescriptor.Builder()
+.name("Environment")
+.description("Environment, dataflow is running in. " +
+"This property will be included as metrics tag.")
+.required(true)
+.expressionLanguageSupported(false)
+.defaultValue("dev")
+.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
+.build();
+
+private MetricsService metricsService;
+private DDMetricRegistryBuilder ddMetricRegistryBuilder;
+private MetricRegistry metricRegistry;
+private String metricsPrefix;
+private String environment;
+private String statusId;
+private ConcurrentHashMap metricsMap;
+private volatile VirtualMachineMetrics virtualMachineMetrics;
+private Logger logger = LoggerFactory.getLogger(getClass().getName());
+
+@OnScheduled
+public void setup(final ConfigurationContext context) throws
IOException {
+metricsService = getMetricsService();
+ddMetricRegistryBuilder = getMetricRegistryBuilder();
+metricRegistry = getMetricRegistry();
+metricsMap = getMetricsMap();
+metricsPrefix = METRICS_PREFIX.getDefaultValue();
+environment = ENVIRONMENT.getDefaultValue();
+virtualMachineMetrics = VirtualMachineMetrics.getInstance();
+ddMetricRegistryBuilder.setMetricRegistry(metricRegistry)
+.setName("nifi_metrics")
+.setTags(Arrays.asList("env", "dataflow_id"))
+.build();
+}
+
+@Override
+protected List getSupportedPropertyDescriptors() {
+final List properties = new ArrayList<>();
+properties.add(REPORTING_PERIOD);
+properties.add(METRICS_PREFIX);
+properties.add(ENVIRONMENT);
+return properties;
+}
+
+@Override
+public void onTrigger(ReportingContext context) {
+final ProcessGroupStatus status =
context.getEventAccess().getControllerStatus();
[jira] [Commented] (NIFI-2282) Purge history not working
[ https://issues.apache.org/jira/browse/NIFI-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382133#comment-15382133 ] Rob Moran commented on NIFI-2282: - [~mcgilman] I probably misinterpreted the 'End date' field – it is working for me now. Would like to confirm with [~andrewmlim] as well as he was having similar issues. > Purge history not working > - > > Key: NIFI-2282 > URL: https://issues.apache.org/jira/browse/NIFI-2282 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Rob Moran > > Tried to purge config history from Flow Configuration History shell. The > purge operation is captured and displayed in the table, but previous > operations are not removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2300) Purge history
Rob Moran created NIFI-2300: --- Summary: Purge history Key: NIFI-2300 URL: https://issues.apache.org/jira/browse/NIFI-2300 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Rob Moran Priority: Minor Selecting an 'End' date/time when purging history is not very intuitive. I propose giving the user an option to select a range of time (e.g., From: – To:). I think this would be more clear and provide a little more control over the history being purged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2282) Purge history not working
[ https://issues.apache.org/jira/browse/NIFI-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382161#comment-15382161 ] Rob Moran commented on NIFI-2282: - Just want to add that I created NIFI-2300 in response to this :) > Purge history not working > - > > Key: NIFI-2282 > URL: https://issues.apache.org/jira/browse/NIFI-2282 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Rob Moran > > Tried to purge config history from Flow Configuration History shell. The > purge operation is captured and displayed in the table, but previous > operations are not removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2300) Improve Purge History interaction (add From/To range)
[ https://issues.apache.org/jira/browse/NIFI-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2300: Summary: Improve Purge History interaction (add From/To range) (was: Purge history) > Improve Purge History interaction (add From/To range) > - > > Key: NIFI-2300 > URL: https://issues.apache.org/jira/browse/NIFI-2300 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Rob Moran >Priority: Minor > > Selecting an 'End' date/time when purging history is not very intuitive. I > propose giving the user an option to select a range of time (e.g., > From: – To:). I think this would be more clear and > provide a little more control over the history being purged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2095) Introduce UI for managing Users & User Groups
[ https://issues.apache.org/jira/browse/NIFI-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2095. --- Resolution: Fixed > Introduce UI for managing Users & User Groups > - > > Key: NIFI-2095 > URL: https://issues.apache.org/jira/browse/NIFI-2095 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Blocker > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2301) Remove policy when component is deleted
Matt Gilman created NIFI-2301: - Summary: Remove policy when component is deleted Key: NIFI-2301 URL: https://issues.apache.org/jira/browse/NIFI-2301 Project: Apache NiFi Issue Type: Sub-task Components: Core Framework Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 1.0.0 When a component is removed, we need to also remove any associated policies. Otherwise, the policies will continue to grow unboundedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2272) Policies: The view/modify drop-down should not be displayed for the "access the user interface" policy
[ https://issues.apache.org/jira/browse/NIFI-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382214#comment-15382214 ] ASF GitHub Bot commented on NIFI-2272: -- GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/666 Fixing issues loading the Policy Management UI NIFI-2272: - Ensuring the appropriate visibility of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mcgilman/nifi NIFI-2272 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/666.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #666 commit a0ab95a8478ec98e50f18b857c5fd8ae09c55867 Author: Matt Gilman Date: 2016-07-18T12:35:00Z NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > Policies: The view/modify drop-down should not be displayed for the "access > the user interface" policy > --- > > Key: NIFI-2272 > URL: https://issues.apache.org/jira/browse/NIFI-2272 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Matt Gilman > Labels: UI > Attachments: NIFI-2272_viewModify.png > > > I reloaded my NiFi instance and selected "Policies" from the control > drop-down menu. As shown in the attached screenshot, for the "access the > user interface" policy, the view/modify drop-down is available. > If you switch to another policy like "query provenance" which correctly > doesn't have the view/modify drop-down, then if you go back to "access the > user interface" policy the view/modify drop-down is now gone. The UI is also > corrected if you close the Access Policies window and then open it again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #666: Fixing issues loading the Policy Management UI
GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/666 Fixing issues loading the Policy Management UI NIFI-2272: - Ensuring the appropriate visibility of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mcgilman/nifi NIFI-2272 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/666.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #666 commit a0ab95a8478ec98e50f18b857c5fd8ae09c55867 Author: Matt Gilman Date: 2016-07-18T12:35:00Z NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #665: NIFI-2289: Directly ask ZooKeeper which node is cluster coo...
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/665 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'
[ https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382216#comment-15382216 ] ASF GitHub Bot commented on NIFI-2289: -- Github user bbende commented on the issue: https://github.com/apache/nifi/pull/665 Reviewing... > Cluster sometimes gets into state where it always says 'no Cluster > Coordinator elected' > --- > > Key: NIFI-2289 > URL: https://issues.apache.org/jira/browse/NIFI-2289 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > Fix For: 1.0.0 > > > When running in clustered mode, occasionally NiFi will get into a state where > it indicates for each request that no cluster coordinator exists, even though > one is clearly elected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2302) Add note to History to indicate it represents only the current Node
Matt Gilman created NIFI-2302: - Summary: Add note to History to indicate it represents only the current Node Key: NIFI-2302 URL: https://issues.apache.org/jira/browse/NIFI-2302 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2298) Add missing futures for ConsumeKafka
[
https://issues.apache.org/jira/browse/NIFI-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Zhurakousky reassigned NIFI-2298:
--
Assignee: Oleg Zhurakousky
> Add missing futures for ConsumeKafka
>
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
> Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor is missing some capabilities that were
> present in old getKafka processor.
> 1. New ConsumeKafka is not writing critical Kafka attributes i.e.,
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes.
> Old getKafka processor:
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
> {quote}
>
> New ConsumeKafka processor :
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x .
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10
> version.
> 3. Support subscribing to multiple topics i.e., topic: topic1,topic2
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-2298) Add missing futures for ConsumeKafka
[
https://issues.apache.org/jira/browse/NIFI-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Zhurakousky updated NIFI-2298:
---
Fix Version/s: 1.0.0
> Add missing futures for ConsumeKafka
>
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
> Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor is missing some capabilities that were
> present in old getKafka processor.
> 1. New ConsumeKafka is not writing critical Kafka attributes i.e.,
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes.
> Old getKafka processor:
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
> {quote}
>
> New ConsumeKafka processor :
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x .
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10
> version.
> 3. Support subscribing to multiple topics i.e., topic: topic1,topic2
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-2298) Add missing futures for ConsumeKafka
[
https://issues.apache.org/jira/browse/NIFI-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Zhurakousky updated NIFI-2298:
---
Issue Type: Improvement (was: Bug)
> Add missing futures for ConsumeKafka
>
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
> Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor is missing some capabilities that were
> present in old getKafka processor.
> 1. New ConsumeKafka is not writing critical Kafka attributes i.e.,
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes.
> Old getKafka processor:
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
> {quote}
>
> New ConsumeKafka processor :
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x .
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10
> version.
> 3. Support subscribing to multiple topics i.e., topic: topic1,topic2
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka
[
https://issues.apache.org/jira/browse/NIFI-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382290#comment-15382290
]
Oleg Zhurakousky commented on NIFI-2298:
Sumo
Thanks for raising it. Will be addressed shortly. Also, I have changed this
from Bug to Improvement since this is a new component and was simply missing
features rather then claiming features that did not work which would then
constitute a bug.
> Add missing futures for ConsumeKafka
>
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
> Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor is missing some capabilities that were
> present in old getKafka processor.
> 1. New ConsumeKafka is not writing critical Kafka attributes i.e.,
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes.
> Old getKafka processor:
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
> {quote}
>
> New ConsumeKafka processor :
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x .
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10
> version.
> 3. Support subscribing to multiple topics i.e., topic: topic1,topic2
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'
[ https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382334#comment-15382334 ] ASF GitHub Bot commented on NIFI-2289: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/665 > Cluster sometimes gets into state where it always says 'no Cluster > Coordinator elected' > --- > > Key: NIFI-2289 > URL: https://issues.apache.org/jira/browse/NIFI-2289 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > Fix For: 1.0.0 > > > When running in clustered mode, occasionally NiFi will get into a state where > it indicates for each request that no cluster coordinator exists, even though > one is clearly elected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #665: NIFI-2289: Directly ask ZooKeeper which node is clus...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/665 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'
[ https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382333#comment-15382333 ] ASF subversion and git services commented on NIFI-2289: --- Commit 5c8636edf4bd8ee32892440794e9b40bd009abb6 in nifi's branch refs/heads/master from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5c8636e ] NIFI-2289: Directly ask ZooKeeper which node is cluster coordinator and add watches on the ZNode rather than relying on Node Status Updates over the cluster protocol because cluster protocol may get the events out-of-order This closes #665. Signed-off-by: Bryan Bende > Cluster sometimes gets into state where it always says 'no Cluster > Coordinator elected' > --- > > Key: NIFI-2289 > URL: https://issues.apache.org/jira/browse/NIFI-2289 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > Fix For: 1.0.0 > > > When running in clustered mode, occasionally NiFi will get into a state where > it indicates for each request that no cluster coordinator exists, even though > one is clearly elected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2289) Cluster sometimes gets into state where it always says 'no Cluster Coordinator elected'
[ https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-2289: -- Resolution: Fixed Status: Resolved (was: Patch Available) Looks good, merged to master. > Cluster sometimes gets into state where it always says 'no Cluster > Coordinator elected' > --- > > Key: NIFI-2289 > URL: https://issues.apache.org/jira/browse/NIFI-2289 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > Fix For: 1.0.0 > > > When running in clustered mode, occasionally NiFi will get into a state where > it indicates for each request that no cluster coordinator exists, even though > one is clearly elected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #502: Nifi-1972 Apache Ignite Put Cache Processor
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/502 Hey @mans2singh, no other comments. Just those couple comments regarding the notice/license and the logging, and it looks like they were addressed. I'll defer to @pvillard31 to finish the review. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-2303) Update lineage styles
Rob Moran created NIFI-2303: --- Summary: Update lineage styles Key: NIFI-2303 URL: https://issues.apache.org/jira/browse/NIFI-2303 Project: Apache NiFi Issue Type: Sub-task Affects Versions: 1.0.0 Reporter: Rob Moran Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2303) Update lineage styles
[ https://issues.apache.org/jira/browse/NIFI-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382352#comment-15382352 ] Rob Moran commented on NIFI-2303: - I'm making a list of basic changes; will add to issue description > Update lineage styles > - > > Key: NIFI-2303 > URL: https://issues.apache.org/jira/browse/NIFI-2303 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2304) Cluster Coordinator reported incorrectly
Bryan Bende created NIFI-2304: - Summary: Cluster Coordinator reported incorrectly Key: NIFI-2304 URL: https://issues.apache.org/jira/browse/NIFI-2304 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.0.0 Reporter: Bryan Bende Assignee: Mark Payne Priority: Minor Fix For: 1.0.0 I created a two node cluster locally, running embedded ZK on node1.. both nodes start up, but when trying to access the UI on the second node, it says no coordinator exists. Looking in the logs the coordinator is being reported as ":8889" where 8889 is the node protocol port. I left the node host blank assuming it would default to localhost, but looks like it isn't. When I filled in the node host everything worked as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #642: NIFI-2156: Add ListDatabaseTables processor
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/642 Alright, after giving it some time and a cup of coffee I realize how off I was at first, lol. This processor reaches out to the DB asking for the tables. Then for each table that isn't already stored in state it creates a flowfile. If the processor is configured to give the count, it needs to send a SQL query asking for it. If that query fails it will remove the flowfile it created and continue onto the next table. If successful, the FQN of the table will then be added to state (after queuing it to transfer). That realization makes my comment about data loss void (was afraid it would get stored in state after un-successfully getting the count). One new comment, would a user want to set an expiration for tables in state? That way they could get updates on the count of a table every X seconds/minutes. In it's current form it will get the table once but never again. You're already storing the timestamp as the value so it should be an easy addition. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2156) Add ListDatabaseTables processor
[ https://issues.apache.org/jira/browse/NIFI-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382368#comment-15382368 ] ASF GitHub Bot commented on NIFI-2156: -- Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/642 Alright, after giving it some time and a cup of coffee I realize how off I was at first, lol. This processor reaches out to the DB asking for the tables. Then for each table that isn't already stored in state it creates a flowfile. If the processor is configured to give the count, it needs to send a SQL query asking for it. If that query fails it will remove the flowfile it created and continue onto the next table. If successful, the FQN of the table will then be added to state (after queuing it to transfer). That realization makes my comment about data loss void (was afraid it would get stored in state after un-successfully getting the count). One new comment, would a user want to set an expiration for tables in state? That way they could get updates on the count of a table every X seconds/minutes. In it's current form it will get the table once but never again. You're already storing the timestamp as the value so it should be an easy addition. > Add ListDatabaseTables processor > > > Key: NIFI-2156 > URL: https://issues.apache.org/jira/browse/NIFI-2156 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess > Fix For: 1.0.0 > > > This processor would use a DatabaseConnectionPool controller service, call > getTables(), and if the (optional, defaulting-to-false) property "Include Row > Count" is set, then a "SELECT COUNT(1) from table" would be issued to the > database. The table catalog, schema, name, type, remarks (and its count if > specified) will be included as attributes in a zero-content flow file. > It will also use State Management to only list tables once. If new tables are > added (and the processor is running), then the new tables' flow files will be > generated. Changing any property that could affect the list of returned > tables (such as the DB Connection, catalog, schema pattern, table name > pattern, or table types) will reset the state and all tables will be fetched > using the new criteria. The state can also be manually cleared using the > standard Clear State link on the View State dialog (available on the > processor's context menu) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster
[ https://issues.apache.org/jira/browse/NIFI-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382389#comment-15382389 ] ASF GitHub Bot commented on NIFI-2305: -- GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/667 NIFI-2305: Do not run processors that are marked as Primary Node Only… … if disconnected from cluster You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-2305 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/667.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #667 commit c333950665adcf7197a5bb6acd54b1f6ef8f599e Author: Mark Payne Date: 2016-07-18T14:50:39Z NIFI-2305: Do not run processors that are marked as Primary Node Only if disconnected from cluster > Nodes run "Primary Node Only" processors when disconnected from cluster > --- > > Key: NIFI-2305 > URL: https://issues.apache.org/jira/browse/NIFI-2305 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.0.0 > > > Nodes that get disconnected from the cluster start running processors that > are considered 'primary node only' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #667: NIFI-2305: Do not run processors that are marked as ...
GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/667 NIFI-2305: Do not run processors that are marked as Primary Node Only⦠⦠if disconnected from cluster You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-2305 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/667.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #667 commit c333950665adcf7197a5bb6acd54b1f6ef8f599e Author: Mark Payne Date: 2016-07-18T14:50:39Z NIFI-2305: Do not run processors that are marked as Primary Node Only if disconnected from cluster --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #655: DataDog support added
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/655 @Ramizjon, the gauges make sense but the last part, "DropWizard framework gets metric values from that structure with specified period of time", doesn't. It seems (looking at this line of code[1]) that the "start" method of the DatadogReporter is causing the reporting with a specified period of time. If you just used one of the "report"[2] methods every onTrigger call you would achieve what I am suggesting. Installing an agent may be very simple, I don't like the idea of requiring a user to install something on the box in order to work (the person configuring the flow may not have access to install locally). I would very much prefer go the extra mile to make this work without an agent locally. You mention that it's the "best way", this means you're able to report without having an agent locally? [1] https://github.com/apache/nifi/pull/655/files#diff-3f6f231dd20c75c7f8830cc0fd156770R55 [2] https://github.com/coursera/metrics-datadog/blob/master/metrics-datadog/src/main/java/org/coursera/metrics/datadog/DatadogReporter.java#L71 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2269) DataDog support added
[ https://issues.apache.org/jira/browse/NIFI-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-2269: --- Status: Patch Available (was: Open) PR posted here: https://github.com/apache/nifi/pull/655 > DataDog support added > - > > Key: NIFI-2269 > URL: https://issues.apache.org/jira/browse/NIFI-2269 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Ramiz Abadulla > Labels: datadog, metrics, nifi, reporting > > Added reporting task, that reports NiFi flow and JVM metrics to DataDog > service. It also reports data to DataDog from every processor. All metrics > are represented as Gauges. The name of each metric for processors has > following format: “nifi..”. In order to use this module, you need to have > DataDog agent installed on your machine. You can configure time period to > send metrics to DataDog by changing “DataDog reporting period” property when > adding reporting task in NiFi UI. > Attached link to corresponding pull request on GitHub. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster
Mark Payne created NIFI-2305: Summary: Nodes run "Primary Node Only" processors when disconnected from cluster Key: NIFI-2305 URL: https://issues.apache.org/jira/browse/NIFI-2305 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Priority: Blocker Fix For: 1.0.0 Nodes that get disconnected from the cluster start running processors that are considered 'primary node only' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #655: DataDog support added
Github user Ramizjon commented on the issue: https://github.com/apache/nifi/pull/655 @JPercivall Yes, i've already did it in the way you recommend, by calling report() method every onTrigger() call. DataDog agent is very commonly used approach of sending metrics to DataDog. Firstly, it goes about aggregation. It is used to aggregate many data points from different sources (not only from NiFi) and send them. So if user is using DataDog for a lot of purposes it's obvious that it is more efficient to use such unified module as agent. Secondly, it works much faster than direct approach, because of accepting custom application metrics points over UDP. The application wonât stop its actual work to wait for a response from the metrics server, which is very important if the metrics server is down or inaccessible. Thirdly, DataDog provides single-line install commands for every OS, so it is absolutely painless. However i suggest to add direct approach as additional feature, for users that don't want to install an Agent. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2303) Update lineage styles
[ https://issues.apache.org/jira/browse/NIFI-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2303: Description: * Selected event: #ba554a / rgb(186, 85, 74) * Other events: #aabbc3 / rgb(170,187,195) * Data provence icon: change to icon-provenance; color:#ad9897 / rgb(173, 152, 151); change background/fill color to white (#fff / rgb(255, 255, 255) * Event type label: change font to Roboto, font-size to 11px * Path link "selected" strokes: change color to #ba554a / rgb(186, 85, 74) * Close icon: use fa-long-arrow-left; change tooltip to "Go back to event list" * Download icon: use fa-file-image-o; change tooltip to "Save image of lineage" * Update timestamp (below timeline slider control) to 13px Roboto Medium #775351 * Update slider to angular material slider? If necessary, the current style is okay for now > Update lineage styles > - > > Key: NIFI-2303 > URL: https://issues.apache.org/jira/browse/NIFI-2303 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Minor > > * Selected event: #ba554a / rgb(186, 85, 74) > * Other events: #aabbc3 / rgb(170,187,195) > * Data provence icon: change to icon-provenance; color:#ad9897 / rgb(173, > 152, 151); change background/fill color to white (#fff / rgb(255, 255, 255) > * Event type label: change font to Roboto, font-size to 11px > * Path link "selected" strokes: change color to #ba554a / rgb(186, 85, 74) > * Close icon: use fa-long-arrow-left; change tooltip to "Go back to event > list" > * Download icon: use fa-file-image-o; change tooltip to "Save image of > lineage" > * Update timestamp (below timeline slider control) to 13px Roboto Medium > #775351 > * Update slider to angular material slider? If necessary, the current style > is okay for now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2305) Nodes run "Primary Node Only" processors when disconnected from cluster
[ https://issues.apache.org/jira/browse/NIFI-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2305: - Fix Version/s: 0.8.0 > Nodes run "Primary Node Only" processors when disconnected from cluster > --- > > Key: NIFI-2305 > URL: https://issues.apache.org/jira/browse/NIFI-2305 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.0.0, 0.8.0 > > > Nodes that get disconnected from the cluster start running processors that > are considered 'primary node only' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2303) Update lineage styles
[ https://issues.apache.org/jira/browse/NIFI-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2303: Description: * Selected event: #ba554a / rgb(186, 85, 74) * Other events: #aabbc3 / rgb(170,187,195) * Data provence icon: change to icon-provenance; color:#ad9897 / rgb(173, 152, 151); change background/fill color to white (#fff / rgb(255, 255, 255) * Event type label: change font to Roboto, font-size to 11px * Path link "selected" strokes: change color to #ba554a / rgb(186, 85, 74) * Close icon: use fa-long-arrow-left; change tooltip to "Go back to event list" * Download icon: use fa-file-image-o; change tooltip to "Save image of lineage" * Update timestamp (below timeline slider control) to 13px Roboto Medium #775351 * Update slider to angular material slider? If necessary, the current style is okay for now was: * Selected event: #ba554a / rgb(186, 85, 74) * Other events: #aabbc3 / rgb(170,187,195) * Data provence icon: change to icon-provenance; color:#ad9897 / rgb(173, 152, 151); change background/fill color to white (#fff / rgb(255, 255, 255) * Event type label: change font to Roboto, font-size to 11px * Path link "selected" strokes: change color to #ba554a / rgb(186, 85, 74) * Close icon: use fa-long-arrow-left; change tooltip to "Go back to event list" * Download icon: use fa-file-image-o; change tooltip to "Save image of lineage" * Update timestamp (below timeline slider control) to 13px Roboto Medium #775351 * Update slider to angular material slider? If necessary, the current style is okay for now > Update lineage styles > - > > Key: NIFI-2303 > URL: https://issues.apache.org/jira/browse/NIFI-2303 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Minor > > * Selected event: #ba554a / rgb(186, 85, 74) > * Other events: #aabbc3 / rgb(170,187,195) > * Data provence icon: change to icon-provenance; color:#ad9897 / rgb(173, > 152, 151); change background/fill color to white (#fff / rgb(255, 255, 255) > * Event type label: change font to Roboto, font-size to 11px > * Path link "selected" strokes: change color to #ba554a / rgb(186, 85, 74) > * Close icon: use fa-long-arrow-left; change tooltip to "Go back to event > list" > * Download icon: use fa-file-image-o; change tooltip to "Save image of > lineage" > * Update timestamp (below timeline slider control) to 13px Roboto Medium > #775351 > * Update slider to angular material slider? If necessary, the current style > is okay for now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2306) Node gets UUID for processor that's different from rest of the cluster
Joseph Percivall created NIFI-2306: -- Summary: Node gets UUID for processor that's different from rest of the cluster Key: NIFI-2306 URL: https://issues.apache.org/jira/browse/NIFI-2306 Project: Apache NiFi Issue Type: Bug Reporter: Joseph Percivall Priority: Blocker Fix For: 1.0.0 I was running a secure 3 node cluster using embedded ZK instances and ran into a problem where one of the three nodes got out of sync with the rest of the cluster. Specifically I had 2 processors in the flow and one of the processors had a UUID of "01551000-3843-1ea3-0001-48be045b" one node but "01551000-3843-1ea3-0002-48be045b" (0001 vs 0002). This of course caused weird problems with the node being out of sync when the framework assumed it couldn't be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #655: DataDog support added
Github user Ramizjon commented on the issue: https://github.com/apache/nifi/pull/655 @JPercivall However, if you strongly recommend using direct approach, i can implement it. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #655: DataDog support added
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/655 @Ramizjon if there are signifiant improvements to do the local agent vs direct, I would suggest making it configurable. That way the user can use the Reporting task without needs access to the box but also make the option available for the users that need the extra performance. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #655: DataDog support added
Github user Ramizjon commented on the issue: https://github.com/apache/nifi/pull/655 @JPercivall totally agree with you. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-1992) Update Site-to-Site Client to support Zero-Master Clustering Paradigm
[ https://issues.apache.org/jira/browse/NIFI-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-1992: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update Site-to-Site Client to support Zero-Master Clustering Paradigm > - > > Key: NIFI-1992 > URL: https://issues.apache.org/jira/browse/NIFI-1992 > Project: Apache NiFi > Issue Type: Task > Components: Core Framework, Tools and Build >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2303) Update lineage styles
[ https://issues.apache.org/jira/browse/NIFI-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2303: Priority: Major (was: Minor) > Update lineage styles > - > > Key: NIFI-2303 > URL: https://issues.apache.org/jira/browse/NIFI-2303 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran > > * Selected event: #ba554a / rgb(186, 85, 74) > * Other events: #aabbc3 / rgb(170,187,195) > * Data provence icon: change to icon-provenance; color:#ad9897 / rgb(173, > 152, 151); change background/fill color to white (#fff / rgb(255, 255, 255) > * Event type label: change font to Roboto, font-size to 11px > * Path link "selected" strokes: change color to #ba554a / rgb(186, 85, 74) > * Close icon: use fa-long-arrow-left; change tooltip to "Go back to event > list" > * Download icon: use fa-file-image-o; change tooltip to "Save image of > lineage" > * Update timestamp (below timeline slider control) to 13px Roboto Medium > #775351 > * Update slider to angular material slider? If necessary, the current style > is okay for now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-929) Ability to generate a 'true' pid file
[ https://issues.apache.org/jira/browse/NIFI-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende reassigned NIFI-929: Assignee: Bryan Bende > Ability to generate a 'true' pid file > - > > Key: NIFI-929 > URL: https://issues.apache.org/jira/browse/NIFI-929 > Project: Apache NiFi > Issue Type: Improvement > Components: Configuration >Affects Versions: 0.3.0 >Reporter: Ali Bajwa >Assignee: Bryan Bende >Priority: Minor > > The nifi pid file does not seem to be a true pid file (it has other info as > well). > For integration with monitoring tools like Ambari it would be nice to have a > true pid file (containing only the pid) created as well (in line with other > Hadoop components). This is coming from the Ambari service I put together: I > had to parse out the pid from Nifi pidfile and maintain another one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-929) Ability to generate a 'true' pid file
[ https://issues.apache.org/jira/browse/NIFI-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382660#comment-15382660 ] Bryan Bende commented on NIFI-929: -- I think I have something working for approach A... will submit shortly. > Ability to generate a 'true' pid file > - > > Key: NIFI-929 > URL: https://issues.apache.org/jira/browse/NIFI-929 > Project: Apache NiFi > Issue Type: Improvement > Components: Configuration >Affects Versions: 0.3.0 >Reporter: Ali Bajwa >Assignee: Bryan Bende >Priority: Minor > > The nifi pid file does not seem to be a true pid file (it has other info as > well). > For integration with monitoring tools like Ambari it would be nice to have a > true pid file (containing only the pid) created as well (in line with other > Hadoop components). This is coming from the Ambari service I put together: I > had to parse out the pid from Nifi pidfile and maintain another one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #668: NIFI-929 Changing RunNiFi to write just the pid to n...
GitHub user bbende opened a pull request: https://github.com/apache/nifi/pull/668 NIFI-929 Changing RunNiFi to write just the pid to nifi.pid and the f⦠â¦ull status to nifi.status You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbende/nifi NIFI-929 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/668.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #668 commit f809e2b517d3e70b168fc43b5800e3f7be7d4ab9 Author: Bryan Bende Date: 2016-07-18T17:30:15Z NIFI-929 Changing RunNiFi to write just the pid to nifi.pid and the full status to nifi.status --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-929) Ability to generate a 'true' pid file
[ https://issues.apache.org/jira/browse/NIFI-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382685#comment-15382685 ] ASF GitHub Bot commented on NIFI-929: - GitHub user bbende opened a pull request: https://github.com/apache/nifi/pull/668 NIFI-929 Changing RunNiFi to write just the pid to nifi.pid and the f… …ull status to nifi.status You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbende/nifi NIFI-929 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/668.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #668 commit f809e2b517d3e70b168fc43b5800e3f7be7d4ab9 Author: Bryan Bende Date: 2016-07-18T17:30:15Z NIFI-929 Changing RunNiFi to write just the pid to nifi.pid and the full status to nifi.status > Ability to generate a 'true' pid file > - > > Key: NIFI-929 > URL: https://issues.apache.org/jira/browse/NIFI-929 > Project: Apache NiFi > Issue Type: Improvement > Components: Configuration >Affects Versions: 0.3.0 >Reporter: Ali Bajwa >Assignee: Bryan Bende >Priority: Minor > > The nifi pid file does not seem to be a true pid file (it has other info as > well). > For integration with monitoring tools like Ambari it would be nice to have a > true pid file (containing only the pid) created as well (in line with other > Hadoop components). This is coming from the Ambari service I put together: I > had to parse out the pid from Nifi pidfile and maintain another one -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #565: NIFI-2090 Add support for HL7 segment names and comp...
Github user jfrazee closed the pull request at: https://github.com/apache/nifi/pull/565 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #565: NIFI-2090 Add support for HL7 segment names and components ...
Github user jfrazee commented on the issue: https://github.com/apache/nifi/pull/565 Closing to resubmit against master. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2090) Add support for HL7 segment names and components in ExtractHL7Attributes
[ https://issues.apache.org/jira/browse/NIFI-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382699#comment-15382699 ] ASF GitHub Bot commented on NIFI-2090: -- Github user jfrazee closed the pull request at: https://github.com/apache/nifi/pull/565 > Add support for HL7 segment names and components in ExtractHL7Attributes > > > Key: NIFI-2090 > URL: https://issues.apache.org/jira/browse/NIFI-2090 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Joseph Witt >Priority: Minor > Fix For: 1.0.0 > > > HL7 segments and components (segment fields) have descriptive names, e.g., > MSH.12 is Version ID and PID.5 is Patient Name. ExtractHL7Attributes should > support using these names in addition to the numeric identifiers. > Some HL7 segment fields are also "composite" and have sub-elements of their > own (separated by ^). For example, PID.5 is the Patient Name, which is > sub-divided into family name, given name, etc. It would be nice to have > access to the individual components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2090) Add support for HL7 segment names and components in ExtractHL7Attributes
[ https://issues.apache.org/jira/browse/NIFI-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382698#comment-15382698 ] ASF GitHub Bot commented on NIFI-2090: -- Github user jfrazee commented on the issue: https://github.com/apache/nifi/pull/565 Closing to resubmit against master. > Add support for HL7 segment names and components in ExtractHL7Attributes > > > Key: NIFI-2090 > URL: https://issues.apache.org/jira/browse/NIFI-2090 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Joseph Witt >Priority: Minor > Fix For: 1.0.0 > > > HL7 segments and components (segment fields) have descriptive names, e.g., > MSH.12 is Version ID and PID.5 is Patient Name. ExtractHL7Attributes should > support using these names in addition to the numeric identifiers. > Some HL7 segment fields are also "composite" and have sub-elements of their > own (separated by ^). For example, PID.5 is the Patient Name, which is > sub-divided into family name, given name, etc. It would be nice to have > access to the individual components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #642: NIFI-2156: Add ListDatabaseTables processor
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/642 Yes, at one point I had a "Refresh Interval" property but I think that was in another branch, will restore it. Also, currently any change to properties will reset the state (since the tables fetched may have changed), I'm thinking of taking that part out. The Refresh Interval would cause all tables to be re-fetched, and/or the user could always manually clear state. What do you think? --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2156) Add ListDatabaseTables processor
[ https://issues.apache.org/jira/browse/NIFI-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382703#comment-15382703 ] ASF GitHub Bot commented on NIFI-2156: -- Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/642 Yes, at one point I had a "Refresh Interval" property but I think that was in another branch, will restore it. Also, currently any change to properties will reset the state (since the tables fetched may have changed), I'm thinking of taking that part out. The Refresh Interval would cause all tables to be re-fetched, and/or the user could always manually clear state. What do you think? > Add ListDatabaseTables processor > > > Key: NIFI-2156 > URL: https://issues.apache.org/jira/browse/NIFI-2156 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess > Fix For: 1.0.0 > > > This processor would use a DatabaseConnectionPool controller service, call > getTables(), and if the (optional, defaulting-to-false) property "Include Row > Count" is set, then a "SELECT COUNT(1) from table" would be issued to the > database. The table catalog, schema, name, type, remarks (and its count if > specified) will be included as attributes in a zero-content flow file. > It will also use State Management to only list tables once. If new tables are > added (and the processor is running), then the new tables' flow files will be > generated. Changing any property that could affect the list of returned > tables (such as the DB Connection, catalog, schema pattern, table name > pattern, or table types) will reset the state and all tables will be fetched > using the new criteria. The state can also be manually cleared using the > standard Clear State link on the View State dialog (available on the > processor's context menu) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #669: NIFI-2090 Add support for HL7 segment names and comp...
GitHub user jfrazee opened a pull request: https://github.com/apache/nifi/pull/669 NIFI-2090 Add support for HL7 segment names and components in ExtractHL7Attributes Note that this doesn't apply the "friendly" names to for composite field types and those are still produced with numeric indexes (e.g., PID.PatientIDInternalID.CX.1). While that's super useful, the only way to get at that with the underlying HAPI library is via reflection, so it will require a separate commit with more extensive testing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jfrazee/nifi NIFI-2090 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/669.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #669 commit 0dc6a278a851334db734363e47165b49df5e9410 Author: Joey Frazee Date: 2016-06-23T04:44:40Z Added options for segment names, parse fields in ExtractHL7Attributes commit 717bd6c09234d609e004de48015d043dbf6ef977 Author: Joey Frazee Date: 2016-06-23T05:04:25Z Fix mislabeled parse-segment-fields property displayName --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2090) Add support for HL7 segment names and components in ExtractHL7Attributes
[ https://issues.apache.org/jira/browse/NIFI-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382704#comment-15382704 ] ASF GitHub Bot commented on NIFI-2090: -- GitHub user jfrazee opened a pull request: https://github.com/apache/nifi/pull/669 NIFI-2090 Add support for HL7 segment names and components in ExtractHL7Attributes Note that this doesn't apply the "friendly" names to for composite field types and those are still produced with numeric indexes (e.g., PID.PatientIDInternalID.CX.1). While that's super useful, the only way to get at that with the underlying HAPI library is via reflection, so it will require a separate commit with more extensive testing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jfrazee/nifi NIFI-2090 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/669.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #669 commit 0dc6a278a851334db734363e47165b49df5e9410 Author: Joey Frazee Date: 2016-06-23T04:44:40Z Added options for segment names, parse fields in ExtractHL7Attributes commit 717bd6c09234d609e004de48015d043dbf6ef977 Author: Joey Frazee Date: 2016-06-23T05:04:25Z Fix mislabeled parse-segment-fields property displayName > Add support for HL7 segment names and components in ExtractHL7Attributes > > > Key: NIFI-2090 > URL: https://issues.apache.org/jira/browse/NIFI-2090 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joey Frazee >Assignee: Joseph Witt >Priority: Minor > Fix For: 1.0.0 > > > HL7 segments and components (segment fields) have descriptive names, e.g., > MSH.12 is Version ID and PID.5 is Patient Name. ExtractHL7Attributes should > support using these names in addition to the numeric identifiers. > Some HL7 segment fields are also "composite" and have sub-elements of their > own (separated by ^). For example, PID.5 is the Patient Name, which is > sub-divided into family name, given name, etc. It would be nice to have > access to the individual components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2283) Audit actions against Users/Groups/Policies
[ https://issues.apache.org/jira/browse/NIFI-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382849#comment-15382849 ] ASF subversion and git services commented on NIFI-2283: --- Commit aa91032cde8ad1cf2caf18fc0f02b5f678e1f3a7 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa91032 ] NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > Audit actions against Users/Groups/Policies > --- > > Key: NIFI-2283 > URL: https://issues.apache.org/jira/browse/NIFI-2283 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Priority: Blocker > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2239) Need 'help' tool-tips in Access Policies dialog
[ https://issues.apache.org/jira/browse/NIFI-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382848#comment-15382848 ] ASF subversion and git services commented on NIFI-2239: --- Commit aa91032cde8ad1cf2caf18fc0f02b5f678e1f3a7 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa91032 ] NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > Need 'help' tool-tips in Access Policies dialog > --- > > Key: NIFI-2239 > URL: https://issues.apache.org/jira/browse/NIFI-2239 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Mark Payne >Assignee: Matt Gilman > Fix For: 1.0.0 > > > When a user navigates to the Access Policies dialog, there are a lot of > different access policies, and it may not always be clear what each of the > access policies means, as the names are kept fairly short. It would be > valuable to have a 'help' icon that provides more information about what each > of the access policies means. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2272) Policies: The view/modify drop-down should not be displayed for the "access the user interface" policy
[ https://issues.apache.org/jira/browse/NIFI-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382846#comment-15382846 ] ASF subversion and git services commented on NIFI-2272: --- Commit aa91032cde8ad1cf2caf18fc0f02b5f678e1f3a7 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa91032 ] NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > Policies: The view/modify drop-down should not be displayed for the "access > the user interface" policy > --- > > Key: NIFI-2272 > URL: https://issues.apache.org/jira/browse/NIFI-2272 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Matt Gilman > Labels: UI > Attachments: NIFI-2272_viewModify.png > > > I reloaded my NiFi instance and selected "Policies" from the control > drop-down menu. As shown in the attached screenshot, for the "access the > user interface" policy, the view/modify drop-down is available. > If you switch to another policy like "query provenance" which correctly > doesn't have the view/modify drop-down, then if you go back to "access the > user interface" policy the view/modify drop-down is now gone. The UI is also > corrected if you close the Access Policies window and then open it again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2273) Policies: Get an "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." error trying to access the policies of a comp
[ https://issues.apache.org/jira/browse/NIFI-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382847#comment-15382847 ] ASF subversion and git services commented on NIFI-2273: --- Commit aa91032cde8ad1cf2caf18fc0f02b5f678e1f3a7 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa91032 ] NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > Policies: Get an "Unable to perform the desired action due to insufficient > permissions. Contact the system administrator." error trying to access the > policies of a component > -- > > Key: NIFI-2273 > URL: https://issues.apache.org/jira/browse/NIFI-2273 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2273_componentError.png > > > User does not have a policy to view a processor. However, when the processor > is selected and "Policies" is selected from the Operator palette, an error > box is displayed with the following message: > Unable to perform the desired action due to insufficient permissions. Contact > the system administrator. > The Policies window should still be displayed/accessible for the user to be > able to make policy changes. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2301) Remove policy when component is deleted
[ https://issues.apache.org/jira/browse/NIFI-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382853#comment-15382853 ] ASF subversion and git services commented on NIFI-2301: --- Commit aa91032cde8ad1cf2caf18fc0f02b5f678e1f3a7 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa91032 ] NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > Remove policy when component is deleted > --- > > Key: NIFI-2301 > URL: https://issues.apache.org/jira/browse/NIFI-2301 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > When a component is removed, we need to also remove any associated policies. > Otherwise, the policies will continue to grow unboundedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2263) History in a Cluster
[ https://issues.apache.org/jira/browse/NIFI-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382850#comment-15382850 ] ASF subversion and git services commented on NIFI-2263: --- Commit aa91032cde8ad1cf2caf18fc0f02b5f678e1f3a7 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa91032 ] NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > History in a Cluster > > > Key: NIFI-2263 > URL: https://issues.apache.org/jira/browse/NIFI-2263 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Blocker > Fix For: 1.0.0 > > > Each node in a cluster records it's own independent history of configuration > actions. Based on how these actions are audited it's not possible to > guarantee the same identifiers for each action on each node. As a result, we > will simply return the history for the node that is currently loaded in the > browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #666: Fixing issues loading the Policy Management UI
Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/666 LGTM. The verbage for the access policies is definitely better imho. +1. Merged to master. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2096) Can't upload template using Firefox
[ https://issues.apache.org/jira/browse/NIFI-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382852#comment-15382852 ] ASF subversion and git services commented on NIFI-2096: --- Commit aa91032cde8ad1cf2caf18fc0f02b5f678e1f3a7 in nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=aa91032 ] NIFI-2272: - Ensuring the appropriate visibilty of the action in the policy management page. NIFI-2273: - Ensuring we load the policy or inform the user of the appropriate permissions of the effective policy. NIFI-2239: - Providing help tooltips for the policies in the management page. NIFI-2283: - Adding auditing for access policies, users, and groups. NIFI-2263: - Not replicating history requests throughout the cluster. NIFI-2096: - Fixing upload template file input in Firefox. NIFI-2301: - Removing relevant policies after component deletion. > Can't upload template using Firefox > --- > > Key: NIFI-2096 > URL: https://issues.apache.org/jira/browse/NIFI-2096 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Moran >Assignee: Matt Gilman >Priority: Blocker > > Tried in FF 40.0.2 and 47 > From the Templates shell, clicking the + icon does not trigger the system > prompt to choose a file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2272) Policies: The view/modify drop-down should not be displayed for the "access the user interface" policy
[ https://issues.apache.org/jira/browse/NIFI-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2272. --- Resolution: Fixed > Policies: The view/modify drop-down should not be displayed for the "access > the user interface" policy > --- > > Key: NIFI-2272 > URL: https://issues.apache.org/jira/browse/NIFI-2272 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Assignee: Matt Gilman > Labels: UI > Attachments: NIFI-2272_viewModify.png > > > I reloaded my NiFi instance and selected "Policies" from the control > drop-down menu. As shown in the attached screenshot, for the "access the > user interface" policy, the view/modify drop-down is available. > If you switch to another policy like "query provenance" which correctly > doesn't have the view/modify drop-down, then if you go back to "access the > user interface" policy the view/modify drop-down is now gone. The UI is also > corrected if you close the Access Policies window and then open it again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi-minifi-cpp issue #4: MINIFI-6: Basic C++ implementation for MiNiFi
Github user apiri commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/4 Reviewing and testing. Will leave comments as they arise. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (NIFI-2273) Policies: Get an "Unable to perform the desired action due to insufficient permissions. Contact the system administrator." error trying to access the policies of a compo
[ https://issues.apache.org/jira/browse/NIFI-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2273. --- Resolution: Fixed > Policies: Get an "Unable to perform the desired action due to insufficient > permissions. Contact the system administrator." error trying to access the > policies of a component > -- > > Key: NIFI-2273 > URL: https://issues.apache.org/jira/browse/NIFI-2273 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim > Labels: UI > Attachments: NIFI-2273_componentError.png > > > User does not have a policy to view a processor. However, when the processor > is selected and "Policies" is selected from the Operator palette, an error > box is displayed with the following message: > Unable to perform the desired action due to insufficient permissions. Contact > the system administrator. > The Policies window should still be displayed/accessible for the user to be > able to make policy changes. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2283) Audit actions against Users/Groups/Policies
[ https://issues.apache.org/jira/browse/NIFI-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2283. --- Resolution: Fixed Assignee: Matt Gilman > Audit actions against Users/Groups/Policies > --- > > Key: NIFI-2283 > URL: https://issues.apache.org/jira/browse/NIFI-2283 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Blocker > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2239) Need 'help' tool-tips in Access Policies dialog
[ https://issues.apache.org/jira/browse/NIFI-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2239. --- Resolution: Fixed > Need 'help' tool-tips in Access Policies dialog > --- > > Key: NIFI-2239 > URL: https://issues.apache.org/jira/browse/NIFI-2239 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Mark Payne >Assignee: Matt Gilman > Fix For: 1.0.0 > > > When a user navigates to the Access Policies dialog, there are a lot of > different access policies, and it may not always be clear what each of the > access policies means, as the names are kept fairly short. It would be > valuable to have a 'help' icon that provides more information about what each > of the access policies means. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2263) History in a Cluster
[ https://issues.apache.org/jira/browse/NIFI-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2263. --- Resolution: Fixed > History in a Cluster > > > Key: NIFI-2263 > URL: https://issues.apache.org/jira/browse/NIFI-2263 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Blocker > Fix For: 1.0.0 > > > Each node in a cluster records it's own independent history of configuration > actions. Based on how these actions are audited it's not possible to > guarantee the same identifiers for each action on each node. As a result, we > will simply return the history for the node that is currently loaded in the > browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #670: Fixes NIFI-2163 LSB Adherence.
GitHub user PuspenduBanerjee opened a pull request: https://github.com/apache/nifi/pull/670 Fixes NIFI-2163 LSB Adherence. Fixes https://issues.apache.org/jira/browse/NIFI-2163 You can merge this pull request into a Git repository by running: $ git pull https://github.com/PuspenduBanerjee/nifi NIFI-2163 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/670.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #670 commit 3dd06ba0cb081602d6ee54ee39cf3d83373675dd Author: puspendu.baner...@gmail.com Date: 2016-07-18T19:18:56Z Fixes NIFI-2163 LSB Adherence. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (NIFI-2301) Remove policy when component is deleted
[ https://issues.apache.org/jira/browse/NIFI-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2301. --- Resolution: Fixed > Remove policy when component is deleted > --- > > Key: NIFI-2301 > URL: https://issues.apache.org/jira/browse/NIFI-2301 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > When a component is removed, we need to also remove any associated policies. > Otherwise, the policies will continue to grow unboundedly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2163) Nifi Service does not follow LSB Sevice Spec
[ https://issues.apache.org/jira/browse/NIFI-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382888#comment-15382888 ] ASF GitHub Bot commented on NIFI-2163: -- GitHub user PuspenduBanerjee opened a pull request: https://github.com/apache/nifi/pull/670 Fixes NIFI-2163 LSB Adherence. Fixes https://issues.apache.org/jira/browse/NIFI-2163 You can merge this pull request into a Git repository by running: $ git pull https://github.com/PuspenduBanerjee/nifi NIFI-2163 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/670.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #670 commit 3dd06ba0cb081602d6ee54ee39cf3d83373675dd Author: puspendu.baner...@gmail.com Date: 2016-07-18T19:18:56Z Fixes NIFI-2163 LSB Adherence. > Nifi Service does not follow LSB Sevice Spec > > > Key: NIFI-2163 > URL: https://issues.apache.org/jira/browse/NIFI-2163 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.7.0 > Environment: Centos >Reporter: Edgardo Vega >Assignee: Puspendu Banerjee >Priority: Critical > > Trying to use the lastest off master with nifi.sh and nifi-env.sh and they do > not follow the spec for services, whcih causes some configuration tools not > to work as they use the return codes to determine if things are running, > dead, or stopped. > http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2096) Can't upload template using Firefox
[ https://issues.apache.org/jira/browse/NIFI-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2096. --- Resolution: Fixed > Can't upload template using Firefox > --- > > Key: NIFI-2096 > URL: https://issues.apache.org/jira/browse/NIFI-2096 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Moran >Assignee: Matt Gilman >Priority: Blocker > > Tried in FF 40.0.2 and 47 > From the Templates shell, clicking the + icon does not trigger the system > prompt to choose a file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #671: NIFI-826 (part duex)
GitHub user olegz opened a pull request: https://github.com/apache/nifi/pull/671 NIFI-826 (part duex) - fixed clustering issues discovered after NIFI-826 was applied You can merge this pull request into a Git repository by running: $ git pull https://github.com/olegz/nifi NIFI-826-F Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/671.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #671 commit 04a726d9d37ee9e84a91947d181428346876ec0d Author: Oleg Zhurakousky Date: 2016-07-18T19:22:54Z NIFI-826 (part duex) - fixed clustering issues discovered after NIFI-826 was applied --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2163) Nifi Service does not follow LSB Sevice Spec
[ https://issues.apache.org/jira/browse/NIFI-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puspendu Banerjee updated NIFI-2163: Labels: platform-consistency (was: ) Fix Version/s: 1.0.0 Affects Version/s: 1.0.0 Status: Patch Available (was: In Progress) > Nifi Service does not follow LSB Sevice Spec > > > Key: NIFI-2163 > URL: https://issues.apache.org/jira/browse/NIFI-2163 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.7.0, 1.0.0 > Environment: Centos >Reporter: Edgardo Vega >Assignee: Puspendu Banerjee >Priority: Critical > Labels: platform-consistency > Fix For: 1.0.0 > > > Trying to use the lastest off master with nifi.sh and nifi-env.sh and they do > not follow the spec for services, whcih causes some configuration tools not > to work as they use the return codes to determine if things are running, > dead, or stopped. > http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-826) Export templates in a deterministic way
[ https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382895#comment-15382895 ] ASF GitHub Bot commented on NIFI-826: - GitHub user olegz opened a pull request: https://github.com/apache/nifi/pull/671 NIFI-826 (part duex) - fixed clustering issues discovered after NIFI-826 was applied You can merge this pull request into a Git repository by running: $ git pull https://github.com/olegz/nifi NIFI-826-F Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/671.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #671 commit 04a726d9d37ee9e84a91947d181428346876ec0d Author: Oleg Zhurakousky Date: 2016-07-18T19:22:54Z NIFI-826 (part duex) - fixed clustering issues discovered after NIFI-826 was applied > Export templates in a deterministic way > --- > > Key: NIFI-826 > URL: https://issues.apache.org/jira/browse/NIFI-826 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Oleg Zhurakousky > Fix For: 1.0.0 > > > Templates should be exported in a deterministic way so that they can be > compared or diff'ed with another. Items to consider... > - The ordering of components > - The id's used to identify the components > - Consider excluding irrelevant items. When components are imported some > settings are ignored (run state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2163) Nifi Service does not follow LSB Sevice Spec
[ https://issues.apache.org/jira/browse/NIFI-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382901#comment-15382901 ] Puspendu Banerjee commented on NIFI-2163: - [~evega] Please review the patch for status. > Nifi Service does not follow LSB Sevice Spec > > > Key: NIFI-2163 > URL: https://issues.apache.org/jira/browse/NIFI-2163 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 1.0.0, 0.7.0 > Environment: Centos >Reporter: Edgardo Vega >Assignee: Puspendu Banerjee >Priority: Critical > Labels: platform-consistency > Fix For: 1.0.0 > > > Trying to use the lastest off master with nifi.sh and nifi-env.sh and they do > not follow the spec for services, whcih causes some configuration tools not > to work as they use the return codes to determine if things are running, > dead, or stopped. > http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2211) Update zero-master-node.png
[ https://issues.apache.org/jira/browse/NIFI-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2211: Attachment: (was: zero-master-node.png) > Update zero-master-node.png > --- > > Key: NIFI-2211 > URL: https://issues.apache.org/jira/browse/NIFI-2211 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation & Website >Reporter: Rob Moran > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2212) Update zero-master-cluster.png
[ https://issues.apache.org/jira/browse/NIFI-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2212: Attachment: zero-master-cluster.png > Update zero-master-cluster.png > -- > > Key: NIFI-2212 > URL: https://issues.apache.org/jira/browse/NIFI-2212 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation & Website >Reporter: Rob Moran > Attachments: zero-master-cluster.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2211) Update zero-master-node.png
[ https://issues.apache.org/jira/browse/NIFI-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2211: Attachment: zero-master-node.png > Update zero-master-node.png > --- > > Key: NIFI-2211 > URL: https://issues.apache.org/jira/browse/NIFI-2211 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation & Website >Reporter: Rob Moran > Attachments: zero-master-node.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #671: NIFI-826 (part deux)
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/671#discussion_r71214452
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/util/SnippetUtils.java
---
@@ -565,13 +567,15 @@ private void updateControllerServiceIdentifiers(final
ProcessorConfigDTO configD
/**
* Generates a new id for the current id that is specified. If no seed
is found, a new random id will be created.
*/
-private String generateId(final String currentId, final String seed) {
+private String generateId(final String currentId, final String seed,
boolean isCopy) {
long msb = UUID.fromString(currentId).getMostSignificantBits();
-long lsb = StringUtils.isBlank(seed)
+int lsb = StringUtils.isBlank(seed)
? Math.abs(new Random().nextInt())
-:
Math.abs(ByteBuffer.wrap(seed.getBytes(StandardCharsets.UTF_8)).getInt());
+: Math.abs(seed.hashCode());
-return new UUID(msb, lsb).toString();
+return isCopy ? TypeOneUUIDGenerator.generateId(msb,
lsb).toString() : new UUID(msb, lsb).toString();
+// return TypeOneUUIDGenerator.generateId(msb, lsb).toString();
--- End diff --
Should be able to remove this now
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Commented] (NIFI-826) Export templates in a deterministic way
[
https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382923#comment-15382923
]
ASF GitHub Bot commented on NIFI-826:
-
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/671#discussion_r71214452
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/util/SnippetUtils.java
---
@@ -565,13 +567,15 @@ private void updateControllerServiceIdentifiers(final
ProcessorConfigDTO configD
/**
* Generates a new id for the current id that is specified. If no seed
is found, a new random id will be created.
*/
-private String generateId(final String currentId, final String seed) {
+private String generateId(final String currentId, final String seed,
boolean isCopy) {
long msb = UUID.fromString(currentId).getMostSignificantBits();
-long lsb = StringUtils.isBlank(seed)
+int lsb = StringUtils.isBlank(seed)
? Math.abs(new Random().nextInt())
-:
Math.abs(ByteBuffer.wrap(seed.getBytes(StandardCharsets.UTF_8)).getInt());
+: Math.abs(seed.hashCode());
-return new UUID(msb, lsb).toString();
+return isCopy ? TypeOneUUIDGenerator.generateId(msb,
lsb).toString() : new UUID(msb, lsb).toString();
+// return TypeOneUUIDGenerator.generateId(msb, lsb).toString();
--- End diff --
Should be able to remove this now
> Export templates in a deterministic way
> ---
>
> Key: NIFI-826
> URL: https://issues.apache.org/jira/browse/NIFI-826
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Oleg Zhurakousky
> Fix For: 1.0.0
>
>
> Templates should be exported in a deterministic way so that they can be
> compared or diff'ed with another. Items to consider...
> - The ordering of components
> - The id's used to identify the components
> - Consider excluding irrelevant items. When components are imported some
> settings are ignored (run state).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (NIFI-2308) Create zero-master-cluster-http-access.png
Rob Moran created NIFI-2308: --- Summary: Create zero-master-cluster-http-access.png Key: NIFI-2308 URL: https://issues.apache.org/jira/browse/NIFI-2308 Project: Apache NiFi Issue Type: Sub-task Reporter: Rob Moran -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2307) Ensure the Connection Configuration and Details Dialog Open
Matt Gilman created NIFI-2307: - Summary: Ensure the Connection Configuration and Details Dialog Open Key: NIFI-2307 URL: https://issues.apache.org/jira/browse/NIFI-2307 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Priority: Blocker Fix For: 1.0.0 The connection dialogs show details about the source and destination components. These need to be loaded/scrubbed according to the permissions of those components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2265) Authorization: Able to see hidden processor information in Status History
[ https://issues.apache.org/jira/browse/NIFI-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2265: -- Priority: Blocker (was: Major) > Authorization: Able to see hidden processor information in Status History > - > > Key: NIFI-2265 > URL: https://issues.apache.org/jira/browse/NIFI-2265 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Blocker > Labels: UI > Attachments: NIFI-2265_Summary.png, NIFI-2265_statusHistory.png > > > When a user is not privileged to see a processor, on the canvas the Name and > Type of the Processor is properly hidden. But if you right-click on the > processor and select "Stats", this information is displayed in the Status > History. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2265) Authorization: Able to see hidden processor information in Status History
[ https://issues.apache.org/jira/browse/NIFI-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2265: -- Fix Version/s: 1.0.0 > Authorization: Able to see hidden processor information in Status History > - > > Key: NIFI-2265 > URL: https://issues.apache.org/jira/browse/NIFI-2265 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Blocker > Labels: UI > Fix For: 1.0.0 > > Attachments: NIFI-2265_Summary.png, NIFI-2265_statusHistory.png > > > When a user is not privileged to see a processor, on the canvas the Name and > Type of the Processor is properly hidden. But if you right-click on the > processor and select "Stats", this information is displayed in the Status > History. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #671: NIFI-826 (part deux)
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/671 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-826) Export templates in a deterministic way
[ https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382937#comment-15382937 ] ASF subversion and git services commented on NIFI-826: -- Commit f4d2919955ff3cbbd0ce4309f2f18ff295481a01 in nifi's branch refs/heads/master from [~ozhurakousky] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f4d2919 ] NIFI-826 (part deux) - fixed clustering issues discovered after NIFI-826 was applied > Export templates in a deterministic way > --- > > Key: NIFI-826 > URL: https://issues.apache.org/jira/browse/NIFI-826 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Oleg Zhurakousky > Fix For: 1.0.0 > > > Templates should be exported in a deterministic way so that they can be > compared or diff'ed with another. Items to consider... > - The ordering of components > - The id's used to identify the components > - Consider excluding irrelevant items. When components are imported some > settings are ignored (run state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-826) Export templates in a deterministic way
[ https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382939#comment-15382939 ] ASF GitHub Bot commented on NIFI-826: - Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/671 > Export templates in a deterministic way > --- > > Key: NIFI-826 > URL: https://issues.apache.org/jira/browse/NIFI-826 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Oleg Zhurakousky > Fix For: 1.0.0 > > > Templates should be exported in a deterministic way so that they can be > compared or diff'ed with another. Items to consider... > - The ordering of components > - The id's used to identify the components > - Consider excluding irrelevant items. When components are imported some > settings are ignored (run state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-826) Export templates in a deterministic way
[ https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382938#comment-15382938 ] ASF subversion and git services commented on NIFI-826: -- Commit f4d2919955ff3cbbd0ce4309f2f18ff295481a01 in nifi's branch refs/heads/master from [~ozhurakousky] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f4d2919 ] NIFI-826 (part deux) - fixed clustering issues discovered after NIFI-826 was applied > Export templates in a deterministic way > --- > > Key: NIFI-826 > URL: https://issues.apache.org/jira/browse/NIFI-826 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Oleg Zhurakousky > Fix For: 1.0.0 > > > Templates should be exported in a deterministic way so that they can be > compared or diff'ed with another. Items to consider... > - The ordering of components > - The id's used to identify the components > - Consider excluding irrelevant items. When components are imported some > settings are ignored (run state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-826) Export templates in a deterministic way
[ https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382941#comment-15382941 ] ASF GitHub Bot commented on NIFI-826: - Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/671 +1 all looks good. I've pushed to master. Thanks for knocking this out! > Export templates in a deterministic way > --- > > Key: NIFI-826 > URL: https://issues.apache.org/jira/browse/NIFI-826 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Oleg Zhurakousky > Fix For: 1.0.0 > > > Templates should be exported in a deterministic way so that they can be > compared or diff'ed with another. Items to consider... > - The ordering of components > - The id's used to identify the components > - Consider excluding irrelevant items. When components are imported some > settings are ignored (run state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #671: NIFI-826 (part deux)
Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/671 +1 all looks good. I've pushed to master. Thanks for knocking this out! --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2265) Authorization: Able to see hidden processor information in Status History
[ https://issues.apache.org/jira/browse/NIFI-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382935#comment-15382935 ] Matt Gilman commented on NIFI-2265: --- This also applies to the Connection source/destination in the Summary table. > Authorization: Able to see hidden processor information in Status History > - > > Key: NIFI-2265 > URL: https://issues.apache.org/jira/browse/NIFI-2265 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Andrew Lim >Priority: Blocker > Labels: UI > Fix For: 1.0.0 > > Attachments: NIFI-2265_Summary.png, NIFI-2265_statusHistory.png > > > When a user is not privileged to see a processor, on the canvas the Name and > Type of the Processor is properly hidden. But if you right-click on the > processor and select "Stats", this information is displayed in the Status > History. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ApacheCon: Getting the word out internally
ApacheCon: Getting the word out internally Dear Apache Enthusiast, As you are no doubt already aware, we will be holding ApacheCon in Seville, Spain, the week of November 14th, 2016. The call for papers (CFP) for this event is now open, and will remain open until September 9th. The event is divided into two parts, each with its own CFP. The first part of the event, called Apache Big Data, focuses on Big Data projects and related technologies. Website: http://events.linuxfoundation.org/events/apache-big-data-europe CFP: http://events.linuxfoundation.org/events/apache-big-data-europe/program/cfp The second part, called ApacheCon Europe, focuses on the Apache Software Foundation as a whole, covering all projects, community issues, governance, and so on. Website: http://events.linuxfoundation.org/events/apachecon-europe CFP: http://events.linuxfoundation.org/events/apachecon-europe/program/cfp ApacheCon is the official conference of the Apache Software Foundation, and is the best place to meet members of your project and other ASF projects, and strengthen your project's community. If your organization is interested in sponsoring ApacheCon, contact Rich Bowen at e...@apache.org ApacheCon is a great place to find the brightest developers in the world, and experts on a huge range of technologies. I hope to see you in Seville! == Melissaon behalf of the ApacheCon Team
[jira] [Updated] (NIFI-2308) Create zero-master-cluster-http-access.png
[ https://issues.apache.org/jira/browse/NIFI-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-2308: Attachment: zero-master-cluster-http-access.png > Create zero-master-cluster-http-access.png > -- > > Key: NIFI-2308 > URL: https://issues.apache.org/jira/browse/NIFI-2308 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation & Website >Reporter: Rob Moran > Attachments: zero-master-cluster-http-access.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #502: Nifi-1972 Apache Ignite Put Cache Processor
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/502#discussion_r71220449
--- Diff:
nifi-nar-bundles/nifi-ignite-bundle/nifi-ignite-processors/src/main/java/org/apache/nifi/processors/ignite/cache/PutIgniteCache.java
---
@@ -0,0 +1,392 @@
+/*
+ * 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.
+ */
+package org.apache.nifi.processors.ignite.cache;
+
+import java.io.IOException;
+import java.io.InputStream;
+import java.util.AbstractMap;
+import java.util.ArrayList;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+
+import org.apache.commons.lang3.StringUtils;
+import org.apache.ignite.IgniteDataStreamer;
+import org.apache.ignite.lang.IgniteFuture;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.annotation.lifecycle.OnStopped;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.expression.AttributeExpression.ResultType;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.io.InputStreamCallback;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.stream.io.StreamUtils;
+
+/**
+ * Put cache processors which pushes the flow file content into Ignite
Cache using
+ * DataStreamer interface
+ */
+@EventDriven
+@SupportsBatching
+@Tags({ "Ignite", "insert", "update", "stream", "write", "put", "cache",
"key" })
+@InputRequirement(Requirement.INPUT_REQUIRED)
+@CapabilityDescription("Stream the contents of a FlowFile to Ignite Cache
using DataStreamer. " +
+"The processor uses the value of FlowFile attribute (Ignite cache
entry key) as the " +
+"cache key and the byte array of the FlowFile as the value of the
cache entry value. Both the string key and a " +
+" non-empty byte array value are required otherwise the FlowFile is
transfered to the failure relation. " +
+"Note - The Ignite Kernel periodically outputs node perforance
statistics to the logs. This message " +
+" can be turned off by setting the log level for logger
'org.apache.ignite' to WARN.")
--- End diff --
typo: "performance"
also I'd say "... to WARN in logback.xml configuration file."
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Commented] (NIFI-2282) Purge history not working
[ https://issues.apache.org/jira/browse/NIFI-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382967#comment-15382967 ] Andrew Lim commented on NIFI-2282: -- I was having issues to even get the Purge History window to open, but that was in an older build. Using a more recent build, I can confirm that Purge History is working as expected so this bug can be closed out. > Purge history not working > - > > Key: NIFI-2282 > URL: https://issues.apache.org/jira/browse/NIFI-2282 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Rob Moran > > Tried to purge config history from Flow Configuration History shell. The > purge operation is captured and displayed in the table, but previous > operations are not removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
