thanks for confirmation. On Mon, May 2, 2011 at 8:48 PM, Todd Lipcon <t...@cloudera.com> wrote:
> On Mon, May 2, 2011 at 6:39 PM, Thanh Do <than...@cs.wisc.edu> wrote: > >> So the order of saving is based on how child list >> is organized. According from the code from >> INodeDirectory.addChild(), every time we add a child, >> we do a binary search to find the appropriate insert location. >> >> So I think the child list is sorted on alphabetical order. >> Am I right? >> > > Yes, I would agree with that. Though "UTF8 bytewise lexicographic order" is > probably more correct. For example, accent characters won't be > alphabetically sorted: > > [todd@monster01 ~]$ hadoop fs -ls > Found 5 items > drwxr-xr-x - todd supergroup 0 2011-05-02 18:47 /user/todd/âpple > drwxr-xr-x - todd supergroup 0 2011-05-02 18:48 /user/todd/èvil > drwx------ - todd supergroup 0 2011-04-06 14:25 > /user/todd/.staging > drwxr-xr-x - todd supergroup 0 2011-05-02 18:47 /user/todd/apple > drwxr-xr-x - todd supergroup 0 2011-05-02 18:47 /user/todd/zebra > > > -Todd > > >> >> Thanh >> >> >> On Mon, May 2, 2011 at 3:51 PM, Todd Lipcon <t...@cloudera.com> wrote: >> >>> On Mon, May 2, 2011 at 1:20 PM, Thanh Do <than...@cs.wisc.edu> wrote: >>> >>>> hi all, >>>> >>>> perhaps this is a dummy question but >>>> can anyone tell me that when >>>> the namenode saves a fsimage, >>>> are the Inodes saved in an alphabetical order? >>>> >>> >>> Hi Thanh, >>> >>> They're saved in directory traversal order (can't remember if it's >>> breadth first or depth first, but the code should tell you) >>> >>> -Todd >>> -- >>> Todd Lipcon >>> Software Engineer, Cloudera >>> >> >> > > > -- > Todd Lipcon > Software Engineer, Cloudera >
