thanks.
On Fri, Jun 22, 2012 at 6:12 PM, Erick Erickson wrote:
> You should be able to compile your new plugin and use the
> directive in solrconfig.xml to point to your new jar. Solr
> should have access to all the lucene jar files at that point.
>
> I usually build plugins after checking out a
You should be able to compile your new plugin and use the
directive in solrconfig.xml to point to your new jar. Solr
should have access to all the lucene jar files at that point.
I usually build plugins after checking out all of the Solr source and
doing an "ant dist" and pathing my IDE correctly
What you are describing corrisponds pretty closely to some work currently
in progress to make the DataImportHandler integrate with the
ExtractingRequestHandler/Tika ...
https://issues.apache.org/jira/browse/SOLR-1358
...in the meantime, your options are either to extract all the metad
: plugin.query.parser.QueryParserPluginOne" in logs. I am sure that the
: request handler with which this query parser plugin is linked is
: working,Because I could find the results of System.out.println()s
: (those included in requesthandler) in log, but not query parser
: plugin's System.outs or
Hi,
I am not changing any URL while querying because the custom query
parser plugin is linked with the default request handler.You may have
a look at my first mail for xml snippets which is included in
solrconfig.xml .
Yeah.. I found the line .. "INFO: created queryParserPluginOne:
plugi
On Oct 27, 2009, at 12:58 PM, Phanindra Reva wrote:
Hello All,
I am a newbie, learning Solr - plugins concept. While
following the tutorials on the same from
http://wiki.apache.org/solr/SolrPlugins , I have tried to work on
Query Parser plugin concept by extending QParserPlugin class.
Hello All,
I am a newbie, learning Solr - plugins concept. While
following the tutorials on the same from
http://wiki.apache.org/solr/SolrPlugins , I have tried to work on
Query Parser plugin concept by extending QParserPlugin class.
I have registered my custom plugin class in solrconf
