As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
the latest version of Maven 3.0.x is quite old. (4 years ago)
We need to update dev-support/docker/Dockerfile to enable Maven 3.1+ for
precommit Jenkins job.
Regards,
Akira
On 2017/04/03 18:49, Sunil G wrote:
Hi Folks,
Recent
Nice work Akira! Appreciate the help with trunk development.
On Mon, Apr 3, 2017 at 1:56 AM, Akira Ajisaka wrote:
> Hi folks,
>
> I've created a repository to build and push Apache Hadoop document (trunk)
> via Travis CI.
> https://github.com/aajisaka/hadoop-document
>
> The document is updated
Thanks for digging that up. I agree with your analysis of our public
documentation, though we still need a transition path. Officially, our
classpath is not covered by compatibility, though we know that in reality,
classpath changes are quite impactful to users.
While we were having a related disc
Hi all,
We just released Apache Hadoop 2.8.0 recently [1] but it is not for
production yet due to some issues identified. Now, we should work towards 2.8.1
release which aim for production deployment. The focus obviously is to fix
blocker/critical issues [2], bug-fixes and *no* features / imp
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/365/
[Apr 3, 2017 4:06:54 AM] (aajisaka) MAPREDUCE-6824.
TaskAttemptImpl#createCommonContainerLaunchContext is
-1 overall
The following subsystems voted -1:
asflicense unit
The following subsystems v
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/277/
[Apr 3, 2017 4:06:54 AM] (aajisaka) MAPREDUCE-6824.
TaskAttemptImpl#createCommonContainerLaunchContext is
-1 overall
The following subsystems voted -1:
compile unit
The following subsystems vote
1.0.4:
"Prints the class path needed to get the Hadoop jar and the required
libraries.”
2.8.0 and 3.0.0:
"Prints the class path needed to get the Hadoop jar and the required
libraries. If called without arguments, then prints the classpath set up by the
command scripts, whic
I agreed with Andrew too. Users have relied for years on `hadoop classpath`
for their script to launch jobs or other tools, perhaps no the best idea to
change the behavior without providing a proper deprecation path.
thanks!
esteban.
--
Cloudera, Inc.
On Mon, Apr 3, 2017 at 10:26 AM, Andrew Wan
What's the current contract for `hadoop classpath`? Would it be safer to
introduce `hadoop userclasspath` or similar for this behavior?
I'm betting that changing `hadoop classpath` will lead to some breakages,
so I'd prefer to make this new behavior opt-in.
Best,
Andrew
On Mon, Apr 3, 2017 at 9:
This morning I had a bit of a shower thought:
With the new shaded hadoop client in 3.0, is there any reason the
default classpath should remain the full blown jar list? e.g., shouldn’t
‘hadoop classpath’ just return configuration, user supplied bits (e.g.,
HADOOP_USER_CLASSPAT
[
https://issues.apache.org/jira/browse/MAPREDUCE-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Sasvari resolved MAPREDUCE-6874.
---
Resolution: Won't Fix
> Make DistributedCache check if the content of a directory
Attila Sasvari created MAPREDUCE-6874:
-
Summary: Make DistributedCache check if the content of a directory
has changed
Key: MAPREDUCE-6874
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6874
Hi Folks,
Recently we were doing build framework up-gradation for Yarn Ui. In order
to compile yarn-ui on various architectures, we were using
frontend-maven-plugin 0.0.22 version.
However build is failing in *ppc64le.* If we could use latest version of
frontend-maven-plugin, we could resolve this
Hi folks,
I've created a repository to build and push Apache Hadoop document
(trunk) via Travis CI.
https://github.com/aajisaka/hadoop-document
The document is updated daily by Travis CI cron job.
https://aajisaka.github.io/hadoop-document/hadoop-project/
Hope it helps!
Regards,
Akira
-
14 matches
Mail list logo
