[1/2] nifi git commit: NIFI-1010: If database driver does not support getting table name for column from ResultSetMetadata, then just use a default name

[markap14]

Repository: nifi
Updated Branches:
  refs/heads/master 0fc5d3046 -> d63cd6bd2


NIFI-1010: If database driver does not support getting table name for column 
from ResultSetMetadata, then just use a default name


Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/88fc8d28
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/88fc8d28
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/88fc8d28

Branch: refs/heads/master
Commit: 88fc8d28a0502fa7d2d6646f31cf33e131be
Parents: 22924c6
Author: Mark Payne 
Authored: Sun Oct 18 22:57:04 2015 -0400
Committer: Mark Payne 
Committed: Fri Oct 23 10:25:59 2015 -0400

--
 .../org/apache/nifi/processors/standard/util/JdbcCommon.java   | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/nifi/blob/88fc8d28/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
--
diff --git 
a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
 
b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
index 6fc69ff..753513b 100644
--- 
a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
+++ 
b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
@@ -51,6 +51,7 @@ import org.apache.avro.generic.GenericData;
 import org.apache.avro.generic.GenericDatumWriter;
 import org.apache.avro.generic.GenericRecord;
 import org.apache.avro.io.DatumWriter;
+import org.apache.commons.lang3.StringUtils;
 
 /**
  * JDBC / SQL common functions.
@@ -95,7 +96,10 @@ public class JdbcCommon {
 public static Schema createSchema(final ResultSet rs) throws SQLException {
 final ResultSetMetaData meta = rs.getMetaData();
 final int nrOfColumns = meta.getColumnCount();
-final String tableName = meta.getTableName(1);
+String tableName = meta.getTableName(1);
+if (StringUtils.isBlank(tableName)) {
+tableName = "NiFi_ExecuteSQL_Record";
+}
 
 final FieldAssembler builder = 
SchemaBuilder.record(tableName).namespace("any.data").fields();
 

[2/2] nifi git commit: Merge branch 'NIFI-1010'

[markap14]

Merge branch 'NIFI-1010'


Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/d63cd6bd
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/d63cd6bd
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/d63cd6bd

Branch: refs/heads/master
Commit: d63cd6bd2f9adc3dfc4c7fe168e38081a5b13564
Parents: 0fc5d30 88fc8d2
Author: Mark Payne 
Authored: Fri Oct 23 14:39:16 2015 -0400
Committer: Mark Payne 
Committed: Fri Oct 23 14:39:16 2015 -0400

--
 .../org/apache/nifi/processors/standard/util/JdbcCommon.java   | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/nifi/blob/d63cd6bd/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
--

[jira] [Created] (NIFI-1057) ConvertJSONToSQL fails with OOM

[Randy Gelhausen (JIRA)]

Randy Gelhausen created NIFI-1057:
-

 Summary: ConvertJSONToSQL fails with OOM
 Key: NIFI-1057
 URL: https://issues.apache.org/jira/browse/NIFI-1057
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Reporter: Randy Gelhausen
 Attachments: nifi-app.log.gz

Running NiFi built from master this afternoon, using Java 1.7.0_79 on OSX.

The flow pulls JSON from a web endpoint, splits into about 200 JSON objects 
which are passed to ConvertJSONToSQL and eventually to PutSQL. Based on 
nifi-app.log, ConvertJSONToSQL is causing an OOM.

This same setup works fine on Centos 6.6 with Java 1.8.0_40



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1010) When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse error: Empty: Name

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971573#comment-14971573
 ] 

ASF subversion and git services commented on NIFI-1010:
---

Commit d63cd6bd2f9adc3dfc4c7fe168e38081a5b13564 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d63cd6b ]

Merge branch 'NIFI-1010'


> When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse 
> error: Empty: Name
> --
>
> Key: NIFI-1010
> URL: https://issues.apache.org/jira/browse/NIFI-1010
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3.0
> Environment: MSSqlServer
>Reporter: Scott
>Assignee: Mark Payne
>  Labels: ExecuteSQL, MSSql
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-1010-If-database-driver-does-not-support-gettin.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When using ExecuteSQL with the MSSqlServerDriver from Microsoft you always 
> get a SchemParseException , Empty: Name.
> This is located in / nifi-nar-bundles / nifi-standard-bundle / 
> nifi-standard-processors / src / main / java / org / apache / nifi / 
> processors / standard / util / JdbcCommon.java line 98.
> The line should read: final String tableName = meta.getTableName(1) == "" ? 
> "table" : meta.getTableName(1);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1010) When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse error: Empty: Name

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971572#comment-14971572
 ] 

ASF subversion and git services commented on NIFI-1010:
---

Commit 88fc8d28a0502fa7d2d6646f31cf33e131be in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=88fc8d2 ]

NIFI-1010: If database driver does not support getting table name for column 
from ResultSetMetadata, then just use a default name


> When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse 
> error: Empty: Name
> --
>
> Key: NIFI-1010
> URL: https://issues.apache.org/jira/browse/NIFI-1010
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3.0
> Environment: MSSqlServer
>Reporter: Scott
>Assignee: Mark Payne
>  Labels: ExecuteSQL, MSSql
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-1010-If-database-driver-does-not-support-gettin.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When using ExecuteSQL with the MSSqlServerDriver from Microsoft you always 
> get a SchemParseException , Empty: Name.
> This is located in / nifi-nar-bundles / nifi-standard-bundle / 
> nifi-standard-processors / src / main / java / org / apache / nifi / 
> processors / standard / util / JdbcCommon.java line 98.
> The line should read: final String tableName = meta.getTableName(1) == "" ? 
> "table" : meta.getTableName(1);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-673) Create ListSFTP, FetchSFTP Processors

[Mark Payne (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971609#comment-14971609
 ] 

Mark Payne commented on NIFI-673:
-

[~aldrin] - seems reasonable. I'll add that in really quickly.

Thanks
-mark

> Create ListSFTP, FetchSFTP Processors
> -
>
> Key: NIFI-673
> URL: https://issues.apache.org/jira/browse/NIFI-673
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-673-Initial-implementation-of-ListSFTP-FetchSFT.patch, 
> 0002-NIFI-673-Added-Completion-Strategy-to-FetchSFTP.patch
>
>
> This will allow us to pull a listing from a single primary node and then 
> distribute the work of pulling and processing the data across the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-1010) When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse error: Empty: Name

[Mark Payne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne updated NIFI-1010:
-
Attachment: (was: 
0001-NIFI-1010-If-database-driver-does-not-support-gettin.patch)

> When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse 
> error: Empty: Name
> --
>
> Key: NIFI-1010
> URL: https://issues.apache.org/jira/browse/NIFI-1010
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3.0
> Environment: MSSqlServer
>Reporter: Scott
>Assignee: Mark Payne
>  Labels: ExecuteSQL, MSSql
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-1010-If-database-driver-does-not-support-gettin.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When using ExecuteSQL with the MSSqlServerDriver from Microsoft you always 
> get a SchemParseException , Empty: Name.
> This is located in / nifi-nar-bundles / nifi-standard-bundle / 
> nifi-standard-processors / src / main / java / org / apache / nifi / 
> processors / standard / util / JdbcCommon.java line 98.
> The line should read: final String tableName = meta.getTableName(1) == "" ? 
> "table" : meta.getTableName(1);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-1056) ExecuteSQL fails when trying to pull a NUMERIC value from Oracle database

[Mark Payne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne updated NIFI-1056:
-
Attachment: 0001-NIFI-1056-Do-not-treat-BigDecimal-BigInteger-the-sam.patch

> ExecuteSQL fails when trying to pull a NUMERIC value from Oracle database
> -
>
> Key: NIFI-1056
> URL: https://issues.apache.org/jira/browse/NIFI-1056
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-1056-Do-not-treat-BigDecimal-BigInteger-the-sam.patch
>
>
> We received the following error message from the mailing list:
> 2015-10-20 15:59:59,859 ERROR [Timer-Driven Process Thread-9] 
> o.a.nifi.processors.standard.ExecuteSQL 
> ExecuteSQL[id=f92d313d-fc87-42a9-ac24-ce7d9b6972c9] 
> ExecuteSQL[id=f92d313d-fc87-42a9-ac24-ce7d9b6972c9] failed to process due to 
> org.apache.avro.file.DataFileWriter$AppendWriteException: 
> java.lang.ClassCastException: java.math.BigDecimal cannot be cast to 
> java.lang.CharSequence; rolling back session: 
> org.apache.avro.file.DataFileWriter$AppendWriteException: 
> java.lang.ClassCastException: java.math.BigDecimal cannot be cast to 
> java.lang.CharSequence
> 2015-10-20 15:59:59,860 ERROR [Timer-Driven Process Thread-9] 
> o.a.nifi.processors.standard.ExecuteSQL 
> ExecuteSQL[id=f92d313d-fc87-42a9-ac24-ce7d9b6972c9] 
> ExecuteSQL[id=f92d313d-fc87-42a9-ac24-ce7d9b6972c9] failed to process session 
> due to org.apache.avro.file.DataFileWriter$AppendWriteException: 
> java.lang.ClassCastException: java.math.BigDecimal cannot be cast to 
> java.lang.CharSequence: 
> org.apache.avro.file.DataFileWriter$AppendWriteException: 
> java.lang.ClassCastException: java.math.BigDecimal cannot be cast to 
> java.lang.CharSequence
> 2015-10-20 15:59:59,860 WARN [Timer-Driven Process Thread-9] 
> o.a.nifi.processors.standard.ExecuteSQL 
> ExecuteSQL[id=f92d313d-fc87-42a9-ac24-ce7d9b6972c9] Processor 
> Administratively Yielded for 1 sec due to processing failure
> 2015-10-20 15:59:59,860 WARN [Timer-Driven Process Thread-9] 
> o.a.n.c.t.ContinuallyRunProcessorTask Administratively Yielding 
> ExecuteSQL[id=f92d313d-fc87-42a9-ac24-ce7d9b6972c9] due to uncaught 
> Exception: org.apache.avro.file.DataFileWriter$AppendWriteException: 
> java.lang.ClassCastException: java.math.BigDecimal cannot be cast to 
> java.lang.CharSequence
> 2015-10-20 15:59:59,864 WARN [Timer-Driven Process Thread-9] 
> o.a.n.c.t.ContinuallyRunProcessorTask
> org.apache.avro.file.DataFileWriter$AppendWriteException: 
> java.lang.ClassCastException: java.math.BigDecimal cannot be cast to 
> java.lang.CharSequence
>   at org.apache.avro.file.DataFileWriter.append(DataFileWriter.java:296) 
> ~[na:na]
>   at 
> org.apache.nifi.processors.standard.util.JdbcCommon.convertToAvroStream(JdbcCommon.java:87)
>  ~[na:na]
>   at 
> org.apache.nifi.processors.standard.ExecuteSQL$1.process(ExecuteSQL.java:142) 
> ~[na:na]
>   at 
> org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:1937)
>  ~[nifi-framework-core-0.3.0.jar:0.3.0]
>   at 
> org.apache.nifi.processors.standard.ExecuteSQL.onTrigger(ExecuteSQL.java:136) 
> ~[na:na]
>   at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-0.3.0.jar:0.3.0]
>   at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1077)
>  ~[nifi-framework-core-0.3.0.jar:0.3.0]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:127)
>  [nifi-framework-core-0.3.0.jar:0.3.0]
>   at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:49)
>  [nifi-framework-core-0.3.0.jar:0.3.0]
>   at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:119)
>  [nifi-framework-core-0.3.0.jar:0.3.0]
>   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
> [na:1.7.0_79]
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) 
> [na:1.7.0_79]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>  [na:1.7.0_79]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.7.0_79]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  [na:1.7.0_79]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  [na:1.7.0_79]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
> Caused by: java.lang.ClassCastException: java.math.BigDecimal 

[jira] [Resolved] (NIFI-1029) Need to add a new attriibute to ExecuteSQL to indicate how many rows were selected

[Mark Payne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne resolved NIFI-1029.
--
Resolution: Fixed

> Need to add a new attriibute to ExecuteSQL to indicate how many rows were 
> selected
> --
>
> Key: NIFI-1029
> URL: https://issues.apache.org/jira/browse/NIFI-1029
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.3.0
>Reporter: Scott
>Priority: Critical
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When running a select we need to provide a rows.count attribute so we can 
> detect if there is any data. This will prevent passing no data to the 
> ConvertAvroToJson and getting an error because there is no data.
> Relates too NIFI-972, but I cannot figure out how to add that in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1029) Need to add a new attriibute to ExecuteSQL to indicate how many rows were selected

[Mark Payne (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971205#comment-14971205
 ] 

Mark Payne commented on NIFI-1029:
--

This issue was resolved in NIFI-972; will mark this ticket as Resolved.

> Need to add a new attriibute to ExecuteSQL to indicate how many rows were 
> selected
> --
>
> Key: NIFI-1029
> URL: https://issues.apache.org/jira/browse/NIFI-1029
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.3.0
>Reporter: Scott
>Priority: Critical
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When running a select we need to provide a rows.count attribute so we can 
> detect if there is any data. This will prevent passing no data to the 
> ConvertAvroToJson and getting an error because there is no data.
> Relates too NIFI-972, but I cannot figure out how to add that in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-997) Kerberos tickets are not being renewed by Hadoop

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971006#comment-14971006
 ] 

ASF GitHub Bot commented on NIFI-997:
-

Github user rickysaltzer commented on the pull request:

https://github.com/apache/nifi/pull/97#issuecomment-150578022
  
I agree with you on the tuple within a tuple, it is pretty confusing. I'll 
work on getting these moved into its own class. You're right, error handling is 
a bit tricky in this area of the code in order to avoid breaking API changes. I 
did the division by 1000 since the threshold is in seconds, but I could change 
that. Precision isn't a big deal here since the renewal isn't millisecond (or 
even second) time sensitive. 


> Kerberos tickets are not being renewed by Hadoop
> 
>
> Key: NIFI-997
> URL: https://issues.apache.org/jira/browse/NIFI-997
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Ricky Saltzer
>Assignee: Ricky Saltzer
>
> I've discovered after some time of having kerberos enabled processors, that 
> the kerberos ticket is not being renewed as it should. This is strange 
> because according to HADOOP-6656, this should be automatically taken care of 
> with a utility thread. I examined the NiFi jstack and saw that the renewal 
> thread was present, so I'm not sure what's going on.
> Does NiFi do something with the processor threads that cause child threads to 
> suspend? I have a patch that I'm currently testing (currently looking good), 
> that will renew the kerberos ticket on getFileSystem() if a threshold is 
> reached (e.g. 4 hours). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[4/5] nifi git commit: Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/nifi

[markap14]

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/nifi


Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/5d90c9be
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/5d90c9be
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/5d90c9be

Branch: refs/heads/master
Commit: 5d90c9be07b40455c831e5a602eeeb6660cdd8c6
Parents: bd506b1 a5a5bad
Author: Mark Payne 
Authored: Fri Oct 23 09:52:33 2015 -0400
Committer: Mark Payne 
Committed: Fri Oct 23 09:52:33 2015 -0400

--
 .../nifi/processors/avro/ConvertAvroToJSON.java | 49 ++--
 .../processors/avro/TestConvertAvroToJSON.java  | 47 +--
 2 files changed, 89 insertions(+), 7 deletions(-)
--

[2/5] nifi git commit: NIFI-972 ExecuteSQL bug in createSchema() create Arvo Schema 1

[markap14]

NIFI-972 ExecuteSQL bug in createSchema() create Arvo Schema 1

Signed-off-by: Toivo Adams 
Signed-off-by: Mark Payne 


Project: http://git-wip-us.apache.org/repos/asf/nifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/ba3225fe
Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/ba3225fe
Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/ba3225fe

Branch: refs/heads/master
Commit: ba3225fe92258a6aca3cb706412ab62955914dc8
Parents: da28b81
Author: Toivo Adams 
Authored: Thu Oct 1 17:22:08 2015 +0300
Committer: Mark Payne 
Committed: Fri Oct 23 09:28:03 2015 -0400

--
 .../nifi-standard-processors/pom.xml|   9 ++
 .../processors/standard/util/JdbcCommon.java|  77 --
 .../standard/util/TestJdbcTypesDerby.java   | 137 +
 .../standard/util/TestJdbcTypesH2.java  | 149 +++
 4 files changed, 357 insertions(+), 15 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/nifi/blob/ba3225fe/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml
--
diff --git 
a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml 
b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml
index 2d94981..b0b3afa 100644
--- a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml
+++ b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/pom.xml
@@ -190,6 +190,15 @@ language governing permissions and limitations under the 
License. -->
 derby
 test
 
+
+
+com.h2database
+h2
+1.4.187
+test
+
+  
+
 
 
 

http://git-wip-us.apache.org/repos/asf/nifi/blob/ba3225fe/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
--
diff --git 
a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
 
b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
index 6fc69ff..de3d5d1 100644
--- 
a/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
+++ 
b/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/JdbcCommon.java
@@ -16,15 +16,20 @@
  */
 package org.apache.nifi.processors.standard.util;
 
