[
https://issues.apache.org/jira/browse/HDDS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683379#comment-16683379
]
Elek, Marton commented on HDDS-818:
-----------------------------------
Thanks [~giovanni.fumarola] to file in this issue. While the patch seems to be
safe for me I would like to understand what the problem is exactly. Especially
to avoid problems in the future (and do some testing if possible).
bq. How to reproduce? Using any REST client tool call
ws/v1/cluster/scheduler-conf from select XML as return format.{quote}
I will try it out, but unfortunately It's not clear for me how can I test it
exactly (this is my limitation, I am not familiar enough with yarn). I guess it
could be a GET call without any parameter on the resource manager, hopefully
with the default settings. Is it true?
As I understood this is a name collision on JAXB level but I don't understand
why Yarn has hdds-common jar files on the classpath. Or is it a test with
ozonefs + jar? In that case we can create a robot test to avoid this issue
(not this jira, but long term).
Could you please helm me to understand the issue in more details?
> OzoneConfiguration uses an existing XMLRoot value
> -------------------------------------------------
>
> Key: HDDS-818
> URL: https://issues.apache.org/jira/browse/HDDS-818
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Giovanni Matteo Fumarola
> Priority: Major
> Attachments: HDDS-818.v0.patch
>
>
> OzoneConfiguration and ConfInfo have
> @XmlRootElement(name = "configuration")
> This makes REST Client crash for XML calls.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
