[
https://issues.apache.org/jira/browse/KNOX-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated KNOX-970:
-
Status: Patch Available (was: Open)
[^KNOX-970-PR-9-updated-full.patch] is the updated patch with full
[
https://issues.apache.org/jira/browse/KNOX-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated KNOX-970:
-
Status: Open (was: Patch Available)
> Add support for proxying NiFi
> -
>
>
[
https://issues.apache.org/jira/browse/KNOX-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated KNOX-970:
-
Attachment: KNOX-970-PR-9-updated-full.patch
> Add support for proxying NiFi
>
[
https://issues.apache.org/jira/browse/KNOX-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Zampino updated KNOX-1064:
---
Attachment: KNOX-1064-001.patch
Updated the patch (attached KNOX-1064-001.patch) to reflect recent
Just that each requested service can be discovered.
The same logic that would need to determine whether to omit a service from
the generated topology.
On Tue, Sep 26, 2017 at 1:21 PM, Philip Zampino
wrote:
> When you say “descriptor check API”, do you mean validating
[
https://issues.apache.org/jira/browse/KNOX-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep More resolved KNOX-1068.
Resolution: Fixed
> Knox returns HTTP 405 Method Not Allowed error with HTTP HEAD method
>
[
https://issues.apache.org/jira/browse/KNOX-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16181274#comment-16181274
]
ASF subversion and git services commented on KNOX-1068:
---
Commit
When you say “descriptor check API”, do you mean validating only that we can
generate correctly-formed URL(s) for the declared services? Or, are you
proposing further validation of the service components’ configurations?
--
Phil
On 9/26/17, 12:38 PM, "larry mccay" wrote:
Yes, the difference will be a service connectivity error vs a 404 not found
if it isn't in the topology at all.
As for HIVE and cliservice - I have never seen anything other than
cliservice be used there. It seems like it is possible to configure it to
something else though.
There is definitely
Hi Phil -
Thanks for bringing this up for discussion.
I do agree with the descriptor author's intent but at the same time, they
also intend for the others to be available.
There isn't much difference between a topology with a service elements that
can't be reached and one without the service
I’ve been thinking about the behavior wrt topology generation when the URL(s)
for a service declared in a simple descriptor cannot be correctly/completely
determined.
The options available include:
1. Abort the topology generation because we can’t produce what has been
requested.
2.
[
https://issues.apache.org/jira/browse/KNOX-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated KNOX-1067:
--
Attachment: 0001-KNOX-1067-Support-different-signature-algorithms-for.patch
> Support
[
https://issues.apache.org/jira/browse/KNOX-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated KNOX-1067:
--
Status: Patch Available (was: Open)
Please review! Tests added plus a few minor
Colm O hEigeartaigh created KNOX-1067:
-
Summary: Support different signature algorithms for JWTs
Key: KNOX-1067
URL: https://issues.apache.org/jira/browse/KNOX-1067
Project: Apache Knox
14 matches
Mail list logo