+import static java.sql.Types.ARRAY;
 import static java.sql.Types.BIGINT;
+import static java.sql.Types.BINARY;
+import static java.sql.Types.BLOB;
 import static java.sql.Types.BOOLEAN;
 import static java.sql.Types.CHAR;
+import static java.sql.Types.CLOB;
 import static java.sql.Types.DATE;
 import static java.sql.Types.DECIMAL;
 import static java.sql.Types.DOUBLE;
 import static java.sql.Types.FLOAT;
 import static java.sql.Types.INTEGER;
 import static java.sql.Types.LONGNVARCHAR;
+import static java.sql.Types.LONGVARBINARY;
 import static java.sql.Types.LONGVARCHAR;
 import static java.sql.Types.NCHAR;
 import static java.sql.Types.NUMERIC;
@@ -35,10 +40,12 @@ import static java.sql.Types.SMALLINT;
 import static java.sql.Types.TIME;
 import static java.sql.Types.TIMESTAMP;
 import static java.sql.Types.TINYINT;
+import static java.sql.Types.VARBINARY;
 import static java.sql.Types.VARCHAR;
 
 import java.io.IOException;
 import java.io.OutputStream;
+import java.nio.ByteBuffer;
 import java.sql.ResultSet;
 import java.sql.ResultSetMetaData;
 import java.sql.SQLException;
