Yongjun Zhang created HDFS-6937:
---
Summary: Another issue in handling checksum errors in write
pipeline
Key: HDFS-6937
URL: https://issues.apache.org/jira/browse/HDFS-6937
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao resolved HDFS-6906.
-
Resolution: Fixed
Hadoop Flags: Reviewed
Archival Storage: Add more tests for BlockStoragePolicy
See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1848/
--
[...truncated 13740 lines...]
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.213 sec - in
org.apache.hadoop.hdfs.web.TestJsonUtil
Running
See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1848/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13933 lines...]
[INFO] ---
Thanks for your input, Steve. Sorry for sending the email out that late, I
sent it as soon as I could.
On Mon, Aug 25, 2014 at 2:20 AM, Steve Loughran ste...@hortonworks.com
wrote:
just caught up with this after some offlininess...15:48 PST is too late for
me.
I'd be -1 to a change to
Do we have any convention about user.name and user.email? For example,
we'd like to use @apache.org for the email.
Moreover, do we want to use --author=Author Name em...@address.com
when committing on behalf of a particular contributor?
On Mon, Aug 25, 2014 at 9:56 AM, Karthik Kambatla
Charles Lamb created HDFS-6938:
--
Summary: Cleanup javac warnings in FSNamesystem.java
Key: HDFS-6938
URL: https://issues.apache.org/jira/browse/HDFS-6938
Project: Hadoop HDFS
Issue Type: Bug
James Thomas created HDFS-6939:
--
Summary: Support path-based filtering of inotify events
Key: HDFS-6939
URL: https://issues.apache.org/jira/browse/HDFS-6939
Project: Hadoop HDFS
Issue Type:
Konstantin Shvachko created HDFS-6940:
-
Summary: Initial refactoring to allow ConsensusNode implementation
Key: HDFS-6940
URL: https://issues.apache.org/jira/browse/HDFS-6940
Project: Hadoop HDFS
Brandon Li created HDFS-6941:
Summary: Add shell based end-to-end NFS test
Key: HDFS-6941
URL: https://issues.apache.org/jira/browse/HDFS-6941
Project: Hadoop HDFS
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HDFS-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai reopened HDFS-6938:
--
Cleanup javac warnings in FSNamesystem.java
---
[
https://issues.apache.org/jira/browse/HDFS-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haohui Mai resolved HDFS-6938.
--
Resolution: Unresolved
Cleanup javac warnings in FSNamesystem.java
Ray Chiang created HDFS-6942:
Summary: Fix typos in log messages
Key: HDFS-6942
URL: https://issues.apache.org/jira/browse/HDFS-6942
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions:
Ming Ma created HDFS-6943:
-
Summary: Improve NN allocateBlock log to include replicas'
datanode IPs
Key: HDFS-6943
URL: https://issues.apache.org/jira/browse/HDFS-6943
Project: Hadoop HDFS
Issue
Thanks for bringing these points up, Zhijie.
By the way, a revised How-to-commit wiki is at:
https://wiki.apache.org/hadoop/HowToCommitWithGit . Please feel free to
make changes and improve it.
On Mon, Aug 25, 2014 at 11:00 AM, Zhijie Shen zs...@hortonworks.com wrote:
Do we have any convention
Let's discuss this on the JIRA. I think Tsuyoshi OZAWA's solution is good.
Colin
On Thu, Aug 21, 2014 at 7:08 AM, Ted Yu yuzhih...@gmail.com wrote:
bq. else there is a memory leak
Moving call of close() would prevent the leak.
bq. but then this code snippet could be java and can be messy
RE: —author
No, we should not do this. This just increases friction. It’s hard enough
getting patches reviewed and committed, esp if you are not @apache.org.
Trying to dig up a valid address (nevermind potentially having to deal with
'nsf...@example.com') is just asking for trouble.
Plus, the
Jing Zhao created HDFS-6944:
---
Summary: Archival Storage: add a test framework for testing
different migration scenarios
Key: HDFS-6944
URL: https://issues.apache.org/jira/browse/HDFS-6944
Project: Hadoop
18 matches
Mail list logo