Thanks for all the positive feedback,
I opened INFRA-18777 to request the proposed change.
Marton
On 7/18/19 10:02 AM, Masatake Iwasaki wrote:
> +1
>
> Thanks,
> Masatake Iwasaki
>
> On 7/17/19 15:07, Elek, Marton wrote:
>> Hi,
>>
>> Github UI (ui!) helps to merge Pull Requests to the propos
@adam.antal
The submarine development team has completed the following preparations:
1. Established a temporary test repository on Github.
2. Change the package name of hadoop submarine from org.hadoop.submarine to
org.submarine
3. Combine the Linkedin/TonY code into the Hadoop submarine module;
4
Gabor Bota created HADOOP-16442:
---
Summary: Intermittent failure of
ITestS3GuardToolDynamoDB#testDynamoDBInitDestroyCycle
Key: HADOOP-16442
URL: https://issues.apache.org/jira/browse/HADOOP-16442
Project
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/390/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc check
Stephen O'Donnell created HADOOP-16443:
--
Summary: Improve help text for setfacl --set option
Key: HADOOP-16443
URL: https://issues.apache.org/jira/browse/HADOOP-16443
Project: Hadoop Common
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1205/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checks
Historically, Hadoop developers create patches and attache them to JIRA,
andthen the Yetus bot runs precommit against the patch in the JIRA.
The Github PR is more convenient for code review and less hassle for
committers to merge a commit. I am proposing for the community to prefer
Github PR over
+1 Absolutely. It also makes it easy/clean for reviewers to leave specific
comments and the authors can make incremental changes without the hassles
of generating iterative patch files.
Thanks,
Dinesh
On Mon, Jul 22, 2019 at 2:06 PM Wei-Chiu Chuang wrote:
> Historically, Hadoop developers cr
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?
Eric
On Mon, Jul 22, 2019 at 1:10 PM Dinesh Chitlangia
wrote:
> +1 Absolutely. It also makes it easy/clean for reviewers to leave specific
> comments and the authors
xia0c created HADOOP-16444:
--
Summary: Updating incompatible issue
Key: HADOOP-16444
URL: https://issues.apache.org/jira/browse/HADOOP-16444
Project: Hadoop Common
Issue Type: Bug
Component
Siddharth Seth created HADOOP-16445:
---
Summary: Allow separate custom signing algorithms for S3 and DDB
Key: HADOOP-16445
URL: https://issues.apache.org/jira/browse/HADOOP-16445
Project: Hadoop Common
xia0c created HADOOP-16446:
--
Summary: Rolling upgrade to Hadoop 3.2.0 breaks due to backward
in-compatible change
Key: HADOOP-16446
URL: https://issues.apache.org/jira/browse/HADOOP-16446
Project: Hadoop Com
Hi, I'm quite interested in this, any updates on event details?
BR
On Sun, Jul 21, 2019 at 12:29 AM Xiaoqiao He wrote:
> Thanks Junping for organizing the event. Looking forward to the coming
> meetup.
>
> BTW, It is hoped to keep running regular Hadoop Contributors Meetups in
> China.
>
> On F
Akira Ajisaka created HADOOP-16447:
--
Summary: Upgrade JUnit5 from 5.3.1 to 5.5+ to support global
timeout
Key: HADOOP-16447
URL: https://issues.apache.org/jira/browse/HADOOP-16447
Project: Hadoop Com
Kaspar Tint created HADOOP-16448:
Summary: Connection to Hadoop homepage is not secure
Key: HADOOP-16448
URL: https://issues.apache.org/jira/browse/HADOOP-16448
Project: Hadoop Common
Issue T
15 matches
Mail list logo
