[jira] [Updated] (YARN-2792) Have a public Test-only API for creating important records that ecosystem projects can depend on

2017-01-06 Thread Junping Du (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junping Du updated YARN-2792:
-
Target Version/s:   (was: 2.8.0)

> Have a public Test-only API for creating important records that ecosystem 
> projects can depend on
> 
>
> Key: YARN-2792
> URL: https://issues.apache.org/jira/browse/YARN-2792
> Project: Hadoop YARN
>  Issue Type: Sub-task
>Reporter: Vinod Kumar Vavilapalli
>
> From YARN-2789,
> {quote}
> Sigh.
> Even though this is a private API, it will be used by downstream projects 
> for testing. It'll be useful for this to be re-instated, maybe with a 
> deprecated annotation, so that older versions of downstream projects can 
> build against Hadoop 2.6.
> I am inclined to have a separate test-only public util API that keeps 
> compatibility for tests. Rather than opening unwanted APIs up. I'll file a 
> separate ticket for this, we need all YARN apps/frameworks to move to that 
> API instead of these private unstable APIs.
> For now, I am okay keeping a private compat for the APIs changed in YARN-2698.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org



[jira] [Updated] (YARN-2792) Have a public Test-only API for creating important records that ecosystem projects can depend on

2015-03-12 Thread Wangda Tan (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wangda Tan updated YARN-2792:
-
Priority: Major  (was: Blocker)

 Have a public Test-only API for creating important records that ecosystem 
 projects can depend on
 

 Key: YARN-2792
 URL: https://issues.apache.org/jira/browse/YARN-2792
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Vinod Kumar Vavilapalli

 From YARN-2789,
 {quote}
 Sigh.
 Even though this is a private API, it will be used by downstream projects 
 for testing. It'll be useful for this to be re-instated, maybe with a 
 deprecated annotation, so that older versions of downstream projects can 
 build against Hadoop 2.6.
 I am inclined to have a separate test-only public util API that keeps 
 compatibility for tests. Rather than opening unwanted APIs up. I'll file a 
 separate ticket for this, we need all YARN apps/frameworks to move to that 
 API instead of these private unstable APIs.
 For now, I am okay keeping a private compat for the APIs changed in YARN-2698.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (YARN-2792) Have a public Test-only API for creating important records that ecosystem projects can depend on

2015-03-11 Thread Vinod Kumar Vavilapalli (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod Kumar Vavilapalli updated YARN-2792:
--
Issue Type: Sub-task  (was: Bug)
Parent: YARN-1953

 Have a public Test-only API for creating important records that ecosystem 
 projects can depend on
 

 Key: YARN-2792
 URL: https://issues.apache.org/jira/browse/YARN-2792
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Vinod Kumar Vavilapalli
Priority: Blocker

 From YARN-2789,
 {quote}
 Sigh.
 Even though this is a private API, it will be used by downstream projects 
 for testing. It'll be useful for this to be re-instated, maybe with a 
 deprecated annotation, so that older versions of downstream projects can 
 build against Hadoop 2.6.
 I am inclined to have a separate test-only public util API that keeps 
 compatibility for tests. Rather than opening unwanted APIs up. I'll file a 
 separate ticket for this, we need all YARN apps/frameworks to move to that 
 API instead of these private unstable APIs.
 For now, I am okay keeping a private compat for the APIs changed in YARN-2698.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)