You may be having classloader issues. I'm not sure where you have the
driver jar, but it may need to be copied into the lib directory with core
Solr jars.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Sep 9, 2022 at 4:58 PM Joel Bernstein wrote:
> Can you post the stack trace from the
Can you post the stack trace from the log?
It looks like the JDBCStream is registered, but the stack trace may provide
some more info on why the driver didn't load.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Sep 9, 2022 at 12:51 PM James Greene
wrote:
> I'm still unable to get the J
Hi All,
When calling the DELETESTATUS API to clear all the stored statues as below
http://localhost:8983/solr/admin/collections?action=DELETESTATUS&flush=true
throws exception
KeeperErrorCode = Directory not empty for
/overseer/collection-map-completed/mn-.auto_add_replicas
at
org.
I'm still unable to get the JDBC stream to work. I've verified that 'jdbc'
shows up in the plugin list:
http://localhost:8983/solr/col1/stream?action=PLUGINS
When using the DIH I use the jdbc driver:
org.mariadb.jdbc.Driver
With connection string:
jdbc:mysql://{{host}}:{{port}}/{{database}}
I
This isn’t documented in the Ref Guide right? @Joel, throw me a JIRA and I’ll
add it ;-)
> On Sep 8, 2022, at 10:15 PM, Joel Bernstein wrote:
>
> The jdbc stream was removed from the standard expression library for
> security reasons. It is still in the jars though and can be included
> throu
Not related to the word-delimiter token filter but I did a study a while
ago on the sow parameter, identified a couple of bugs and fixed one (the
other was discussed and in the end not accepted as an improvement as it was
controversial).
https://sease.io/2021/05/apache-solr-sow-parameter-split-on-
Automatic pre-processing of documents may be a good fit for an Update
Request Processor.
In Apache Solr I contributed a while back to the:
https://sease.io/2015/07/solr-document-classification-part-1-indexing-time.html
This update request processor internally uses the Apache Lucene document
class
I made this work with 6.x but don’t remember the details, sorry. I think it
wanted application/something, maybe the POST format.
wunder
> On Sep 9, 2022, at 1:38 PM, Mikhail Khludnev wrote:
>
> Hold on. JSON query DSL lets you pass quite long content via body. It
> should support {!mlt}. At
Hold on. JSON query DSL lets you pass quite long content via body. It
should support {!mlt}. At least it's worth a try.!
On Thu, Sep 8, 2022 at 2:53 PM Mikhail Khludnev wrote:
> Hello Batanun
> I checked {!mlt} source code. It can't swallow external content. I've
> found that Lucene XML parser
>
