Thanks Yonik, I think commiting code to solr would not fix the problem. I don't want to have to go through the HTTP stack to create an index. I need to create various indices with different params for testing purposes. In this case, its easiest to just use lucene.
I used the TrieDate.createField() to get the date working properly. I think for people wanting to create indices themselves very quickly, they can use the DocumentBuilder class. It needs certain objects which contain the configurations in the schema file. I did not have the time to investigate quick ways to load these objects using a schema file. I'm sure the code is there somewhere in solr.core package. If that is the case, I would suggest people having the same problem as me should use DocumentBuilder to convert SolrInputDocuments to Lucene Documents. There is probably a way to read in a schema file, and this would greatly decrease index generation time. Thanks, Brad 2010/1/25 Yonik Seeley <yo...@lucidimagination.com> > On Mon, Jan 25, 2010 at 8:03 PM, brad anderson <solrinter...@gmail.com> > wrote: > > I'm trying to create a faster index generator for testing purposes. Using > > lucene has helped immensely to increase indexing speed. > > Have you tried using other indexing methods such as CSV or > StreamingUpdateSolrServer? > If there are any performance issues, fixing it once and letting > everyone enjoy the benefits is preferable than having everyone write > their own indexing code. > > [...] > > Does anyone > > know how to correctly index a TrieDateField using Lucene API's? > > Check the code for TrieDateField.createField(). The stored value is a > binary long. > > -Yonik > http://www.lucidimagination.com >
