Re: [DISCUSS] Mysql-connector-java is GPL licensed; Hadoop can't use it.

his case, RBF is used by a small set of Hadoop users, moreover an even > smaller subset of them will choose to use the mysql backend. > > (And there need to be instructions for how to acquire the mysql connector > jar since it's not shipped in the convenience binary) > > On Thu,

Re: [DISCUSS] Mysql-connector-java is GPL licensed; Hadoop can't use it.

The relevant url is https://www.apache.org/legal/resolved.html#optional On Fri, Jun 9, 2023 at 6:54 AM Owen O'Malley wrote: > We are allowed to use category X software in optional components. > Furthermore, the dependency is marked as provided, so it won't be pulled > into a

Re: [DISCUSS] Mysql-connector-java is GPL licensed; Hadoop can't use it.

We are allowed to use category X software in optional components. Furthermore, the dependency is marked as provided, so it won't be pulled into a transitive closure. You are right that I should have included a comment about that on the original jira. .. Owen On Fri, Jun 9, 2023 at 1:58 AM Wei-C

Re: [DISCUSS] new repo/sub-project, fs-api-shim

For the case in question, ORC can extend its shim module to do exactly this. Let me take a look at the async ORC patch to see what needs to happen. BTW, Steve I'll be at Buzzwords for your talk. It may make sense to have such a library, but ORC already has that mechanism. .. Owen On Thu, Jun 1,

[jira] [Resolved] (HADOOP-18535) Implement token storage solution based on MySQL

[ https://issues.apache.org/jira/browse/HADOOP-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18535. Fix Version/s: 3.3.6 3.4.0 Resolution: Fixed Thanks, H

[jira] [Resolved] (HADOOP-18324) Interrupting RPC Client calls can lead to thread exhaustion

[ https://issues.apache.org/jira/browse/HADOOP-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18324. Fix Version/s: 3.4.0 3.3.5 2.10.3 Resol

[jira] [Resolved] (HADOOP-18444) Add Support for localized trash for ViewFileSystem in Trash.moveToAppropriateTrash

[ https://issues.apache.org/jira/browse/HADOOP-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18444. Fix Version/s: 3.4.0 3.3.9 Resolution: Fixed > Add Sup

[jira] [Created] (HADOOP-18434) Proxy users do not share RPC connections

Owen O'Malley created HADOOP-18434: -- Summary: Proxy users do not share RPC connections Key: HADOOP-18434 URL: https://issues.apache.org/jira/browse/HADOOP-18434 Project: Hadoop Common

[jira] [Resolved] (HADOOP-18406) Adds alignment context to call path for creating RPC proxy with multiple connections per user.

[ https://issues.apache.org/jira/browse/HADOOP-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18406. Fix Version/s: 3.4.0 3.3.9 Resolution: Fixed > Adds a

[jira] [Resolved] (HADOOP-18345) Enhance client protocol to propagate last seen state IDs for multiple nameservices.

[ https://issues.apache.org/jira/browse/HADOOP-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18345. Fix Version/s: 3.4.0 3.3.9 Resolution: Fixed > Enhanc

style rules

I keep stubbing my toe on the unfortunate Hadoop style rule that says final variables can't be all caps. :( Does this frustrate anyone else? .. Owen

[jira] [Created] (HADOOP-18324) Interrupting RPC Client calls can lead to thread exhaustion

Owen O'Malley created HADOOP-18324: -- Summary: Interrupting RPC Client calls can lead to thread exhaustion Key: HADOOP-18324 URL: https://issues.apache.org/jira/browse/HADOOP-18324 Project: H

[jira] [Resolved] (HADOOP-18193) Support nested mount points in INodeTree

[ https://issues.apache.org/jira/browse/HADOOP-18193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18193. Fix Version/s: 3.4.0 Resolution: Fixed I just committed this. Thanks

Re: [DISCUSS] cull unused modules from under hadoop-tools

We really need input from the users as well. In trunk, hadoop-ozone and hadoop-ant are already gone. Used: hadoop-aliyun hadoop-aws hadoop-distcp hadoop-azure-datalake hadoop-azure hadoop-dynamometer hadoop-federation-balance Questions: hadoop-archive-logs hadoop-archives hadoop-datajoin hadoop-e

[jira] [Resolved] (HADOOP-18169) getDelegationTokens in ViewFs should also fetch the token from the fallback FS

[ https://issues.apache.org/jira/browse/HADOOP-18169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18169. Fix Version/s: 3.4.0 3.3.3 Resolution:

[jira] [Resolved] (HADOOP-18129) Change URI[] in INodeLink to String[] to reduce memory footprint of ViewFileSystem

[ https://issues.apache.org/jira/browse/HADOOP-18129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18129. Fix Version/s: 3.4.0 3.3.3 Resolution: Fixed I committed

[jira] [Resolved] (HADOOP-18127) Backport HADOOP-13055 into branch-2.10

[ https://issues.apache.org/jira/browse/HADOOP-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18127. Resolution: Fixed I just committed these backports. > Backport HADOOP-13055 int

[jira] [Resolved] (HADOOP-18144) getTrashRoot/s in ViewFileSystem should return viewFS path, not targetFS path

[ https://issues.apache.org/jira/browse/HADOOP-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18144. Fix Version/s: 3.4.0 Resolution: Fixed > getTrashRoot/s in ViewFileSyste

[jira] [Created] (HADOOP-18153) The CallerContext should not use ":" as the separator.

Owen O'Malley created HADOOP-18153: -- Summary: The CallerContext should not use ":" as the separator. Key: HADOOP-18153 URL: https://issues.apache.org/jira/browse/HADOOP-18153 Project

[jira] [Resolved] (HADOOP-18139) Allow configuration of zookeeper server principal

[ https://issues.apache.org/jira/browse/HADOOP-18139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18139. Fix Version/s: 3.4.0 3.3.3 Resolution: Fixed Thanks fo

[jira] [Created] (HADOOP-18139) RBF: Allow configuration of zookeeper server principal in router

Owen O'Malley created HADOOP-18139: -- Summary: RBF: Allow configuration of zookeeper server principal in router Key: HADOOP-18139 URL: https://issues.apache.org/jira/browse/HADOOP-18139 Pr

[jira] [Resolved] (HADOOP-18110) ViewFileSystem: Add Support for Localized Trash Root

[ https://issues.apache.org/jira/browse/HADOOP-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-18110. Fix Version/s: 3.4.0 Resolution: Fixed > ViewFileSystem: Add Sup

[DISCUSS] Removing the archiac master branch

We unfortunately have a lot of master/slave and whitelist/blacklist terminology usage in Hadoop. It will take a while to fix them all, but one is easy to fix. In particular, we have a "master" branch that hasn't been used since the project reunification and we use "trunk" as the main branch. I pro

Re: Signing hadoop releases

For completeness, this is the SVN path where the dist directory for Hadoop lives: https://dist.apache.org/repos/dist/release/hadoop/ On Wed, Apr 29, 2020 at 10:41 AM Owen O'Malley wrote: > > Also sending to the list. > .. Owen > > -- Forwarded message ----- &

Fwd: Signing hadoop releases

Also sending to the list. .. Owen -- Forwarded message - From: Owen O'Malley Date: Wed, Apr 29, 2020 at 10:40 AM Subject: Re: Signing hadoop releases To: Gabor Bota There is a readme in the hadoop/common dist directory that points to https://infra.apache.org/re

Re: Hadoop File API v.s. Commons VFS

It would be a lot of work. Of course there is a lot of overlap, but they have different use cases, so there are significant differences. From the big data side, there are a lot of blockers. 1. CVFS does not have the concept of replication, so there is no way to get or set a file's replicatio

Re: Needs support to add more entropy to improve cryptographic randomness on Linux VMs

For testing, it is important to be able to use Random instead of SecureRandom. We should never be using the OS entropy for unit tests. .. Owen On Tue, Jan 14, 2020 at 1:05 PM Ahmed Hussein wrote: > I tried setting JVM option "-Djava.security.egd=file:///dev/./urandom" > from the command line b

Re: [DISCUSS] About creation of Hadoop Thirdparty repository for shaded artifacts

I'm very unhappy with this direction. In particular, I don't think git is a good place for distribution of binary artifacts. Furthermore, the PMC shouldn't be releasing anything without a release vote. I'd propose that we make a third party module that contains the *source* of the pom files to bui

Re: [VOTE] Moving Submarine to a separate Apache project proposal

Since you don't have any Apache Members, I'll join to provide Apache oversight. .. Owen On Fri, Sep 6, 2019 at 1:38 PM Owen O'Malley wrote: > +1 for moving to a new project. > > On Sat, Aug 31, 2019 at 10:19 PM Wangda Tan wrote: > >> Hi all, >> >&

Re: [VOTE] Moving Submarine to a separate Apache project proposal

+1 for moving to a new project. On Sat, Aug 31, 2019 at 10:19 PM Wangda Tan wrote: > Hi all, > > As we discussed in the previous thread [1], > > I just moved the spin-off proposal to CWIKI and completed all TODO parts. > > > https://cwiki.apache.org/confluence/display/HADOOP/Submarine+Project+Sp

Re: About supporting upcoming java versions

On Wed, Nov 7, 2018 at 2:18 AM Steve Loughran wrote: > > If there are problems w/ JDK11 then we should be talking to oracle about > them to have them fixed. Is there an ASF JIRA on this issue yet? > I must admit when the ORC unit tests failed with jdk11 and the debugger showed that it was failin

Re: About supporting upcoming java versions

I’m less convinced. I’ve hit at least one pretty serious JVM bug in JDK 11, so there is value in enabling JDK 9 and 10 even with blockers on JDK 11. That said, I’d be surprised if the work items for JDK 9 and 10 aren’t a strict subset of the issues getting to JDK 11. .. Owen > On Nov 5, 2018,

[jira] [Resolved] (HADOOP-15896) Refine Kerberos based AuthenticationHandler to check proxyuser ACL

[ https://issues.apache.org/jira/browse/HADOOP-15896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-15896. Resolution: Not A Problem This is working correctly. Do not attempt to change

Re: site doc cleanup

If propose keeping the last patch release on each X.Y branch and only keep the versions that have been being maintained (a patch release in the last year?) recently. Thoughts? .. Owen > On Jun 28, 2018, at 19:19, Steve Loughran wrote: > > Rm'd all of 3.0.0-* ; left the current/stable symlink

Re: Changes in Java

In my experience, most Hadoop users have moved from the Oracle JDK to OpenJDK, where the support windows are much longer. For example, on RedHat the Java support looks like: https://access.redhat.com/articles/1299013 which currently shows Java 8 as supported until October 2020. .. Owen

Re: [VOTE] Merging branch HDFS-7240 to trunk

Andrew and Daryn, Do you have any feedback on the proposal? Otherwise, we can start a vote for "adoption of new codebase" tomorrow. .. Owen On Wed, Mar 14, 2018 at 1:50 PM, Owen O'Malley wrote: > This discussion seems to have died down coming closer consensus without a >

Re: [VOTE] Merging branch HDFS-7240 to trunk

This discussion seems to have died down coming closer consensus without a resolution. I'd like to propose the following compromise: * HDSL become a subproject of Hadoop. * HDSL will release separately from Hadoop. Hadoop releases will not contain HDSL and vice versa. * HDSL will get its own jira

Re: Cleaning up the Hadoop dist area

: > On Mon, Mar 5, 2018 at 1:24 PM, Owen O'Malley > wrote: > > The Apache Release Process > > https://www.apache.org/legal/release-policy.html says > > that we should only keep the latest release on each branch. That would > take > > us to: > > >

Re: [VOTE] Merging branch HDFS-7240 to trunk

Hi Joep, On Tue, Mar 6, 2018 at 6:50 PM, J. Rottinghuis wrote: Obviously when people do want to use Ozone, then having it in the same repo > is easier. The flipside is that, separate top-level project in the same > repo or not, it adds to the Hadoop releases. > Apache projects are about the gro

Cleaning up the Hadoop dist area

All, We should clean up some of our old releases out of the dist area. Note that old releases (all of the way back to 0.1.0 are available on from the archive https://archive.apache.org/dist/hadoop/common/ . The current contents: - hadoop-1.2.1 - hadoop-2.6.5 - hadoop-2.7.4 - hadoo

Re: [VOTE] Merging branch HDFS-7240 to trunk

On Thu, Mar 1, 2018 at 11:03 PM, Andrew Wang wrote: Owen mentioned making a Hadoop subproject; we'd have to > hash out what exactly this means (I assume a separate repo still managed by > the Hadoop project), but I think we could make this work if it's more > attractive than incubation or a new T

Re: [VOTE] Merging branch HDFS-7240 to trunk

I think it would be good to get this in sooner rather than later, but I have some thoughts. 1. It is hard to tell what has changed. git rebase -i tells me the branch has 722 commits. The rebase failed with a conflict. It would really help if you rebased to current trunk. 2. I think Ozo

[CFP] Dataworks Summit San Jose Call for Presentations closes Friday 9 Feb

All, Dataworks Summit San Jose 2018 is June 17-21. The call for abstracts is open through February 9th. One of the tracks is Big Compute And Storage, which is great for talks about Hadoop. You can submit an abstract at https://dataworkssummit.com/san-jose-2018/ Thanks, Owen

Re: I want to inquire about hadoop licence.

There is a licensing FAQ for that http://www.apache.org/foundation/license-faq.html#IsItFee .. Owen > On Jan 17, 2018, at 11:06, 파란구름 wrote: > > Dear in charge of the hadoop manager. > > Thank you for providing hadoop service. > I want to inquire about hadoop licence. > Recently, I'm making

Re: stringifyException

It is a very old relic from when logging the exception just gave you the message. It can should be replaced at some point. .. Owen On Thu, Oct 12, 2017 at 1:17 PM, dam6923 . wrote: > Hello, > > Can someone please explain what the value of > org.apache.hadoop.util.StringUtils#stringifyException

Re: zstd compression

I'd support asking Facebook to change it with both my hadoop and orc hats on. .. Owen > On Jul 24, 2017, at 23:43, Sean Busbey wrote: > > Nope. Once I found out HBase's use was compliant as an optional runtime > dependency I stopped looking. > >> On Jul 24, 2017 7:22 PM, "Andrew Wang" wrote:

Re: HADOOP-14163 proposal for new hadoop.apache.org

Thanks for addressing this. Getting rid of Hadoop's use of forrest is a good thing. In terms of content, the documentation links should be sorted by number with only the latest from each minor release line (eg. 3.0, 2.7, 2.6). The download page points to the mirrors for checksums and signatures.

Re: gpg signing of commits

I think gpg signing of commits is a good practice. It also strongly discourages rebasing on master and release branches, which is also a good thing. On ORC, we try to sign all of our commits. .. Owen On Fri, Feb 24, 2017 at 3:36 AM, Steve Loughran wrote: > > For the next few days I'm experiment

Hadoop Summit EU 2017

The DataWorks Summit EU 2017 (including Hadoop Summit) is going to be in Munich April 5-6 2017 . I’ve pasted the text from the CFP below. Would you like to share your knowledge with the best and brightest in the data community? If so, we encourage you to submit an abstract for DataWorks Summit wi

[jira] [Created] (HADOOP-13434) Add quoting to Shell class

Owen O'Malley created HADOOP-13434: -- Summary: Add quoting to Shell class Key: HADOOP-13434 URL: https://issues.apache.org/jira/browse/HADOOP-13434 Project: Hadoop Common Issue Type

Re: Commit History Edit Alert

commit messages with > > > periods, e.g.: > > > > > > HADOOP-13011. Clearly Document the Password Details for Keystore-based > > > Credential Providers. > > > > > > > > > On Thu, Apr 21, 2016 at 8:26 PM, larry mccay > wrote: > > > >

Re: Github integration for Hadoop

On Sun, Nov 1, 2015 at 2:07 PM, Chris Douglas wrote: > Wow, this happened quickly. > > Owen, could you please create a Wiki describing the proposal and > cataloging infra references so others can understand the > implementation in detail? Even after reading this thread, I'm still > confused what

Re: Github integration for Hadoop

On Fri, Oct 30, 2015 at 2:37 PM, Andrew Wang wrote: > > Strongly agree that we need documentation for all this. Agreed. > Some of my open questions are also still pending. > Which open questions? Owen, are you chasing all of this down? Do we need some JIRAs to track? > Yeah, I'll take a fi

Re: Github integration for Hadoop

ol and getting github integration enabled is easy. Furthermore, it isn't exclusive. There will still be people uploading patches on jira. This is about giving the contributors and committers the ability to use a popular review tool .. Owen > Best, > Andrew > > > On Fri, Oct

Re: [GitHub] hadoop pull request: HADOOP-11919 Testing Github integration

Responding to a comment on github. On Fri, Oct 30, 2015 at 10:11 AM, omalley wrote: > Github user omalley commented on the pull request: > > https://github.com/apache/hadoop/pull/40#issuecomment-152589471 > > Testing comments on github pull requests. > > > --- > If your project is set up

Re: Github integration for Hadoop

It seems like there is overwhelming support for enabling the github integration, so I went ahead and filed the infra ticket . This is explicitly not changing the way that we commit on Hadoop and commits should be squashed an

Re: Github integration for Hadoop

On Thu, Oct 29, 2015 at 2:42 PM, Andrew Wang wrote: > > If I had my druthers, we'd focus on Gerrit rather than Github as a > successor review system. Better review, better fits our dev workflow. The > only question is JIRA integration. > Last time I asked, Apache Infra wasn't willing to support

Re: Github integration for Hadoop

On Thu, Oct 29, 2015 at 1:34 PM, Andrew Wang wrote: > Has anything changed regarding the github integration since the last time > we discussed this? There is a lot more experience with it now and opinions change over time. Clearly, there is overwhelming support for this idea now. > There are

Github integration for Hadoop

All, For code & patch review, many of the newer projects are using the Github pull request integration. You can read about it here: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and It basically lets you: * have mirroring between comments on pull requests and jira *

Hadoop Summit Passes

All, We'd like to thank all of the committers that have worked on Hadoop over the years. I have a registration code for the Hadoop Summit San Jose that Hadoop committers can use to get free registration. Please send me email off list (omal...@apache.org) and I'll send it to you. .. Owen

[jira] [Created] (HADOOP-11919) Add release 2.4.1 to the table at the top of the releases page

Owen O'Malley created HADOOP-11919: -- Summary: Add release 2.4.1 to the table at the top of the releases page Key: HADOOP-11919 URL: https://issues.apache.org/jira/browse/HADOOP-11919 Project: H

[jira] [Resolved] (HADOOP-11896) Redesign the releases page on the Hadoop site

[ https://issues.apache.org/jira/browse/HADOOP-11896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-11896. Resolution: Fixed Fix Version/s: site I committed this with 1677710. >

[jira] [Created] (HADOOP-11902) Prune old javadoc versions from the website.

Owen O'Malley created HADOOP-11902: -- Summary: Prune old javadoc versions from the website. Key: HADOOP-11902 URL: https://issues.apache.org/jira/browse/HADOOP-11902 Project: Hadoop C

[jira] [Created] (HADOOP-11896) Redesign the releases page on the Hadoop site

Owen O'Malley created HADOOP-11896: -- Summary: Redesign the releases page on the Hadoop site Key: HADOOP-11896 URL: https://issues.apache.org/jira/browse/HADOOP-11896 Project: Hadoop C

[jira] [Created] (HADOOP-10912) Modify scripts to use relative paths

Owen O'Malley created HADOOP-10912: -- Summary: Modify scripts to use relative paths Key: HADOOP-10912 URL: https://issues.apache.org/jira/browse/HADOOP-10912 Project: Hadoop Common

[jira] [Resolved] (HADOOP-10793) Key Shell args use double dash style

[ https://issues.apache.org/jira/browse/HADOOP-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-10793. Resolution: Invalid The unix standard is for long options to be double dash. We s

[jira] [Resolved] (HADOOP-10757) KeyProvider KeyVersion should provide the key name

[ https://issues.apache.org/jira/browse/HADOOP-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-10757. Resolution: Invalid > KeyProvider KeyVersion should provide the

Re: Moving to JDK7, JDK8 and new major releases

On Tue, Jun 24, 2014 at 4:44 PM, Alejandro Abdelnur wrote: > After reading this thread and thinking a bit about it, I think it should be > OK such move up to JDK7 in Hadoop I agree with Alejandro. Changing minimum JDKs is not an incompatible change and is fine in the 2 branch. (Although I think

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

+1 On Wed, Jun 25, 2014 at 7:27 AM, Vinayakumar B wrote: > +1 (binding) > > Regards, > Vinay > > > On Wed, Jun 25, 2014 at 4:13 AM, Vinod Kumar Vavilapalli < > vino...@apache.org > > wrote: > > > +1 > > > > Vinod > > > > On Jun 24, 2014, at 1:53 AM, Arun C Murthy wrote: > > > > > Folks, > > >

[jira] [Resolved] (HADOOP-10430) KeyProvider Metadata should have an optional description, there should be a method to retrieve the metadata from all keys

[ https://issues.apache.org/jira/browse/HADOOP-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-10430. Resolution: Fixed Ok, I've created HADOOP-10534 for the follow up. >

[jira] [Created] (HADOOP-10534) KeyProvider API should using windowing for retrieving metadata

Owen O'Malley created HADOOP-10534: -- Summary: KeyProvider API should using windowing for retrieving metadata Key: HADOOP-10534 URL: https://issues.apache.org/jira/browse/HADOOP-10534 Project: H

[jira] [Resolved] (HADOOP-10431) Change visibility of KeyStore.Options getter methods to public

[ https://issues.apache.org/jira/browse/HADOOP-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-10431. Resolution: Fixed Sorry, looked at the wrong version of the patch. > Change vi

[jira] [Reopened] (HADOOP-10431) Change visibility of KeyStore.Options getter methods to public

[ https://issues.apache.org/jira/browse/HADOOP-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley reopened HADOOP-10431: NO, this is not ok. The user API doesn't need the additional visibility.

[jira] [Reopened] (HADOOP-10430) KeyProvider Metadata should have an optional description, there should be a method to retrieve the metadata from all keys

[ https://issues.apache.org/jira/browse/HADOOP-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley reopened HADOOP-10430: This is the *user* API. It doesn't control the remote interface. You should *NO

[jira] [Created] (HADOOP-10177) Create CLI tools for managing keys via the KeyProvider API

Owen O'Malley created HADOOP-10177: -- Summary: Create CLI tools for managing keys via the KeyProvider API Key: HADOOP-10177 URL: https://issues.apache.org/jira/browse/HADOOP-10177 Project: H

[jira] [Created] (HADOOP-10149) Create ByteBuffer-based cipher API

Owen O'Malley created HADOOP-10149: -- Summary: Create ByteBuffer-based cipher API Key: HADOOP-10149 URL: https://issues.apache.org/jira/browse/HADOOP-10149 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-10141) Create an API to separate encryption key storage from applications

Owen O'Malley created HADOOP-10141: -- Summary: Create an API to separate encryption key storage from applications Key: HADOOP-10141 URL: https://issues.apache.org/jira/browse/HADOOP-10141 Pr

[jira] [Resolved] (HADOOP-8828) Support distcp from secure to insecure clusters

[ https://issues.apache.org/jira/browse/HADOOP-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-8828. --- Resolution: Not A Problem To copy data from a secure cluster to insecure cluster, ru

Re: Release numbering for branch-2 releases

I think that using "-(alpha,beta)" tags on the release versions is a really bad idea. All releases should follow the strictly numeric (Major.Minor.Patch) pattern that we've used for all of the releases except the 2.0.x ones. -- Owen On Mon, Feb 4, 2013 at 11:53 AM, Stack wrote: > On Mon, Feb 4

Re: [VOTE] Hadoop-1.0.4-rc0

On Wed, Oct 10, 2012 at 8:57 AM, Matt Foley wrote: > Please vote. Vote on 1.0.4-rc0 closes tomorrow. Vote on 1.1.0-rc5 closes > Friday. +1 on 1.0.4-rc0. I checked the signatures, compiled, and tested it. -- Owen

[jira] [Created] (HADOOP-8782) Make serialization of Delegation Tokens extensible

Owen O'Malley created HADOOP-8782: - Summary: Make serialization of Delegation Tokens extensible Key: HADOOP-8782 URL: https://issues.apache.org/jira/browse/HADOOP-8782 Project: Hadoop C

Re: [VOTE] 0.23.3 release

On Mon, Sep 10, 2012 at 12:19 PM, Robert Evans wrote: > Thanks for the info Owen I was not aware of that, I can see at the > beginning of the twiki > http://wiki.apache.org/hadoop/HowToReleasePostMavenization that it is kind > of implied by the skip this section comment. But, I was just confused

Re: [VOTE] 0.23.3 release

On Fri, Sep 7, 2012 at 12:56 PM, Bobby Evans wrote: > I have built an RC0 for 0.23.3 and am calling a vote on it Hi Bobby, I noticed that you created a branch-0.23.3. The pattern we have used in Hadoop is that there is a release branch that is for a minor release (branch-0.23) and tags for the

Re: Branch 2 release names

On Wed, Sep 5, 2012 at 11:04 AM, Andrew Purtell wrote: > If it's all the same to you, I'd prefer you leave the branch, or at least a > tag, and just ignore it. We're pretty far away from branch-2.1.0 following > branch-2 but started from that point. Subversion you don't actually ever delete anyth

Branch 2 release names

While cleaning up the subversion branches, I thought more about the branch 2 release names. I'm concerned if we backtrack and reuse release numbers it will be extremely confusing to users. It also creates problems for tools like Maven that parse version numbers and expect a left to right release nu

Re: Jetty fixes for Hadoop

--Bobby > > On 7/10/12 5:19 PM, "Todd Lipcon" wrote: > >> +1 from me too. We've had this in CDH since Sep '11 and been working >> much better than the stock 6.1.26. >> >> -Todd >> >> On Tue, Jul 10, 2012 at 3:14 PM, Owen O

Re: Jetty fixes for Hadoop

On Tue, Jul 10, 2012 at 2:59 PM, Thomas Graves wrote: > I'm +1 for adding it. > I'm +1 also. -- Owen

Re: Doubt regarding use of HTTP during Shuffle phase

Pavan, This is a very big project. Look at the users of IFile.java. IFile is the format for storing the shuffle outputs. -- Owen

Re: Doubt regarding use of HTTP during Shuffle phase

On Wed, Jun 27, 2012 at 9:33 AM, Pavan Kulkarni wrote: Why is HTTP used during the Shuffle phase > instead of just creating a Hardlink? > The reduces run on a separate machine that the map. Hadoop doesn't use a shared NFS file system between the machines, because it doesn't scale. -- Owen

Re: cmake

After a quick look at cmake, it seems reasonable. Please use feature tests rather than OS tests. (By that I mean that if Solaris needs "foobar.h" and RHEL needs "sys/foobar.h" to get the definition for foobar, the code should ifdef whether they need sys/foobar.h and not if it is solaris or not.) O

[jira] [Resolved] (HADOOP-8352) We should always generate a new configure script for the c++ code

[ https://issues.apache.org/jira/browse/HADOOP-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-8352. --- Resolution: Fixed Fix Version/s: 1.1.0 1.0.3 Ass

[jira] [Created] (HADOOP-8352) We should always generate a new configure script for the c++ code

Owen O'Malley created HADOOP-8352: - Summary: We should always generate a new configure script for the c++ code Key: HADOOP-8352 URL: https://issues.apache.org/jira/browse/HADOOP-8352 Project: H

[jira] [Resolved] (HADOOP-8338) Can't renew or cancel HDFS delegation tokens over secure RPC

[ https://issues.apache.org/jira/browse/HADOOP-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-8338. --- Resolution: Fixed Fix Version/s: 1.1.0 1.0.3 Hadoop

[jira] [Created] (HADOOP-8338) Can't renew or cancel HDFS delegation tokens over secure RPC

Owen O'Malley created HADOOP-8338: - Summary: Can't renew or cancel HDFS delegation tokens over secure RPC Key: HADOOP-8338 URL: https://issues.apache.org/jira/browse/HADOOP-8338 Proje

[jira] [Created] (HADOOP-8337) Clarify the usage documentation for fetchdt

Owen O'Malley created HADOOP-8337: - Summary: Clarify the usage documentation for fetchdt Key: HADOOP-8337 URL: https://issues.apache.org/jira/browse/HADOOP-8337 Project: Hadoop Common

Re: Hadoop-1.0.3 and 1.1 release / code freeze proposals

I also think we need two minor build problems fixed: HDFS-3316 HADOOP-8307 -- Owen

Re: Hadoop-1.0.3 and 1.1 release / code freeze proposals

On Sat, Apr 21, 2012 at 8:18 AM, Kihwal Lee wrote: > I think HADOOP-8294 is a good candidate to include. Without this, a transient > dns problem can make a large number of data nodes unavailable.  The fix is > backport of HADOOP-7428. I'm +1 on HADOOP-8294 (aka HADOOP-7428). Matt?

[jira] [Created] (HADOOP-8307) The task-controller is not packaged in the tarball

Owen O'Malley created HADOOP-8307: - Summary: The task-controller is not packaged in the tarball Key: HADOOP-8307 URL: https://issues.apache.org/jira/browse/HADOOP-8307 Project: Hadoop C

[jira] [Resolved] (HADOOP-8293) The native library's Makefile.am doesn't include JNI path

[ https://issues.apache.org/jira/browse/HADOOP-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen O'Malley resolved HADOOP-8293. --- Resolution: Fixed Fix Version/s: (was: 3.0.0)

[jira] [Created] (HADOOP-8293) The native library's Makefile.am doesn't include JNI path

Type: Bug Components: build Reporter: Owen O'Malley Assignee: Owen O'Malley Fix For: 1.0.3, 3.0.0 When compiling on centos 6, I get the following error when compiling the native library: {code} [exec] /usr/bin/ld: cannot find -ljvm {code} The proble

  1   2   3   4   >