[GitHub] nifi pull request #479: NIFI-1937 GetHTTP configurable redirect cookie polic...
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/479#discussion_r66699726
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/GetHTTP.java
---
@@ -197,6 +198,30 @@
.addValidator(StandardValidators.PORT_VALIDATOR)
.build();
+public static final String DEFAULT_COOKIE_POLICY_STR = "default";
+public static final String STANDARD_COOKIE_POLICY_STR = "standard";
+public static final String STRICT_COOKIE_POLICY_STR = "strict";
+public static final String NETSCAPE_COOKIE_POLICY_STR = "netscape";
+public static final String IGNORE_COOKIE_POLICY_STR = "ignore";
+public static final AllowableValue DEFAULT_COOKIE_POLICY = new
AllowableValue(DEFAULT_COOKIE_POLICY_STR, DEFAULT_COOKIE_POLICY_STR,
+"Default cookie policy that provides a higher degree of
compatibility with common cookie management of popular HTTP agents for
non-standard (Netscape style) cookies.");
+public static final AllowableValue STANDARD_COOKIE_POLICY = new
AllowableValue(STANDARD_COOKIE_POLICY_STR, STANDARD_COOKIE_POLICY_STR,
+"RFC 6265 compliant cookie policy (interoperability
profile).");
+public static final AllowableValue STRICT_COOKIE_POLICY = new
AllowableValue(STRICT_COOKIE_POLICY_STR, STRICT_COOKIE_POLICY_STR,
+"RFC 6265 compliant cookie policy (strict profile).");
+public static final AllowableValue NETSCAPE_COOKIE_POLICY = new
AllowableValue(NETSCAPE_COOKIE_POLICY_STR, NETSCAPE_COOKIE_POLICY_STR,
+"Netscape draft compliant cookie policy.");
+public static final AllowableValue IGNORE_COOKIE_POLICY = new
AllowableValue(IGNORE_COOKIE_POLICY_STR, IGNORE_COOKIE_POLICY_STR,
+"A cookie policy that ignores cookies.");
+
+public static final PropertyDescriptor REDIRECT_COOKIE_POLICY = new
PropertyDescriptor.Builder()
+.name("redirect-cookie-policy")
+.displayName("Redirect Cookie Policy")
+.description("When a HTTP server responds to a request with a
redirect, this is the cookie policy used to copy cookies to the following
request.")
+.allowableValues(DEFAULT_COOKIE_POLICY,
STANDARD_COOKIE_POLICY, STRICT_COOKIE_POLICY, NETSCAPE_COOKIE_POLICY,
IGNORE_COOKIE_POLICY)
+.defaultValue(DEFAULT_COOKIE_POLICY_STR)
--- End diff --
I was just about to merge this in, and realized that we might want to have
a different default for 0.x and 1.x. 0.x prior to this had CookieSpecs.STANDARD
set, and this would potentially change behavior without reconfiguring a flow
back to standard, but admittedly, I had no success making a test that worked
with CookieSpecs.STANDARD and broke with CookieSpecs.DEFAULT. @mosermw - how
do you feel about .defaultValue(STANDARD_COOKIE_POLICY_STR) in 0.x for flow
compatibility versus writing a migration note, and
.defaultValue(DEFAULT_COOKIE_POLICY_STR) in 1.x which is what I think a
reasonable default where flow compatibility is less an issue?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi issue #475: - Add Maven profile to compile nifi-hadoop-libraries-nar us...
Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/475 @trixpan @mattyb149 We don't need to aim to cover any or all vendors. If someone wants to submit a patch for whatever vendor's specific distribution they want then that is fine provided all the typical licensing and notice considerations are adhered to. I haven't looked into MapRs licensing for the dependent libraries we need here but if it is compatible with the proper ASF/ASLv2 licensing then great. If not then it should not be included even as a profile. Technically speaking we do not official release binary builds at all. We do provide them as a convenience and we do have to ensure even those binary builds have full valid licensing. The thing we are officially releasing is the source release so yes we could probably 'get away with' leaving the profile in but it seems quite avoidable. If we want to allow someone to augment their hadoop dependent libraries with vendor specific things and we're worried about licensing we could simply have default pure ASF dependency profi le and then let users override the profile using their settings.xml which we can document how to do. But, if MapR or CDH or HDP libraries are valid then anyone can make those available. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #475: - Add Maven profile to compile nifi-hadoop-libraries-nar us...
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/475 MapR against a MapR cluster, the client is ok and I used the same *-site.xml files, although they are notably silent due to the need to install the client. Do I need additional measures to add the libraries (native or not) or client directories (like /opt/mapr/conf) to the environment? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #475: - Add Maven profile to compile nifi-hadoop-libraries-nar us...
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/475 @mattyb149 Having problens with MapR profile against a MapR cluster or with MapR profile against a HDP or CDH cluster? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Nifi in Maven archetypes for Intellij?
Experts, I can create a Nifi Processor or Service on the command line, then open the project in intellij... But Intellij has the ability to do this from the start... I can't seem to find the way, and values, to enter into intellij to allow this to happen... Has anyone been able to crerate a Nifi project in Maven through archetypes in intellij? Thanks! [pat](http://about.me/PatTrainor) ( ͡° ͜ʖ ͡°)
[GitHub] nifi pull request #523: [NIFI-1879] Responsive dialogs and dialog UX refresh
GitHub user scottyaslan opened a pull request: https://github.com/apache/nifi/pull/523 [NIFI-1879] Responsive dialogs and dialog UX refresh You can merge this pull request into a Git repository by running: $ git pull https://github.com/scottyaslan/nifi responsiveDevBranch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/523.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 #523 commit 25a040a6403a981c5f28a08604c6cfa13b42b7ca Author: Scott Aslan Date: 2016-06-10T22:42:38Z [NIFI-1879] Responsive dialogs and dialog UX refresh --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [GitHub] nifi issue #239: Nifi 1540 - AWS Kinesis Get and Put Processors
Ahh just saw this. Will take a look into licensing. On Jun 8, 2016 2:31 PM, "jvwing" wrote: > Github user jvwing commented on the issue: > > https://github.com/apache/nifi/pull/239 > > @joewitt, would you please help us with the licensing/notice > requirements for using the Kinesis Client Library and Kinesis Producer > Library? The Kinesis libraries are licensed under the [Amazon Software > License](https://aws.amazon.com/asl/). This does not appear on the > published [list of Apache-compatible licenses]( > http://www.apache.org/legal/resolved.html#category-a). > > The Apache Spark project includes comparable use of the Kinesis > library, although they have chosen to [present their Kinesis integration as > an optional add-on]( > http://spark.apache.org/docs/latest/streaming-kinesis-integration.html). > Comparable code is in fact [checked into the Spark repo]( > https://github.com/apache/spark/tree/master/external), but I did not find > mention of the ASL in a NOTICE file. I was really hoping to copy and > paste. I found a [JIRA issue raised by the Spark team for the license > discussion](https://issues.apache.org/jira/browse/LEGAL-198) which > discusses the add-on nature of the component, but not specific referencing > language. > > Is this OK? How can we determine what needs to be added to the NOTICE > file in nifi-aws-nar? > > > > --- > If your project is set up for it, you can reply to this email and have your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, please > contact infrastructure at infrastruct...@apache.org or file a JIRA ticket > with INFRA. > --- >
[GitHub] nifi issue #502: Nifi-1972 Apache Ignite Put Cache Processor
Github user mans2singh commented on the issue: https://github.com/apache/nifi/pull/502 Hi @pvillard31 - I've made the changes that you've recommended except for the provenance since I could not find any method to support a collection of flow files. Please let me know if I have missed anything or you have additional suggestions for me. Thanks --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #522: NIFI-2000: Ensure that if we override setters in App...
GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/522 NIFI-2000: Ensure that if we override setters in ApplicationResource ⦠â¦that we call the super class's setter as well You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-2000 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/522.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 #522 commit 54b965dd90d90efd9eae826e73b5c60b761bd2a8 Author: Mark Payne Date: 2016-06-10T21:08:30Z NIFI-2000: Ensure that if we override setters in ApplicationResource that we call the super class's setter as well --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Rate of the data flow is exceeding the provenance recording rate. Slowing down flow to accomodate
What you were seeing was a warning that nifi was intentionally slowing the flow thanks to back pressure from provenance indexing. By switching to volatile thee won't be any back pressure so yes you'll be faster. Thanks Joe On Jun 10, 2016 4:51 PM, "Shaine Berube" < shaine.ber...@perfectsearchcorp.com> wrote: > So will that remove the error then? I'm really trying to remove all the > slow downs in this data flow. > > On Fri, Jun 10, 2016 at 2:23 PM, Joe Witt wrote: > > > Shaine, > > > > You can switch to using volatile/transient provenance storage. To do > > this edit nifi.properties > > > > Find this entry > > > > # Provenance Repository Properties > > > > > nifi.provenance.repository.implementation=org.apache.nifi.provenance.PersistentProvenanceRepository > > > > Change the value to > > > > # Provenance Repository Properties > > > > > nifi.provenance.repository.implementation=org.apache.nifi.provenance.VolatileProvenanceRepository > > > > Restart and you'll have in-memory only provenance for a very small > > number of events. We will add ways to more efficiently index the > > provenance events so that even with full persistence on it will > > support the kinds of usage patterns that can stress the current > > approach. > > > > Thanks > > Joe > > > > On Fri, Jun 10, 2016 at 4:19 PM, Shaine Berube > > wrote: > > > Any way I can stop this error? I mean, I love the provenance > recorder... > > > but I don't care enough about it to slow down the data flow. > > > > > > -- > > > *Shaine Berube* > > > > > > -- > *Shaine Berube* >
Re: Rate of the data flow is exceeding the provenance recording rate. Slowing down flow to accomodate
So will that remove the error then? I'm really trying to remove all the slow downs in this data flow. On Fri, Jun 10, 2016 at 2:23 PM, Joe Witt wrote: > Shaine, > > You can switch to using volatile/transient provenance storage. To do > this edit nifi.properties > > Find this entry > > # Provenance Repository Properties > > nifi.provenance.repository.implementation=org.apache.nifi.provenance.PersistentProvenanceRepository > > Change the value to > > # Provenance Repository Properties > > nifi.provenance.repository.implementation=org.apache.nifi.provenance.VolatileProvenanceRepository > > Restart and you'll have in-memory only provenance for a very small > number of events. We will add ways to more efficiently index the > provenance events so that even with full persistence on it will > support the kinds of usage patterns that can stress the current > approach. > > Thanks > Joe > > On Fri, Jun 10, 2016 at 4:19 PM, Shaine Berube > wrote: > > Any way I can stop this error? I mean, I love the provenance recorder... > > but I don't care enough about it to slow down the data flow. > > > > -- > > *Shaine Berube* > -- *Shaine Berube*
Re: Rate of the data flow is exceeding the provenance recording rate. Slowing down flow to accomodate
Shaine, You can switch to using volatile/transient provenance storage. To do this edit nifi.properties Find this entry # Provenance Repository Properties nifi.provenance.repository.implementation=org.apache.nifi.provenance.PersistentProvenanceRepository Change the value to # Provenance Repository Properties nifi.provenance.repository.implementation=org.apache.nifi.provenance.VolatileProvenanceRepository Restart and you'll have in-memory only provenance for a very small number of events. We will add ways to more efficiently index the provenance events so that even with full persistence on it will support the kinds of usage patterns that can stress the current approach. Thanks Joe On Fri, Jun 10, 2016 at 4:19 PM, Shaine Berube wrote: > Any way I can stop this error? I mean, I love the provenance recorder... > but I don't care enough about it to slow down the data flow. > > -- > *Shaine Berube*
Rate of the data flow is exceeding the provenance recording rate. Slowing down flow to accomodate
Any way I can stop this error? I mean, I love the provenance recorder... but I don't care enough about it to slow down the data flow. -- *Shaine Berube*
[GitHub] nifi issue #477: NIFI-1663: Add ConvertAvroToORC processor
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/477 @omalley Thanks! I updated the version in the POM to 1.1.0 and force-pushed the branch. Hopefully Travis will find the release JARs and complete successfully :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #475: - Add Maven profile to compile nifi-hadoop-libraries-nar us...
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/475 Do you mind filing a Jira case for this, and updating the PR title with the Jira case number? It will make things easier to track, please and thanks! I am having trouble with PutHDFS at the moment, it is hanging forever during the FileSystem.getFileStatus() call. Were you able to run PutHDFS successfully against these JARs? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #521: NIFI-1998: Upgraded Cassandra driver to 3.0.2
GitHub user mattyb149 opened a pull request: https://github.com/apache/nifi/pull/521 NIFI-1998: Upgraded Cassandra driver to 3.0.2 This should apply cleanly to both master and 0.x branches You can merge this pull request into a Git repository by running: $ git pull https://github.com/mattyb149/nifi cassandra3 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/521.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 #521 commit c360c657cea74e8ae79874bedc0b82fcb9b7fc62 Author: Matt Burgess Date: 2016-06-10T19:25:09Z NIFI-1998: Upgraded Cassandra driver to 3.0.2 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #239: Nifi 1540 - AWS Kinesis Get and Put Processors
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/239
@mans2singh thanks for your recent updates, the property descriptor
improvements look good to me.
As far as property descriptors for data size ("10 KB") and duration ("1
minute") - I believe it is possible to let users specify "1 minute" or "5
minutes" while validating the range in milliseconds and retrieving the value in
milliseconds as a long integer. I also understand the value of transparently
passing values through to Kinesis library, and I don't feel strongly about this
either way. Let me know if some sample code would help.
Outstanding issues as I understand them:
* **AWS Processor Base Class** - I do not believe we need to change the
base class hierarchy for all AWS processors as part of this PR. I recommend
merging the code currently in AbstractBaseAWSProcessor into
AbstractKinesisProcessor, and reverting changes to AbstractAWSProcessor.
* **Notice/License text** - We will need to figure out what text is
required in the notice files for the KCL/KPL.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] nifi pull request #520: NIFI-1997: Use the 'autoResumeState' property define...
GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/520 NIFI-1997: Use the 'autoResumeState' property defined in nifi.properties on each node instead of inheriting the property from the Cluster Coordinator Use the 'autoResumeState' property defined in nifi.properties on each node instead of inheriting the property from the Cluster Coordinator You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-1997 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/520.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 #520 commit 8cebe78d8e93694bce847c3e3c38802aa4f701eb Author: Mark Payne Date: 2016-06-10T18:35:47Z NIFI-1996: Fixed bug in the generation of UUID's for components when dealing with Snippets commit 4f997585c3ff4c3997f76f0183ee234032d23251 Author: Mark Payne Date: 2016-06-10T19:16:18Z NIFI-1997: Use the 'autoResumeState' property defined in nifi.properties on each node instead of inheriting the property from the Cluster Coordinator --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #477: NIFI-1663: Add ConvertAvroToORC processor
Github user omalley commented on the issue: https://github.com/apache/nifi/pull/477 The ORC 1.1.0 jars are on Maven Central. :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #519: NIFI-1996: Fixed bug in the generation of UUID's for...
GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/519 NIFI-1996: Fixed bug in the generation of UUID's for components when dealing with Snippets Fixed bug in the generation of UUID's for components when dealing with Snippets You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-1996 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/519.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 #519 commit 8cebe78d8e93694bce847c3e3c38802aa4f701eb Author: Mark Payne Date: 2016-06-10T18:35:47Z NIFI-1996: Fixed bug in the generation of UUID's for components when dealing with Snippets --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #516: NIFI-1993 upgraded CGLIB to 3.2.2
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/516 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #516: NIFI-1993 upgraded CGLIB to 3.2.2
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/516 +1 LGTM, tested #515 with and without this commit, verified the test fails without this commit. Merged to master --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #497: NIFI-1857: HTTPS Site-to-Site
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/497 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #493: NIFI-1037 Created processor that handles HDFS' inotify even...
Github user jjmeyer0 commented on the issue: https://github.com/apache/nifi/pull/493 Sorry for the late response, this week has been a bit crazy. I updated the processor to add all the suggestions (except the filtering update you talked about). I will look into updating the way the processor does filtering, but I have a couple concerns. For example, the comma-separated list of paths won't always work. HDFS directories can technically have commas. Also, I couldn't find an example of how regular expressions work with the expression language. I'm a but curious how'll they'll interact with one another. I'll try to find some time to play around with it this weekend to see. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #501: NIFI-1974 - Support Custom Properties in Expression Languag...
Github user YolandaMDavis commented on the issue: https://github.com/apache/nifi/pull/501 @markap14 per our offline discussion I made changes that provides variable registry via constructors and eliminated the access from the ControllerServiceLookup. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #518: NIFI-1901: Component based access control tests
GitHub user mcgilman opened a pull request: https://github.com/apache/nifi/pull/518 NIFI-1901: Component based access control tests - Building component based access control tests for Connections, Funnels, Labels, Input Ports, Output Ports, Processors, and Process Groups. - Tests for remaining APIs (Queue's, Controller, History, etc) will be coming in a subsequent commit. - Restoring Access Token Endpoint tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mcgilman/nifi NIFI-1901 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/518.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 #518 commit a5fecda5a2ffb35e21d950aa19a07127e19a419e Author: Bryan Rosander Date: 2016-05-27T14:56:02Z NIFI-1975 - Processor for parsing evtx files Signed-off-by: Matt Burgess This closes #492 commit c120c4982d4fc811b06b672e3983b8ca5fb8ae64 Author: Koji Kawamura Date: 2016-06-06T13:19:26Z NIFI-1857: HTTPS Site-to-Site - Enable HTTP(S) for Site-to-Site communication - Support HTTP Proxy in the middle of local and remote NiFi - Support BASIC and DIGEST auth with Proxy Server - Provide 2-phase style commit same as existing socket version - [WIP] Test with the latest cluster env (without NCM) hasn't tested yet - Fixed Buffer handling issues at asyc http client POST - Fixed JS error when applying Remote Process Group Port setting from UI - Use compression setting from UI - Removed already finished TODO comments - Added additional buffer draining code after receiving EOF - Added inspection and assert code to make sure Site-to-Site client has written data fully to output stream - Changed default nifi.remote.input.secure from true to false This closes #497. commit d9dcb46dc4be926275131a5b552dfbd33db4f3ad Author: Matt Gilman Date: 2016-06-10T11:57:02Z NIFI-1901: - Building component based access control tests for Connections, Funnels, Labels, Input Ports, Output Ports, Processors, and Process Groups. - Restoring Access Token Endpoint tests. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
