Akira Ajisaka created HADOOP-16454:
--
Summary: Share delegation tokens between multiple HttpFS servers
Key: HADOOP-16454
URL: https://issues.apache.org/jira/browse/HADOOP-16454
Project: Hadoop Common
Hi Junping
My team and I work for helping more open source projects run on ARM server,
foucs on big data projects in this stage, like: Hadoop, Spark, Flink and so
on,
I would like to share a topic about it with local community, include:
current progress, faced issue and future plan.
Thank you hol
Lisheng Sun created HADOOP-16453:
Summary: Remove useless trace log in NetUtils.java
Key: HADOOP-16453
URL: https://issues.apache.org/jira/browse/HADOOP-16453
Project: Hadoop Common
Issue Typ
Wei-Chiu Chuang created HADOOP-16452:
Summary: Increase ipc.maximum.data.length default from 64MB to
128MB
Key: HADOOP-16452
URL: https://issues.apache.org/jira/browse/HADOOP-16452
Project: Hadoop
a word of caution. according to INFRA-18748, asf infra is going to be
cutting out blind PR building. So we'll need to be sure that precommit
integration works e.g. testing PRs because there's a JIRA that a
whitelisted contributor has associated and put in patch available
status.
On Mon, Jul 22, 20
[
https://issues.apache.org/jira/browse/HADOOP-16380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-16380.
-
Resolution: Fixed
Fixed -thanks for help in testing this
> S3A tombstones can confuse
Wei-Chiu Chuang created HADOOP-16451:
Summary: Update jackson-databind to 2.9.9.1
Key: HADOOP-16451
URL: https://issues.apache.org/jira/browse/HADOOP-16451
Project: Hadoop Common
Issue Ty
Steve Loughran created HADOOP-16450:
---
Summary: ITestS3ACommitterFactory failing, S3 client is not
inconsistent
Key: HADOOP-16450
URL: https://issues.apache.org/jira/browse/HADOOP-16450
Project: Hado
Thanks Wei-Chiu for starting this discussion.
+1 (non-binding) for turning code review to GitHub PR and keep other
comments/discussions on JIRA.
1. In my experience, JIRA is better at tracking and recording information.
2. It is confused that no guide (`How to contribute`) about submit PR to
JIRA
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/391/
[Jul 23, 2019 1:36:43 AM] (aajisaka) MAPREDUCE-7076.
TestNNBench#testNNBenchCreateReadAndDelete failing in
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit
Although we will use github with PRs, I'd still prefer adding a +1 as a
jira comment stating which PR was the last and approved one among the many.
On Tue, Jul 23, 2019 at 11:22 AM Steve Loughran
wrote:
> On Mon, Jul 22, 2019 at 7:29 PM Eric Badger
> wrote:
>
> > Where would JIRA fit into the P
Hi Junping
Thanks. I would like to get a slot to talk about our new open source project:
YuniKorn.
Thanks
Weiwei
On Jul 23, 2019, 5:08 PM +0800, 俊平堵 , wrote:
> Thanks for these positive feedbacks! The local community has voted the date
> and location to be 8/10, Beijing. So please book your tim
[
https://issues.apache.org/jira/browse/HADOOP-16446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-16446.
-
Resolution: Won't Fix
I'm going to have to close this as a wontfix. I Feel your pain -I
On Mon, Jul 22, 2019 at 7:29 PM Eric Badger
wrote:
> Where would JIRA fit into the PR workflow? Would we file JIRAs just to
> track github PRs and have all of the discussion on the PR?
>
>
Every code contribution needs its JIRA for: tracking, release notes, cross
referencing; every committed patc
Thanks for these positive feedbacks! The local community has voted the date
and location to be 8/10, Beijing. So please book your time ahead if you
have interest to join.
I have gathered a few topics, and some candidate places for hosting this
meetup. If you would like to propose more topics, pleas
Siddharth Seth created HADOOP-16449:
---
Summary: Allow an empty credential provider chain, separate chains
for S3 and DDB
Key: HADOOP-16449
URL: https://issues.apache.org/jira/browse/HADOOP-16449
Proj
16 matches
Mail list logo
