> Building on a library like jQuery (which is a great lib) opens the door to
> some hairy namespacing conflicts with existing libraries (prototype and moo,
> for instance), or handcoded javascript that may exist on the current site.
This is actually one of the areas where jQuery offers capabilit
I just installed SOLR-75 patch and the "schema browser" is able to view
the schema perfectly. When I used the default schema with SOLR,
everything is fine, but when I replace my schema ... it's throws this
NullPointerException
One thing to note is that the "schema browser" as currently in
This page on the wiki is probably your best place to start:
http://wiki.apache.org/solr/UpdateXmlMessages
-Greg
On 4/6/07, Bill Tantzen <[EMAIL PROTECTED]> wrote:
>
> There's no way to do that directly at the moment, you'll need
> to convert them to the XML format that Solr expects.
>
Would s
I'm still surprised we have solr plugins instead of "Solr Panels."
On 12/22/06, Kevin Lewandowski <[EMAIL PROTECTED]> wrote:
Yes! There's no shortage of puns when using solr. We're always talking
about "creating a solr system" or "one of the solr systems is down" :)
On 12/21/06, Erik Hatcher <[
I have created one in a sample application (i.e. it works, but I have
not used it in any heavy load or production sense) using the
SpellChecker package from the Lucene 2.1 branch. Solr provides an
excellent foundation for extension, so it is not too difficult to get
going, but it does take some j