@@ -70,17 +77,34 @@ public class JdbcCommon {
 long nrOfRows = 0;
 while (rs.next()) {
 for (int i = 1; i <= nrOfColumns; i++) {
+final int javaSqlType = meta.getColumnType(i);
 final Object value = rs.getObject(i);
 
-// The different types that we support are numbers (int, 
long, double, float),
-// as well as boolean values and Strings. Since Avro 
doesn't provide
-// timestamp types, we want to convert those to Strings. 
So we will cast anything other
-// than numbers or booleans to strings by using to 
toString() method.
 if (value == null) {
 rec.put(i - 1, null);
+
+} else if (javaSqlType==BINARY || javaSqlType==VARBINARY 
|| javaSqlType==LONGVARBINARY || javaSqlType==ARRAY || javaSqlType==BLOB || 
javaSqlType==CLOB) {
+

[jira] [Commented] (NIFI-972) ExecuteSQL bug in createSchema() create Arvo Schema method

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971051#comment-14971051
 ] 

ASF subversion and git services commented on NIFI-972:
--

Commit bd506b1e10ebc2ce025e836f83cb0f77562deba4 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=bd506b1 ]

NIFI-972: Added additional unit test; deleted lines that were commented out


> ExecuteSQL bug in createSchema() create Arvo Schema method
> --
>
> Key: NIFI-972
> URL: https://issues.apache.org/jira/browse/NIFI-972
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Toivo Adams
>Assignee: Toivo Adams
> Fix For: 0.4.0
>
> Attachments: NIFI-972_23oct2015.patch, nifi-972_01oct2015.patch
>
>
> Jonathan Lyons reported:
> Just getting started with NiFi here. I am attempting to run a static query
> in MySQL using the ExecuteSQL processor. It is set to run on a 5 second
> interval. Since ExecuteSQL appears to need an input flow file I'm using a
> GenerateFlowFile processor to produce a random file every 5 seconds.
> Unfortunately, I'm getting a very vague ArrayIndexOutOfBounds exception
> when I hit play on the flow:
> java.lang.ArrayIndexOutOfBoundsException: 8
> at org.apache.avro.generic.GenericData$Record.put(GenericData.java:129)
> at org.apache.nifi.processors.standard.util.JdbcCommon.convertToAvroStream
> at
> org.apache.nifi.processors.standard.ExecuteSQL$1.process(ExecuteSQL.java:141)
> It’s seem to be bug in createSchema() which creates Arvo schema.
> When createSchema() will encounter unknown type, no Arvo column info will be 
> created. And Arvo schema has less columns than ResultSet row…



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-972) ExecuteSQL bug in createSchema() create Arvo Schema method

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971049#comment-14971049
 ] 

ASF subversion and git services commented on NIFI-972:
--

Commit ba3225fe92258a6aca3cb706412ab62955914dc8 in nifi's branch 
refs/heads/master from [~Toivo Adams]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ba3225f ]

NIFI-972 ExecuteSQL bug in createSchema() create Arvo Schema 1

Signed-off-by: Toivo Adams 
Signed-off-by: Mark Payne 


