[
https://issues.apache.org/jira/browse/KNOX-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Gupta updated KNOX-413:
-
Attachment: KNOX-413.patch
> Yarn responses with TrackingUrl in the body not getting blanked out
> -
[
https://issues.apache.org/jira/browse/KNOX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Minder updated KNOX-419:
--
Assignee: Sumit Gupta
> WebHdfs HA loses original error after failover/retry limit is reached
> --
[
https://issues.apache.org/jira/browse/KNOX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118980#comment-14118980
]
Kevin Minder commented on KNOX-419:
---
commit f0af8bd6ca966319a234c83a8527245442cb
Autho
[
https://issues.apache.org/jira/browse/KNOX-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118962#comment-14118962
]
Kevin Minder commented on KNOX-349:
---
Commit 02d9b39d77cf2256fe318980d0f5fee4b4b3e96e contr
[
https://issues.apache.org/jira/browse/KNOX-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Minder updated KNOX-349:
--
Attachment: KNOX-349-4.patch
Contributed by Zachary Blanco
> Knox API for Topology Management
> -
[
https://issues.apache.org/jira/browse/KNOX-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Minder updated KNOX-349:
--
Attachment: (was: KNOX-349-4.patch)
> Knox API for Topology Management
> -
[
https://issues.apache.org/jira/browse/KNOX-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118959#comment-14118959
]
ASF subversion and git services commented on KNOX-349:
--
Commit 02d9b39d
[
https://issues.apache.org/jira/browse/KNOX-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Gupta updated KNOX-419:
-
Attachment: KNOX-419.patch
> WebHdfs HA loses original error after failover/retry limit is reached
> ---
Thanks for the questions.
Yes, that is exactly what I was proposing - I want to make it extremely
easy to copy without much chance for messing up:
cp -r demo/conf conf
is all that we would have to do.
We could move it under templates (samples aren't the same thing) and it
would look like:
cp -
Can you be a bit more specific about what you are considering doing in
the source tree? Are you saying that you will be adding these directories:
gateway-release/home/demo
gateway-release/home/demo/conf
My only concern is that we already have these:
gateway-release/home/templates
gateway-rele
Sumit Gupta created KNOX-419:
Summary: WebHdfs HA loses original error after failover/retry
limit is reached
Key: KNOX-419
URL: https://issues.apache.org/jira/browse/KNOX-419
Project: Apache Knox
All -
In order to describe the installation of a production deployment vs a demo
deployment, I would like to separate the out-of-the-box install from demo
setup.
Currently, when you unpack the knox archive, the conf directory includes a
couple artifacts that are demo specific and are not likely r
All,
We will be branching for 0.5.0 at the end of today (9/2) if there are no
objections.
Once that is done, all changes for 0.5.0 will need to be made first on
master and then picked into the 0.5.0 branch.
Let me know if you have any questions or concerns about this.
--larry
13 matches
Mail list logo
