hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miklos Szegedi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14897) Loosen compatibility guidelines for native dependencies
Date Fri, 22 Sep 2017 17:18:01 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176747#comment-16176747

Miklos Szegedi commented on HADOOP-14897:

[~chris.douglas]. Given we are talking about external dependencies, we cannot assume that
they use the same versioning standard. However, talking about Hadoop versioning standard,
I would assume that a minor release requires only minor releases in dependencies. Let's be
more specific with an example. If we ship Hadoop 5.0 with support for C++ standards before
C++14, this requirement would assume that 5.1 will not add a requirement of C++14 as a minimum.
In case of Java I would rephrase this question, would you allow Hadoop 2.9 ship with a requirement
of Java 8, if 2.8 depended on Java 7 before?

> Loosen compatibility guidelines for native dependencies
> -------------------------------------------------------
>                 Key: HADOOP-14897
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14897
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation, native
>            Reporter: Chris Douglas
>            Assignee: Daniel Templeton
>            Priority: Blocker
> Within a major version, the compatibility guidelines forbid raising the minimum required
version of any native dependency or tool required to build native components.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message