> ExecuteSQL bug in createSchema() create Arvo Schema method
> --
>
> Key: NIFI-972
> URL: https://issues.apache.org/jira/browse/NIFI-972
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Toivo Adams
>Assignee: Toivo Adams
> Fix For: 0.4.0
>
> Attachments: NIFI-972_23oct2015.patch, nifi-972_01oct2015.patch
>
>
> Jonathan Lyons reported:
> Just getting started with NiFi here. I am attempting to run a static query
> in MySQL using the ExecuteSQL processor. It is set to run on a 5 second
> interval. Since ExecuteSQL appears to need an input flow file I'm using a
> GenerateFlowFile processor to produce a random file every 5 seconds.
> Unfortunately, I'm getting a very vague ArrayIndexOutOfBounds exception
> when I hit play on the flow:
> java.lang.ArrayIndexOutOfBoundsException: 8
> at org.apache.avro.generic.GenericData$Record.put(GenericData.java:129)
> at org.apache.nifi.processors.standard.util.JdbcCommon.convertToAvroStream
> at
> org.apache.nifi.processors.standard.ExecuteSQL$1.process(ExecuteSQL.java:141)
> It’s seem to be bug in createSchema() which creates Arvo schema.
> When createSchema() will encounter unknown type, no Arvo column info will be 
> created. And Arvo schema has less columns than ResultSet row…



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-1055) Build of master branch fails due to contrib-check violations

[Mark Payne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne resolved NIFI-1055.
--
Resolution: Fixed
  Assignee: Mark Payne

> Build of master branch fails due to contrib-check violations
> 
>
> Key: NIFI-1055
> URL: https://issues.apache.org/jira/browse/NIFI-1055
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.4.0
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-925) Upgrade to Hadoop 2.7.1

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971009#comment-14971009
 ] 

ASF GitHub Bot commented on NIFI-925:
-

Github user busbey commented on the pull request:

https://github.com/apache/nifi/pull/83#issuecomment-150578536
  
On the one hand, I prefer to engage hadoop-as-it-is rather than waiting for 
changes.

On the other hand, 2.6.2 RC0 closes in 5 days, so figure about a week for 
there to be artifacts presuming it passes?

2.6.1 has the critical problems fixed (like corrupting data when writing to 
HDFS encrypted directories), so I'd rather upgrade to it now and then go to 
2.6.2 if/when it gets released.


> Upgrade to Hadoop 2.7.1
> ---
>
> Key: NIFI-925
> URL: https://issues.apache.org/jira/browse/NIFI-925
> Project: Apache NiFi
>  Issue Type: Task
>Reporter: Jean-Baptiste Onofré
>Priority: Trivial
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-972) ExecuteSQL bug in createSchema() create Arvo Schema method

[Mark Payne (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971053#comment-14971053
 ] 

Mark Payne commented on NIFI-972:
-

[~Toivo Adams] - much appreciate you knocking this out! It's been merged into 
master.

Thanks
-Mark

> ExecuteSQL bug in createSchema() create Arvo Schema method
> --
>
> Key: NIFI-972
> URL: https://issues.apache.org/jira/browse/NIFI-972
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Toivo Adams
>Assignee: Toivo Adams
> Fix For: 0.4.0
>
> Attachments: NIFI-972_23oct2015.patch, nifi-972_01oct2015.patch
>
>
> Jonathan Lyons reported:
> Just getting started with NiFi here. I am attempting to run a static query
> in MySQL using the ExecuteSQL processor. It is set to run on a 5 second
> interval. Since ExecuteSQL appears to need an input flow file I'm using a
> GenerateFlowFile processor to produce a random file every 5 seconds.
> Unfortunately, I'm getting a very vague ArrayIndexOutOfBounds exception
> when I hit play on the flow:
> java.lang.ArrayIndexOutOfBoundsException: 8
> at org.apache.avro.generic.GenericData$Record.put(GenericData.java:129)
> at org.apache.nifi.processors.standard.util.JdbcCommon.convertToAvroStream
> at
> org.apache.nifi.processors.standard.ExecuteSQL$1.process(ExecuteSQL.java:141)
> It’s seem to be bug in createSchema() which creates Arvo schema.
> When createSchema() will encounter unknown type, no Arvo column info will be 
> created. And Arvo schema has less columns than ResultSet row…



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-1010) When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse error: Empty: Name

[Aldrin Piri (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971301#comment-14971301
 ] 

Aldrin Piri commented on NIFI-1010:
---

Reviewed this using an RDS instance of SQL Server and verified the associated 
functionality before and after the patch.  Behavior is as anticipated as 
outlined in the discussion.  Build and contrib were good.  +1.

> When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse 
> error: Empty: Name
> --
>
> Key: NIFI-1010
> URL: https://issues.apache.org/jira/browse/NIFI-1010
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3.0
> Environment: MSSqlServer
>Reporter: Scott
>Assignee: Mark Payne
>  Labels: ExecuteSQL, MSSql
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-1010-If-database-driver-does-not-support-gettin.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When using ExecuteSQL with the MSSqlServerDriver from Microsoft you always 
> get a SchemParseException , Empty: Name.
> This is located in / nifi-nar-bundles / nifi-standard-bundle / 
> nifi-standard-processors / src / main / java / org / apache / nifi / 
> processors / standard / util / JdbcCommon.java line 98.
> The line should read: final String tableName = meta.getTableName(1) == "" ? 
> "table" : meta.getTableName(1);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-673) Create ListSFTP, FetchSFTP Processors

[Aldrin Piri (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971449#comment-14971449
 ] 

Aldrin Piri commented on NIFI-673:
--

Reviewed this again.  This patch sequence certainly made much more sense and 
looks good.  Build and contrib all passed.

+1 overall.

I would like to see actual user name of the account that was used to list the 
files (the username property of the processor configuration) from ListSFTP make 
it into the attributes.  We currently have file owner in terms of ID, so the 
actual name seems to make sense as well.  With that change, we could 
additionally have FetchSFTP make its username property support Expression 
Language and give a bit more flexibility in that retrieval process.  Understood 
that password likely isn't feasible, but, with appropriate system and key 
configuration, there is some nice utility that is provided.  Thoughts?

> Create ListSFTP, FetchSFTP Processors
> -
>
> Key: NIFI-673
> URL: https://issues.apache.org/jira/browse/NIFI-673
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-673-Initial-implementation-of-ListSFTP-FetchSFT.patch, 
> 0002-NIFI-673-Added-Completion-Strategy-to-FetchSFTP.patch
>
>
> This will allow us to pull a listing from a single primary node and then 
> distribute the work of pulling and processing the data across the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-1058) Update documentation for switch from nifi.content.repository.archive.enabled defaulting to true

[Joseph Witt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Witt updated NIFI-1058:
--
Fix Version/s: 0.4.0

> Update documentation for switch from nifi.content.repository.archive.enabled 
> defaulting to true
> ---
>
> Key: NIFI-1058
> URL: https://issues.apache.org/jira/browse/NIFI-1058
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 0.3.0
>Reporter: Aldrin Piri
>Priority: Minor
> Fix For: 0.4.0
>
>
> There was a switch from 0.2.0 to 0.3.0 to make 
> nifi.content.repository.archive.enabled default to true.  This needs updating 
> at least in the Administration Guide.  If this was not captured in the 
> release notes, this should be additionally highlighted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-673) Create ListSFTP, FetchSFTP Processors

