I don't think that there are any TFile issues specifically. I just thought that bloomfilter map file was postponed because it was expected that TFile would replace it.
--- Jim Kellerman, Powerset (Live Search, Microsoft Corporation) > -----Original Message----- > From: Bruce Williams [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 02, 2008 2:44 PM > To: [email protected] > Subject: Re: Bloom filters > > Ok, Andrzej Bialecki is finishing the patch in the next few days, > including the moving MurmurHash code to Hadoop. > > https://issues.apache.org/jira/browse/HADOOP-3063 > > Are there any "TFile" issues he should be aware of? :-) > > Bruce > > On Tue, Dec 2, 2008 at 2:35 PM, Bruce Williams <[EMAIL PROTECTED]> > wrote: > > Jim, > > > > Could you comment on "derailed by TFile"? > > > > Thanks, > > > > Bruce > > > > On Tue, Dec 2, 2008 at 8:20 AM, Jim Kellerman (POWERSET) > > <[EMAIL PROTECTED]> wrote: > >> That patch was never committed to the Hadoop code base, (I > >> believe it got derailed by TFile). Until the code is in > >> Hadoop, we cannot remove it from HBase. > >> > >> --- > >> Jim Kellerman, Powerset (Live Search, Microsoft Corporation) > >> > >>> -----Original Message----- > >>> From: Bruce Williams [mailto:[EMAIL PROTECTED] > >>> Sent: Tuesday, December 02, 2008 4:02 AM > >>> To: [email protected] > >>> Subject: Re: Bloom filters > >>> > >>> On Mon, Dec 1, 2008 at 12:36 PM, stack <[EMAIL PROTECTED]> wrote: > >>> > Bruce Williams wrote: > >>> >> > >>> >> My understanding, which may be faulty, is the option works until a > >>> >> column is modified and then it fails in a difficult-to-fix manner. > The > >>> >> jira hints that the issue could impact how clients, such as > ZooKeeper, > >>> >> function as well as HBase. > >>> >> > >>> > > >>> > HBase shouldn't NPE. If bloomfilters are enabled on a table where > >>> before > >>> > there were none, the table should just evolve gracefully adding the > >>> filters > >>> > as it runs (Same should happen when they are disabled; any filters > >>> should be > >>> > gradually disposed-of). > >>> > > >>> >> I will continue to dig, but coming up to speed on the HBase > >>> >> implementation will take my time short term, can someone comment on > >>> >> the "client issues"? > >>> >> > >>> > > >>> > Keep asking questions if it'll maximize the time you have for hbase. > >>> > > >>> > Please expand on what you mean by 'client' issues in the above. > >>> > > >>> > Thanks, > >>> > St.Ack > >>> > > >>> > >>> Thanks, St. Ack > >>> > >>> Bloom Filter Code has been moved from HBase to Hadoop Core? > >>> > >>> https://issues.apache.org/jira/browse/HADOOP-3063 > >>> > >>> Updated patch. This patch imports the Bloom filter classes into > >>> org.apache.hadoop.util.bloom, and adds a notice to LICENSE.txt. > >>> [ Show > ] > >>> Andrzej Bialecki - 29/Mar/08 02:50 PM Updated patch. This patch > >>> imports the Bloom filter classes into org.apache.hadoop.util.bloom, > >>> and adds a notice to LICENSE.txt. > >>> > >>> Doug Cutting and Owen O'Malley think we should remove the code from > >>> HBase and use the Hadoop code. > >>> > >>> We have https://issues.apache.org/jira/browse/HBASE-553 to remove the > >>> code from HBase. > >>> > >>> Comment? > >>> > >>> > >>> Bruce > >>> > >>> -- > >>> > >>> "Discovering...discovering...we will never cease discovering... > >>> and the end of all our discovering will be > >>> to return to the place where we began > >>> and to know it for the first time." > >>> -T.S. Eliot > >> > >> > > > > > > > > -- > > > > "Discovering...discovering...we will never cease discovering... > > and the end of all our discovering will be > > to return to the place where we began > > and to know it for the first time." > > -T.S. Eliot > > > > > > -- > > "Discovering...discovering...we will never cease discovering... > and the end of all our discovering will be > to return to the place where we began > and to know it for the first time." > -T.S. Eliot
