<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Creating a sample bugzilla database using kettle</title>
	<atom:link href="http://blog.mozilla.com/data/2009/06/05/creating-a-sample-bugzilla-database-using-kettle/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/data/2009/06/05/creating-a-sample-bugzilla-database-using-kettle/</link>
	<description>Mozilla metrics team&#039;s technical articles</description>
	<lastBuildDate>Fri, 28 Aug 2009 18:54:26 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nicholas Goodman</title>
		<link>http://blog.mozilla.com/data/2009/06/05/creating-a-sample-bugzilla-database-using-kettle/comment-page-1/#comment-9</link>
		<dc:creator>Nicholas Goodman</dc:creator>
		<pubDate>Thu, 11 Jun 2009 15:36:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/data/?p=13#comment-9</guid>
		<description>Daniel is spot on.... The current SQR does a horribily inefficient processing on the bug changes.  Making it smaller to do the development (to simply change the ETL to use Analytic Query step) makes perfect sense.  Adding back in the 5 million records should certainly be feasible, once the ETL is refactored.</description>
		<content:encoded><![CDATA[<p>Daniel is spot on&#8230;. The current SQR does a horribily inefficient processing on the bug changes.  Making it smaller to do the development (to simply change the ETL to use Analytic Query step) makes perfect sense.  Adding back in the 5 million records should certainly be feasible, once the ETL is refactored.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deinspanjer</title>
		<link>http://blog.mozilla.com/data/2009/06/05/creating-a-sample-bugzilla-database-using-kettle/comment-page-1/#comment-4</link>
		<dc:creator>deinspanjer</dc:creator>
		<pubDate>Mon, 08 Jun 2009 12:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/data/?p=13#comment-4</guid>
		<description>The bmo bugs_activity table has several million records in it.  The size of this table was a limitation due to the way the ETL is processing history currently.  The only tables we did special processing on were bugs, bugs_activity, and users.

The other tables that we didn&#039;t copy were left out simply to make it easier to develop, test, and debug out ETL processes.</description>
		<content:encoded><![CDATA[<p>The bmo bugs_activity table has several million records in it.  The size of this table was a limitation due to the way the ETL is processing history currently.  The only tables we did special processing on were bugs, bugs_activity, and users.</p>
<p>The other tables that we didn&#8217;t copy were left out simply to make it easier to develop, test, and debug out ETL processes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Kanat-Alexander</title>
		<link>http://blog.mozilla.com/data/2009/06/05/creating-a-sample-bugzilla-database-using-kettle/comment-page-1/#comment-3</link>
		<dc:creator>Max Kanat-Alexander</dc:creator>
		<pubDate>Mon, 08 Jun 2009 04:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/data/?p=13#comment-3</guid>
		<description>This is really incredible and involved, but for the copying part, why didn&#039;t you just copy everything except for longdescs and attach_data? Those are the only two tables that are of any size. All of the other tables are pretty tiny, relatively.

-Max</description>
		<content:encoded><![CDATA[<p>This is really incredible and involved, but for the copying part, why didn&#8217;t you just copy everything except for longdescs and attach_data? Those are the only two tables that are of any size. All of the other tables are pretty tiny, relatively.</p>
<p>-Max</p>
]]></content:encoded>
	</item>
</channel>
</rss>