[Mark Payne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne updated NIFI-673:

Attachment: 0001-NIFI-673-Added-sftp.listing.user-attribute-to-FlowFi.patch

> Create ListSFTP, FetchSFTP Processors
> -
>
> Key: NIFI-673
> URL: https://issues.apache.org/jira/browse/NIFI-673
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-673-Added-sftp.listing.user-attribute-to-FlowFi.patch, 
> 0001-NIFI-673-Initial-implementation-of-ListSFTP-FetchSFT.patch, 
> 0002-NIFI-673-Added-Completion-Strategy-to-FetchSFTP.patch
>
>
> This will allow us to pull a listing from a single primary node and then 
> distribute the work of pulling and processing the data across the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-997) Kerberos tickets are not being renewed by Hadoop

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971736#comment-14971736
 ] 

ASF GitHub Bot commented on NIFI-997:
-

Github user rickysaltzer commented on the pull request:

https://github.com/apache/nifi/pull/97#issuecomment-150675281
  
I don't think we would have NPE'd because of the order that getFileSystem() 
ends up being called, but it's good to take care of anyway just in case. 


> Kerberos tickets are not being renewed by Hadoop
> 
>
> Key: NIFI-997
> URL: https://issues.apache.org/jira/browse/NIFI-997
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Ricky Saltzer
>Assignee: Ricky Saltzer
>
> I've discovered after some time of having kerberos enabled processors, that 
> the kerberos ticket is not being renewed as it should. This is strange 
> because according to HADOOP-6656, this should be automatically taken care of 
> with a utility thread. I examined the NiFi jstack and saw that the renewal 
> thread was present, so I'm not sure what's going on.
> Does NiFi do something with the processor threads that cause child threads to 
> suspend? I have a patch that I'm currently testing (currently looking good), 
> that will renew the kerberos ticket on getFileSystem() if a threshold is 
> reached (e.g. 4 hours). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-1059) NiFi cluster node commands timeout. Must manually kill process.

[Matthew Clarke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthew Clarke updated NIFI-1059:
-
Summary: NiFi cluster node commands timeout.  Must manually kill process.  
(was: NiFi cluster node commands time.  Must manually kill process.)

> NiFi cluster node commands timeout.  Must manually kill process.
> 
>
> Key: NIFI-1059
> URL: https://issues.apache.org/jira/browse/NIFI-1059
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.3.0
>Reporter: Matthew Clarke
>Priority: Minor
>
> I had a NiFi cluster Node deliberately configured to use a unsigned/untrusted 
> keystore.  When I tried tried to join it to my cluster, i got the expected 
> javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated errors.  The 
> problem I did not expect is that I could no longer issue commands to the 
> cluster Node nifi.sh (stop, restart, or dump).
> STOP Command:
> ERROR [main] org.apache.nifi.bootstrap.Command Failed to send shutdown 
> command to port 43821 due to java.net.SocketTimeoutException: Read timed out
> java.net.SocketTimeoutException: Read timed out
>   at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.7.0_85]
>   at java.net.SocketInputStream.read(SocketInputStream.java:152) 
> ~[na:1.7.0_85]
>   at java.net.SocketInputStream.read(SocketInputStream.java:122) 
> ~[na:1.7.0_85]
>   at java.net.SocketInputStream.read(SocketInputStream.java:210) 
> ~[na:1.7.0_85]
>   at org.apache.nifi.bootstrap.RunNiFi.stop(RunNiFi.java:647) 
> [nifi-bootstrap-1.0.0.0-7.jar:1.0.0.0-7]
>   at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:206) 
> [nifi-bootstrap-1.0.0.0-7.jar:1.0.0.0-7]
> DUMP Command:
> Exception in thread "main" java.net.SocketTimeoutException: Read timed out
>   at java.net.SocketInputStream.socketRead0(Native Method)
>   at java.net.SocketInputStream.read(SocketInputStream.java:152)
>   at java.net.SocketInputStream.read(SocketInputStream.java:122)
>   at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
>   at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
>   at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
>   at java.io.InputStreamReader.read(InputStreamReader.java:184)
>   at java.io.BufferedReader.fill(BufferedReader.java:154)
>   at java.io.BufferedReader.readLine(BufferedReader.java:317)
>   at java.io.BufferedReader.readLine(BufferedReader.java:382)
>   at org.apache.nifi.bootstrap.RunNiFi.dump(RunNiFi.java:583)
>   at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:216)
> I was forced to manually kill the NiFi process to stop it.
> After installing the good keystore, the Node started and joined the cluster 
> as expected. I was able to successfully issue stop, restart, and dump 
> commands at this time as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-1059) NiFi cluster node commands time. Must manually kill process.

[Matthew Clarke (JIRA)]

Matthew Clarke created NIFI-1059:


 Summary: NiFi cluster node commands time.  Must manually kill 
process.
 Key: NIFI-1059
 URL: https://issues.apache.org/jira/browse/NIFI-1059
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 0.3.0
Reporter: Matthew Clarke
Priority: Minor


I had a NiFi cluster Node deliberately configured to use a unsigned/untrusted 
keystore.  When I tried tried to join it to my cluster, i got the expected 
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated errors.  The 
problem I did not expect is that I could no longer issue commands to the 
cluster Node nifi.sh (stop, restart, or dump).

STOP Command:
ERROR [main] org.apache.nifi.bootstrap.Command Failed to send shutdown command 
to port 43821 due to java.net.SocketTimeoutException: Read timed out
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.7.0_85]
at java.net.SocketInputStream.read(SocketInputStream.java:152) 
~[na:1.7.0_85]
at java.net.SocketInputStream.read(SocketInputStream.java:122) 
~[na:1.7.0_85]
at java.net.SocketInputStream.read(SocketInputStream.java:210) 
~[na:1.7.0_85]
at org.apache.nifi.bootstrap.RunNiFi.stop(RunNiFi.java:647) 
[nifi-bootstrap-1.0.0.0-7.jar:1.0.0.0-7]
at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:206) 
[nifi-bootstrap-1.0.0.0-7.jar:1.0.0.0-7]

DUMP Command:
Exception in thread "main" java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:152)
at java.net.SocketInputStream.read(SocketInputStream.java:122)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:154)
at java.io.BufferedReader.readLine(BufferedReader.java:317)
at java.io.BufferedReader.readLine(BufferedReader.java:382)
at org.apache.nifi.bootstrap.RunNiFi.dump(RunNiFi.java:583)
at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:216)

I was forced to manually kill the NiFi process to stop it.
After installing the good keystore, the Node started and joined the cluster as 
expected. I was able to successfully issue stop, restart, and dump commands at 
this time as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-997) Kerberos tickets are not being renewed by Hadoop

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972260#comment-14972260
 ] 

ASF GitHub Bot commented on NIFI-997:
-

Github user trkurc commented on the pull request:

https://github.com/apache/nifi/pull/97#issuecomment-150736369
  
My kerberos hadoop vm has gone south. I've got to rebuild it.


> Kerberos tickets are not being renewed by Hadoop
> 
>
> Key: NIFI-997
> URL: https://issues.apache.org/jira/browse/NIFI-997
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Ricky Saltzer
>Assignee: Ricky Saltzer
>
> I've discovered after some time of having kerberos enabled processors, that 
> the kerberos ticket is not being renewed as it should. This is strange 
> because according to HADOOP-6656, this should be automatically taken care of 
> with a utility thread. I examined the NiFi jstack and saw that the renewal 
> thread was present, so I'm not sure what's going on.
> Does NiFi do something with the processor threads that cause child threads to 
> suspend? I have a patch that I'm currently testing (currently looking good), 
> that will renew the kerberos ticket on getFileSystem() if a threshold is 
> reached (e.g. 4 hours). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

