Duo Zhang created HADOOP-18208:
--
Summary: Remove all the log4j reference in modules other than
hadoop-logging
Key: HADOOP-18208
URL: https://issues.apache.org/jira/browse/HADOOP-18208
Project: Hadoop
Duo Zhang created HADOOP-18207:
--
Summary: Introduce a hadoop-logging module
Key: HADOOP-18207
URL: https://issues.apache.org/jira/browse/HADOOP-18207
Project: Hadoop Common
Issue Type: Sub-task
Duo Zhang created HADOOP-18206:
--
Summary: Cleanup the commons-logging references in the code base
Key: HADOOP-18206
URL: https://issues.apache.org/jira/browse/HADOOP-18206
Project: Hadoop Common
t; wrote:
> >
> > Reload4J has fixed all of those CVEs without requiring an upgrade.
> >
> >> On Jan 20, 2022, at 5:56 AM, Duo Zhang wrote:
> >>
> >> There are 3 new CVEs for log4j1 reported recently[1][2][3]. So I think
> it
> >> is time t
trics come to mind. There may be others.
>
> Thanks,
> Arpit
>
>
> > On Jan 20, 2022, at 5:55 AM, Duo Zhang wrote:
> >
> > There are 3 new CVEs for log4j1 reported recently[1][2][3]. So I think it
> > is time to speed up the migration to log4j2 work[4] now.
>
There are 3 new CVEs for log4j1 reported recently[1][2][3]. So I think it
is time to speed up the migration to log4j2 work[4] now.
You can see the discussion on the jira issue[4], our goal is to fully
migrate to log4j2 and the current most blocking issue is lack of the
"log4j.rootLogger=INFO,Conso
Thank you Ayush.
Let me file an issue.
Ayush Saxena 于2021年10月14日周四 下午1:26写道:
> I can not think of any reason for not including that, If you were able to
> make it work in the other docker images as well. I think that would be
> sufficient enough to try add in the other Dockerfiles.
>
> Checked
The docker images on our trunk are very useful when building the native
code for hadoop, it really helped me a lot.
But when using the Centos 7 image, I found that the final dist does not
have isa-l support, then I realized that only the default Dockerfile(which
is Ubuntu) and the Dockerfile for d
+1 for 100 instead of 80.
I can see that some projects have already changed to 120.
Akira Ajisaka 于2021年5月20日周四 上午10:01写道:
> I'm +1 to allow <= 100 chars.
>
> FYI: There were some discussions long before:
> -
> https://lists.apache.org/thread.html/7813c2f8a49b1d1e7655dad180f2d915a280b2f4d562cfe
Yes, HBase is proposing to bump hadoop versions for new release lines, so
we want to know which release lines are still alive for hadoop.
Thanks.
Wei-Chiu Chuang 于2019年12月26日周四 下午6:59写道:
> Hi!
>
> Duo found out that the last 2.9.x release, 2.9.2 was GA in Nov 2018, which
> is a little more than
+1
Akira Ajisaka 于2019年10月24日周四 下午3:21写道:
> Hi folks,
>
> Both Ozone and Apache Submarine have separate repositories.
> Can we remove these modules from hadoop-trunk?
>
> Regards,
> Akira
>
Duo Zhang created HADOOP-16664:
--
Summary: Backport "HADOOP-16561 [MAPREDUCE] use
protobuf-maven-plugin to generate protobuf classes" to all active branches
Key: HADOOP-16664
URL: https://issues.apach
Duo Zhang created HADOOP-16663:
--
Summary: Backport
Key: HADOOP-16663
URL: https://issues.apache.org/jira/browse/HADOOP-16663
Project: Hadoop Common
Issue Type: Sub-task
Reporter
For HBase we have a separated repo for hbase-thirdparty
https://github.com/apache/hbase-thirdparty
We will publish the artifacts to nexus so we do not need to include
binaries in our git repo, just add a dependency in the pom.
https://mvnrepository.com/artifact/org.apache.hbase.thirdparty/hbase-
[
https://issues.apache.org/jira/browse/HADOOP-16611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HADOOP-16611.
Resolution: Not A Problem
> Make test4tests vote for -0 instead of
Duo Zhang created HADOOP-16611:
--
Summary: Make test4tests vote for -0 instead of -1
Key: HADOOP-16611
URL: https://issues.apache.org/jira/browse/HADOOP-16611
Project: Hadoop Common
Issue Type
Duo Zhang created HADOOP-16610:
--
Summary: Upgrade to yetus 0.11.0 and use emoji vote on github pre
commit
Key: HADOOP-16610
URL: https://issues.apache.org/jira/browse/HADOOP-16610
Project: Hadoop Common
Duo Zhang created HADOOP-16609:
--
Summary: Add Jenkinsfile for all active branches
Key: HADOOP-16609
URL: https://issues.apache.org/jira/browse/HADOOP-16609
Project: Hadoop Common
Issue Type
Duo Zhang created HADOOP-16608:
--
Summary: Improve the github pre commit job
Key: HADOOP-16608
URL: https://issues.apache.org/jira/browse/HADOOP-16608
Project: Hadoop Common
Issue Type
Duo Zhang created HADOOP-16598:
--
Summary: Backport "HADOOP-16558 [COMMON+HDFS] use
protobuf-maven-plugin to generate protobuf classes" to all active branches
Key: HADOOP-16598
URL: https://issues.apach
Duo Zhang created HADOOP-16597:
--
Summary: Backport the protobuf maven plugin change to all active
branches
Key: HADOOP-16597
URL: https://issues.apache.org/jira/browse/HADOOP-16597
Project: Hadoop
The new protobuf plugin related issues have all been pushed to trunk(though
I think we'd better port them to all active branches).
So what's the next step? Shade and relocated protobuf? HBase has already
done this before so I do not think it will take too much time. If we all
agree on the solution
Duo Zhang created HADOOP-16593:
--
Summary: Polish the protobuf plugin for hadoop-yarn-csi
Key: HADOOP-16593
URL: https://issues.apache.org/jira/browse/HADOOP-16593
Project: Hadoop Common
Issue
[
https://issues.apache.org/jira/browse/HADOOP-16559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HADOOP-16559.
Assignee: (was: Duo Zhang)
Resolution: Duplicate
> [HDFS] use protobuf-maven-plugin
I think this one is alread in place so we have to upgrade...
https://issues.apache.org/jira/browse/HADOOP-16557
Wangda Tan 于2019年9月21日周六 上午7:19写道:
> Hi Vinay,
>
> A bit confused, I saw the HADOOP-13363 is still pending. Do we need to
> upgrade protobuf version to 3.7.1 NOW or once HADOOP-13363
As suggested before, please consider switching to maven protobuf plugin
first before upgrading the protobuf dependency.
https://www.xolstice.org/protobuf-maven-plugin/examples/protoc-artifact.html
This plugin will download the protoc binary automatically so we do not need
to have developers inst
OK, the indexing is finished
[Tue Sep 10 14:25:07 UTC 2019] Finished branch indexing. Indexing took 15 min
So maybe 30 minutes is better... And we really should cleanup the stale PRs
and branches...
张铎(Duo Zhang) 于2019年9月10日周二 下午10:20写道:
> Actually the job for testing PR is here...
>
&
nterval, maybe 20 or 30 minutes?
Thanks.
Steve Loughran 于2019年9月10日周二 下午7:36写道:
>
>
> On Tue, Sep 10, 2019 at 9:07 AM 张铎(Duo Zhang)
> wrote:
>
>> Nits: You can change the jenkins job config to not trigger pre commit
>> build
>> for stale PRs if only the base branc
Nits: You can change the jenkins job config to not trigger pre commit build
for stale PRs if only the base branch is changed. By default, either the PR
itself changed, or the base branch is changed, the branch sources plugin
will both trigger a build. You can add a Change requests option, and selec
d, Sep 4, 2019 at 4:39 PM Ayush Saxena wrote:
>
>> Thanx Vinay for the initiative, Makes sense to add support for different
>> architectures.
>>
>> +1, for the branch idea.
>> Good Luck!!!
>>
>> -Ayush
>>
>> > On 03-Sep-2019, at 6:19 AM, 张铎(D
For HBase, we purged all the protobuf related things from the public API,
and then upgraded to a shaded and relocated version of protobuf. We have
created a repo for this:
https://github.com/apache/hbase-thirdparty
But since the hadoop dependencies still pull in the protobuf 2.5 jars, our
coproce
Duo Zhang created HADOOP-16488:
--
Summary: Deprecated JsonSerialization and move it out of
hadoop-common
Key: HADOOP-16488
URL: https://issues.apache.org/jira/browse/HADOOP-16488
Project: Hadoop Common
IIRC we have a 2.8.5 release?
On the download page:
2.8.5 2018 Sep 15
Wei-Chiu Chuang 于2019年7月25日周四 上午9:39写道:
> The last 2.8 release (2.8.4) was made in the last May, more than a year
> ago. https://hadoop.apache.org/old/releases.html
>
> How do folks feel about the fate of branch-2.8? During
Anyway, for HBase, we'd better align our trace library with Hadoop,
especially HDFS. A full trace from the hbase client down to the datanode
will be really helpful for debugging and monitoring.
2018-07-31 6:06 GMT+08:00 Stack :
> There is a healthy discussion going on over in HADOOP-15566 on trac
Started from this build
https://builds.apache.org/job/PreCommit-Admin/329113/
Have dug a bit, it seems that now jira does not allow our query to be run
by unauthorized user, you will get a 400 if you do not login. This is the
error page when accessing
https://issues.apache.org/jira/sr/jira.issue
[
https://issues.apache.org/jira/browse/HADOOP-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HADOOP-13433:
Reopen to attach patches for branch-2.8 and branch-2.7.
> Race in UGI.reloginFromKey
Duo Zhang created HADOOP-13433:
--
Summary: Race in UGI.reloginFromKeytab
Key: HADOOP-13433
URL: https://issues.apache.org/jira/browse/HADOOP-13433
Project: Hadoop Common
Issue Type: Bug
37 matches
Mail list logo