Re: SOLR-470 & default value in schema with NOW (update)

2008-05-16 Thread Chris Hostetter
: The problem appeared for me any time I tried to mix using the default : value NOW with any documents that had this data. That should be a 2 : document set to recreate the problem if it is the case. I didn't try : that hard to isolate the problem, I just changed my data and removed the : defa

Re: SOLR-470 & default value in schema with NOW (update)

2008-05-07 Thread Mike Klaas
On 7-May-08, at 5:04 AM, Daniel Papasian wrote: Chris Hostetter wrote: The two exceptions you cited both indicate there was at least one date instance with no millis included -- NOW can't do that. it always inlcudes millis (even though it shouldn't). I've seen people suggest, for perform

Re: SOLR-470 & default value in schema with NOW (update)

2008-05-07 Thread Daniel Papasian
Chris Hostetter wrote: > The two exceptions you cited both indicate there was at least one date > instance with no millis included -- NOW can't do that. it always inlcudes > millis (even though it shouldn't). I've seen people suggest, for performance reasons, that they reduce the granularity o

Re: SOLR-470 & default value in schema with NOW (update)

2008-05-06 Thread Brian Johnson
ema. Thanks, Brian - Original Message From: Chris Hostetter <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Tuesday, May 6, 2008 9:41:20 PM Subject: Re: SOLR-470 & default value in schema with NOW (update) : Second Try: : * same date column setup : * 2 files uploaded into th

Re: SOLR-470 & default value in schema with NOW (update)

2008-05-06 Thread Chris Hostetter
: Second Try: : * same date column setup : * 2 files uploaded into the index. Updated the file with the timestamps : to be 3 digit millis to 'match' what NOW was supposed to be doing. I : left the other file alone. : --> got the exception.. check data in Luke to confirm it was all 3 digit : mi

Re: SOLR-470 & default value in schema with NOW (update)

2008-04-27 Thread Brian Johnson
: termfrequency : 2008-04-24T09:03:53Z11076 : 2008-04-24T09:03:55Z10036 i'm assuming "11076" and "10036" are the term frequencies? Yes - the cut-n-paste didn't do a good job separating the columns : This now seems to be something different than SOLR-470 and SOLR-544 : since the format seems to

Re: SOLR-470 & default value in schema with NOW (update)

2008-04-27 Thread Chris Hostetter
: Ok, I thought the quickest thing to try out would be (B) so now all of : my feeds have the same format and I have removed the default value "NOW" : from my schema.xml file. ... : I rebuilt my index with consistent date formats in all my files but my : exception remains unchanged.

Re: SOLR-470 & default value in schema with NOW

2008-04-27 Thread Chris Hostetter
: Now finally, my problem. The format for NOW doesn't seem to be : documented so I have no idea what I need to 'match' (or even that : matching is necessary from the documentation outside these 2 bugs) in : order to take advantage of the default value feature and mix that with : data from my s

Re: SOLR-470 & default value in schema with NOW (update)

2008-04-24 Thread Brian Johnson
x, but is still not accepted at query time. Anyone have a suggestion? Thanks, Brian Johnson - Original Message From: Brian Johnson <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Wednesday, April 23, 2008 11:23:54 AM Subject: SOLR-470 & default value in schema

SOLR-470 & default value in schema with NOW

2008-04-23 Thread Brian Johnson
So I just ran into this bug: https://issues.apache.org/jira/browse/SOLR-470 and read about this related one: https://issues.apache.org/jira/browse/SOLR-544 Here is the relevant trace: Apr 22, 2008 10:59:01 PM org.apache.solr.common.SolrException log SEVERE: java.lang.RuntimeException: ja