svn commit: r10899 - in /release/nifi: 0.0.1-incubating/ 0.0.2-incubating/ 0.1.0-incubating/ 0.2.0-incubating/ nifi-nar-maven-plugin-1.0.0-incubating/

[joewitt]

Author: joewitt
Date: Sat Oct 24 01:44:56 2015
New Revision: 10899

Log:
NIFI-961

Removed:
release/nifi/0.0.1-incubating/
release/nifi/0.0.2-incubating/
release/nifi/0.1.0-incubating/
release/nifi/0.2.0-incubating/
release/nifi/nifi-nar-maven-plugin-1.0.0-incubating/

svn commit: r10900 - /release/nifi/0.2.1/

[joewitt]

Author: joewitt
Date: Sat Oct 24 01:45:57 2015
New Revision: 10900

Log:
NIFI-961

Removed:
release/nifi/0.2.1/

[jira] [Commented] (NIFI-961) Please delete old releases from mirroring system

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972269#comment-14972269
 ] 

ASF subversion and git services commented on NIFI-961:
--

Commit 1710297 from [~joewitt] in branch 'site/trunk'
[ https://svn.apache.org/r1710297 ]

NIFI-961

> Please delete old releases from mirroring system
> 
>
> Key: NIFI-961
> URL: https://issues.apache.org/jira/browse/NIFI-961
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Joseph Witt
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases? i.e. all except 0.2.1
> The earlier releases can still be mentioned on the download page, but the 
> links should point to the archive server, i.e.
> http://archive.apache.org/dist/nifi/
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

nifi-site git commit: NIFI-961

[joewitt]

Repository: nifi-site
Updated Branches:
  refs/heads/master 04c4d00ac -> a08e1236f


NIFI-961


Project: http://git-wip-us.apache.org/repos/asf/nifi-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi-site/commit/a08e1236
Tree: http://git-wip-us.apache.org/repos/asf/nifi-site/tree/a08e1236
Diff: http://git-wip-us.apache.org/repos/asf/nifi-site/diff/a08e1236

Branch: refs/heads/master
Commit: a08e1236ffb5e148024c042df41bccdd2da23b71
Parents: 04c4d00
Author: joewitt 
Authored: Fri Oct 23 21:56:26 2015 -0400
Committer: joewitt 
Committed: Fri Oct 23 21:56:26 2015 -0400

--
 src/pages/html/download.hbs | 26 +++---
 1 file changed, 3 insertions(+), 23 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/nifi-site/blob/a08e1236/src/pages/html/download.hbs
--
diff --git a/src/pages/html/download.hbs b/src/pages/html/download.hbs
index bc9b93a..7050641 100644
--- a/src/pages/html/download.hbs
+++ b/src/pages/html/download.hbs
@@ -48,40 +48,20 @@ title: Apache NiFi Downloads
 
 Sources:
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.1/nifi-0.2.1-source-release.zip;>nifi-0.2.1-source-release.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-source-release.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-source-release.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-source-release.zip.sha1;>sha1
 )
+https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip;>nifi-0.2.1-source-release.zip
 ( https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip.asc;>asc,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip.md5;>md5,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip.sha1;>sha1
 )
 
 
 
 Binaries
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.1/nifi-0.2.1-bin.tar.gz;>nifi-0.2.1-bin.tar.gz
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.sha1;>sha1
 )
+https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz;>nifi-0.2.1-bin.tar.gz
 ( https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.asc;>asc,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.md5;>md5,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.sha1;>sha1
 )
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.1/nifi-0.2.1-bin.zip;>nifi-0.2.1-bin.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.zip.sha1;>sha1
 )
+https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip;>nifi-0.2.1-bin.zip
 ( https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip.asc;>asc,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip.md5;>md5,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip.sha1;>sha1
 )
 
 
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.2.1;>Release
 Notes


-0.2.0-incubating
-
-   Note: This release is considered unstable due to https://issues.apache.org/jira/browse/NIFI-777>NIFI-777.
-   This will be addressed in 0.2.1.
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12332286;>Release
 Notes
-
-Sources:
-
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip;>nifi-0.2.0-incubating-source-release.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip.sha1;>sha1
 )
-
-
-   

svn commit: r1710297 - /nifi/site/trunk/download.html

[joewitt]

Author: joewitt
Date: Sat Oct 24 01:57:17 2015
New Revision: 1710297

URL: http://svn.apache.org/viewvc?rev=1710297=rev
Log:
NIFI-961

Modified:
nifi/site/trunk/download.html

Modified: nifi/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/download.html?rev=1710297=1710296=1710297=diff
==
--- nifi/site/trunk/download.html (original)
+++ nifi/site/trunk/download.html Sat Oct 24 01:57:17 2015
@@ -140,40 +140,20 @@
 
 Sources:
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.1/nifi-0.2.1-source-release.zip;>nifi-0.2.1-source-release.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-source-release.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-source-release.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-source-release.zip.sha1;>sha1
 )
+https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip;>nifi-0.2.1-source-release.zip
 ( https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip.asc;>asc,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip.md5;>md5,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-source-release.zip.sha1;>sha1
 )
 
 
 
 Binaries
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.1/nifi-0.2.1-bin.tar.gz;>nifi-0.2.1-bin.tar.gz
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.sha1;>sha1
 )
+https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz;>nifi-0.2.1-bin.tar.gz
 ( https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.asc;>asc,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.md5;>md5,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.tar.gz.sha1;>sha1
 )
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.1/nifi-0.2.1-bin.zip;>nifi-0.2.1-bin.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.1/nifi-0.2.1-bin.zip.sha1;>sha1
 )
+https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip;>nifi-0.2.1-bin.zip
 ( https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip.asc;>asc,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip.md5;>md5,
 https://archive.apache.org/dist/nifi/0.2.1/nifi-0.2.1-bin.zip.sha1;>sha1
 )
 
 
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.2.1;>Release
 Notes


-0.2.0-incubating
-
-   Note: This release is considered unstable due to https://issues.apache.org/jira/browse/NIFI-777>NIFI-777.
-   This will be addressed in 0.2.1.
-https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12332286;>Release
 Notes
-
-Sources:
-
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip;>nifi-0.2.0-incubating-source-release.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-source-release.zip.sha1;>sha1
 )
-
-
-
-Binaries
-
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.0-incubating/nifi-0.2.0-incubating-bin.tar.gz;>nifi-0.2.0-incubating-bin.tar.gz
 ( https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-bin.tar.gz.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-bin.tar.gz.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.2.0-incubating/nifi-0.2.0-incubating-bin.tar.gz.sha1;>sha1
 )
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.2.0-incubating/nifi-0.2.0-incubating-bin.zip;>nifi-0.2.0-incubating-bin.zip
 ( 

[jira] [Commented] (NIFI-960) Hashes, keys and sigs must be downloaded from the ASF mirror source

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972277#comment-14972277
 ] 

