<?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: Exploring Lucene and Solr&#8217;s TrieRange Capabilities</title>
	<atom:link href="http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/</link>
	<description>Exclusively dedicated to Apache Lucene/Solr open source search technology</description>
	<lastBuildDate>Sat, 04 Feb 2012 01:13:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Todd Nine</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-6485</link>
		<dc:creator>Todd Nine</dc:creator>
		<pubDate>Wed, 06 Oct 2010 18:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-6485</guid>
		<description>Hey guys,
  Just an FYI, numeric ranges aren&#039;t properly indexed or returned in Lucene unless you use a precision step of Integer.MAX.  This is currently a bug within the LuceneTermEnum not enumerating over results properly.  I&#039;ve filed the bug and I&#039;m working on the fix, but you should be leery of depending on accurate results with the current source version ( 56007e4630932be57699)

http://github.com/tjake/Lucandra/issues#issue/40</description>
		<content:encoded><![CDATA[<p>Hey guys,<br />
  Just an FYI, numeric ranges aren&#8217;t properly indexed or returned in Lucene unless you use a precision step of Integer.MAX.  This is currently a bug within the LuceneTermEnum not enumerating over results properly.  I&#8217;ve filed the bug and I&#8217;m working on the fix, but you should be leery of depending on accurate results with the current source version ( 56007e4630932be57699)</p>
<p><a href="http://github.com/tjake/Lucandra/issues#issue/40" rel="nofollow">http://github.com/tjake/Lucandra/issues#issue/40</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucid Imagination &#187; Lucene and Solr: the Java of data</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3952</link>
		<dc:creator>Lucid Imagination &#187; Lucene and Solr: the Java of data</dc:creator>
		<pubDate>Fri, 23 Oct 2009 15:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3952</guid>
		<description>[...] there. One new thing you can do with Lucene 2.9 and Solr 1.4 more readily, is to use the new numeric search to encode proprietary business rules around ranges within data. In general, since the data is [...]</description>
		<content:encoded><![CDATA[<p>[...] there. One new thing you can do with Lucene 2.9 and Solr 1.4 more readily, is to use the new numeric search to encode proprietary business rules around ranges within data. In general, since the data is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucid Imagination &#187; Ranges over Functions in Solr 1.4</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3535</link>
		<dc:creator>Lucid Imagination &#187; Ranges over Functions in Solr 1.4</dc:creator>
		<pubDate>Tue, 07 Jul 2009 01:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3535</guid>
		<description>[...] course, Solr 1.4 also contains the new TrieRange functionality that will generally have the best time/space profile for range queries over numeric [...]</description>
		<content:encoded><![CDATA[<p>[...] course, Solr 1.4 also contains the new TrieRange functionality that will generally have the best time/space profile for range queries over numeric [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ranges over Functions in Solr 1.4 &#171; Solr &#8216;n Stuff</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3534</link>
		<dc:creator>Ranges over Functions in Solr 1.4 &#171; Solr &#8216;n Stuff</dc:creator>
		<pubDate>Tue, 07 Jul 2009 01:37:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3534</guid>
		<description>[...] course, Solr 1.4 also contains the new TrieRange functionality that will generally have the best time/space profile for range queries over numeric [...]</description>
		<content:encoded><![CDATA[<p>[...] course, Solr 1.4 also contains the new TrieRange functionality that will generally have the best time/space profile for range queries over numeric [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uwe Schindler</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3452</link>
		<dc:creator>Uwe Schindler</dc:creator>
		<pubDate>Wed, 03 Jun 2009 14:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3452</guid>
		<description>Hi Aleksander,

the only drawbacks of TrieRange are a little bit larger index sizes, because of the additional terms indexed, and you cannot read the values with tools like Luke at the moment.

TrieRange fields can be natively sorted (so the FieldCache uses no String comparison, they are parsed to longs/ints/...) and so function queries are also possible. Additionally TrieRange also supports dates (there is a &quot;tdate&quot;, too), which are stored natively (as unix ts in long format, see Date.getTime()). So sorting by date is very fast and you can also do ranges down to the millisecond. So I would recommend tdate for every date-time datatype! Date math is also possible in queries like with standard dt field types.</description>
		<content:encoded><![CDATA[<p>Hi Aleksander,</p>
<p>the only drawbacks of TrieRange are a little bit larger index sizes, because of the additional terms indexed, and you cannot read the values with tools like Luke at the moment.</p>
<p>TrieRange fields can be natively sorted (so the FieldCache uses no String comparison, they are parsed to longs/ints/&#8230;) and so function queries are also possible. Additionally TrieRange also supports dates (there is a &#8220;tdate&#8221;, too), which are stored natively (as unix ts in long format, see Date.getTime()). So sorting by date is very fast and you can also do ranges down to the millisecond. So I would recommend tdate for every date-time datatype! Date math is also possible in queries like with standard dt field types.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant Ingersoll</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3411</link>
		<dc:creator>Grant Ingersoll</dc:creator>
		<pubDate>Wed, 20 May 2009 11:11:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3411</guid>
		<description>Hi Aleksander,

I&#039;m not sure on your questions just yet, as I have only begun to explore the TrieRange capability.  One thought, though, on dates, is I think Dates are currently stored as Strings (I presume you are talking Solr) and thus, storing as primitive Dates should be more compact, thus using less disk space, memory, etc.  That being said, we likely should have a new Date field in Solr that stores as primitives even w/o the primitives.</description>
		<content:encoded><![CDATA[<p>Hi Aleksander,</p>
<p>I&#8217;m not sure on your questions just yet, as I have only begun to explore the TrieRange capability.  One thought, though, on dates, is I think Dates are currently stored as Strings (I presume you are talking Solr) and thus, storing as primitive Dates should be more compact, thus using less disk space, memory, etc.  That being said, we likely should have a new Date field in Solr that stores as primitives even w/o the primitives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Solr/Lucene Feature Alert: TrieRange Capabilities &#124; Productification</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3407</link>
		<dc:creator>Solr/Lucene Feature Alert: TrieRange Capabilities &#124; Productification</dc:creator>
		<pubDate>Wed, 20 May 2009 01:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3407</guid>
		<description>[...] you want to read more, you can read the article posted by Grant on Lucid&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] you want to read more, you can read the article posted by Grant on Lucid&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StauthamerNet :: Staut&#8217;s Family Blog&#187; Blog Archive &#187; links for 2009-05-17</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3398</link>
		<dc:creator>StauthamerNet :: Staut&#8217;s Family Blog&#187; Blog Archive &#187; links for 2009-05-17</dc:creator>
		<pubDate>Sun, 17 May 2009 23:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3398</guid>
		<description>[...] Lucid Imagination » Exploring Lucene and Solr’s TrieRange Capabilities Recently, Uwe Schindler and others have added a new capability to Lucene and Solr to make working with numeric ranges a lot faster. I haven’t tried out this new functionality yet, so I thought I would walk through it here and explore it’s capabilities. [...]</description>
		<content:encoded><![CDATA[<p>[...] Lucid Imagination » Exploring Lucene and Solr’s TrieRange Capabilities Recently, Uwe Schindler and others have added a new capability to Lucene and Solr to make working with numeric ranges a lot faster. I haven’t tried out this new functionality yet, so I thought I would walk through it here and explore it’s capabilities. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Webhamer Weblog: Search &#38; ICT-related blogging &#187; links for 2009-05-17</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3397</link>
		<dc:creator>Webhamer Weblog: Search &#38; ICT-related blogging &#187; links for 2009-05-17</dc:creator>
		<pubDate>Sun, 17 May 2009 22:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3397</guid>
		<description>[...] Lucid Imagination » Exploring Lucene and Solr’s TrieRange Capabilities Recently, Uwe Schindler and others have added a new capability to Lucene and Solr to make working with numeric ranges a lot faster. I haven’t tried out this new functionality yet, so I thought I would walk through it here and explore it’s capabilities. [...]</description>
		<content:encoded><![CDATA[<p>[...] Lucid Imagination » Exploring Lucene and Solr’s TrieRange Capabilities Recently, Uwe Schindler and others have added a new capability to Lucene and Solr to make working with numeric ranges a lot faster. I haven’t tried out this new functionality yet, so I thought I would walk through it here and explore it’s capabilities. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aleksander Stensby</title>
		<link>http://www.lucidimagination.com/blog/2009/05/13/exploring-lucene-and-solrs-trierange-capabilities/comment-page-1/#comment-3390</link>
		<dc:creator>Aleksander Stensby</dc:creator>
		<pubDate>Fri, 15 May 2009 09:23:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.lucidimagination.com/blog/?p=646#comment-3390</guid>
		<description>Great overview, Grant! What would you say are the drawbacks of using the trie range field type for foreign key like fields that you sometimes want to sort on or put range limitations on? And do you have any thoughts on efficiency of representing dates as primitives instead of the Date field, if you use date as a sort field very often?
- Aleksander</description>
		<content:encoded><![CDATA[<p>Great overview, Grant! What would you say are the drawbacks of using the trie range field type for foreign key like fields that you sometimes want to sort on or put range limitations on? And do you have any thoughts on efficiency of representing dates as primitives instead of the Date field, if you use date as a sort field very often?<br />
- Aleksander</p>
]]></content:encoded>
	</item>
</channel>
</rss>

