Jason Lowe created HADOOP-9344:
--
Summary: Configuration.writeXml can warn about deprecated
properties user did not set
Key: HADOOP-9344
URL: https://issues.apache.org/jira/browse/HADOOP-9344
Project: Had
+1 (non-binding)
I am really glad to see this happening! As people already mentioned, this has
been a great engineering effort involving many people!
Folks raised some valid concerns below and I thought it would be good to share
my 2 cents. In my opinion, we don't have to solve all these probl
Siddharth Seth created HADOOP-9343:
--
Summary: Allow additional exceptions through the RPC layer
Key: HADOOP-9343
URL: https://issues.apache.org/jira/browse/HADOOP-9343
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur resolved HADOOP-9342.
Resolution: Fixed
Hadoop Flags: Reviewed
Thanks Thomas. Committed to trunk a
Thomas Weise created HADOOP-9342:
Summary: Remove ancient jline from distribution
Key: HADOOP-9342
URL: https://issues.apache.org/jira/browse/HADOOP-9342
Project: Hadoop Common
Issue Type: Bu
On Wed, Feb 27, 2013 at 2:54 PM, Suresh Srinivas wrote:
> With that we need to decide how our precommit process looks.
> My inclination is to wait for +1 from precommit builds on
> both the platforms to ensure no issues are introduced.
> Thoughts?
>
> 2. Feature development impact
> Some questions
Daryn Sharp created HADOOP-9341:
---
Summary: Secret Managers should allow explicit purging of tokens
and secret keys
Key: HADOOP-9341
URL: https://issues.apache.org/jira/browse/HADOOP-9341
Project: Hadoop
Thanks for raising good questions.
Currently the merge patch passes all the tests on Linux, hence
the proposal for merging the patch to trunk. But as Bobby, Harsh
and Eli pointed out, before declaring support for Windows, we need the
discussion on the following:
1. Precommit and development proce
+1 non-binding.
I have extensively tested this on both Windows and Linux over the last few
months.
Thanks,
-Arpit
On Wed, Feb 27, 2013 at 11:56 AM, Eli Collins wrote:
> Bobby raises some good questions. A related one, since most current
> developers won't add Windows support for new features
Bobby raises some good questions. A related one, since most current
developers won't add Windows support for new features that are
platform specific is it assumed that Windows development will either
lag or will people actively work on keeping Windows up with the
latest? And vice versa in case Wi
Similar personal concern as Robert: Does this bring about a
development process change? Do new features all need to work on
Windows as well to go into trunk (i.e. immediately or eventually,
either way requires a new policy for all of us devs)? Not that anyone
would be avoiding doing that, I just as
Daryn Sharp created HADOOP-9339:
---
Summary: IPC.Server incorrectly sets UGI auth type
Key: HADOOP-9339
URL: https://issues.apache.org/jira/browse/HADOOP-9339
Project: Hadoop Common
Issue Type: B
Nick White created HADOOP-9338:
--
Summary: FsShell Copy Commands Should Optionally Preserve File
Attributes
Key: HADOOP-9338
URL: https://issues.apache.org/jira/browse/HADOOP-9338
Project: Hadoop Common
After this is merged in is Windows still going to be a second class
citizen but happens to work for more than just development or is it a
fully supported platform where if something breaks it can block a release?
How do we as a community intend to keep Windows support from breaking?
We don't have
Ivan A. Veselovsky created HADOOP-9337:
--
Summary: org.apache.hadoop.fs.DF.getMount() does not work on Mac OS
Key: HADOOP-9337
URL: https://issues.apache.org/jira/browse/HADOOP-9337
Project: Hadoop
15 matches
Mail list logo