ASF subversion and git services commented on NIFI-960:
--

Commit 1710298 from [~joewitt] in branch 'site/trunk'
[ https://svn.apache.org/r1710298 ]

NIFI-960

> Hashes, keys and sigs must be downloaded from the ASF mirror source
> ---
>
> Key: NIFI-960
> URL: https://issues.apache.org/jira/browse/NIFI-960
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Joseph Witt
>
> The download page links to KEYS, hashes and sigs, which is good.
> However, it links to the release area in SVN, which is the wrong place.
> They should be downloaded from the ASF mirror source which is
> http://www.apache.org/dist/nifi
> The www.apache.org systems are set up for higher traffic levels and are 
> mirrored in EU and US.
> The SVN dist system is not intended for downloading files by 3rd parties - it 
> is the staging area from which the main ASF hosts are populated.
> Please update the download page to correct the links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-960) Hashes, keys and sigs must be downloaded from the ASF mirror source

[Joseph Witt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Witt resolved NIFI-960.
--
Resolution: Fixed

> Hashes, keys and sigs must be downloaded from the ASF mirror source
> ---
>
> Key: NIFI-960
> URL: https://issues.apache.org/jira/browse/NIFI-960
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Joseph Witt
>
> The download page links to KEYS, hashes and sigs, which is good.
> However, it links to the release area in SVN, which is the wrong place.
> They should be downloaded from the ASF mirror source which is
> http://www.apache.org/dist/nifi
> The www.apache.org systems are set up for higher traffic levels and are 
> mirrored in EU and US.
> The SVN dist system is not intended for downloading files by 3rd parties - it 
> is the staging area from which the main ASF hosts are populated.
> Please update the download page to correct the links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

svn commit: r1710298 - /nifi/site/trunk/download.html

[joewitt]

Author: joewitt
Date: Sat Oct 24 02:13:37 2015
New Revision: 1710298

URL: http://svn.apache.org/viewvc?rev=1710298=rev
Log:
NIFI-960

Modified:
nifi/site/trunk/download.html

Modified: nifi/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/download.html?rev=1710298=1710297=1710298=diff
==
--- nifi/site/trunk/download.html (original)
+++ nifi/site/trunk/download.html Sat Oct 24 02:13:37 2015
@@ -121,15 +121,15 @@
 
 Sources:
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.3.0/nifi-0.3.0-source-release.zip;>nifi-0.3.0-source-release.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-source-release.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-source-release.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-source-release.zip.sha1;>sha1
 )
+https://www.apache.org/dyn/closer.lua?path=/nifi/0.3.0/nifi-0.3.0-source-release.zip;>nifi-0.3.0-source-release.zip
 ( https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-source-release.zip.asc;>asc,
 https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-source-release.zip.md5;>md5,
 https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-source-release.zip.sha1;>sha1
 )
 
 
 
 Binaries
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.3.0/nifi-0.3.0-bin.tar.gz;>nifi-0.3.0-bin.tar.gz
 ( https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-bin.tar.gz.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-bin.tar.gz.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-bin.tar.gz.sha1;>sha1
 )
+https://www.apache.org/dyn/closer.lua?path=/nifi/0.3.0/nifi-0.3.0-bin.tar.gz;>nifi-0.3.0-bin.tar.gz
 ( https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-bin.tar.gz.asc;>asc,
 https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-bin.tar.gz.md5;>md5,
 https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-bin.tar.gz.sha1;>sha1
 )
 
-https://www.apache.org/dyn/closer.lua?path=/nifi/0.3.0/nifi-0.3.0-bin.zip;>nifi-0.3.0-bin.zip
 ( https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-bin.zip.asc;>asc,
 https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-bin.zip.md5;>md5,
 https://dist.apache.org/repos/dist/release/nifi/0.3.0/nifi-0.3.0-bin.zip.sha1;>sha1
 )
+https://www.apache.org/dyn/closer.lua?path=/nifi/0.3.0/nifi-0.3.0-bin.zip;>nifi-0.3.0-bin.zip
 ( https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-bin.zip.asc;>asc, 
https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-bin.zip.md5;>md5, 
https://www.apache.org/dist/nifi/0.3.0/nifi-0.3.0-bin.zip.sha1;>sha1 
)
 
 
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.3.0;>Release
 Notes

[jira] [Commented] (NIFI-960) Hashes, keys and sigs must be downloaded from the ASF mirror source

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972282#comment-14972282
 ] 

ASF subversion and git services commented on NIFI-960:
--

Commit 1710299 from [~joewitt] in branch 'site/trunk'
[ https://svn.apache.org/r1710299 ]

NIFI-960 updating release guidance to capture NIFI-960 and NIFI-961 feedback

> Hashes, keys and sigs must be downloaded from the ASF mirror source
> ---
>
> Key: NIFI-960
> URL: https://issues.apache.org/jira/browse/NIFI-960
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Joseph Witt
>
> The download page links to KEYS, hashes and sigs, which is good.
> However, it links to the release area in SVN, which is the wrong place.
> They should be downloaded from the ASF mirror source which is
> http://www.apache.org/dist/nifi
> The www.apache.org systems are set up for higher traffic levels and are 
> mirrored in EU and US.
> The SVN dist system is not intended for downloading files by 3rd parties - it 
> is the staging area from which the main ASF hosts are populated.
> Please update the download page to correct the links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-961) Please delete old releases from mirroring system

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972283#comment-14972283
 ] 

ASF subversion and git services commented on NIFI-961:
--

Commit 1710299 from [~joewitt] in branch 'site/trunk'
[ https://svn.apache.org/r1710299 ]

NIFI-960 updating release guidance to capture NIFI-960 and NIFI-961 feedback

> Please delete old releases from mirroring system
> 
>
> Key: NIFI-961
> URL: https://issues.apache.org/jira/browse/NIFI-961
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Joseph Witt
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases? i.e. all except 0.2.1
> The earlier releases can still be mentioned on the download page, but the 
> links should point to the archive server, i.e.
> http://archive.apache.org/dist/nifi/
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

svn commit: r1710299 - /nifi/site/trunk/release-guide.html

[joewitt]

Author: joewitt
Date: Sat Oct 24 02:20:04 2015
New Revision: 1710299

URL: http://svn.apache.org/viewvc?rev=1710299=rev
Log:
NIFI-960 updating release guidance to capture NIFI-960 and NIFI-961 feedback

Modified:
nifi/site/trunk/release-guide.html

Modified: nifi/site/trunk/release-guide.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/release-guide.html?rev=1710299=1710298=1710299=diff
==
--- nifi/site/trunk/release-guide.html (original)
+++ nifi/site/trunk/release-guide.html Sat Oct 24 02:20:04 2015
@@ -318,7 +318,7 @@ Now all the voting is done and the relea
 
 Merge the release branch into master
 
-Update the NiFi website to point to the new download(s)
+Update the NiFi website to point to the new download(s).  Remove older 
release artifacts from download page (leave the current release and the 
previous one).  For the release just previous to this new one change the links 
to point to the archive location.  See current page as an example of the needed 
URL changes.  In addition to updating the download page as described delete 
artifacts other than the current/new release from the dist/nifi SVN storage.  
They are already in the archive location so no need to do anything else.
 
 Update the https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance;>Migration
 Guide on the Wiki.
 

[jira] [Commented] (NIFI-1010) When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse error: Empty: Name

[Andrew Grande (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971061#comment-14971061
 ] 

Andrew Grande commented on NIFI-1010:
-

On the patch - isn't smth like StringUtils.isBlank() be better?

> When using MSSqlServer Driver with ExecuteSQL always recieve Avro parse 
> error: Empty: Name
> --
>
> Key: NIFI-1010
> URL: https://issues.apache.org/jira/browse/NIFI-1010
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.3.0
> Environment: MSSqlServer
>Reporter: Scott
>Assignee: Mark Payne
>  Labels: ExecuteSQL, MSSql
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-1010-If-database-driver-does-not-support-gettin.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When using ExecuteSQL with the MSSqlServerDriver from Microsoft you always 
> get a SchemParseException , Empty: Name.
> This is located in / nifi-nar-bundles / nifi-standard-bundle / 
> nifi-standard-processors / src / main / java / org / apache / nifi / 
> processors / standard / util / JdbcCommon.java line 98.
> The line should read: final String tableName = meta.getTableName(1) == "" ? 
> "table" : meta.getTableName(1);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-997) Kerberos tickets are not being renewed by Hadoop

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971088#comment-14971088
 ] 

