RE: ord on TrieDateField always returning max

. Perhaps I'll file a bug... a field would have to be declared to have no more than 1 token and features that require it would have to check. ~ David Smiley hossman wrote: : My 'inspiration' for the ord method was actually the Solr 1.4 Enterprise : Search server book. Page 126 has a section

query function query; what's it for?

It's not clear to me what purpose the query function query solves. I've read the description: http://wiki.apache.org/solr/FunctionQuery#query but it doesn't really explain the point of it. I'm sure it has to do with subtleties in how scoring is done. Can someone please present a use-case? ~

Re: Using Solr for term-completion with counts

Jon, there actually is an example of this in my book. Go to page 156. I looked and found term-suggest in the index. ~ David Smiley Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/ Jonathan Hendler-3 wrote: Greetings all, We're happily migrating our MySQL fulltext

Re: search by some functionality

Maybe I'm missing something, but function queries aren't involved in determining whether a document matches or not, only its score. How is a a custom function / value-source going to filter? ~ David Smiley hossman wrote: : I read about this chapter before. It did not mention how

Re: spellcheck.onlyMorePopular

I know your issue has already been addressed but you may want to consider gran being a synonym for grand and then analyzing it as such. ~ David Smiley Marcus Stratmann wrote: Hello, I have another question concerning the spell checking mechanism. Setting onlyMorePopular=true and using

Re: NPE in MultiSegmentReader$MultiTermDocs.doc

Although I'm not answering your question (others have), why are you even doing this at all with Solr when you could take advantage of Solr's filter queries (fq param)? ~ David Smiley Comron Sattari-3 wrote: I've recently upgraded to Solr 1.3 using Lucene 2.4. One of the reasons I upgraded

Re: Release of solr 1.4 autosuggest

Sorry for budding in on this thread but what value is added by TermComponent when you can use faceting for auto-suggest? And with faceting, you can limit the suggestion by existing words before the word the user is typing by using it for q. ~ David Smiley Pooja Verlani wrote: Hi All, I am

Lucene project subprojects news RSS feed?

On the main lucene web page: http://lucene.apache.org/index.html There is a list of news items spanning all the lucene subprojects. Does anyone know if there is an RSS feed or announce mailing list that has this information? ~ David Smiley -- View this message in context: http

dataimport, both splitBy and dateTimeFormat

trying to apply the dateTimeFormat before splitBy. I think this is a bug... dataimport should apply DateFormatTransformer and NumberFormatTransformer last. ~ David Smiley -- View this message in context: http://www.nabble.com/dataimport%2C-both-splitBy-and-dateTimeFormat-tp20013006p20013006

Re: dataimport, both splitBy and dateTimeFormat

in which you specify them. So make sure your entity has transformers=RegexTransformer,DateFormatTransformer. On Thu, Oct 16, 2008 at 6:14 PM, David Smiley @MITRE.org [EMAIL PROTECTED]wrote: I'm trying out the dataimport capability. I have a column that is a series of dates separated

Re: AW: Cross-context-forward to solr-instance

/servlet servlet-mapping servlet-nameselectDefaultCore/servlet-name url-pattern/select/*/url-pattern /servlet-mapping The only problem I've seen so far is that if I echo the params (echoParams=all), I see the output doubled. Weird but inconsequential. ~ David Smiley Hachmann wrote

SolrCore, reload, synonyms not reloaded

the index actually doesn't get reloaded somehow and so it still uses the old synonyms file. I have no idea; just a shot in the dark. ~ David Smiley -- View this message in context: http://www.nabble.com/SolrCore%2C-reload%2C-synonyms-not-reloaded-tp19339767p19339767.html Sent from the Solr - User

Re: boost ignored with wildcard queries

Curious... Why is ConstantScoreQuery only applied to prefix queries? Your rationale suggests that it is also applicable wildcard query and fuzzy query too (basically any place an analyzer isn't used). ~ David Smiley Yonik Seeley wrote: On Tue, Feb 26, 2008 at 7:23 PM, Head [EMAIL PROTECTED

Re: Log levels setting

I agree with you Jerome. It seems to me that the SolrCore.execute() should log at DEBUG level (aka FINE in JUL parlance), not INFO. I too don't want to raise the log level to WARN which would throw out the baby with the bath water. For now, I'm just going to modify SolrCore line 958 since I'm

Re: Standard vs. DisMaxQueryHandler

(which is perhaps why this is a problem to this day). At least that's my plan, having not gotten started. ~ David Smiley hossman wrote: : I am frustrated that I have to pick between the two because I want both. The : way I look at it, there should be a more configurable query handler which

Re: Standard vs. DisMaxQueryHandler

(which is perhaps why this is a problem to this day). At least that's my plan, having not gotten started. ~ David Smiley hossman wrote: : I am frustrated that I have to pick between the two because I want both. The : way I look at it, there should be a more configurable query handler which

Re: Standard vs. DisMaxQueryHandler

encapsulate these internal details into my search service -- where it belongs IMO. ~ David Smiley hossman_lucene wrote: : Is the main difference between the StandardQueryHandler and : DisMaxQueryHandler the supported query syntax (and different query : parser used in each of them), and the fact

Re: Standard vs. DisMaxQueryHandler

Now you've got it Hossman. I don't plan on mucking with the parser syntax. I look at this feature as a smarter default field. Instead of it being one field, it is an array of them constructed via Dismax with various boosts. ~ David hossman wrote: : Either I use defType of DISMAX to get

Re: Standard vs. DisMaxQueryHandler

it belongs IMO. ~ David Smiley hossman_lucene wrote: : Is the main difference between the StandardQueryHandler and : DisMaxQueryHandler the supported query syntax (and different query : parser used in each of them), and the fact that the latter creates : DisjunctionMaxQueries, while

Re: XSLT transform before update?

field column=field1_2 template=${e.field1} ${e.field2}/ /entity Please let us know what u think about this. And keep giving us these great use-cases so that we can make the tool better. --Noble On Mon, Apr 21, 2008 at 12:07 AM, David Smiley @MITRE.org [EMAIL PROTECTED] wrote

Re: XSLT transform before update?

need, let me see how best we can accomodate it in DataImportHandler. Which XSLT processor will you prefer? On Sat, Apr 19, 2008 at 12:13 AM, David Smiley @MITRE.org [EMAIL PROTECTED] wrote: I'm in the same situation as you Daniel. The DataImportHandler is pretty awesome but I'd also

Re: XSLT transform before update?

I'm in the same situation as you Daniel. The DataImportHandler is pretty awesome but I'd also prefer it had the power of XSLT. The XPath support in it doesn't suffice for me. And I can't do very basic things like concatenate one value with another, say a constant even. It's too bad there

<    1   2   3   4