Build failed in Jenkins: HBase-TRUNK #1915

See Changes: [nspiegelberg] HBASE-3877 Determine Proper Defaults for Compaction ThreadPools -- [...truncated 3061 lines...] Generating

Re: [ANN]: HBaseWD: Distribute Sequential Writes in HBase

> The start/end rows may be written twice. Yeah, I know. I meant that size of startRow+stopRow data is "bearable" in attribute value no matter how long are they (keys), since we already OK with transferring them initially (i.e. we should be OK with transferring 2x times more). So, what about the

Re: [ANN]: HBaseWD: Distribute Sequential Writes in HBase

> Can you remove the first version ? Isn't it ok to keep it in JIRA issue? > In HBaseWD, can you use reflection to detect whether Scan supports setAttribute() ? > If it does, can you encode start row and end row as "sourceScan" attribute ? Yeah, smth like this is going to be implemented. Though I

Re: Build failed in Jenkins: HBase-TRUNK #1914

Build is broke. This test fails for me local. I opened HBASE-3876 St.Ack On Wed, May 11, 2011 at 10:58 AM, Apache Jenkins Server wrote: > See > > -- > [...truncated 3062 lines...] > Generating >

Build failed in Jenkins: HBase-TRUNK #1914

See -- [...truncated 3062 lines...] Generating

Build failed in Jenkins: HBase-TRUNK #1913

See -- [...truncated 3068 lines...] Generating

Re: Build failed in Jenkins: HBase-TRUNK #1912

Looks like a jenkins hiccup rather than a failed build. St.Ack On Tue, May 10, 2011 at 11:08 PM, Apache Jenkins Server wrote: > See > > -- > Started by an SCM change > Started by an SCM change > Build

Build failed in Jenkins: HBase-TRUNK #1912

See -- Started by an SCM change Started by an SCM change Building remotely on ubuntu2 hudson.util.IOException2: remote file operation failed: at

Re: about HTable and HConnectionImplementation thread-safety

Very useful thanks! Fixed the link: http://zhihongyu.blogspot.com/2011/04/managing-connections-in-hbase-090-and.html On 05/11/2011 03:33 PM, Ted Yu wrote: See http://zhihongyu.blogspot.com/2011/04/managing-connections-in-hbase-090-and.htmlfor your first question. On Wed, May 11, 2011 at 2:39 A

Re: about HTable and HConnectionImplementation thread-safety

See http://zhihongyu.blogspot.com/2011/04/managing-connections-in-hbase-090-and.htmlfor your first question. On Wed, May 11, 2011 at 2:39 AM, Ferdy Galema wrote: > I understand HTable is not thread-safe. How about > HConnectionImplementation? I presume it is thread-safe, because otherwise > creat

about HTable and HConnectionImplementation thread-safety

I understand HTable is not thread-safe. How about HConnectionImplementation? I presume it is thread-safe, because otherwise creating a HTable for each thread will only work when each thread uses it's own Configuration. (Since Configuration is mapped to a HConnectionImplementation). So, how does

Re: HBase version numbers

0.91, if used, will be used for a developer-preview. Much as there was a 0.89 Developer Preview, then a 0.90.x DPs tend to be marked by the date they were cut, since there is no real "version", and it is not expected the average user run a DP in production (nor advised!) -ryan On Tue, May 10, 2