ASF GitHub Bot commented on NIFI-997:
-

Github user rickysaltzer commented on the pull request:

https://github.com/apache/nifi/pull/97#issuecomment-150593718
  
I will squash these changes before we commit. Keeping a revision history in 
this pull request for clarity. 


> Kerberos tickets are not being renewed by Hadoop
> 
>
> Key: NIFI-997
> URL: https://issues.apache.org/jira/browse/NIFI-997
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Ricky Saltzer
>Assignee: Ricky Saltzer
>
> I've discovered after some time of having kerberos enabled processors, that 
> the kerberos ticket is not being renewed as it should. This is strange 
> because according to HADOOP-6656, this should be automatically taken care of 
> with a utility thread. I examined the NiFi jstack and saw that the renewal 
> thread was present, so I'm not sure what's going on.
> Does NiFi do something with the processor threads that cause child threads to 
> suspend? I have a patch that I'm currently testing (currently looking good), 
> that will renew the kerberos ticket on getFileSystem() if a threshold is 
> reached (e.g. 4 hours). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-961) Please delete old releases from mirroring system

[Joseph Witt (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972175#comment-14972175
 ] 

Joseph Witt commented on NIFI-961:
--

doh - my bad.  Will do tonight

> Please delete old releases from mirroring system
> 
>
> Key: NIFI-961
> URL: https://issues.apache.org/jira/browse/NIFI-961
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Joseph Witt
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases? i.e. all except 0.2.1
> The earlier releases can still be mentioned on the download page, but the 
> links should point to the archive server, i.e.
> http://archive.apache.org/dist/nifi/
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-994) Processor to tail files

[Mark Payne (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972213#comment-14972213
 ] 

Mark Payne commented on NIFI-994:
-

All,

I uploaded an initial implementation of TailFile. Please feel free to try 
out/test/review and provide any feedback. We can iterate as necessary.

Thanks
-Mark

> Processor to tail files
> ---
>
> Key: NIFI-994
> URL: https://issues.apache.org/jira/browse/NIFI-994
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 0.4.0
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments: 0001-NIFI-994-Initial-import-of-TailFile.patch
>
>
> It's a very common data ingest situation to want to input text into the 
> system by "tailing" a file, most commonly log files. Currently we don't have 
> an easy way to do this. 
> A simple processor to tail a file would benefit many users. There would need 
> to be an option to not just tail a file but pick up where the processor left 
> off if it is interrupted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-994) Processor to tail files

[Mark Payne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne updated NIFI-994:

Attachment: 0001-NIFI-994-Initial-import-of-TailFile.patch

> Processor to tail files
> ---
>
> Key: NIFI-994
> URL: https://issues.apache.org/jira/browse/NIFI-994
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 0.4.0
>Reporter: Joseph Percivall
>Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments: 0001-NIFI-994-Initial-import-of-TailFile.patch
>
>
> It's a very common data ingest situation to want to input text into the 
> system by "tailing" a file, most commonly log files. Currently we don't have 
> an easy way to do this. 
> A simple processor to tail a file would benefit many users. There would need 
> to be an option to not just tail a file but pick up where the processor left 
> off if it is interrupted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-1061) DBConnectionPool service unable to terminate

[Randy Gelhausen (JIRA)]

Randy Gelhausen created NIFI-1061:
-

 Summary: DBConnectionPool service unable to terminate
 Key: NIFI-1061
 URL: https://issues.apache.org/jira/browse/NIFI-1061
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Randy Gelhausen
 Fix For: 0.4.0


I had a defined flow with an enabled DBConnectionPool using the 
phoenix-client.jar driver. After stopping the NiFi process and restarting it, 
the connection pool is unable to reconnect. Attempting to disable the pool 
never completes the operation. See attached screenshot & nifi-app.log file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-1061) DBConnectionPool service unable to terminate

[Randy Gelhausen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Randy Gelhausen updated NIFI-1061:
--
Attachment: nifi-app.log.gz
Screen Shot 2015-10-23 at 7.17.31 PM.png

> DBConnectionPool service unable to terminate
> 
>
> Key: NIFI-1061
> URL: https://issues.apache.org/jira/browse/NIFI-1061
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Randy Gelhausen
> Fix For: 0.4.0
>
> Attachments: Screen Shot 2015-10-23 at 7.17.31 PM.png, nifi-app.log.gz
>
>
> I had a defined flow with an enabled DBConnectionPool using the 
> phoenix-client.jar driver. After stopping the NiFi process and restarting it, 
> the connection pool is unable to reconnect. Attempting to disable the pool 
> never completes the operation. See attached screenshot & nifi-app.log file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-961) Please delete old releases from mirroring system

[Sebb (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972012#comment-14972012
 ] 

Sebb commented on NIFI-961:
---

PING

The directory at
https://dist.apache.org/repos/dist/release/nifi/
still contains multiple releases; it should only contain the latest active 
release.

Please delete all the incubating releases, plus 0.2.1

> Please delete old releases from mirroring system
> 
>
> Key: NIFI-961
> URL: https://issues.apache.org/jira/browse/NIFI-961
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Joseph Witt
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases? i.e. all except 0.2.1
> The earlier releases can still be mentioned on the download page, but the 
> links should point to the archive server, i.e.
> http://archive.apache.org/dist/nifi/
> Thanks!
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-673) Create ListSFTP, FetchSFTP Processors

[Aldrin Piri (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972018#comment-14972018
 ] 

Aldrin Piri commented on NIFI-673:
--

Awesome, looks good.  +1

> Create ListSFTP, FetchSFTP Processors
> -
>
> Key: NIFI-673
> URL: https://issues.apache.org/jira/browse/NIFI-673
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 0.4.0
>
> Attachments: 
> 0001-NIFI-673-Added-sftp.listing.user-attribute-to-FlowFi.patch, 
> 0001-NIFI-673-Initial-implementation-of-ListSFTP-FetchSFT.patch, 
> 0002-NIFI-673-Added-Completion-Strategy-to-FetchSFTP.patch
>
>
> This will allow us to pull a listing from a single primary node and then 
> distribute the work of pulling and processing the data across the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)