[ 
https://issues.apache.org/jira/browse/SOLR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806798#comment-13806798
 ] 

ettey siva commented on SOLR-1604:
----------------------------------

Hi Ahmet
I have installed complexphrase parser and followed all instructions for 
installation... 
Everything is fine except getting NULL Pointer exception when I start JBOSS.

19:46:03,909 ERROR [SolrCore] java.lang.NullPointerException
        at 
org.apache.solr.schema.IndexSchema$DynamicReplacement$DynamicPattern$NameEndsWith.matches(IndexSchema.java:960)
        at 
org.apache.solr.schema.IndexSchema$DynamicReplacement.matches(IndexSchema.java:974)
        at 
org.apache.solr.schema.IndexSchema.getDynamicFieldType(IndexSchema.java:1221)
        at 
org.apache.solr.schema.IndexSchema$SolrQueryAnalyzer.getWrappedAnalyzer(IndexSchema.java:418)
        at 
org.apache.lucene.analysis.AnalyzerWrapper.initReader(AnalyzerWrapper.java:81)
        at org.apache.lucene.analysis.Analyzer.tokenStream(Analyzer.java:175)
        at 
org.apache.lucene.queryparser.classic.QueryParserBase.newFieldQuery(QueryParserBase.java:507)
        at 
org.apache.lucene.queryparser.classic.QueryParserBase.getFieldQuery(QueryParserBase.java:495)
        at 
org.apache.lucene.queryparser.classic.QueryParserBase.handleBareTokenQuery(QueryParserBase.java:1109)
        at 
org.apache.lucene.queryparser.classic.QueryParser.Term(QueryParser.java:358)
        at 
org.apache.lucene.queryparser.classic.QueryParser.Clause(QueryParser.java:257)
        at 
org.apache.lucene.queryparser.classic.QueryParser.Query(QueryParser.java:181)
        at 
org.apache.lucene.queryparser.classic.QueryParser.TopLevelQuery(QueryParser.java:170)
        at 
org.apache.lucene.queryparser.classic.QueryParserBase.parse(QueryParserBase.java:121)
        at 
org.apache.lucene.queryparser.classic.ComplexPhraseQueryParser.parse(ComplexPhraseQueryParser.java:107)
        at 
org.apache.solr.search.ComplexPhraseQParser.parse(ComplexPhraseQParserPlugin.java:108)
        at org.apache.solr.search.QParser.getQuery(QParser.java:142)
        at 
org.apache.solr.handler.component.QueryComponent.prepare(QueryComponent.java:142)
        at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:187)
        at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:1904)
        at 
org.apache.solr.core.QuerySenderListener.newSearcher(QuerySenderListener.java:64)
        at org.apache.solr.core.SolrCore$5.call(SolrCore.java:1693)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Thanks in advance.

> Wildcards, ORs etc inside Phrase Queries
> ----------------------------------------
>
>                 Key: SOLR-1604
>                 URL: https://issues.apache.org/jira/browse/SOLR-1604
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers, search
>    Affects Versions: 1.4
>            Reporter: Ahmet Arslan
>            Priority: Minor
>         Attachments: ASF.LICENSE.NOT.GRANTED--ComplexPhrase.zip, 
> ComplexPhrase-4.2.1.zip, ComplexPhraseQueryParser.java, 
> ComplexPhrase_solr_3.4.zip, ComplexPhrase.zip, ComplexPhrase.zip, 
> ComplexPhrase.zip, ComplexPhrase.zip, ComplexPhrase.zip, ComplexPhrase.zip, 
> SOLR-1604-alternative.patch, SOLR-1604.patch, SOLR-1604.patch
>
>
> Solr Plugin for ComplexPhraseQueryParser (LUCENE-1486) which supports 
> wildcards, ORs, ranges, fuzzies inside phrase queries.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to