: "The request sent by the client was syntactically incorrect (missing content
: stream)"
that usually means either the content type wasn't set, or there was no
post data
: curl http://localhost:8983/solr/update/csv --data-binary @blog.csv -H
: 'Content-type:text/plain; charset=utf-8'
:
:
Make a view in your database and index that. No point in duplicating
database views in Solr. --wunder
On 9/27/08 2:47 PM, "Britske" <[EMAIL PROTECTED]> wrote:
>
> Looking at the wiki, code of DataImportHandler and it looks impressive.
> There's talk about ways to use Transformers to be able to cr
If I understand your question right ... you would not need a
transformer, basically you nest entities under each other ... ie:
driver="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost/nhldb?
connectTimeout=0&autoReconnect=true" user="root" password=""
batchSize="-1"/>
process
Looking at the wiki, code of DataImportHandler and it looks impressive.
There's talk about ways to use Transformers to be able to create several
rows (solr docs) based on a single db row.
I'd like to know if it's possible to do the exact opposite: to build
customer transformers that take multip
Hello,
I would like to update my index with a csv file, but for some reason I get
the following error:
"The request sent by the client was syntactically incorrect (missing content
stream)"
I get it after using the following statement:
curl http://localhost:8983/solr/update/csv --data-binary @b
The question I have is what is the optimal approach for integrating
realtime into SOLR? What classes should be extended or created?
On Sat, Sep 27, 2008 at 9:40 AM, Otis Gospodnetic
<[EMAIL PROTECTED]> wrote:
> Solr today is not suited for real-time search (seeing newly added docs in
> search re
Solr today is not suited for real-time search (seeing newly added docs in
search results as soon as they've been added - the way databases work, for
example). Work on that is in progress, though.
Otis --
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
>
On Sep 26, 2008, at 2:10 PM, Otis Gospodnetic wrote:
It might be easiest to store the thread ID and the number of replies
in the thread in each post Document in Solr.
Yeah, but that would mean updating every document in a thread every
time a new reply is added.
I still keep going back to
I am indexing data provided by the users our web site. If load on the site
increases, the rate of the commits also increases. The nature of the data is
such that it should get reflected in the index instantaneously.
On Sat, Sep 27, 2008 at 4:00 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Fri
