[
https://issues.apache.org/jira/browse/SQOOP-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276035#comment-14276035
]
Abraham Elmahrek commented on SQOOP-1926:
-----------------------------------------
It seems the interfaces are marked as Evolving themselves. I've started a
thread in [email protected] with the subject: "InterfaceStability
and InterfaceAudience stability". I don't think this should stop us from using
these annotations since they've rarely changed in the last 4 years.
I'll send a patch with a proposed API change shortly.
> Sqoop2: Add annotations for visibilty and compatibility guarantees
> ------------------------------------------------------------------
>
> Key: SQOOP-1926
> URL: https://issues.apache.org/jira/browse/SQOOP-1926
> Project: Sqoop
> Issue Type: New Feature
> Reporter: Abraham Elmahrek
> Assignee: Abraham Elmahrek
> Fix For: 1.99.5
>
>
> In Hadoop, there are annotations that describe the visibility of an API and
> its compatibility story:
> {noformat:title=https://github.com/apache/hadoop/blob/branch-2.6/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/Job.java#L76}
> @InterfaceAudience.Public
> @InterfaceStability.Evolving
> {noformat}
> It would be nice to use some thing similar to this (if not the same thing)
> and define our own (or same) compatibility story.
> This lock down the connector APIs and define a better contract about what can
> be modified.
> Reference:
> #
> http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Compatibility.html
> #
> http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/InterfaceClassification.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
