[jira] [Created] (HADOOP-13777) Trim configuration values in `rumen`
Tianyin Xu created HADOOP-13777: --- Summary: Trim configuration values in `rumen` Key: HADOOP-13777 URL: https://issues.apache.org/jira/browse/HADOOP-13777 Project: Hadoop Common Issue Type: Bug Components: tools Affects Versions: 3.0.0-alpha1 Reporter: Tianyin Xu Priority: Minor The current implementation of {{ClassName.java}} in {{rumen}} does not follow the practice of trimming configuration values. This leads to silent and hard-to-diagnosis errors if users set values containing space or newline---basically classes supposed to need anonymization will not do. See the previous commits as reference (just list a few): HADOOP-6578. Configuration should trim whitespace around a lot of value types HADOOP-6534. Trim whitespace from directory lists initializing Patch is available against trunk HDFS-9708. FSNamesystem.initAuditLoggers() doesn't trim classnames HDFS-2799. Trim fs.checkpoint.dir values. YARN-3395. FairScheduler: Trim whitespaces when using username for queuename. YARN-2869. CapacityScheduler should trim sub queue names when parse configuration. Patch is available against trunk (tested): {code:title=ClassName.java|borderStyle=solid} @@ -43,15 +43,13 @@ protected String getPrefix() { @Override protected boolean needsAnonymization(Configuration conf) { -String[] preserves = conf.getStrings(CLASSNAME_PRESERVE_CONFIG); -if (preserves != null) { - // do a simple starts with check - for (String p : preserves) { -if (className.startsWith(p)) { - return false; -} +String[] preserves = conf.getTrimmedStrings(CLASSNAME_PRESERVE_CONFIG); +// do a simple starts with check +for (String p : preserves) { + if (className.startsWith(p)) { +return false; } } return true; } {code} (the NULL check is no longer needed because {{getTrimmedStrings}} returns an empty array if nothing is set) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
any suggestions for HADOOP-13773
here is my report https://issues.apache.org/jira/browse/HADOOP-13773 any suggestions?
[jira] [Created] (HADOOP-13776) remove redundant classpath entries in RunJar
Sangjin Lee created HADOOP-13776: Summary: remove redundant classpath entries in RunJar Key: HADOOP-13776 URL: https://issues.apache.org/jira/browse/HADOOP-13776 Project: Hadoop Common Issue Type: Bug Components: util Reporter: Sangjin Lee Assignee: Sangjin Lee Today when you run a "hadoop jar" command, the content of the jar gets added to the classpath twice, once in the jar form, and again in an unpacked form. We should include the content of the jar to the classpath only once. We should keep the jar in the classpath (to support {{setJarByClass}} and other useful use cases) but remove the root of the unpacked directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-13775) KMS Client does not encode key names in the URL path correctly
Xiao Chen created HADOOP-13775: -- Summary: KMS Client does not encode key names in the URL path correctly Key: HADOOP-13775 URL: https://issues.apache.org/jira/browse/HADOOP-13775 Project: Hadoop Common Issue Type: Bug Components: kms Affects Versions: 2.6.0 Reporter: Xiao Chen Assignee: Xiao Chen HADOOP-12962 fixed the KMS server to encode special characters correctly when they're part of the [URI|https://docs.oracle.com/javase/7/docs/api/java/net/URI.html] query. It turns out they can also cause trouble when being the URI path. This time it's the client-side that's broken. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-13774) Rest Loaded App fails
Omar Bouras created HADOOP-13774: Summary: Rest Loaded App fails Key: HADOOP-13774 URL: https://issues.apache.org/jira/browse/HADOOP-13774 Project: Hadoop Common Issue Type: Bug Environment: Hadoop Map Reduce REST Reporter: Omar Bouras Priority: Minor Fix For: 2.7.3 Hello, I am launching an app within a MR REST. This app executes well within Hadoop normal invocation. However, when I use the rest {code} curl -i -X POST -H 'Accept: application/json' -H 'Content-Type: application/json' http://localhost:8088/ws/v1/cluster/apps?user.name=exo -d @app.json {code} 6/10/31 21:42:13 INFO client.RMProxy: Connecting to ResourceManager at /0.0.0.0:8032 16/10/31 21:42:14 INFO input.FileInputFormat: Total input paths to process : 4 16/10/31 21:42:14 INFO mapreduce.JobSubmitter: number of splits:4 16/10/31 21:42:14 INFO mapreduce.JobSubmitter: Submitting tokens for job: job_1477946173138_0003 16/10/31 21:42:14 INFO mapreduce.JobSubmitter: Kind: YARN_AM_RM_TOKEN, Service: , Ident: (appAttemptId { application_id { id: 3 cluster_timestamp: 1477946173138 } attemptId: 1 } keyId: -678745738) 16/10/31 21:42:15 INFO impl.YarnClientImpl: Submitted application application_1477946173138_0003 16/10/31 21:42:15 INFO mapreduce.Job: The url to track the job: http://MEA-029-L:8088/proxy/application_1477946173138_0003/ 16/10/31 21:42:15 INFO mapreduce.Job: Running job: job_1477946173138_0003 16/10/31 21:52:53 INFO mapreduce.Job: Job job_1477946173138_0003 running in uber mode : false 16/10/31 21:52:53 INFO mapreduce.Job: map 0% reduce 0% 16/10/31 21:52:53 INFO mapreduce.Job: Job job_1477946173138_0003 failed with state FAILED due to: Application application_1477946173138_0003 failed 1 times due to ApplicationMaster for attempt appattempt_1477946173138_0003_01 timed out. Failing the application. 16/10/31 21:52:53 INFO mapreduce.Job: Counters: 0 {code} The main job always ends fail with timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Reopened] (HADOOP-10300) Allowed deferred sending of call responses
[ https://issues.apache.org/jira/browse/HADOOP-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang reopened HADOOP-10300: I think this'd be a good addition to branch-2.7; all other subtasks under the umbrella JIRA are actually in 2.3. Attaching a branch-2.7 patch to trigger Jenkins. [~daryn] [~kihwal] LMK if you have any concerns about the backport. > Allowed deferred sending of call responses > -- > > Key: HADOOP-10300 > URL: https://issues.apache.org/jira/browse/HADOOP-10300 > Project: Hadoop Common > Issue Type: Sub-task > Components: ipc >Affects Versions: 2.0.0-alpha, 3.0.0-alpha1 >Reporter: Daryn Sharp >Assignee: Daryn Sharp > Labels: BB2015-05-TBR > Fix For: 2.8.0, 3.0.0-alpha1 > > Attachments: HADOOP-10300-branch-2.7.0.patch, HADOOP-10300.patch, > HADOOP-10300.patch, HADOOP-10300.patch > > > RPC handlers currently do not return until the RPC call completes and > response is sent, or a partially sent response has been queued for the > responder. It would be useful for a proxy method to notify the handler to > not yet the send the call's response. > An potential use case is a namespace handler in the NN might want to return > before the edit log is synced so it can service more requests and allow > increased batching of edits per sync. Background syncing could later trigger > the sending of the call response to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Apache Hadoop qbt Report: trunk+JDK8 on Linux/ppc64le
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/ [Oct 30, 2016 6:52:51 PM] (brahma) HDFS-10455. Logging the username when deny the setOwner operation. [Oct 30, 2016 11:08:20 PM] (naganarasimha_gr) YARN-4498. Application level node labels stats to be available in REST. [Oct 31, 2016 6:17:20 AM] (aajisaka) MAPREDUCE-6799. Document mapreduce.jobhistory.webapp.https.address in -1 overall The following subsystems voted -1: compile unit The following subsystems voted -1 but were configured to be filtered/ignored: cc javac The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: Failed junit tests : hadoop.ha.TestZKFailoverController hadoop.hdfs.server.datanode.TestNNHandlesBlockReportPerStorage hadoop.hdfs.tools.offlineImageViewer.TestOfflineImageViewer hadoop.hdfs.TestRollingUpgrade hadoop.hdfs.web.TestWebHDFS hadoop.hdfs.web.TestWebHdfsTimeouts hadoop.fs.http.client.TestHttpFSFWithSWebhdfsFileSystem hadoop.yarn.server.nodemanager.recovery.TestNMLeveldbStateStoreService hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestLogAggregationService hadoop.yarn.server.nodemanager.TestNodeManagerShutdown hadoop.yarn.server.timeline.TestRollingLevelDB hadoop.yarn.server.timeline.TestTimelineDataManager hadoop.yarn.server.timeline.TestLeveldbTimelineStore hadoop.yarn.server.timeline.recovery.TestLeveldbTimelineStateStore hadoop.yarn.server.timeline.TestRollingLevelDBTimelineStore hadoop.yarn.server.applicationhistoryservice.TestApplicationHistoryServer hadoop.yarn.server.timelineservice.storage.common.TestRowKeys hadoop.yarn.server.timelineservice.storage.common.TestKeyConverters hadoop.yarn.server.timelineservice.storage.common.TestSeparator hadoop.yarn.server.resourcemanager.recovery.TestLeveldbRMStateStore hadoop.yarn.server.resourcemanager.TestRMRestart hadoop.yarn.server.resourcemanager.TestResourceTrackerService hadoop.yarn.server.TestMiniYarnClusterNodeUtilization hadoop.yarn.server.TestContainerManagerSecurity hadoop.yarn.server.timeline.TestLevelDBCacheTimelineStore hadoop.yarn.server.timeline.TestOverrideTimelineStoreYarnClient hadoop.yarn.server.timeline.TestEntityGroupFSTimelineStore hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageApps hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRunCompaction hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineStorageEntities hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowRun hadoop.yarn.server.timelineservice.storage.TestPhoenixOfflineAggregationWriterImpl hadoop.yarn.server.timelineservice.reader.TestTimelineReaderWebServicesHBaseStorage hadoop.yarn.server.timelineservice.storage.flow.TestHBaseStorageFlowActivity hadoop.yarn.applications.distributedshell.TestDistributedShell hadoop.mapred.TestShuffleHandler hadoop.mapreduce.v2.hs.TestHistoryServerLeveldbStateStoreService hadoop.fs.azure.TestNativeAzureFileSystemOperationsMocked Timed out junit tests : org.apache.hadoop.hdfs.server.datanode.TestFsDatasetCache org.apache.hadoop.mapred.TestMRIntermediateDataEncryption org.apache.hadoop.tools.TestHadoopArchives compile: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-compile-root.txt [320K] cc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-compile-root.txt [320K] javac: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-compile-root.txt [320K] unit: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt [124K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [292K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-httpfs.txt [16K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt [52K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-applicationhistoryservice.txt [52K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/141/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-timelineservice.txt
[jira] [Reopened] (HADOOP-9424) The "hadoop jar" invocation should include the passed jar on the classpath as a whole
[ https://issues.apache.org/jira/browse/HADOOP-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee reopened HADOOP-9424: - I would keep this issue open as it still is a real issue. Let's find a way to address this in the best way possible. It is not as urgent as other issues, so we can take some time to think it through. > The "hadoop jar" invocation should include the passed jar on the classpath as > a whole > - > > Key: HADOOP-9424 > URL: https://issues.apache.org/jira/browse/HADOOP-9424 > Project: Hadoop Common > Issue Type: Bug > Components: util >Affects Versions: 2.0.3-alpha >Reporter: Harsh J >Assignee: Harsh J >Priority: Minor > Attachments: HADOOP-9424.patch > > > When you have a case such as this: > {{X.jar -> Classes = Main, Foo}} > {{Y.jar -> Classes = Bar}} > With implementation details such as: > * Main references Bar and invokes a public, static method on it. > * Bar does a class lookup to find Foo (Class.forName("Foo")). > Then when you do a {{HADOOP_CLASSPATH=Y.jar hadoop jar X.jar Main}}, the > Bar's method fails with a ClassNotFound exception cause of the way RunJar > runs. > RunJar extracts the passed jar and includes its contents on the ClassLoader > of its current thread but the {{Class.forName(…)}} call from another class > does not check that class loader and hence cannot find the class as its not > on any classpath it is aware of. > The script of "hadoop jar" should ideally include the passed jar argument to > the CLASSPATH before RunJar is invoked, for this above case to pass. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-13772) ITestS3AContractRootDir still playing up, bug in eventually() retry logic?
[ https://issues.apache.org/jira/browse/HADOOP-13772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-13772. - Resolution: Duplicate Just saw that HADOOP-13713 was still open; this is a duplicate of that. Changes in the test runner which should have fix it, clearly, haven't > ITestS3AContractRootDir still playing up, bug in eventually() retry logic? > -- > > Key: HADOOP-13772 > URL: https://issues.apache.org/jira/browse/HADOOP-13772 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3, test >Affects Versions: 2.9.0 >Reporter: Steve Loughran >Assignee: Steve Loughran > > Just got a transient failure in, {{ITestS3AContractRootDir}}, one which > should have been handled by retrying; maybe the {{LambdaTestUtils}} code > isn't doing its job right. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/ [Oct 30, 2016 6:52:51 PM] (brahma) HDFS-10455. Logging the username when deny the setOwner operation. [Oct 30, 2016 11:08:20 PM] (naganarasimha_gr) YARN-4498. Application level node labels stats to be available in REST. [Oct 31, 2016 6:17:20 AM] (aajisaka) MAPREDUCE-6799. Document mapreduce.jobhistory.webapp.https.address in -1 overall The following subsystems voted -1: asflicense unit The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace The following subsystems are considered long running: (runtime bigger than 1h 0m 0s) unit Specific tests: Failed junit tests : hadoop.security.authentication.client.TestKerberosAuthenticator hadoop.hdfs.TestEncryptionZones hadoop.yarn.server.nodemanager.containermanager.queuing.TestQueuingContainerManager hadoop.yarn.server.TestMiniYarnClusterNodeUtilization hadoop.yarn.server.TestContainerManagerSecurity hadoop.fs.azure.TestNativeAzureFileSystemOperationsMocked Timed out junit tests : org.apache.hadoop.tools.TestHadoopArchives cc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/diff-compile-cc-root.txt [4.0K] javac: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/diff-compile-javac-root.txt [168K] checkstyle: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/diff-checkstyle-root.txt [16M] pylint: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/diff-patch-pylint.txt [16K] shellcheck: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/diff-patch-shellcheck.txt [20K] shelldocs: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/diff-patch-shelldocs.txt [16K] whitespace: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/whitespace-eol.txt [11M] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/whitespace-tabs.txt [1.3M] javadoc: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/diff-javadoc-javadoc-root.txt [2.2M] unit: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-unit-hadoop-common-project_hadoop-auth.txt [12K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt [180K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt [36K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-tests.txt [316K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-nativetask.txt [124K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-unit-hadoop-tools_hadoop-archives.txt [8.0K] https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-unit-hadoop-tools_hadoop-azure.txt [16K] asflicense: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/211/artifact/out/patch-asflicense-problems.txt [4.0K] Powered by Apache Yetus 0.4.0-SNAPSHOT http://yetus.apache.org - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-13773) wrong HADOOP_CLIENT_OPTS in hadoop-env on branch-2
Fei Hui created HADOOP-13773: Summary: wrong HADOOP_CLIENT_OPTS in hadoop-env on branch-2 Key: HADOOP-13773 URL: https://issues.apache.org/jira/browse/HADOOP-13773 Project: Hadoop Common Issue Type: Bug Components: conf Affects Versions: 2.7.3, 2.6.1 Reporter: Fei Hui Fix For: 2.8.0, 2.9.0, 2.7.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-13772) ITestS3AContractRootDir still playing up, bug in eventually() retry logic?
Steve Loughran created HADOOP-13772: --- Summary: ITestS3AContractRootDir still playing up, bug in eventually() retry logic? Key: HADOOP-13772 URL: https://issues.apache.org/jira/browse/HADOOP-13772 Project: Hadoop Common Issue Type: Sub-task Components: fs/s3, test Affects Versions: 2.9.0 Reporter: Steve Loughran Assignee: Steve Loughran Just got a transient failure in, {{ITestS3AContractRootDir}}, one which should have been handled by retrying; maybe the {{LambdaTestUtils}} code isn't doing its job right. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
RE: Updated 2.8.0-SNAPSHOT artifact
Thanks Akira and Karthik for replies. If there is no significant benefit over current branch-2.8 ,re-cutting will be an good idea, As we can reduce the maintenance effort. --Brahma Reddy Battula -Original Message- From: Akira Ajisaka [mailto:ajisa...@oss.nttdata.co.jp] Sent: 31 October 2016 14:06 To: Karthik Kambatla Cc: Brahma Reddy Battula; Vinod Kumar Vavilapalli; common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: Updated 2.8.0-SNAPSHOT artifact Thanks Karthik for the comment. Pros: * (Probably) we can release 2.8.0 earlier. * New feature in 2.8.0 will be available sooner. * We can deprecate APIs sooner. After 2.8.0 is released, we can remove them from trunk. Cons: * Maintenance cost becomes higher because # of branches becomes more. * New feature in 2.9.0 will be available later I'm okay with either releasing current branch-2.8 or re-cutting it. Thoughts? Regards, Akira On 10/26/16 07:30, Karthik Kambatla wrote: > Is there value in releasing current branch-2.8? Aren't we better off > re-cutting the branch off of branch-2? > > On Tue, Oct 25, 2016 at 12:20 AM, Akira Ajisaka > > wrote: > >> It's almost a year since branch-2.8 has cut. >> I'm thinking we need to release 2.8.0 ASAP. >> >> According to the following list, there are 5 blocker and 6 critical issues. >> https://issues.apache.org/jira/issues/?filter=12334985 >> >> Regards, >> Akira >> >> >> On 10/18/16 10:47, Brahma Reddy Battula wrote: >> >>> Hi Vinod, >>> >>> Any plan on first RC for branch-2.8 ? I think, it has been long time. >>> >>> >>> >>> >>> --Brahma Reddy Battula >>> >>> -Original Message- >>> From: Vinod Kumar Vavilapalli [mailto:vino...@apache.org] >>> Sent: 20 August 2016 00:56 >>> To: Jonathan Eagles >>> Cc: common-dev@hadoop.apache.org >>> Subject: Re: Updated 2.8.0-SNAPSHOT artifact >>> >>> Jon, >>> >>> That is around the time when I branched 2.8, so I guess you were >>> getting SNAPSHOT artifacts till then from the branch-2 nightly builds. >>> >>> If you need it, we can set up SNAPSHOT builds. Or just wait for the >>> first RC, which is around the corner. >>> >>> +Vinod >>> >>> On Jul 28, 2016, at 4:27 PM, Jonathan Eagles wrote: Latest snapshot is uploaded in Nov 2015, but checkins are still coming in quite frequently. https://repository.apache.org/content/repositories/snapshots/org/ap ach e/hadoop/hadoop-yarn-api/ Are there any plans to start producing updated SNAPSHOT artifacts for current hadoop development lines? >>> >>> >>> >>> - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org >>> For additional commands, e-mail: common-dev-h...@hadoop.apache.org >>> >>> >>> >>> - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org >>> For additional commands, e-mail: common-dev-h...@hadoop.apache.org >>> >>> >> >> - >> To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org >> >> >