RE: SolrException: Invalid Date String:'oracle.sql.TIMESTAMP

2012-01-12 Thread Colin Bennett
Hi,

It looks like a date formatting issue, the Solr date field expects something
like 1995-12-31T23:59:59.999Z

See http://lucene.apache.org/solr/api/org/apache/solr/schema/DateField.html

The data import handler does have a date transformer to convert dates

http://wiki.apache.org/solr/DataImportHandler#DateFormatTransformer


Colin.



-Original Message-
From: Joey Grimm [mailto:jgr...@rim.com] 
Sent: Thursday, January 12, 2012 1:05 PM
To: solr-user@lucene.apache.org
Subject: SolrException: Invalid Date String:'oracle.sql.TIMESTAMP

Hi,

I am trying to use a dataImportHandler to import data from an oracle DB.  It
works for non-date fields but is throwing an exception once I included the
MODIFIEDDATE field (oracle.timestamp field).  Can anyone see what I'm doing
wrong here?  Thanks.



schema.xml
   


db-data-config.xml











WARNING: Error creating document :
SolrInputDocument[{catModifiedDate=catModifiedDate(1.0)={oracle.sql.TIMESTAM
P@1e58565},
masterId=masterId(1.0)={124}, catParentId=catParentId(1.0)={118},
catIconId=catIconId(1.0)={304856}}]
org.apache.solr.common.SolrException: ERROR: [doc=124] Error adding field
'catModifiedDate'='oracle.sql.TIMESTAMP@1e58565'
at
org.apache.solr.update.DocumentBuilder.toDocument(DocumentBuilder.java:324)
at
org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProc
essorFactory.java:60)
at
org.apache.solr.update.processor.LogUpdateProcessor.processAdd(LogUpdateProc
essorFactory.java:115)
at
org.apache.solr.handler.dataimport.SolrWriter.upload(SolrWriter.java:73)
at
org.apache.solr.handler.dataimport.DataImportHandler$1.upload(DataImportHand
ler.java:293)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:
636)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:268
)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:187)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.ja
va:359)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:427
)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:408)
Caused by: org.apache.solr.common.SolrException: Invalid Date
String:'oracle.sql.TIMESTAMP@1e58565'
at org.apache.solr.schema.DateField.parseMath(DateField.java:165)
at org.apache.solr.schema.TrieField.createField(TrieField.java:421)
at
org.apache.solr.schema.TrieDateField.createField(TrieDateField.java:120)
at
org.apache.solr.schema.SchemaField.createField(SchemaField.java:104)
at
org.apache.solr.update.DocumentBuilder.addField(DocumentBuilder.java:203)
at
org.apache.solr.update.DocumentBuilder.toDocument(DocumentBuilder.java:281)

--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrException-Invalid-Date-String-oracle-
sql-TIMESTAMP-tp3654419p3654419.html
Sent from the Solr - User mailing list archive at Nabble.com.





RE: Hitting the URI limit, how to get around this?

2011-06-03 Thread Colin Bennett
It sounds like you need to increase the HTTP header size.

In tomcat the default is 4096 bytes, and to change it you need to add
maxHttpHeaderSize="" to the connector definition in server.xml 

Colin.

-Original Message-
From: Ken Krugler [mailto:kkrugler_li...@transpac.com] 
Sent: Friday, June 03, 2011 12:39 PM
To: solr-user@lucene.apache.org
Subject: Re: Hitting the URI limit, how to get around this?

It sounds like you're hitting the max URL length (8K is a common default)
for the HTTP web server that you're using to run Solr.

All of the web servers I know about let you bump this limit up via
configuration settings.

-- Ken

On Jun 3, 2011, at 9:27am, JohnRodey wrote:

> So here's what I'm seeing: I'm running Solr 3.1
> I'm running a java client that executes a Httpget (I tried HttpPost) with
a
> large shard list.  If I remove a few shards from my current list it
returns
> fine, when I use my full shard list I get a "HTTP/1.1 400 Bad Request".
If
> I execute it in firefox with a few shards removed it returns fine, with
the
> full shard list I get a blank screen returned immediately.
> 
> My URI works at around 7800 characters but adding one more shard to it
blows
> up.
> 
> Any ideas? 
> 
> I've tried using SolrJ rather than httpget before but ran into similar
> issues but with even less shards.
> See 
>
http://lucene.472066.n3.nabble.com/Long-list-of-shards-breaks-solrj-query-td
2748556.html
>
http://lucene.472066.n3.nabble.com/Long-list-of-shards-breaks-solrj-query-td
2748556.html 
> 
> My shards are added dynamically, every few hours I am adding new shards or
> cores into the cluster.  so I cannot have a shard list in the config files
> unless I can somehow update them while the system is running.
> 
> --
> View this message in context:
http://lucene.472066.n3.nabble.com/Hitting-the-URI-limit-how-to-get-around-t
his-tp3017837p3020185.html
> Sent from the Solr - User mailing list archive at Nabble.com.

--
Ken Krugler
+1 530-210-6378
http://bixolabs.com
custom data mining solutions