<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Python on Insignificant Bits</title>
    <link>https://bobcopeland.com/blog/tags/python/</link>
    <description>Recent content in Python on Insignificant Bits</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 16 Feb 2012 13:44:12 +0000</lastBuildDate>
    <atom:link href="https://bobcopeland.com/blog/tags/python/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Parsing HRegionInfo in Python</title>
      <link>https://bobcopeland.com/blog/2012/02/parsing-hregioninfo-in-python/</link>
      <pubDate>Thu, 16 Feb 2012 13:44:12 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1790</guid> 
      <description>&lt;p&gt;I&amp;rsquo;ve been doing a fair amount of HBase work lately at $work, not least of which is &lt;a href=&#34;https://github.com/bcopeland/pybase&#34;&gt;pybase&lt;/a&gt;, a python module that encapsulates Thrift and puts it under an API that looks more or less like the Cassandra wrapper &lt;a href=&#34;https://github.com/pycassa/pycassa&#34;&gt;pycassa&lt;/a&gt; (which we also use).&lt;/p&gt;
&lt;p&gt;When running an HBase cluster, one must very quickly learn the stack from top to bottom and be ready to fix the metadata when catastrophe strikes. Most of the necessary information about HBase regions is stored in the .META. table; unfortunately some of the values therein are serialized HBase Writables. One usually uses JRuby and directly loads Java classes to deal with the deserialization, but we&amp;rsquo;re a Python shop and doing it all over thrift would be ideal.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
