[
https://issues.apache.org/jira/browse/HADOOP-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208606#comment-16208606
]
Daniel Templeton commented on HADOOP-14876:
-------------------------------------------
Thanks, [~steve_l].
bq. add: sometimes things are marked as private...
Excellent point.
bq. We are not in a position to tell people not to use @Private, not given we
consider doing so essential even for basic example yarn apps.
We should file JIRAs to either fixed dist shell or make the private things
public.
bq. What does it mean if something is tagged as LimitedPrivate...
I agree that Limited-Private is an issue. The only way that I can see it
making sense is if it's held to only components of Hadoop itself. Otherwise,
as you say, it's Public. (Of course, depending on how one looks at it, keeping
it within Hadoop isn't any different from Private.) For extra-Hadoop
Limited-Private annotations, I'd file JIRAs to make those interfaces Public.
bq. What does it mean if a release removes/changes something you depended on...
Sure. This falls in line with your first point. I'll add a section on
interacting with the Hadoop community.
bq. L113. yeah right. It's usually the first port of call, & if you think
otherwise, you're not writing enough downstream code.
I know it is, but that's broken. Reading the code creates unnecessary
dependencies on implementation. I'm doing something wrong if I don't
discourage people from reading our code. It's then on us as a community to
provide reasonable alternatives.
bq. the original Compatibility.md calls out that some bits of the system have
non-normative specifications...
I'll take a look and see what I may have trimmed out.
bq. maybe mention StreamCapabilities.hasCapability ...
OK
bq. L160 ...
Good catch.
bq. L189 ...
Uh... Setup logging to go to a file instead of the console?
bq. L208 ...
Good point.
bq. L229 ...
I'll update it.
bq. 298 ...
OK
bq. No statement on supported operating systems...
I left that out because I didn't think it would affect downstream developers
much. If you disagree, I'll add it.
bq. Concurrency ...
What do you mean with concurrency? As a downstream developer experiences
Hadoop's concurrency, I would assume it would just show up as
performance/latency.
> Create downstream developer docs from the compatibility guidelines
> ------------------------------------------------------------------
>
> Key: HADOOP-14876
> URL: https://issues.apache.org/jira/browse/HADOOP-14876
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.0.0-beta1
> Reporter: Daniel Templeton
> Assignee: Daniel Templeton
> Priority: Critical
> Attachments: HADOOP-14876.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
