On Wed, Mar 21, 2012 at 3:48 PM, <milind.bhandar...@emc.com> wrote: > Eli, > > If HDFS-3120 is committed to both 1.x and trunk/0.23.x, then one will be > able to disable appends (while keeping hflush) using different config > variables. By default (I.e. In hdfs-default.xlm), we should set > dfs.support.append to false, and dfs.support.hsync to true. >
Agree, thanks for the thoughts. > That way, we get enough time to fix append, and if we decide to remove it, > then we can do that without causing major distress in 0.24. > > Thoughts ? > Sounds good. Thanks, Eli > - Milind > > On 3/21/12 3:16 PM, "Eli Collins" <e...@cloudera.com> wrote: > >>On Wed, Mar 21, 2012 at 3:06 PM, <milind.bhandar...@emc.com> wrote: >>> >>>> >>>>Absolutely, I'd like to learn more about what append/truncate buys us. >>> >>> Indeed. Lets postpone this discussion to Q2 then. >>> >> >>I'd still like to hear what other people think if they haven't chimed >>in. Even if we decide to remove it, I don't think we need to do so >>next week, eg can wait to hear more about what you're working on. >> >>One of the reasons I raised this topic now is that it the not too >>distant future 0.23 will become the stable release, and we'll >>effectively lose the ability to remove append once we're stable. Not >>that I expect people will stabilize append before this happens, it >>doesn't seem to be a priority for anyone, though perhaps you'll end up >>doing that work for your project. >> >>Thanks, >>Eli >> >>> Thanks, >>> >>> - milind >>> >>> --- >>> Milind Bhandarkar >>> Greenplum Labs, EMC >>> (Disclaimer: Opinions expressed in this email are those of the author, >>>and >>> do not necessarily represent the views of any organization, past or >>> present, the author might be affiliated with.) >>> >>> >>>> >>> >> >
