[jira] [Commented] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[ https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236280#comment-15236280 ] ASF subversion and git services commented on NIFI-1748: --- Commit 5e0476c364fe0ffcdb8a6598558217a8c4c4aaca in nifi's branch refs/heads/0.x from [~ozhurakousky] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5e0476c ] NIFI-1748 removed un-used test data This closes #344. Signed-off-by: Joe Skora > Remove potentially copyrighted text from KafkaPublisherTest > --- > > Key: NIFI-1748 > URL: https://issues.apache.org/jira/browse/NIFI-1748 > Project: Apache NiFi > Issue Type: Task >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Trivial > Fix For: 1.0.0, 0.7.0, 0.6.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
nifi git commit: NIFI-1748 removed un-used test data
Repository: nifi
Updated Branches:
refs/heads/0.x bfa8e2bd6 -> 5e0476c36
NIFI-1748 removed un-used test data
This closes #344.
Signed-off-by: Joe Skora
Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/5e0476c3
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/5e0476c3
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/5e0476c3
Branch: refs/heads/0.x
Commit: 5e0476c364fe0ffcdb8a6598558217a8c4c4aaca
Parents: bfa8e2b
Author: Oleg Zhurakousky
Authored: Sat Apr 9 17:24:37 2016 -0400
Committer: Joe Skora
Committed: Mon Apr 11 20:00:57 2016 -0400
--
.../processors/kafka/KafkaPublisherTest.java| 44
1 file changed, 7 insertions(+), 37 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/nifi/blob/5e0476c3/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
--
diff --git
a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
index 3e582a6..46507d2 100644
---
a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
+++
b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
@@ -43,13 +43,6 @@ import kafka.javaapi.consumer.ConsumerConnector;
public class KafkaPublisherTest {
-private static final String sampleData = "The true sign of intelligence is
not knowledge but imagination.\n"
-+ "It's not that I'm so smart, it's just that I stay with problems
longer.\n"
-+ "The only source of knowledge is experience.\n"
-+ "Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former.\n";
-
-private static final String sampleData2 = "foo|bar|baz";
-
private static EmbeddedKafka kafkaLocal;
private static EmbeddedKafkaProducerHelper producerHelper;
@@ -69,7 +62,7 @@ public class KafkaPublisherTest {
@Test
public void validateSuccessfulSendAsWhole() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData.getBytes(StandardCharsets.UTF_8));
+InputStream fis = new ByteArrayInputStream("Hello
Kafka".getBytes(StandardCharsets.UTF_8));
String topicName = "validateSuccessfulSendAsWhole";
Properties kafkaProperties = this.buildProducerProperties();
@@ -93,7 +86,8 @@ public class KafkaPublisherTest {
@Test
public void validateSuccessfulSendAsDelimited() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData.getBytes(StandardCharsets.UTF_8));
+InputStream fis = new ByteArrayInputStream(
+"Hello Kafka 1\nHello Kafka 2\nHello Kafka 3\nHello Kafka
4\n".getBytes(StandardCharsets.UTF_8));
String topicName = "validateSuccessfulSendAsDelimited";
Properties kafkaProperties = this.buildProducerProperties();
@@ -118,33 +112,9 @@ public class KafkaPublisherTest {
}
@Test
-public void validateSuccessfulSendAsDelimited2() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData2.getBytes(StandardCharsets.UTF_8));
-String topicName = "validateSuccessfulSendAsDelimited2";
-
-Properties kafkaProperties = this.buildProducerProperties();
-KafkaPublisher publisher = new KafkaPublisher(kafkaProperties);
-
-SplittableMessageContext messageContext = new
SplittableMessageContext(topicName, null, "|".getBytes(StandardCharsets.UTF_8));
-
-publisher.publish(messageContext, fis, null, 2000);
-publisher.close();
-
-ConsumerIterator iter = this.buildConsumer(topicName);
-assertNotNull(iter.next());
-assertNotNull(iter.next());
-assertNotNull(iter.next());
-try {
-iter.next();
-fail();
-} catch (ConsumerTimeoutException e) {
-// that's OK since this is the Kafka mechanism to unblock
-}
-}
-
-@Test
public void validateSuccessfulReSendOfFailedSegments() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData.getBytes(StandardCharsets.UTF_8));
+InputStream fis = new ByteArrayInputStream(
+"Hello Kafka 1\nHello Kafka 2\nHello Kafka 3\nHello Kafka
4\n".getBytes(StandardCharsets.UTF_8));
String topicName = "validateSuccessfulReSendOfFailedSegments";
Properties kafkaProperties = this.buildProducerProperties();
@@ -160,8
[jira] [Commented] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[ https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236277#comment-15236277 ] ASF GitHub Bot commented on NIFI-1748: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/344 > Remove potentially copyrighted text from KafkaPublisherTest > --- > > Key: NIFI-1748 > URL: https://issues.apache.org/jira/browse/NIFI-1748 > Project: Apache NiFi > Issue Type: Task >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Trivial > Fix For: 1.0.0, 0.7.0, 0.6.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[ https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236276#comment-15236276 ] ASF subversion and git services commented on NIFI-1748: --- Commit bd1f0a82aedb6939a74a6d9428e623d8ff83b863 in nifi's branch refs/heads/master from [~ozhurakousky] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=bd1f0a8 ] NIFI-1748 removed un-used test data This closes #344. Signed-off-by: Joe Skora > Remove potentially copyrighted text from KafkaPublisherTest > --- > > Key: NIFI-1748 > URL: https://issues.apache.org/jira/browse/NIFI-1748 > Project: Apache NiFi > Issue Type: Task >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Trivial > Fix For: 1.0.0, 0.7.0, 0.6.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
nifi git commit: NIFI-1748 removed un-used test data
Repository: nifi
Updated Branches:
refs/heads/master e76a75c26 -> bd1f0a82a
NIFI-1748 removed un-used test data
This closes #344.
Signed-off-by: Joe Skora
Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/bd1f0a82
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/bd1f0a82
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/bd1f0a82
Branch: refs/heads/master
Commit: bd1f0a82aedb6939a74a6d9428e623d8ff83b863
Parents: e76a75c
Author: Oleg Zhurakousky
Authored: Sat Apr 9 17:24:37 2016 -0400
Committer: Joe Skora
Committed: Mon Apr 11 19:50:22 2016 -0400
--
.../processors/kafka/KafkaPublisherTest.java| 44
1 file changed, 7 insertions(+), 37 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/nifi/blob/bd1f0a82/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
--
diff --git
a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
index 3e582a6..46507d2 100644
---
a/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
+++
b/nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
@@ -43,13 +43,6 @@ import kafka.javaapi.consumer.ConsumerConnector;
public class KafkaPublisherTest {
-private static final String sampleData = "The true sign of intelligence is
not knowledge but imagination.\n"
-+ "It's not that I'm so smart, it's just that I stay with problems
longer.\n"
-+ "The only source of knowledge is experience.\n"
-+ "Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former.\n";
-
-private static final String sampleData2 = "foo|bar|baz";
-
private static EmbeddedKafka kafkaLocal;
private static EmbeddedKafkaProducerHelper producerHelper;
@@ -69,7 +62,7 @@ public class KafkaPublisherTest {
@Test
public void validateSuccessfulSendAsWhole() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData.getBytes(StandardCharsets.UTF_8));
+InputStream fis = new ByteArrayInputStream("Hello
Kafka".getBytes(StandardCharsets.UTF_8));
String topicName = "validateSuccessfulSendAsWhole";
Properties kafkaProperties = this.buildProducerProperties();
@@ -93,7 +86,8 @@ public class KafkaPublisherTest {
@Test
public void validateSuccessfulSendAsDelimited() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData.getBytes(StandardCharsets.UTF_8));
+InputStream fis = new ByteArrayInputStream(
+"Hello Kafka 1\nHello Kafka 2\nHello Kafka 3\nHello Kafka
4\n".getBytes(StandardCharsets.UTF_8));
String topicName = "validateSuccessfulSendAsDelimited";
Properties kafkaProperties = this.buildProducerProperties();
@@ -118,33 +112,9 @@ public class KafkaPublisherTest {
}
@Test
-public void validateSuccessfulSendAsDelimited2() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData2.getBytes(StandardCharsets.UTF_8));
-String topicName = "validateSuccessfulSendAsDelimited2";
-
-Properties kafkaProperties = this.buildProducerProperties();
-KafkaPublisher publisher = new KafkaPublisher(kafkaProperties);
-
-SplittableMessageContext messageContext = new
SplittableMessageContext(topicName, null, "|".getBytes(StandardCharsets.UTF_8));
-
-publisher.publish(messageContext, fis, null, 2000);
-publisher.close();
-
-ConsumerIterator iter = this.buildConsumer(topicName);
-assertNotNull(iter.next());
-assertNotNull(iter.next());
-assertNotNull(iter.next());
-try {
-iter.next();
-fail();
-} catch (ConsumerTimeoutException e) {
-// that's OK since this is the Kafka mechanism to unblock
-}
-}
-
-@Test
public void validateSuccessfulReSendOfFailedSegments() throws Exception {
-InputStream fis = new
ByteArrayInputStream(sampleData.getBytes(StandardCharsets.UTF_8));
+InputStream fis = new ByteArrayInputStream(
+"Hello Kafka 1\nHello Kafka 2\nHello Kafka 3\nHello Kafka
4\n".getBytes(StandardCharsets.UTF_8));
String topicName = "validateSuccessfulReSendOfFailedSegments";
Properties kafkaProperties = this.buildProducerProperties();
@@ -
[jira] [Commented] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[ https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236113#comment-15236113 ] ASF GitHub Bot commented on NIFI-1748: -- Github user jskora commented on the pull request: https://github.com/apache/nifi/pull/344#issuecomment-208593602 Reviewing. > Remove potentially copyrighted text from KafkaPublisherTest > --- > > Key: NIFI-1748 > URL: https://issues.apache.org/jira/browse/NIFI-1748 > Project: Apache NiFi > Issue Type: Task >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Trivial > Fix For: 1.0.0, 0.7.0, 0.6.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[
https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236108#comment-15236108
]
ASF GitHub Bot commented on NIFI-1748:
--
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/344#discussion_r59292437
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
---
@@ -124,33 +112,9 @@ public void validateSuccessfulSendAsDelimited() throws
Exception {
}
@Test
-public void validateSuccessfulSendAsDelimited2() throws Exception {
--- End diff --
No, that was actually an addition when we tried to use Scanner from java
that would parse using regex, so need to test for special character, but since
that approach never seen the light of day that test was obsolete from the get
go.
> Remove potentially copyrighted text from KafkaPublisherTest
> ---
>
> Key: NIFI-1748
> URL: https://issues.apache.org/jira/browse/NIFI-1748
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
>Priority: Trivial
> Fix For: 1.0.0, 0.7.0, 0.6.1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[
https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236105#comment-15236105
]
ASF GitHub Bot commented on NIFI-1748:
--
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/344#discussion_r59292187
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/KafkaPublisherTest.java
---
@@ -124,33 +112,9 @@ public void validateSuccessfulSendAsDelimited() throws
Exception {
}
@Test
-public void validateSuccessfulSendAsDelimited2() throws Exception {
--- End diff --
I see this test is just like the previous test, but is anything lost by not
testing with a different delimiter?
> Remove potentially copyrighted text from KafkaPublisherTest
> ---
>
> Key: NIFI-1748
> URL: https://issues.apache.org/jira/browse/NIFI-1748
> Project: Apache NiFi
> Issue Type: Task
>Reporter: Oleg Zhurakousky
>Assignee: Oleg Zhurakousky
>Priority: Trivial
> Fix For: 1.0.0, 0.7.0, 0.6.1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1323) UI visual design enhancement
[ https://issues.apache.org/jira/browse/NIFI-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236087#comment-15236087 ] Joe Skora commented on NIFI-1323: - [~rmoran], very nice work! [~boardm26] was just commenting on how the UI is the killer component of NiFi, other dataflow tools just don't provide the GUI flowgraph definition and management that makes NiFi so easy for the user. I wasn't concerned about changing it at first, but this is starting to grow on me. It is still very clean but seems to add information with sacrificing the excellent usability of the current UI. The one thing I have noticed is that the samples seem large. It may just be scale or that they seems to reflect sizing for a 800px screen, but they look bigger. In spite of my perception, are the processors and configuration dialogs basically the same size as in the current UI? > UI visual design enhancement > > > Key: NIFI-1323 > URL: https://issues.apache.org/jira/browse/NIFI-1323 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Trivial > Attachments: flowfont.zip, nifi-add-processor-dialog.png, > nifi-component-samples.png, > nifi-configure-processor-properties-set-value.png, > nifi-configure-processor-properties.png, > nifi-configure-processor-scheduling.png, > nifi-configure-processor-settings.png, nifi-dialog-samp...@800px.png, > nifi-drop.svg, nifi-global-menu.png, nifi-interaction-and-menu-samples.png, > nifi-lineage-gra...@800px.png, nifi-logo.svg, nifi-sample-fl...@800px.png, > nifi-sample-flow.png, nifi-shell-samp...@800px.png > > > (I will attach mockups and supporting files as they become available) > I am starting to work on a design to modernize the look and feel of the NiFi > UI. The initial focus of the design is to freshen the UI (flat design, SVG > icons, etc.). Additionally, the new design will propose usability > improvements such as exposing more flow-related actions into collapsible > panes, improving hierarchy of information, etc. > Going forward, the design plan is to help lay the foundation for other UI/UX > related issues such as those documented in NIFI-951. > --- > *flowfont.zip* > Contains icon font and supporting files > *nifi-add-processor-dialog.png* > Dialog sample. This sample shows the 'Add Processor' dialog. > *nifi-component-samples.png* > To show styling for all components > *nifi-configure-processor-properties* > *nifi-configure-processor-properties-set-value* > *nifi-configure-processor-scheduling* > *nifi-configure-processor-settings* > Configure Processor dialog. See related Comments below (in Activity section). > *nifi-dialog-sample-@800px* > Dialog sample in 800px wide viewport. This sample shows the the 'Details' tab > of a provenance event. > *nifi-drop.svg* > NiFi logo without 'nifi > *nifi-global-menu* > To show global menu > *nifi-interaction-and-menu-samples.png* > To demonstrate user interactions - hover states, tooltips, menus, etc. > *nifi-lineage-graph-@800px* > To show lineage graph with explicit action to get back to data provenance > event list. > *nifi-sample-flow-@800px* > Shows a very useable UI down to around 800px in width. The thinking here is > that at anything lower than this, the NiFi user experience will change to > more of a monitoring and/or administrative type workflow. Future mockups will > be created to illustrate this. > *nifi-logo.svg* > NiFi logo complete > *nifi-sample-flow.png* > Mockup of sample flow. Updated to show revised tool and status bars. > Management related actions will move to a menu via mouseover (see > _nifi-global-menu_). Added benefits here include reducing clutter and more > user-friendly menu with text labels to reduce time spent scanning only a > large set of icons. This also helps gain valuable viewport width in a browser > (see _nifi-sample-flow-@800px_) > *nifi-shell-sample-@800px* > Shell sample in 800px wide viewport. This sample shows the 'Data Provenance' > table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236007#comment-15236007 ] James Wing commented on NIFI-1752: -- Not reliably, although it has seemed to fix both environments for long enough to get my hopes up. Sometimes, after another restart, things go back to failing, so maybe the synchronization is irrelevant or simply moves the timing condition around. I'm going to add some logging and try to make sense of it. > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[ https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235948#comment-15235948 ] ASF GitHub Bot commented on NIFI-1748: -- GitHub user olegz opened a pull request: https://github.com/apache/nifi/pull/344 NIFI-1748 removed un-used test data You can merge this pull request into a Git repository by running: $ git pull https://github.com/olegz/nifi NIFI-1748 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/344.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 #344 commit 8f0b95179adbc44807c3a2f13aa84896db241e5c Author: Oleg Zhurakousky Date: 2016-04-09T21:24:37Z NIFI-1748 removed un-used test data > Remove potentially copyrighted text from KafkaPublisherTest > --- > > Key: NIFI-1748 > URL: https://issues.apache.org/jira/browse/NIFI-1748 > Project: Apache NiFi > Issue Type: Task >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Trivial > Fix For: 1.0.0, 0.7.0, 0.6.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (NIFI-1748) Remove potentially copyrighted text from KafkaPublisherTest
[ https://issues.apache.org/jira/browse/NIFI-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt reopened NIFI-1748: --- This is not resolved. There is still an Einstein quote in it and this is entirely unnecessary. I'm not a lawyer so I don't know. But quick check on copyright of quotes (even if famous) leaves me unclear and given how completely avoidable and not necessary it is we must remove this. > Remove potentially copyrighted text from KafkaPublisherTest > --- > > Key: NIFI-1748 > URL: https://issues.apache.org/jira/browse/NIFI-1748 > Project: Apache NiFi > Issue Type: Task >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Trivial > Fix For: 1.0.0, 0.7.0, 0.6.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235888#comment-15235888 ] Joseph Witt commented on NIFI-1752: --- Did your synchornization fix help in both environments? > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235883#comment-15235883 ] James Wing commented on NIFI-1752: -- I tried it in two environments, and experience the issue on both: Windows 10 java version "1.8.0_66" Java(TM) SE Runtime Environment (build 1.8.0_66-b18) Java HotSpot(TM) 64-Bit Server VM (build 25.66-b18, mixed mode) Amazon Linux (March 2016) openjdk version "1.8.0_77" OpenJDK Runtime Environment (build 1.8.0_77-b03) OpenJDK 64-Bit Server VM (build 25.77-b03, mixed mode) > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1323) UI visual design enhancement
[ https://issues.apache.org/jira/browse/NIFI-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-1323: Attachment: flowfont.zip > UI visual design enhancement > > > Key: NIFI-1323 > URL: https://issues.apache.org/jira/browse/NIFI-1323 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Trivial > Attachments: flowfont.zip, nifi-add-processor-dialog.png, > nifi-component-samples.png, > nifi-configure-processor-properties-set-value.png, > nifi-configure-processor-properties.png, > nifi-configure-processor-scheduling.png, > nifi-configure-processor-settings.png, nifi-dialog-samp...@800px.png, > nifi-drop.svg, nifi-global-menu.png, nifi-interaction-and-menu-samples.png, > nifi-lineage-gra...@800px.png, nifi-logo.svg, nifi-sample-fl...@800px.png, > nifi-sample-flow.png, nifi-shell-samp...@800px.png > > > (I will attach mockups and supporting files as they become available) > I am starting to work on a design to modernize the look and feel of the NiFi > UI. The initial focus of the design is to freshen the UI (flat design, SVG > icons, etc.). Additionally, the new design will propose usability > improvements such as exposing more flow-related actions into collapsible > panes, improving hierarchy of information, etc. > Going forward, the design plan is to help lay the foundation for other UI/UX > related issues such as those documented in NIFI-951. > --- > *flowfont.zip* > Contains icon font and supporting files > *nifi-add-processor-dialog.png* > Dialog sample. This sample shows the 'Add Processor' dialog. > *nifi-component-samples.png* > To show styling for all components > *nifi-configure-processor-properties* > *nifi-configure-processor-properties-set-value* > *nifi-configure-processor-scheduling* > *nifi-configure-processor-settings* > Configure Processor dialog. See related Comments below (in Activity section). > *nifi-dialog-sample-@800px* > Dialog sample in 800px wide viewport. This sample shows the the 'Details' tab > of a provenance event. > *nifi-drop.svg* > NiFi logo without 'nifi > *nifi-global-menu* > To show global menu > *nifi-interaction-and-menu-samples.png* > To demonstrate user interactions - hover states, tooltips, menus, etc. > *nifi-lineage-graph-@800px* > To show lineage graph with explicit action to get back to data provenance > event list. > *nifi-sample-flow-@800px* > Shows a very useable UI down to around 800px in width. The thinking here is > that at anything lower than this, the NiFi user experience will change to > more of a monitoring and/or administrative type workflow. Future mockups will > be created to illustrate this. > *nifi-logo.svg* > NiFi logo complete > *nifi-sample-flow.png* > Mockup of sample flow. Updated to show revised tool and status bars. > Management related actions will move to a menu via mouseover (see > _nifi-global-menu_). Added benefits here include reducing clutter and more > user-friendly menu with text labels to reduce time spent scanning only a > large set of icons. This also helps gain valuable viewport width in a browser > (see _nifi-sample-flow-@800px_) > *nifi-shell-sample-@800px* > Shell sample in 800px wide viewport. This sample shows the 'Data Provenance' > table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1323) UI visual design enhancement
[ https://issues.apache.org/jira/browse/NIFI-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-1323: Attachment: (was: flowfont.zip) > UI visual design enhancement > > > Key: NIFI-1323 > URL: https://issues.apache.org/jira/browse/NIFI-1323 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Trivial > Attachments: nifi-add-processor-dialog.png, > nifi-component-samples.png, > nifi-configure-processor-properties-set-value.png, > nifi-configure-processor-properties.png, > nifi-configure-processor-scheduling.png, > nifi-configure-processor-settings.png, nifi-dialog-samp...@800px.png, > nifi-drop.svg, nifi-global-menu.png, nifi-interaction-and-menu-samples.png, > nifi-lineage-gra...@800px.png, nifi-logo.svg, nifi-sample-fl...@800px.png, > nifi-sample-flow.png, nifi-shell-samp...@800px.png > > > (I will attach mockups and supporting files as they become available) > I am starting to work on a design to modernize the look and feel of the NiFi > UI. The initial focus of the design is to freshen the UI (flat design, SVG > icons, etc.). Additionally, the new design will propose usability > improvements such as exposing more flow-related actions into collapsible > panes, improving hierarchy of information, etc. > Going forward, the design plan is to help lay the foundation for other UI/UX > related issues such as those documented in NIFI-951. > --- > *flowfont.zip* > Contains icon font and supporting files > *nifi-add-processor-dialog.png* > Dialog sample. This sample shows the 'Add Processor' dialog. > *nifi-component-samples.png* > To show styling for all components > *nifi-configure-processor-properties* > *nifi-configure-processor-properties-set-value* > *nifi-configure-processor-scheduling* > *nifi-configure-processor-settings* > Configure Processor dialog. See related Comments below (in Activity section). > *nifi-dialog-sample-@800px* > Dialog sample in 800px wide viewport. This sample shows the the 'Details' tab > of a provenance event. > *nifi-drop.svg* > NiFi logo without 'nifi > *nifi-global-menu* > To show global menu > *nifi-interaction-and-menu-samples.png* > To demonstrate user interactions - hover states, tooltips, menus, etc. > *nifi-lineage-graph-@800px* > To show lineage graph with explicit action to get back to data provenance > event list. > *nifi-sample-flow-@800px* > Shows a very useable UI down to around 800px in width. The thinking here is > that at anything lower than this, the NiFi user experience will change to > more of a monitoring and/or administrative type workflow. Future mockups will > be created to illustrate this. > *nifi-logo.svg* > NiFi logo complete > *nifi-sample-flow.png* > Mockup of sample flow. Updated to show revised tool and status bars. > Management related actions will move to a menu via mouseover (see > _nifi-global-menu_). Added benefits here include reducing clutter and more > user-friendly menu with text labels to reduce time spent scanning only a > large set of icons. This also helps gain valuable viewport width in a browser > (see _nifi-sample-flow-@800px_) > *nifi-shell-sample-@800px* > Shell sample in 800px wide viewport. This sample shows the 'Data Provenance' > table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[nifi] Git Push Summary
Repository: nifi Updated Branches: refs/heads/NIFI-1654 [deleted] 3970c5e13
[jira] [Commented] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
[ https://issues.apache.org/jira/browse/NIFI-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235750#comment-15235750 ] Joe Skora commented on NIFI-1754: - Tagging flowfiles when they are rolled back crossed my mind. I'll dig through [~JPercivall]'s new In-Depth Developer Docs too, but is there a good place to look to get on the session, flowfile queue, etc. that this will require? > Rollback log messages should include the flowfile filename and UUID to assist > in flow management. > - > > Key: NIFI-1754 > URL: https://issues.apache.org/jira/browse/NIFI-1754 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.0.0, 0.7.0 >Reporter: Joe Skora >Assignee: Joe Skora > > When a processor calls rollback on a flowfile, the filename and UUID of the > flowfile should be included in log entry to make it easier for the offending > files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[nifi] Git Push Summary
Repository: nifi Updated Tags: refs/tags/nifi-0.6.1-RC1 [deleted] 8ecd3d6fd
[nifi] Git Push Summary
Repository: nifi Updated Branches: refs/heads/NIFI-1729-RC1 [deleted] 8e2cb102f
[jira] [Updated] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt updated NIFI-1752: -- Fix Version/s: (was: 0.7.0) (was: 1.0.0) > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235728#comment-15235728 ] Joseph Witt commented on NIFI-1752: --- dumped fix version references until we get closer to understanding/resolution. > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt updated NIFI-1752: -- Fix Version/s: (was: 0.6.1) > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > Fix For: 1.0.0, 0.7.0 > > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235719#comment-15235719 ] Joseph Witt commented on NIFI-1752: --- [~jameswing] [~dionosys] Can you share more about your environment? I tested the processor using a flow like what I thought you described and using James' template and it worked great. I was on both linux and osx using different JDKs openjdk version "1.8.0_71" OpenJDK Runtime Environment (build 1.8.0_71-b15) OpenJDK 64-Bit Server VM (build 25.71-b15, mixed mode) java version "1.8.0_65" Java(TM) SE Runtime Environment (build 1.8.0_65-b17) Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode) java version "1.7.0_80" Java(TM) SE Runtime Environment (build 1.7.0_80-b15) Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode) The synchronization thing James mentions seems interesting but if this was ok before 0.6.0 seems like a smaller concern perhaps. Not sure. > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > Fix For: 1.0.0, 0.7.0, 0.6.1 > > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
[ https://issues.apache.org/jira/browse/NIFI-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235717#comment-15235717 ] Joseph Witt commented on NIFI-1754: --- ok and taking this a step further just for the sake of dreaming among friends in JIRA... It would be cool if a flowfile involved in a rollback had some flag set so when inspecting the queue you could see ones that were involved in rollback and perhaps the rollback message/exception it was associated with. Dang that would be nice! Something to think about at some point. > Rollback log messages should include the flowfile filename and UUID to assist > in flow management. > - > > Key: NIFI-1754 > URL: https://issues.apache.org/jira/browse/NIFI-1754 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.0.0, 0.7.0 >Reporter: Joe Skora >Assignee: Joe Skora > > When a processor calls rollback on a flowfile, the filename and UUID of the > flowfile should be included in log entry to make it easier for the offending > files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
[ https://issues.apache.org/jira/browse/NIFI-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235709#comment-15235709 ] Joe Skora commented on NIFI-1754: - Yeah, I think this will make the queue inspection and management tools even more valuable for flow managers. > Rollback log messages should include the flowfile filename and UUID to assist > in flow management. > - > > Key: NIFI-1754 > URL: https://issues.apache.org/jira/browse/NIFI-1754 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.0.0, 0.7.0 >Reporter: Joe Skora >Assignee: Joe Skora > > When a processor calls rollback on a flowfile, the filename and UUID of the > flowfile should be included in log entry to make it easier for the offending > files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1752) EvaluateXPath invalid when starting processor
[
https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235704#comment-15235704
]
James Wing commented on NIFI-1752:
--
The underlying exception, "javax.xml.xpath.XPathFactoryConfigurationException:
No XPathFactory implementation found for the object model:
http://saxon.sf.net/jaxp/xpath/om"; is thrown by XPathValidator while executing
on EvaluateXPath.java:436:
{code}
XPathFactory factory =
XPathFactory.newInstance(NamespaceConstant.OBJECT_MODEL_SAXON);
{code}
>From watching in the debugger, *sometimes* the exception is thrown, but also
>*sometimes not* - and validation continues to compile the expression
>successfully and validate the property (seen by watching
>{{evaluator.compile(input);}} on line 441).
One possible explanation would be multi-threading. There are several
validation operations in progress at the time the exceptions occur. And the
[documentation for
XPathFactory|https://docs.oracle.com/javase/7/docs/api/javax/xml/xpath/XPathFactory.html]
states that it is not thread safe.
bq. The XPathFactory class is not thread-safe. In other words, it is the
application's responsibility to ensure that at most one thread is using a
XPathFactory object at any given moment. Implementations are encouraged to mark
methods as synchronized to protect themselves from broken clients.
I made an experimental change to synchronize the creation and use of
XPathFactory, and that seems to resolve the issue on my machine. But I'm not
sure how multi-threading would relate to changes introduced in 0.6.0. Proving
that multi-threading is or is not the actual problem and that a {{synchronize}}
block is the right fix is the next step.
> EvaluateXPath invalid when starting processor
> -
>
> Key: NIFI-1752
> URL: https://issues.apache.org/jira/browse/NIFI-1752
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 0.6.0
>Reporter: Joseph Witt
> Fix For: 1.0.0, 0.7.0, 0.6.1
>
>
> Guillaume Pool:
> Hi,
>
> If anyone could help I would appreciate it:
>
> After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid
> with nothing specific reported as the error.
>
> I use flowfile attribute as the destination, xpath query similar to
> /message/address
>
> Return type auto-detect / string
>
> Error:
>
> 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629]
> org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous)
> PUT
> http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad
> (source ip: 172.27.0.97)
> 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629]
> o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException:
> EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid
> state. Returning Conflict response.
>
> Reports this even if you drop a new processor in.
> James Wing:
> I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi
> 0.6.0. I created a template gist at
> https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that
> illustrates this for me. You don't even need to run the whole thing, just
> try to start the EvaluateXPath processor. I see a pop-up error trying to
> start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a
> valid state".
> Trying to troubleshoot this, I attached a debugger and found an
> IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on
> line 1141. The error text was:
> 'address' validated against '/message/address' is invalid because Unable to
> initialize XPath engine due to
> javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory
> implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om
> I haven't figured out what change is the root cause, but the trail seems to
> lead into validating the dynamic XPath attribute.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
[ https://issues.apache.org/jira/browse/NIFI-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235658#comment-15235658 ] Joseph Witt commented on NIFI-1754: --- Certainly. It is a good idea. I've definitely wanted something similar because otherwise for someone debugging something nasty it is all a bit magic. So when rollback occurs and it calls the logger this can be more diagnostic context it puts out. Good call for sure. On the plus side now since we can inspect flow file queues at runtime it has taken a bit of the sting out of needing this. Still should do this just pointing out we've put some more tools in play. > Rollback log messages should include the flowfile filename and UUID to assist > in flow management. > - > > Key: NIFI-1754 > URL: https://issues.apache.org/jira/browse/NIFI-1754 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.0.0, 0.7.0 >Reporter: Joe Skora >Assignee: Joe Skora > > When a processor calls rollback on a flowfile, the filename and UUID of the > flowfile should be included in log entry to make it easier for the offending > files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
[ https://issues.apache.org/jira/browse/NIFI-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235654#comment-15235654 ] Joe Skora commented on NIFI-1754: - [~joewitt], thanks, that should saving me some digging. > Rollback log messages should include the flowfile filename and UUID to assist > in flow management. > - > > Key: NIFI-1754 > URL: https://issues.apache.org/jira/browse/NIFI-1754 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.0.0, 0.7.0 >Reporter: Joe Skora >Assignee: Joe Skora > > When a processor calls rollback on a flowfile, the filename and UUID of the > flowfile should be included in log entry to make it easier for the offending > files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
[ https://issues.apache.org/jira/browse/NIFI-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Skora reassigned NIFI-1754: --- Assignee: Joe Skora > Rollback log messages should include the flowfile filename and UUID to assist > in flow management. > - > > Key: NIFI-1754 > URL: https://issues.apache.org/jira/browse/NIFI-1754 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.0.0, 0.7.0 >Reporter: Joe Skora >Assignee: Joe Skora > > When a processor calls rollback on a flowfile, the filename and UUID of the > flowfile should be included in log entry to make it easier for the offending > files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
[ https://issues.apache.org/jira/browse/NIFI-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235615#comment-15235615 ] Joseph Witt commented on NIFI-1754: --- An easy way to do this would be have some sort of debug/toString variant on ProcessSession which would log the toString of any FlowFiles involved in that session ordered by things it pull from its queues, then things it created, and so on. > Rollback log messages should include the flowfile filename and UUID to assist > in flow management. > - > > Key: NIFI-1754 > URL: https://issues.apache.org/jira/browse/NIFI-1754 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.0.0, 0.7.0 >Reporter: Joe Skora > > When a processor calls rollback on a flowfile, the filename and UUID of the > flowfile should be included in log entry to make it easier for the offending > files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1754) Rollback log messages should include the flowfile filename and UUID to assist in flow management.
Joe Skora created NIFI-1754: --- Summary: Rollback log messages should include the flowfile filename and UUID to assist in flow management. Key: NIFI-1754 URL: https://issues.apache.org/jira/browse/NIFI-1754 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.0.0, 0.7.0 Reporter: Joe Skora When a processor calls rollback on a flowfile, the filename and UUID of the flowfile should be included in log entry to make it easier for the offending files to be found and fixed or removed from the flow by the dataflow managers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1749) Test failures when building without access to internet
[
https://issues.apache.org/jira/browse/NIFI-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235584#comment-15235584
]
Joseph Witt commented on NIFI-1749:
---
+1. Merged to all lines.
> Test failures when building without access to internet
> --
>
> Key: NIFI-1749
> URL: https://issues.apache.org/jira/browse/NIFI-1749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 0.6.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Minor
> Fix For: 1.0.0, 0.7.0, 0.6.1
>
>
> Given the needed dependencies within the Maven local repository, some tests
> will fail without access to the Internet.
> {code}
> testCSSSelectorSyntaxValidator(org.apache.nifi.TestGetHTMLElement) Time
> elapsed: 0.947 sec <<< ERROR!
> java.net.UnknownHostException: www.google.com
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:512)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:493)
> at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:205)
> at org.jsoup.helper.HttpConnection.get(HttpConnection.java:194)
> at org.jsoup.Jsoup.parse(Jsoup.java:183)
> at
> org.apache.nifi.TestGetHTMLElement.testCSSSelectorSyntaxValidator(TestGetHTMLElement.java:49)
> {code}
> {quote}
> DeleteDynamoDBTest.testStringHashStringRangeDeleteOnlyHashFailure:89 null
> GetDynamoDBTest.testStringHashStringRangeGetOnlyHashFailure:421 null
> PutDynamoDBTest.testStringHashStringRangePutOnlyHashFailure:92 null
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-1749) Test failures when building without access to internet
[
https://issues.apache.org/jira/browse/NIFI-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-1749:
--
Fix Version/s: 0.6.1
0.7.0
1.0.0
> Test failures when building without access to internet
> --
>
> Key: NIFI-1749
> URL: https://issues.apache.org/jira/browse/NIFI-1749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 0.6.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Minor
> Fix For: 1.0.0, 0.7.0, 0.6.1
>
>
> Given the needed dependencies within the Maven local repository, some tests
> will fail without access to the Internet.
> {code}
> testCSSSelectorSyntaxValidator(org.apache.nifi.TestGetHTMLElement) Time
> elapsed: 0.947 sec <<< ERROR!
> java.net.UnknownHostException: www.google.com
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:512)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:493)
> at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:205)
> at org.jsoup.helper.HttpConnection.get(HttpConnection.java:194)
> at org.jsoup.Jsoup.parse(Jsoup.java:183)
> at
> org.apache.nifi.TestGetHTMLElement.testCSSSelectorSyntaxValidator(TestGetHTMLElement.java:49)
> {code}
> {quote}
> DeleteDynamoDBTest.testStringHashStringRangeDeleteOnlyHashFailure:89 null
> GetDynamoDBTest.testStringHashStringRangeGetOnlyHashFailure:421 null
> PutDynamoDBTest.testStringHashStringRangePutOnlyHashFailure:92 null
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1749) Test failures when building without access to internet
[
https://issues.apache.org/jira/browse/NIFI-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235581#comment-15235581
]
ASF subversion and git services commented on NIFI-1749:
---
Commit bfa8e2bd6a22f1d9f0da6b2c2c158e46496374e2 in nifi's branch refs/heads/0.x
from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=bfa8e2b ]
NIFI-1749 Adjusting tests that fail without a connection to the Internet and
removing attributable elements from test resources.
Signed-off-by: joewitt
> Test failures when building without access to internet
> --
>
> Key: NIFI-1749
> URL: https://issues.apache.org/jira/browse/NIFI-1749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 0.6.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Minor
> Fix For: 1.0.0, 0.7.0, 0.6.1
>
>
> Given the needed dependencies within the Maven local repository, some tests
> will fail without access to the Internet.
> {code}
> testCSSSelectorSyntaxValidator(org.apache.nifi.TestGetHTMLElement) Time
> elapsed: 0.947 sec <<< ERROR!
> java.net.UnknownHostException: www.google.com
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:512)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:493)
> at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:205)
> at org.jsoup.helper.HttpConnection.get(HttpConnection.java:194)
> at org.jsoup.Jsoup.parse(Jsoup.java:183)
> at
> org.apache.nifi.TestGetHTMLElement.testCSSSelectorSyntaxValidator(TestGetHTMLElement.java:49)
> {code}
> {quote}
> DeleteDynamoDBTest.testStringHashStringRangeDeleteOnlyHashFailure:89 null
> GetDynamoDBTest.testStringHashStringRangeGetOnlyHashFailure:421 null
> PutDynamoDBTest.testStringHashStringRangePutOnlyHashFailure:92 null
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-1753) Legacy X.509 certificate handling code should be upgraded
[
https://issues.apache.org/jira/browse/NIFI-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-1753:
--
Fix Version/s: 1.0.0
> Legacy X.509 certificate handling code should be upgraded
> -
>
> Key: NIFI-1753
> URL: https://issues.apache.org/jira/browse/NIFI-1753
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
> Fix For: 1.0.0, 0.7.0
>
>
> There are multiple instances throughout the codebase [1][2] where legacy
> {{javax.security.cert.X509Certificate}} class is used rather than the current
> (Java SE 6) {{java.security.cert.X509Certificate}}. The {{javax.*}} classes
> are provided for legacy compatibility with JSSE [3][4]. This can manifest as
> an exception:
> {{java.lang.ClassCastException: [Ljava.security.cert.X509Certificate; cannot
> be cast to [Ljavax.security.cert.X509Certificate}}
> The {{CertificateFactory}} class allows conversion to the new format.
> [1]
> https://git1-us-west.apache.org/repos/asf?p=nifi.git;a=blob;f=nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/main/java/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidator.java;hb=ffbfffce
> [2
> ]https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpRequest.java#L40
> [3] http://stackoverflow.com/a/24600621/70465
> [4]
> https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSession.html#getPeerCertificates%28%29
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-1753) Legacy X.509 certificate handling code should be upgraded
[
https://issues.apache.org/jira/browse/NIFI-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-1753:
--
Fix Version/s: 0.7.0
> Legacy X.509 certificate handling code should be upgraded
> -
>
> Key: NIFI-1753
> URL: https://issues.apache.org/jira/browse/NIFI-1753
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
> Fix For: 1.0.0, 0.7.0
>
>
> There are multiple instances throughout the codebase [1][2] where legacy
> {{javax.security.cert.X509Certificate}} class is used rather than the current
> (Java SE 6) {{java.security.cert.X509Certificate}}. The {{javax.*}} classes
> are provided for legacy compatibility with JSSE [3][4]. This can manifest as
> an exception:
> {{java.lang.ClassCastException: [Ljava.security.cert.X509Certificate; cannot
> be cast to [Ljavax.security.cert.X509Certificate}}
> The {{CertificateFactory}} class allows conversion to the new format.
> [1]
> https://git1-us-west.apache.org/repos/asf?p=nifi.git;a=blob;f=nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/main/java/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidator.java;hb=ffbfffce
> [2
> ]https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpRequest.java#L40
> [3] http://stackoverflow.com/a/24600621/70465
> [4]
> https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSession.html#getPeerCertificates%28%29
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
nifi git commit: NIFI-1749 Adjusting tests that fail without a connection to the Internet and removing attributable elements from test resources.
Repository: nifi
Updated Branches:
refs/heads/0.x 3e6f1f835 -> bfa8e2bd6
NIFI-1749 Adjusting tests that fail without a connection to the Internet and
removing attributable elements from test resources.
Signed-off-by: joewitt
Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/bfa8e2bd
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/bfa8e2bd
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/bfa8e2bd
Branch: refs/heads/0.x
Commit: bfa8e2bd6a22f1d9f0da6b2c2c158e46496374e2
Parents: 3e6f1f8
Author: Aldrin Piri
Authored: Sun Apr 10 15:59:51 2016 -0400
Committer: joewitt
Committed: Mon Apr 11 13:31:44 2016 -0400
--
.../aws/dynamodb/AbstractDynamoDBTest.java | 41
.../aws/dynamodb/DeleteDynamoDBTest.java| 26 +++--
.../aws/dynamodb/GetDynamoDBTest.java | 18 -
.../aws/dynamodb/PutDynamoDBTest.java | 18 -
.../java/org/apache/nifi/AbstractHTMLTest.java | 2 +-
.../org/apache/nifi/TestGetHTMLElement.java | 21 --
.../src/test/resources/Weather.html | 2 +-
7 files changed, 106 insertions(+), 22 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/nifi/blob/bfa8e2bd/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
--
diff --git
a/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
new file mode 100644
index 000..486bc31
--- /dev/null
+++
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
@@ -0,0 +1,41 @@
+/**
+ * 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.aws.dynamodb;
+
+import com.amazonaws.AmazonServiceException;
+import com.amazonaws.AmazonServiceException.ErrorType;
+
+/**
+ * Provides reused elements and utilities for the AWS DynamoDB related tests
+ *
+ * @see GetDynamoDBTest
+ * @see PutDynamoDBTest
+ * @see DeleteDynamoDBTest
+ */
+public abstract class AbstractDynamoDBTest {
+
+protected AmazonServiceException getSampleAwsServiceException() {
+final AmazonServiceException testServiceException = new
AmazonServiceException("Test AWS Service Exception");
+testServiceException.setErrorCode("8673509");
+testServiceException.setErrorMessage("This request cannot be serviced
right now.");
+testServiceException.setErrorType(ErrorType.Service);
+testServiceException.setServiceName("Dynamo DB");
+testServiceException.setRequestId("TestRequestId-1234567890");
+
+return testServiceException;
+}
+}
http://git-wip-us.apache.org/repos/asf/nifi/blob/bfa8e2bd/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
--
diff --git
a/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
index fa0e605..56067e7 100644
---
a/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
+++
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
@@ -26,6 +26,14 @@ import java.util.HashMap;
import java.util.List;
import java.util.Map;
+import org.apache.nifi.util.MockFlowFile;
+import org.apache.nifi.util.TestRunner;
+import org.apache.nifi.util.TestRunners;
+import org.junit.Before;
+import org.junit.Te
[jira] [Updated] (NIFI-1753) Legacy X.509 certificate handling code should be upgraded
[
https://issues.apache.org/jira/browse/NIFI-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto updated NIFI-1753:
Description:
There are multiple instances throughout the codebase [1][2] where legacy
{{javax.security.cert.X509Certificate}} class is used rather than the current
(Java SE 6) {{java.security.cert.X509Certificate}}. The {{javax.*}} classes are
provided for legacy compatibility with JSSE [3][4]. This can manifest as an
exception:
{{java.lang.ClassCastException: [Ljava.security.cert.X509Certificate; cannot be
cast to [Ljavax.security.cert.X509Certificate}}
The {{CertificateFactory}} class allows conversion to the new format.
[1]
https://git1-us-west.apache.org/repos/asf?p=nifi.git;a=blob;f=nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/main/java/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidator.java;hb=ffbfffce
[2
]https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpRequest.java#L40
[3] http://stackoverflow.com/a/24600621/70465
[4]
https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSession.html#getPeerCertificates%28%29
was:
There are multiple instances throughout the codebase [1][2] where legacy
`javax.security.cert.X509Certificate` class is used rather than the current
(Java SE 6) `java.security.cert.X509Certificate`. The `javax.*` classes are
provided for legacy compatibility with JSSE [3][4]. This can manifest as an
exception:
`java.lang.ClassCastException: [Ljava.security.cert.X509Certificate; cannot be
cast to [Ljavax.security.cert.X509Certificate`
The `CertificateFactory` class allows conversion to the new format.
[1]
https://git1-us-west.apache.org/repos/asf?p=nifi.git;a=blob;f=nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/main/java/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidator.java;hb=ffbfffce
[2
]https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpRequest.java#L40
[3] http://stackoverflow.com/a/24600621/70465
[4]
https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSession.html#getPeerCertificates%28%29
> Legacy X.509 certificate handling code should be upgraded
> -
>
> Key: NIFI-1753
> URL: https://issues.apache.org/jira/browse/NIFI-1753
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>
> There are multiple instances throughout the codebase [1][2] where legacy
> {{javax.security.cert.X509Certificate}} class is used rather than the current
> (Java SE 6) {{java.security.cert.X509Certificate}}. The {{javax.*}} classes
> are provided for legacy compatibility with JSSE [3][4]. This can manifest as
> an exception:
> {{java.lang.ClassCastException: [Ljava.security.cert.X509Certificate; cannot
> be cast to [Ljavax.security.cert.X509Certificate}}
> The {{CertificateFactory}} class allows conversion to the new format.
> [1]
> https://git1-us-west.apache.org/repos/asf?p=nifi.git;a=blob;f=nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/main/java/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidator.java;hb=ffbfffce
> [2
> ]https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpRequest.java#L40
> [3] http://stackoverflow.com/a/24600621/70465
> [4]
> https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSession.html#getPeerCertificates%28%29
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (NIFI-1753) Legacy X.509 certificate handling code should be upgraded
Andy LoPresto created NIFI-1753: --- Summary: Legacy X.509 certificate handling code should be upgraded Key: NIFI-1753 URL: https://issues.apache.org/jira/browse/NIFI-1753 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.6.1 Reporter: Andy LoPresto Assignee: Andy LoPresto There are multiple instances throughout the codebase [1][2] where legacy `javax.security.cert.X509Certificate` class is used rather than the current (Java SE 6) `java.security.cert.X509Certificate`. The `javax.*` classes are provided for legacy compatibility with JSSE [3][4]. This can manifest as an exception: `java.lang.ClassCastException: [Ljava.security.cert.X509Certificate; cannot be cast to [Ljavax.security.cert.X509Certificate` The `CertificateFactory` class allows conversion to the new format. [1] https://git1-us-west.apache.org/repos/asf?p=nifi.git;a=blob;f=nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/src/main/java/org/apache/nifi/web/security/x509/ocsp/OcspCertificateValidator.java;hb=ffbfffce [2 ]https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/HandleHttpRequest.java#L40 [3] http://stackoverflow.com/a/24600621/70465 [4] https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSession.html#getPeerCertificates%28%29 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1749) Test failures when building without access to internet
[
https://issues.apache.org/jira/browse/NIFI-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235550#comment-15235550
]
ASF subversion and git services commented on NIFI-1749:
---
Commit e76a75c26bbe64adc8a35fa1f8846c3fd45f632d in nifi's branch
refs/heads/master from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e76a75c ]
NIFI-1749 This closes #342. Adjusting tests that fail without a connection to
the Internet and removing attributable elements from test resources.
Signed-off-by: joewitt
> Test failures when building without access to internet
> --
>
> Key: NIFI-1749
> URL: https://issues.apache.org/jira/browse/NIFI-1749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 0.6.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Minor
>
> Given the needed dependencies within the Maven local repository, some tests
> will fail without access to the Internet.
> {code}
> testCSSSelectorSyntaxValidator(org.apache.nifi.TestGetHTMLElement) Time
> elapsed: 0.947 sec <<< ERROR!
> java.net.UnknownHostException: www.google.com
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:512)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:493)
> at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:205)
> at org.jsoup.helper.HttpConnection.get(HttpConnection.java:194)
> at org.jsoup.Jsoup.parse(Jsoup.java:183)
> at
> org.apache.nifi.TestGetHTMLElement.testCSSSelectorSyntaxValidator(TestGetHTMLElement.java:49)
> {code}
> {quote}
> DeleteDynamoDBTest.testStringHashStringRangeDeleteOnlyHashFailure:89 null
> GetDynamoDBTest.testStringHashStringRangeGetOnlyHashFailure:421 null
> PutDynamoDBTest.testStringHashStringRangePutOnlyHashFailure:92 null
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1749) Test failures when building without access to internet
[
https://issues.apache.org/jira/browse/NIFI-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235556#comment-15235556
]
ASF GitHub Bot commented on NIFI-1749:
--
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/342
> Test failures when building without access to internet
> --
>
> Key: NIFI-1749
> URL: https://issues.apache.org/jira/browse/NIFI-1749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 0.6.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Minor
>
> Given the needed dependencies within the Maven local repository, some tests
> will fail without access to the Internet.
> {code}
> testCSSSelectorSyntaxValidator(org.apache.nifi.TestGetHTMLElement) Time
> elapsed: 0.947 sec <<< ERROR!
> java.net.UnknownHostException: www.google.com
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:512)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:493)
> at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:205)
> at org.jsoup.helper.HttpConnection.get(HttpConnection.java:194)
> at org.jsoup.Jsoup.parse(Jsoup.java:183)
> at
> org.apache.nifi.TestGetHTMLElement.testCSSSelectorSyntaxValidator(TestGetHTMLElement.java:49)
> {code}
> {quote}
> DeleteDynamoDBTest.testStringHashStringRangeDeleteOnlyHashFailure:89 null
> GetDynamoDBTest.testStringHashStringRangeGetOnlyHashFailure:421 null
> PutDynamoDBTest.testStringHashStringRangePutOnlyHashFailure:92 null
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
nifi git commit: NIFI-1749 This closes #342. Adjusting tests that fail without a connection to the Internet and removing attributable elements from test resources.
Repository: nifi
Updated Branches:
refs/heads/master 95dda1d92 -> e76a75c26
NIFI-1749 This closes #342. Adjusting tests that fail without a connection to
the Internet and removing attributable elements from test resources.
Signed-off-by: joewitt
Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/e76a75c2
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/e76a75c2
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/e76a75c2
Branch: refs/heads/master
Commit: e76a75c26bbe64adc8a35fa1f8846c3fd45f632d
Parents: 95dda1d
Author: Aldrin Piri
Authored: Sun Apr 10 15:59:51 2016 -0400
Committer: joewitt
Committed: Mon Apr 11 13:22:00 2016 -0400
--
.../aws/dynamodb/AbstractDynamoDBTest.java | 41
.../aws/dynamodb/DeleteDynamoDBTest.java| 26 +++--
.../aws/dynamodb/GetDynamoDBTest.java | 18 -
.../aws/dynamodb/PutDynamoDBTest.java | 18 -
.../java/org/apache/nifi/AbstractHTMLTest.java | 2 +-
.../org/apache/nifi/TestGetHTMLElement.java | 21 --
.../src/test/resources/Weather.html | 2 +-
7 files changed, 106 insertions(+), 22 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/nifi/blob/e76a75c2/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
--
diff --git
a/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
new file mode 100644
index 000..486bc31
--- /dev/null
+++
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBTest.java
@@ -0,0 +1,41 @@
+/**
+ * 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.aws.dynamodb;
+
+import com.amazonaws.AmazonServiceException;
+import com.amazonaws.AmazonServiceException.ErrorType;
+
+/**
+ * Provides reused elements and utilities for the AWS DynamoDB related tests
+ *
+ * @see GetDynamoDBTest
+ * @see PutDynamoDBTest
+ * @see DeleteDynamoDBTest
+ */
+public abstract class AbstractDynamoDBTest {
+
+protected AmazonServiceException getSampleAwsServiceException() {
+final AmazonServiceException testServiceException = new
AmazonServiceException("Test AWS Service Exception");
+testServiceException.setErrorCode("8673509");
+testServiceException.setErrorMessage("This request cannot be serviced
right now.");
+testServiceException.setErrorType(ErrorType.Service);
+testServiceException.setServiceName("Dynamo DB");
+testServiceException.setRequestId("TestRequestId-1234567890");
+
+return testServiceException;
+}
+}
http://git-wip-us.apache.org/repos/asf/nifi/blob/e76a75c2/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
--
diff --git
a/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
index fa0e605..56067e7 100644
---
a/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
+++
b/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/dynamodb/DeleteDynamoDBTest.java
@@ -26,6 +26,14 @@ import java.util.HashMap;
import java.util.List;
import java.util.Map;
+import org.apache.nifi.util.MockFlowFile;
+import org.apache.nifi.util.TestRunner;
+import org.apache.nifi.util.TestRunners;
+import org.junit.Befo
[jira] [Updated] (NIFI-1752) EvaluateXPath invalid when starting processor
[ https://issues.apache.org/jira/browse/NIFI-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt updated NIFI-1752: -- Fix Version/s: 0.6.1 0.7.0 1.0.0 > EvaluateXPath invalid when starting processor > - > > Key: NIFI-1752 > URL: https://issues.apache.org/jira/browse/NIFI-1752 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.6.0 >Reporter: Joseph Witt > Fix For: 1.0.0, 0.7.0, 0.6.1 > > > Guillaume Pool: > Hi, > > If anyone could help I would appreciate it: > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > Return type auto-detect / string > > Error: > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > Reports this even if you drop a new processor in. > James Wing: > I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi > 0.6.0. I created a template gist at > https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that > illustrates this for me. You don't even need to run the whole thing, just > try to start the EvaluateXPath processor. I see a pop-up error trying to > start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a > valid state". > Trying to troubleshoot this, I attached a debugger and found an > IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on > line 1141. The error text was: > 'address' validated against '/message/address' is invalid because Unable to > initialize XPath engine due to > javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory > implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om > I haven't figured out what change is the root cause, but the trail seems to > lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1749) Test failures when building without access to internet
[
https://issues.apache.org/jira/browse/NIFI-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235529#comment-15235529
]
ASF subversion and git services commented on NIFI-1749:
---
Commit abbd21531b7d133e86726790eb7a4557356ae8f1 in nifi's branch
refs/heads/support/nifi-0.6.x from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=abbd215 ]
NIFI-1749 Adjusting tests that fail without a connection to the Internet and
removing attributable elements from test resources.
Signed-off-by: joewitt
> Test failures when building without access to internet
> --
>
> Key: NIFI-1749
> URL: https://issues.apache.org/jira/browse/NIFI-1749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 0.6.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Minor
>
> Given the needed dependencies within the Maven local repository, some tests
> will fail without access to the Internet.
> {code}
> testCSSSelectorSyntaxValidator(org.apache.nifi.TestGetHTMLElement) Time
> elapsed: 0.947 sec <<< ERROR!
> java.net.UnknownHostException: www.google.com
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:512)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:493)
> at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:205)
> at org.jsoup.helper.HttpConnection.get(HttpConnection.java:194)
> at org.jsoup.Jsoup.parse(Jsoup.java:183)
> at
> org.apache.nifi.TestGetHTMLElement.testCSSSelectorSyntaxValidator(TestGetHTMLElement.java:49)
> {code}
> {quote}
> DeleteDynamoDBTest.testStringHashStringRangeDeleteOnlyHashFailure:89 null
> GetDynamoDBTest.testStringHashStringRangeGetOnlyHashFailure:421 null
> PutDynamoDBTest.testStringHashStringRangePutOnlyHashFailure:92 null
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
nifi git commit: NIFI-1749 Adjusting tests that fail without a connection to the Internet and removing attributable elements from test resources.
Repository: nifi
Updated Branches:
refs/heads/support/nifi-0.6.x ee0025a4f -> abbd21531
NIFI-1749 Adjusting tests that fail without a connection to the Internet and
removing attributable elements from test resources.
Signed-off-by: joewitt
Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/abbd2153
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/abbd2153
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/abbd2153
Branch: refs/heads/support/nifi-0.6.x
Commit: abbd21531b7d133e86726790eb7a4557356ae8f1
Parents: ee0025a
Author: Aldrin Piri
Authored: Sun Apr 10 15:59:51 2016 -0400
Committer: joewitt
Committed: Mon Apr 11 12:23:35 2016 -0400
--
.../java/org/apache/nifi/AbstractHTMLTest.java | 2 +-
.../org/apache/nifi/TestGetHTMLElement.java | 21
.../src/test/resources/Weather.html | 2 +-
3 files changed, 10 insertions(+), 15 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/nifi/blob/abbd2153/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/AbstractHTMLTest.java
--
diff --git
a/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/AbstractHTMLTest.java
b/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/AbstractHTMLTest.java
index 10bc33e..53ce645 100644
---
a/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/AbstractHTMLTest.java
+++
b/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/AbstractHTMLTest.java
@@ -22,7 +22,7 @@ public abstract class AbstractHTMLTest {
protected final String GDR_WEATHER_TEXT = "Grand Rapids Weather";
protected final String ATL_WEATHER_LINK =
"http://w1.weather.gov/obhistory/KPDK.html";;
protected final String GR_WEATHER_LINK =
"http://w1.weather.gov/obhistory/KGRR.html";;
-protected final String AUTHOR_NAME = "Jeremy Dyer";
+protected final String AUTHOR_NAME = "Apache NiFi Community";
protected final String ATL_ID = "ATL";
protected final String GDR_ID = "GDR";
}
http://git-wip-us.apache.org/repos/asf/nifi/blob/abbd2153/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/TestGetHTMLElement.java
--
diff --git
a/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/TestGetHTMLElement.java
b/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/TestGetHTMLElement.java
index 4839fce..4b215fd 100644
---
a/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/TestGetHTMLElement.java
+++
b/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/java/org/apache/nifi/TestGetHTMLElement.java
@@ -16,6 +16,11 @@
*/
package org.apache.nifi;
+import java.io.File;
+import java.io.IOException;
+import java.nio.charset.StandardCharsets;
+import java.util.List;
+
import org.apache.nifi.util.MockFlowFile;
import org.apache.nifi.util.TestRunner;
import org.apache.nifi.util.TestRunners;
@@ -25,12 +30,6 @@ import org.jsoup.select.Selector;
import org.junit.Before;
import org.junit.Test;
-import java.io.File;
-import java.io.IOException;
-import java.lang.Exception;
-import java.net.URL;
-import java.util.List;
-
public class TestGetHTMLElement extends AbstractHTMLTest {
private TestRunner testRunner;
@@ -44,14 +43,10 @@ public class TestGetHTMLElement extends AbstractHTMLTest {
testRunner.setProperty(GetHTMLElement.HTML_CHARSET, "UTF-8");
}
-@Test
+@Test(expected = Selector.SelectorParseException.class)
public void testCSSSelectorSyntaxValidator() throws IOException {
-Document doc = Jsoup.parse(new URL("http://www.google.com";), 5000);
-try {
-doc.select("---jeremy");
-} catch (Selector.SelectorParseException ex) {
-ex.printStackTrace();
-}
+Document doc = Jsoup.parse(new
File("src/test/resources/Weather.html"), StandardCharsets.UTF_8.name());
+doc.select("---invalidCssSelector");
}
@Test
http://git-wip-us.apache.org/repos/asf/nifi/blob/abbd2153/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/resources/Weather.html
--
diff --git
a/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/resources/Weather.html
b/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/resources/Weather.html
index 673f7cb..a715a1d 100644
---
a/nifi-nar-bundles/nifi-html-bundle/nifi-html-processors/src/test/resources/Weather.html
+++
b/ni
[jira] [Created] (NIFI-1752) EvaluateXPath invalid when starting processor
Joseph Witt created NIFI-1752: - Summary: EvaluateXPath invalid when starting processor Key: NIFI-1752 URL: https://issues.apache.org/jira/browse/NIFI-1752 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.6.0 Reporter: Joseph Witt Guillaume Pool: Hi, If anyone could help I would appreciate it: After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid with nothing specific reported as the error. I use flowfile attribute as the destination, xpath query similar to /message/address Return type auto-detect / string Error: 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) PUT http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad (source ip: 172.27.0.97) 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid state. Returning Conflict response. Reports this even if you drop a new processor in. James Wing: I am able to see the same EvaluateXPath issue Guillame Pool reported on NiFi 0.6.0. I created a template gist at https://gist.github.com/jvwing/7e7948d8eb5ad3643f38966b4ba3ce2e that illustrates this for me. You don't even need to run the whole thing, just try to start the EvaluateXPath processor. I see a pop-up error trying to start it "EvaluateXPath[id=b481c570-686a-4b6e-859c-9ebe27398fe1] is not in a valid state". Trying to troubleshoot this, I attached a debugger and found an IllegalStateException thrown by StandardProcessorNode.verifyCanStart() on line 1141. The error text was: 'address' validated against '/message/address' is invalid because Unable to initialize XPath engine due to javax.xml.xpath.XPathFactoryConfigurationException: No XPathFactory implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om I haven't figured out what change is the root cause, but the trail seems to lead into validating the dynamic XPath attribute. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1654) Integrate Appveyor for Windows CI
[ https://issues.apache.org/jira/browse/NIFI-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235455#comment-15235455 ] ASF GitHub Bot commented on NIFI-1654: -- Github user apiri commented on the pull request: https://github.com/apache/nifi/pull/343#issuecomment-208441553 Just wanted to verify we were enabled. Will continue off this PR to get it out and update with a note once it is working and ready for a review. > Integrate Appveyor for Windows CI > - > > Key: NIFI-1654 > URL: https://issues.apache.org/jira/browse/NIFI-1654 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri > > Windows support for Travis CI is still being developed. In the interim, > Appveyor supports Windows environments and could provide some automated > testing and builds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1654) Integrate Appveyor for Windows CI
[ https://issues.apache.org/jira/browse/NIFI-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235453#comment-15235453 ] ASF GitHub Bot commented on NIFI-1654: -- GitHub user apiri opened a pull request: https://github.com/apache/nifi/pull/343 NIFI-1654 Creating an initial appveyor.yml file. Working PR to verify successful integration of Appveyor You can merge this pull request into a Git repository by running: $ git pull https://github.com/apiri/incubator-nifi NIFI-1654 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/343.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 #343 commit 4ab65f7b35c4a42b8ea7ca8001ac8b68841eabf3 Author: Aldrin Piri Date: 2016-03-25T14:54:50Z NIFI-1654 Creating an initial appveyor.yml file. > Integrate Appveyor for Windows CI > - > > Key: NIFI-1654 > URL: https://issues.apache.org/jira/browse/NIFI-1654 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri > > Windows support for Travis CI is still being developed. In the interim, > Appveyor supports Windows environments and could provide some automated > testing and builds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1751) Update HTTP processors to allow a proxy authentication strategy
David A. Wynne created NIFI-1751: Summary: Update HTTP processors to allow a proxy authentication strategy Key: NIFI-1751 URL: https://issues.apache.org/jira/browse/NIFI-1751 Project: Apache NiFi Issue Type: Improvement Reporter: David A. Wynne Priority: Minor If trying to use the HTTP processors from behind a proxy server, the following error occurs: Received error HTTP_ERROR: HTTP/1.1 407 Proxy Authentication Required. Will attempt to reconnect The library NiFi uses for HTTP processors has the ability to set a proxy authentication strategy but currently doesn't use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1712) HBaseClientService unable to connect when Phoenix is installed
[
https://issues.apache.org/jira/browse/NIFI-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235302#comment-15235302
]
Josh Elser commented on NIFI-1712:
--
bq. Ok, so changing the default_realm the HDP.SUPERGRP.NET in the krb5.conf
resolved the rest of it.
Great, that's along the lines of what I thought the problem was. I wonder if
the lack of entries in {{\[domain_realm\]}} in your krb5.conf were an issue.
e.g.
{noformat}
.hdp.supergrp.net = HDP.SUPERGRP.NET
hdp.supergrp.net = HDP.SUPERGRP.NET
{noformat}
Glad you got it working though.
bq. Only have the temp solution for phoenix in at this stage, adding the
phoenix-$version-client.jar into the working directory as described by Bryan
earlier in this JIRA.
PHOENIX-2535 will provide some shaded artifacts which should help alleviate any
concern of Phoenix-required libraries from impacting anything else. Until then,
I think it would just be an administrative decision "Do the current Phoenix
dependencies shaded (but not relocated) affect anything else in NiFi? If not,
just ship it".
> HBaseClientService unable to connect when Phoenix is installed
> --
>
> Key: NIFI-1712
> URL: https://issues.apache.org/jira/browse/NIFI-1712
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Bryan Bende
>Priority: Minor
>
> A user reported running HDP 2.3.2 with Phoenix installed, and NiFi 0.6.0,
> with the following error:
>
> 2016-03-31 13:24:23,916 INFO [StandardProcessScheduler Thread-5]
> o.a.nifi.hbase.HBase_1_1_2_ClientService
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] HBase
> Security Enabled, logging in as principal n...@hdp.supergrp.net with keytab
> /app/env/nifi.keytab
> 2016-03-31 13:24:23,984 WARN [StandardProcessScheduler Thread-5]
> org.apache.hadoop.util.NativeCodeLoader Unable to load native-hadoop library
> for your platform... using builtin-java classes where applicable
> 2016-03-31 13:24:24,101 INFO [StandardProcessScheduler Thread-5]
> o.a.nifi.hbase.HBase_1_1_2_ClientService
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2]
> Successfully logged in as principal n...@hdp.supergrp.net with keytab
> /app/env/nifi.keytab
> 2016-03-31 13:24:24,177 ERROR [StandardProcessScheduler Thread-5]
> o.a.n.c.s.StandardControllerServiceNode
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] Failed to
> invoke @OnEnabled method due to java.io.IOException:
> java.lang.reflect.InvocationTargetException
> 2016-03-31 13:24:24,182 ERROR [StandardProcessScheduler Thread-5]
> o.a.n.c.s.StandardControllerServiceNode
> java.io.IOException: java.lang.reflect.InvocationTargetException
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240)
> ~[hbase-client-1.1.2.jar:1.1.2]
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
> ~[hbase-client-1.1.2.jar:1.1.2]
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
> ~[hbase-client-1.1.2.jar:1.1.2]
> at
> org.apache.nifi.hbase.HBase_1_1_2_ClientService$1.run(HBase_1_1_2_ClientService.java:215)
> ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at
> org.apache.nifi.hbase.HBase_1_1_2_ClientService$1.run(HBase_1_1_2_ClientService.java:212)
> ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_71]
> at javax.security.auth.Subject.doAs(Subject.java:422) ~[na:1.8.0_71]
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1656)
> ~[hadoop-common-2.6.2.jar:na]
> at
> org.apache.nifi.hbase.HBase_1_1_2_ClientService.createConnection(HBase_1_1_2_ClientService.java:212)
> ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at
> org.apache.nifi.hbase.HBase_1_1_2_ClientService.onEnabled(HBase_1_1_2_ClientService.java:161)
> ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_71]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_71]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_71]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_71]
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
> ~[na:na]
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
> ~[na:na]
> at
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(Refle
[jira] [Commented] (NIFI-1668) Intermittent Test Failure for TestProcessorLifecycle
[ https://issues.apache.org/jira/browse/NIFI-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235146#comment-15235146 ] ASF GitHub Bot commented on NIFI-1668: -- Github user pvillard31 commented on the pull request: https://github.com/apache/nifi/pull/324#issuecomment-208369542 @olegz Tests on master are OK but not when testing this PR. Windows 10 / Maven 3.3.9 : Java 1.0.8_74 ``` --- T E S T S --- Running TestSuite Tests run: 182, Failures: 29, Errors: 0, Skipped: 1, Time elapsed: 135.132 sec <<< FAILURE! - in TestSuite validateSuccessfullAndOrderlyShutdown on validateSuccessfullAndOrderlyShutdown(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)(org.apache.nifi.controller.scheduling.T estProcessorLifecycle) Time elapsed: 5.267 sec <<< FAILURE! java.io.IOException: Unable to delete file: .\target\test-repo\wali.lock at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2279) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) at org.apache.nifi.controller.scheduling.TestProcessorLifecycle.after(TestProcessorLifecycle.java:90) validateStopCallsAreMeaninglessIfProcessorNotStarted on validateStopCallsAreMeaninglessIfProcessorNotStarted(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)(org.apach e.nifi.controller.scheduling.TestProcessorLifecycle) Time elapsed: 0.001 sec <<< FAILURE! java.lang.RuntimeException: java.nio.channels.OverlappingFileLockException at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255) at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152) at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1063) at java.nio.channels.FileChannel.lock(FileChannel.java:1053) at org.wali.MinimalLockingWriteAheadLog.(MinimalLockingWriteAheadLog.java:179) at org.wali.MinimalLockingWriteAheadLog.(MinimalLockingWriteAheadLog.java:108) at org.apache.nifi.controller.repository.WriteAheadFlowFileRepository.initialize(WriteAheadFlowFileRepository.java:139) at org.apache.nifi.controller.FlowController.createFlowFileRepository(FlowController.java:547) at org.apache.nifi.controller.FlowController.(FlowController.java:411) at org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:360) at org.apache.nifi.controller.scheduling.TestProcessorLifecycle.buildFlowControllerForTest(TestProcessorLifecycle.java:607) at org.apache.nifi.controller.scheduling.TestProcessorLifecycle.before(TestProcessorLifecycle.java:85) validateStopCallsAreMeaninglessIfProcessorNotStarted on validateStopCallsAreMeaninglessIfProcessorNotStarted(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)(org.apach e.nifi.controller.scheduling.TestProcessorLifecycle) Time elapsed: 0.001 sec <<< FAILURE! java.io.IOException: Unable to delete file: .\target\test-repo\wali.lock at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2279) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) at org.apache.nifi.controller.scheduling.TestProcessorLifecycle.after(TestProcessorLifecycle.java:90) validateLifecycleOperationOrderWithConcurrentCallsToStartStop on validateLifecycleOperationOrderWithConcurrentCallsToStartStop(org.apache.nifi.controller.scheduling.TestProcessorLi fecycle)(org.apache.nifi.controller.scheduling.TestProcessorLifecycle) Time elapsed: 0.001 sec <<< FAILURE! java.lang.RuntimeException: java.nio.channels.OverlappingFileLockException at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255) at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152) at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1063) at java.nio.channels.FileChannel.lock(FileChannel.java:1053) at org.wali.MinimalLockingWriteAheadLog.(MinimalLockingWriteAheadLog.java:179) at org.wali.MinimalLockingWriteAheadLog.(MinimalLockingWriteAheadLog.java:108) at org.apache.nifi.controller.repository.WriteAheadFlowFileRepository.initialize(WriteAheadFlowFileRepository.java:139) at org.apache.nifi.controller.FlowController.createFlowFileRepository(FlowController.java:547) at org.apache.nifi.controller.FlowController.(FlowController.java:411) at org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:360) at org.apache.nifi.controller.scheduling.TestProcessorLifecycle.buildFlowControlle
[jira] [Commented] (NIFI-1749) Test failures when building without access to internet
[
https://issues.apache.org/jira/browse/NIFI-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235103#comment-15235103
]
ASF GitHub Bot commented on NIFI-1749:
--
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/342#issuecomment-208351339
Tests executed successfully without connection to the Internet. +1
> Test failures when building without access to internet
> --
>
> Key: NIFI-1749
> URL: https://issues.apache.org/jira/browse/NIFI-1749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 0.6.0
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Minor
>
> Given the needed dependencies within the Maven local repository, some tests
> will fail without access to the Internet.
> {code}
> testCSSSelectorSyntaxValidator(org.apache.nifi.TestGetHTMLElement) Time
> elapsed: 0.947 sec <<< ERROR!
> java.net.UnknownHostException: www.google.com
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
> at sun.net.www.http.HttpClient.(HttpClient.java:211)
> at sun.net.www.http.HttpClient.New(HttpClient.java:308)
> at sun.net.www.http.HttpClient.New(HttpClient.java:326)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1169)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:512)
> at
> org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:493)
> at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:205)
> at org.jsoup.helper.HttpConnection.get(HttpConnection.java:194)
> at org.jsoup.Jsoup.parse(Jsoup.java:183)
> at
> org.apache.nifi.TestGetHTMLElement.testCSSSelectorSyntaxValidator(TestGetHTMLElement.java:49)
> {code}
> {quote}
> DeleteDynamoDBTest.testStringHashStringRangeDeleteOnlyHashFailure:89 null
> GetDynamoDBTest.testStringHashStringRangeGetOnlyHashFailure:421 null
> PutDynamoDBTest.testStringHashStringRangePutOnlyHashFailure:92 null
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-619) update MonitorActivity processor to be cluster friendly
[ https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235055#comment-15235055 ] Joseph Witt commented on NIFI-619: -- Good point [~ijokarumawak]. I think perhaps we should offer two modes of operation. One mode would apply the monitoring across the whole of the cluster and the other would be independent nodes. Our state management capability supports this distinction. I also agree we must carefully use state management when distributing across the cluster. Probably only write new values every so many seconds or so. > update MonitorActivity processor to be cluster friendly > --- > > Key: NIFI-619 > URL: https://issues.apache.org/jira/browse/NIFI-619 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Brandon DeVries >Priority: Minor > > This processor should be able to be used to monitor activity across the > cluster. In its current state, alerting is based on activity of a single > node, not the entire cluster. > For example, in a 2 node cluster, if system A is getting data from a given > flow and system B is not, system B will alert for lack of activity even > though the flow is functioning "normally". > The ideal behavior would be fore an alert to be generated only if both > systems did not see data in the specified time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (NIFI-619) update MonitorActivity processor to be cluster friendly
[ https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234852#comment-15234852 ] Koji Kawamura edited comment on NIFI-619 at 4/11/16 10:57 AM: -- It maybe ideal to NOT alert when there is less load than the configured cluster capacity, for example in a cluster as written in the description, even if one of two nodes doesn't do any processing at all. However, in an environment that DFM expects every node should receive incoming flow file regularly, each node should report based on its own activity/inactivity. I think it'd be best to add a property named 'Monitor across cluster' (boolean) to indicate whether this processor should check inactivity cluster-wide or individual node. When 'Monitor across cluster' is true, every node update its activity using the cluster level StateProvider. Then the processor running on Primary Node checks cluster-wide inactiveness by checking each node's last activity which is stored on the StateProvider. We should be careful about updating the StateProvider too frequently. It should update StateProvider only when its activeness changes. was (Author: ijokarumawak): It maybe ideal to NOT alert when there is less load than the configured cluster capacity, for example in a cluster as written in the description, even if one of two nodes doesn't do any processing at all. However, in an environment that DFM expects every node should receive incoming flow file regularly, each node should report based on its own activity/inactivity. I think it'd be best to add a property named 'Monitor across cluster' (boolean) to indicate whether this processor should check inactivity cluster-wide or individual node. Additionally, when 'Monitor across cluster' is true, then this processor should be scheduled with 'on Primary Node'. > update MonitorActivity processor to be cluster friendly > --- > > Key: NIFI-619 > URL: https://issues.apache.org/jira/browse/NIFI-619 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Brandon DeVries >Priority: Minor > > This processor should be able to be used to monitor activity across the > cluster. In its current state, alerting is based on activity of a single > node, not the entire cluster. > For example, in a 2 node cluster, if system A is getting data from a given > flow and system B is not, system B will alert for lack of activity even > though the flow is functioning "normally". > The ideal behavior would be fore an alert to be generated only if both > systems did not see data in the specified time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-619) update MonitorActivity processor to be cluster friendly
[ https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234852#comment-15234852 ] Koji Kawamura commented on NIFI-619: It maybe ideal to NOT alert when there is less load than the configured cluster capacity, for example in a cluster as written in the description, even if one of two nodes doesn't do any processing at all. However, in an environment that DFM expects every node should receive incoming flow file regularly, each node should report based on its own activity/inactivity. I think it'd be best to add a property named 'Monitor across cluster' (boolean) to indicate whether this processor should check inactivity cluster-wide or individual node. Additionally, when 'Monitor across cluster' is true, then this processor should be scheduled with 'on Primary Node'. > update MonitorActivity processor to be cluster friendly > --- > > Key: NIFI-619 > URL: https://issues.apache.org/jira/browse/NIFI-619 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Brandon DeVries >Priority: Minor > > This processor should be able to be used to monitor activity across the > cluster. In its current state, alerting is based on activity of a single > node, not the entire cluster. > For example, in a 2 node cluster, if system A is getting data from a given > flow and system B is not, system B will alert for lack of activity even > though the flow is functioning "normally". > The ideal behavior would be fore an alert to be generated only if both > systems did not see data in the specified time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1712) HBaseClientService unable to connect when Phoenix is installed
[ https://issues.apache.org/jira/browse/NIFI-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234786#comment-15234786 ] Guillaume Pool commented on NIFI-1712: -- Ok, so changing the default_realm the HDP.SUPERGRP.NET in the krb5.conf resolved the rest of it. Only have the temp solution for phoenix in at this stage, adding the phoenix-$version-client.jar into the working directory as described by Bryan earlier in this JIRA. Not sure if we can get it added into the standard build or do we need to make some provision for using it when required in a specific environment. Thanks Guys. > HBaseClientService unable to connect when Phoenix is installed > -- > > Key: NIFI-1712 > URL: https://issues.apache.org/jira/browse/NIFI-1712 > Project: Apache NiFi > Issue Type: Bug >Reporter: Bryan Bende >Priority: Minor > > A user reported running HDP 2.3.2 with Phoenix installed, and NiFi 0.6.0, > with the following error: > > 2016-03-31 13:24:23,916 INFO [StandardProcessScheduler Thread-5] > o.a.nifi.hbase.HBase_1_1_2_ClientService > HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] HBase > Security Enabled, logging in as principal n...@hdp.supergrp.net with keytab > /app/env/nifi.keytab > 2016-03-31 13:24:23,984 WARN [StandardProcessScheduler Thread-5] > org.apache.hadoop.util.NativeCodeLoader Unable to load native-hadoop library > for your platform... using builtin-java classes where applicable > 2016-03-31 13:24:24,101 INFO [StandardProcessScheduler Thread-5] > o.a.nifi.hbase.HBase_1_1_2_ClientService > HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] > Successfully logged in as principal n...@hdp.supergrp.net with keytab > /app/env/nifi.keytab > 2016-03-31 13:24:24,177 ERROR [StandardProcessScheduler Thread-5] > o.a.n.c.s.StandardControllerServiceNode > HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] Failed to > invoke @OnEnabled method due to java.io.IOException: > java.lang.reflect.InvocationTargetException > 2016-03-31 13:24:24,182 ERROR [StandardProcessScheduler Thread-5] > o.a.n.c.s.StandardControllerServiceNode > java.io.IOException: java.lang.reflect.InvocationTargetException > at > org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240) > ~[hbase-client-1.1.2.jar:1.1.2] > at > org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218) > ~[hbase-client-1.1.2.jar:1.1.2] > at > org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119) > ~[hbase-client-1.1.2.jar:1.1.2] > at > org.apache.nifi.hbase.HBase_1_1_2_ClientService$1.run(HBase_1_1_2_ClientService.java:215) > ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0] > at > org.apache.nifi.hbase.HBase_1_1_2_ClientService$1.run(HBase_1_1_2_ClientService.java:212) > ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0] > at java.security.AccessController.doPrivileged(Native Method) > ~[na:1.8.0_71] > at javax.security.auth.Subject.doAs(Subject.java:422) ~[na:1.8.0_71] > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1656) > ~[hadoop-common-2.6.2.jar:na] > at > org.apache.nifi.hbase.HBase_1_1_2_ClientService.createConnection(HBase_1_1_2_ClientService.java:212) > ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0] > at > org.apache.nifi.hbase.HBase_1_1_2_ClientService.onEnabled(HBase_1_1_2_ClientService.java:161) > ~[nifi-hbase_1_1_2-client-service-0.6.0.jar:0.6.0] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_71] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_71] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_71] > at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_71] > at > org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137) > ~[na:na] > at > org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125) > ~[na:na] > at > org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70) > ~[na:na] > at > org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47) > ~[na:na] > at > org.apache.nifi.controller.service.StandardControllerServiceNode$1.run(StandardControllerServiceNode.java:285) > ~[na:na] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_71] > at java.util.concurrent.FutureTask.run(FutureTask.java:266
[jira] [Commented] (NIFI-1712) HBaseClientService unable to connect when Phoenix is installed
[
https://issues.apache.org/jira/browse/NIFI-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234614#comment-15234614
]
Guillaume Pool commented on NIFI-1712:
--
the bootstrap log though shows more information:
{noformat}
2016-04-11 09:25:16,559 INFO [NiFi logging handler] org.apache.nifi.StdOut Java
config name: /etc/krb5.conf
2016-04-11 09:25:16,560 INFO [NiFi logging handler] org.apache.nifi.StdOut
Loaded from Java config
2016-04-11 09:25:16,695 INFO [NiFi logging handler] org.apache.nifi.StdOut Java
config name: /etc/krb5.conf
2016-04-11 09:25:16,696 INFO [NiFi logging handler] org.apache.nifi.StdOut
Loaded from Java config
2016-04-11 09:25:16,697 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KdcAccessibility: reset
2016-04-11 09:25:16,697 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KdcAccessibility: reset
2016-04-11 09:25:16,698 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): HDP.SUPERGRP.NET
2016-04-11 09:25:16,699 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): nifi
2016-04-11 09:25:16,699 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTab: load() entry length: 71; type: 18
2016-04-11 09:25:16,699 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): HDP.SUPERGRP.NET
2016-04-11 09:25:16,699 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): nifi
2016-04-11 09:25:16,699 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTab: load() entry length: 55; type: 17
2016-04-11 09:25:16,699 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): HDP.SUPERGRP.NET
2016-04-11 09:25:16,699 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): nifi
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTab: load() entry length: 63; type: 16
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): HDP.SUPERGRP.NET
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): nifi
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTab: load() entry length: 55; type: 23
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): HDP.SUPERGRP.NET
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): nifi
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTab: load() entry length: 47; type: 8
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): HDP.SUPERGRP.NET
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTabInputStream, readName(): nifi
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut >>>
KeyTab: load() entry length: 47; type: 3
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut
Looking for keys for: n...@hdp.supergrp.net
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut
Found unsupported keytype (3) for n...@hdp.supergrp.net
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut
Found unsupported keytype (8) for n...@hdp.supergrp.net
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 23version: 4
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 16version: 4
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 17version: 4
2016-04-11 09:25:16,700 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 18version: 4
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Looking for keys for: n...@hdp.supergrp.net
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Found unsupported keytype (3) for n...@hdp.supergrp.net
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Found unsupported keytype (8) for n...@hdp.supergrp.net
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 23version: 4
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 16version: 4
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 17version: 4
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Added key: 18version: 4
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
Using builtin default etypes for default_tkt_enctypes
2016-04-11 09:25:16,701 INFO [NiFi logging handler] org.apache.nifi.StdOut
default etypes for default_tkt_enctypes: 18 17 16 23.
2016-04-11 09:25:16,702 INFO [NiFi lo
[jira] [Commented] (NIFI-1712) HBaseClientService unable to connect when Phoenix is installed
[
https://issues.apache.org/jira/browse/NIFI-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234600#comment-15234600
]
Guillaume Pool commented on NIFI-1712:
--
Hi,
I added it into the bootstrap before my last post:
{noformat}
# Java command to use when running NiFi
java=java
# Username to use when running NiFi. This value will be ignored on Windows.
run.as=
# Configure where NiFi's lib and conf directories live
lib.dir=./lib
conf.dir=./conf
# How long to wait after telling NiFi to shutdown before explicitly killing the
Process
graceful.shutdown.seconds=20
# Disable JSR 199 so that we can use JSP's without running a JDK
java.arg.1=-Dorg.apache.jasper.compiler.disablejsr199=true
# JVM memory settings
java.arg.2=-Xms512m
java.arg.3=-Xmx16384m
# Enable Remote Debugging
#java.arg.debug=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=80
00
java.arg.4=-Djava.net.preferIPv4Stack=true
# allowRestrictedHeaders is required for Cluster/Node communications to work
pro perly
java.arg.5=-Dsun.net.http.allowRestrictedHeaders=true
java.arg.6=-Djava.protocol.handler.pkgs=sun.net.www.protocol
# Java 7 and below have issues with Code Cache. The following lines allow us to
run well even with
# many classes loaded in the JVM.
#java.arg.7=-XX:ReservedCodeCacheSize=256m
#java.arg.8=-XX:CodeCacheFlushingMinimumFreeSpace=10m
#java.arg.9=-XX:+UseCodeCacheFlushing
#java.arg.11=-XX:PermSize=128M
#java.arg.12=-XX:MaxPermSize=128M
# The G1GC is still considered experimental but has proven to be very
advantageo us in providing
great
# performance without significant "stop-the-world" delays.
#java.arg.13=-XX:+UseG1GC
#Set headless mode by default
java.arg.14=-Djava.awt.headless=true
#Kerberos Config
java.arg.15=-Djava.security.auth.login.config=./conf/zookeeper-jaas.conf
java.arg.16=-Dsun.security.krb5.debug=true
###
# Notification Services for notifying interested parties when NiFi is stopped,
s tarted, dies
###
# XML File that contains the definitions of the notification services
notification.services.file=./conf/bootstrap-notification-services.xml
# In the case that we are unable to send a notification for an event, how many
t imes should we retry?
notification.max.attempts=5
# Comma-separated list of identifiers that are present in the
notification.servi
ces.file; which services should be used to notify when NiFi is started?
#nifi.start.notification.services=email-notification
# Comma-separated list of identifiers that are present in the
notification.servi
ces.file; which services should be used to notify when NiFi is stopped?
#nifi.stop.notification.services=email-notification
# Comma-separated list of identifiers that are present in the
notification.servi
ces.file; which services should be used to notify when NiFi dies?
#nifi.dead.notification.services=email-notification
{noformat}
Arg 16
Here is my zookeeper-jaas.conf
{noformat}
[root@sv-hdpdf1 conf]# cat zookeeper-jaas.conf
Client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
keyTab="/app/env/nifi.keytab"
storeKey=true
useTicketCache=false
principal="n...@hdp.supergrp.net";
};
{noformat}
> HBaseClientService unable to connect when Phoenix is installed
> --
>
> Key: NIFI-1712
> URL: https://issues.apache.org/jira/browse/NIFI-1712
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Bryan Bende
>Priority: Minor
>
> A user reported running HDP 2.3.2 with Phoenix installed, and NiFi 0.6.0,
> with the following error:
>
> 2016-03-31 13:24:23,916 INFO [StandardProcessScheduler Thread-5]
> o.a.nifi.hbase.HBase_1_1_2_ClientService
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2] HBase
> Security Enabled, logging in as principal n...@hdp.supergrp.net with keytab
> /app/env/nifi.keytab
> 2016-03-31 13:24:23,984 WARN [StandardProcessScheduler Thread-5]
> org.apache.hadoop.util.NativeCodeLoader Unable to load native-hadoop library
> for your platform... using builtin-java classes where applicable
> 2016-03-31 13:24:24,101 INFO [StandardProcessScheduler Thread-5]
> o.a.nifi.hbase.HBase_1_1_2_ClientService
> HBase_1_1_2_ClientService[id=e7e9b2ed-d336-34be-acb4-6c8b60c735c2]
> Successfully logged in as principal n...@hdp.supergrp.ne
