Brad,
Please contact me at marcusattrueprobitydotcom...I would like to touch base
with you.
Thanks
Marcus
I like the embedded solr client suggestion. I'll try that one out. I don't
think sending a CSV file will work for my case, I will have to go generate a
CSV then index the CSV, as opposed to indexing while generating my content.
Thanks
2010/1/28 Yonik Seeley
> On Thu, Jan 28, 2010 at 4:58 PM, br
On Thu, Jan 28, 2010 at 4:58 PM, brad anderson wrote:
> 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.
Why not? If you use something like SolrJ, it's an implementation
detail if there is a transport, and what it i
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(
On Mon, Jan 25, 2010 at 8:03 PM, brad anderson 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 perfor
Greetings,
I'm trying to create a faster index generator for testing purposes. Using
lucene has helped immensely to increase indexing speed. However, my schema
includes a TrieDateField. I do not know how to correctly index this field
type using Lucene's API's.
I've tried the following:
new DateFi
