[jira] [Assigned] (NIFI-170) nar-maven-plugin does not have any kind of tests (unit- nor integration tests)
[ https://issues.apache.org/jira/browse/NIFI-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan reassigned NIFI-170: Assignee: (was: Arun Manivannan) > nar-maven-plugin does not have any kind of tests (unit- nor integration tests) > -- > > Key: NIFI-170 > URL: https://issues.apache.org/jira/browse/NIFI-170 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 0.0.1 >Reporter: Karl Heinz Marbaise >Priority: Major > Labels: beginner > > There should be some kind of unit and/or integration tests for the plugin to > check if the plugin does what it should and of course make changes easier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4416) CSVRecordReader does not accept escaped character as delimiter
[ https://issues.apache.org/jira/browse/NIFI-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179555#comment-16179555 ] Arun Manivannan commented on NIFI-4416: --- Thanks a ton, [~jtstorck] Greatly appreciate it. > CSVRecordReader does not accept escaped character as delimiter > -- > > Key: NIFI-4416 > URL: https://issues.apache.org/jira/browse/NIFI-4416 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.2.0 >Reporter: Arun Manivannan >Assignee: Arun Manivannan >Priority: Minor > Fix For: 1.4.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > The CSVReader doesn't accept unicode character as the value delimiter - > \u0001, \t for example. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (NIFI-4416) CSVRecordReader does not accept escaped character as delimiter
[ https://issues.apache.org/jira/browse/NIFI-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan updated NIFI-4416: -- Status: Patch Available (was: In Progress) > CSVRecordReader does not accept escaped character as delimiter > -- > > Key: NIFI-4416 > URL: https://issues.apache.org/jira/browse/NIFI-4416 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.2.0 >Reporter: Arun Manivannan >Assignee: Arun Manivannan >Priority: Minor > Original Estimate: 48h > Remaining Estimate: 48h > > The CSVReader doesn't accept unicode character as the value delimiter - > \u0001, \t for example. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4416) CSVRecordReader does not accept escaped character as delimiter
Arun Manivannan created NIFI-4416: - Summary: CSVRecordReader does not accept escaped character as delimiter Key: NIFI-4416 URL: https://issues.apache.org/jira/browse/NIFI-4416 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.2.0 Reporter: Arun Manivannan Assignee: Arun Manivannan Priority: Minor The CSVReader doesn't accept unicode character as the value delimiter - \u0001, \t for example. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (NIFI-170) nar-maven-plugin does not have any kind of tests (unit- nor integration tests)
[ https://issues.apache.org/jira/browse/NIFI-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan reassigned NIFI-170: Assignee: Arun Manivannan > nar-maven-plugin does not have any kind of tests (unit- nor integration tests) > -- > > Key: NIFI-170 > URL: https://issues.apache.org/jira/browse/NIFI-170 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 0.0.1 >Reporter: Karl Heinz Marbaise >Assignee: Arun Manivannan > Labels: beginner > > There should be some kind of unit and/or integration tests for the plugin to > check if the plugin does what it should and of course make changes easier. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan updated NIFI-4198: -- Affects Version/s: 1.4.0 Status: Patch Available (was: In Progress) > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Andre F de Miranda >Assignee: Arun Manivannan > Attachments: NIFI-4198-ElasticProxy-TestFixtures.pdf, > NIFI-4198-ElasticProxy.xml > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan updated NIFI-4198: -- Attachment: NIFI-4198-ElasticProxy.xml NIFI-4198-ElasticProxy-TestFixtures.pdf > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda >Assignee: Arun Manivannan > Attachments: NIFI-4198-ElasticProxy-TestFixtures.pdf, > NIFI-4198-ElasticProxy.xml > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127497#comment-16127497 ] Arun Manivannan edited comment on NIFI-4198 at 8/15/17 4:38 PM: [~trixpan] Managed to create an integration testing environment for easier testing with squid on docker, as suggested by [~joewitt]. Patch is on the way. https://github.com/arunma/elastic-behind-a-proxy was (Author: arunodhaya80): [~trixpan] Managed to create an integration testing environment for easier testing. Patch is on the way. https://github.com/arunma/elastic-behind-a-proxy > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda >Assignee: Arun Manivannan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127497#comment-16127497 ] Arun Manivannan commented on NIFI-4198: --- [~trixpan] Managed to create an integration testing environment for easier testing. Patch is on the way. https://github.com/arunma/elastic-behind-a-proxy > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda >Assignee: Arun Manivannan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan reassigned NIFI-4198: - Assignee: Arun Manivannan > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda >Assignee: Arun Manivannan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan reopened NIFI-4198: --- > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan resolved NIFI-4198. --- Resolution: Unresolved > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan reassigned NIFI-4198: - Assignee: (was: Arun Manivannan) > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4062) Provide an option to disable DTD validation for EvaluateXPath and EvaluateXQuery
[ https://issues.apache.org/jira/browse/NIFI-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124968#comment-16124968 ] Arun Manivannan commented on NIFI-4062: --- [~joewitt] Apologies. I reset my master branch with upstream without realising that the older PR would be closed automatically. Have made a fresh PR. > Provide an option to disable DTD validation for EvaluateXPath and > EvaluateXQuery > > > Key: NIFI-4062 > URL: https://issues.apache.org/jira/browse/NIFI-4062 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Arun Manivannan > Labels: beginner > > Currently EvaluateXPath and EvaluateXQuery can fail if the source document > has DOCTYPE definition in it, especially using external DTD. It would be > useful if these processor provides a property to disable DTD validation when > evaluate XPath or XQuery. > References: > https://community.hortonworks.com/questions/107121/does-evaluatexpath-support-doctype.html > https://stackoverflow.com/questions/243728/how-to-disable-dtd-at-runtime-in-javas-xpath -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (NIFI-4198) *ElasticsearchHttp processors do not expose Proxy settings
[ https://issues.apache.org/jira/browse/NIFI-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan reassigned NIFI-4198: - Assignee: Arun Manivannan > *ElasticsearchHttp processors do not expose Proxy settings > -- > > Key: NIFI-4198 > URL: https://issues.apache.org/jira/browse/NIFI-4198 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Andre F de Miranda >Assignee: Arun Manivannan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4062) Provide an option to disable DTD validation for EvaluateXPath and EvaluateXQuery
[ https://issues.apache.org/jira/browse/NIFI-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124595#comment-16124595 ] Arun Manivannan commented on NIFI-4062: --- [~joewitt] Sorry about that. Will follow through in my subsequent commits. This is my first contribution. Trying hard to fit myself into the process. > Provide an option to disable DTD validation for EvaluateXPath and > EvaluateXQuery > > > Key: NIFI-4062 > URL: https://issues.apache.org/jira/browse/NIFI-4062 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Arun Manivannan > Labels: beginner > > Currently EvaluateXPath and EvaluateXQuery can fail if the source document > has DOCTYPE definition in it, especially using external DTD. It would be > useful if these processor provides a property to disable DTD validation when > evaluate XPath or XQuery. > References: > https://community.hortonworks.com/questions/107121/does-evaluatexpath-support-doctype.html > https://stackoverflow.com/questions/243728/how-to-disable-dtd-at-runtime-in-javas-xpath -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (NIFI-4062) Provide an option to disable DTD validation for EvaluateXPath and EvaluateXQuery
[ https://issues.apache.org/jira/browse/NIFI-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan updated NIFI-4062: -- Fix Version/s: 1.4.0 Status: Patch Available (was: In Progress) > Provide an option to disable DTD validation for EvaluateXPath and > EvaluateXQuery > > > Key: NIFI-4062 > URL: https://issues.apache.org/jira/browse/NIFI-4062 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Arun Manivannan > Labels: beginner > Fix For: 1.4.0 > > > Currently EvaluateXPath and EvaluateXQuery can fail if the source document > has DOCTYPE definition in it, especially using external DTD. It would be > useful if these processor provides a property to disable DTD validation when > evaluate XPath or XQuery. > References: > https://community.hortonworks.com/questions/107121/does-evaluatexpath-support-doctype.html > https://stackoverflow.com/questions/243728/how-to-disable-dtd-at-runtime-in-javas-xpath -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (NIFI-4062) Provide an option to disable DTD validation for EvaluateXPath and EvaluateXQuery
[ https://issues.apache.org/jira/browse/NIFI-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Manivannan reassigned NIFI-4062: - Assignee: Arun Manivannan > Provide an option to disable DTD validation for EvaluateXPath and > EvaluateXQuery > > > Key: NIFI-4062 > URL: https://issues.apache.org/jira/browse/NIFI-4062 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Arun Manivannan > Labels: beginner > > Currently EvaluateXPath and EvaluateXQuery can fail if the source document > has DOCTYPE definition in it, especially using external DTD. It would be > useful if these processor provides a property to disable DTD validation when > evaluate XPath or XQuery. > References: > https://community.hortonworks.com/questions/107121/does-evaluatexpath-support-doctype.html > https://stackoverflow.com/questions/243728/how-to-disable-dtd-at-runtime-in-javas-xpath -- This message was sent by Atlassian JIRA (v6.4.14#64029)
