Phrase field matches not counting towards minimum match
Ok let me explain what I am trying to do first since there may be a better approach. Recently I had been trying to increase solr's matching precision by requiring that all of the words in a field match before allowing a match on a field. I am using edismax as my query parser and since it tokenizes on white space there's no way to make sure that if my query is q=foo bar and I have a field named somefield indexed as a text field with foo bar that foo doesn't match and bar doesn't match but the phrase "foo bar" does match. I feel like I'm not explaining this very well but basically what I want to do has already been done by Lucid works: https://lucidworks.com/2014/07/02/automatic-phrase-tokenization-improving-lucene-search-precision-by-more-precise-linguistic-analysis/ However their solution requires that you use a pluggable query parser which is not an extension of edismax. Now I haven't done a deep comparison but I'm assuming I would lose access to all of edismax's parameters if I used their pluggable query parser. So instead I tried to replicate this functionality using edismax's pf2 and pf3 parameters. It all works beautifully the way I have it setup except that phrase field matches don't count towards my mm count. Ok so now I will go into detail about how I have my index setup for this specific example. I am using solr's default text field to index a field named manufacturer2 here are the relevant parameters of my search q=livex lighting 8193 qf=productid, manufacturer_stop pf2=manufacturer2 mm=3<-1 5<-2 6<90% now I am stopping the word lighting from my manufacturer_stop field using stopwords so only livex is matching in the manufacturer_stop field However "livex lighting" is matching in the manufacturer2 field using phrase field matching in the pf2 parameter. so my matches are the following: MATCH livex in manufacturer_stop field MATCH 8193 in productid field MATCH "livex lighting" in manufacturer 2 field as a phrase field match so I have three matches... however the phrase field match doesn't seem be be counting towards my mm match requirement of 3 tokens passed 3 must match. If I change my mm to require only 2 tokens must match I get the expected result. But I want my phrase field to count towards my mm match requirement since lighting is matching in my phrase field. Any assistance would be appreciated Or if someone could suggest a better approach that would also be appreciated. -- View this message in context: http://lucene.472066.n3.nabble.com/Phrase-field-matches-not-counting-towards-minimum-match-tp4322066.html Sent from the Solr - User mailing list archive at Nabble.com.
Solr Suggest and weightField
I am trying to figure out how to give weights to my suggestions but I can find no documentation on how to do this correctly. Here is my configuration: solrconfig.xml mySuggester DocumentDictionaryFactory FuzzyLookupFactory suggest popularity textSuggest false true The popularity field and weightField are defined in my schema In my suggest field I copy several other fields to be used for suggestions: However whenever I perform a search I get 0 for the weights even though popularity values exist for the documents. /solr/productindex/select?suggest=true=koh=true Results: 1 kohler 0 Can someone please explain to me how to use weightField and payload so that I can give some ranking to my suggested terms. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Suggest-and-weightField-tp4234681.html Sent from the Solr - User mailing list archive at Nabble.com.
Solr DIH using JDBC with TIKA
I'm trying to index certain data from a table and documents located on disk
using jdbc and tika. I can derive the file locations from the table and
using that data I want to also import documents into Solr. However I'm
having trouble with my configuration.
dataConfig
dataSource type=JdbcDataSource
name=db
jndiName=java:comp/env/jdbc/BuildDB
/
dataSource name=data type=BinURLDataSource /
dataSource name=dataUrl type=BinURLDataSource/
document
entity
name=productDocument
onError=skip
datsource=db
query=SELECT pa.prdAttachmentID id, pa.productId, pa.manufacturer,
pa.fileName, pa.attachmentType, pa.displayName,
lower('/mnt/shares/nasdev/mediabase/specifications/' +
pa.manufacturer +
'/' + CAST(pm.productid_manufacturer_id AS VARCHAR(50))) basePath,
pa.fileName
FROM mmc.dbo.product_attachments pa WITH (NOLOCK)
INNER JOIN mmc.dbo.productid_manufacturer pm WITH
(NOLOCK) ON
pa.productId = pm.productid and pa.manufacturer = pm.manufacturer
WHERE pa.productid = '3551LF'
field column=id name=id/
field column=productCompositeid name=productCompositeid/
field column=productid name=productid/
field column=manufacturer name=manufacturer/
field column=filename name=filename/
field column=displayname name=displayname/
field column=attachmentType type=text indexed=true
stored=true /
entity name=f processor=FileListEntityProcessor
baseDir=${productDocument.basePath} fileName=${productDocument.filename}
dataSource=data onError=skip
entity name=extract processor=TikaEntityProcessor
url=${f.fileAbsolutePath}
field column=title meta=true name=author/
field column=text name=text/
/entity
/entity
/entity
/document
/dataConfig
The error is as follows:
32367126 [Thread-1180] ERROR org.apache.solr.handler.dataimport.DocBuilder
? Exception while processing: productDocument document :
SolrInputDocument(fields: [id=395623, manufacturer=Delta,
filename=delta_3551lf_parts_1027.pdf, displayname=Parts Breakdown,
attachmentType=ExplodedParts,
productid=3551LF]):org.apache.solr.handler.dataimport.DataImportHandlerException:
Unable to execute query:
/mnt/shares/nasdev/mediabase/specifications/delta/181075/delta_3551lf_spec_1027.pdf
Processing Document # 1
at
org.apache.solr.handler.dataimport.DataImportHandlerException.wrapAndThrow(DataImportHandlerException.java:71)
at
org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.init(JdbcDataSource.java:281)
at
org.apache.solr.handler.dataimport.JdbcDataSource.getData(JdbcDataSource.java:238)
at
org.apache.solr.handler.dataimport.JdbcDataSource.getData(JdbcDataSource.java:42)
at
org.apache.solr.handler.dataimport.TikaEntityProcessor.nextRow(TikaEntityProcessor.java:112)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:243)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:477)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:503)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:503)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:416)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:331)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:239)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:411)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:483)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:464)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax
near '/'.
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:792)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:662)
at
org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
at
Re: Solr DIH using JDBC with TIKA
Got it working with the updated config:
dataConfig
dataSource type=JdbcDataSource
name=db
jndiName=java:comp/env/jdbc/BuildDB
/
dataSource name=bin type=BinFileDataSource /
document
entity
name=productDocument
onError=skip
datsource=db
query=SELECT pa.prdAttachmentID id, pa.productId, pa.manufacturer,
pa.fileName, pa.attachmentType, pa.displayName,
lower('/mnt/shares/nasdev/mediabase/specifications/' +
pa.manufacturer +
'/' + CAST(pm.productid_manufacturer_id AS VARCHAR(50)) + '/' + pa.fileName)
URL
FROM mmc.dbo.product_attachments pa WITH (NOLOCK)
INNER JOIN mmc.dbo.productid_manufacturer pm WITH
(NOLOCK) ON
pa.productId = pm.productid and pa.manufacturer = pm.manufacturer
WHERE pa.productid = '3551LF'
field column=id name=id/
field column=productCompositeid name=productCompositeid/
field column=productid name=productid/
field column=manufacturer name=manufacturer/
field column=filename name=filename/
field column=displayname name=displayname/
field column=attachmentType type=text indexed=true
stored=true /
entity name=extract dataSource=bin
processor=TikaEntityProcessor url=${productDocument.URL} format=text
field column=title meta=true name=title/
field column=text name=text/
/entity
/entity
/document
/dataConfig
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-DIH-using-JDBC-with-TIKA-tp4180737p4180742.html
Sent from the Solr - User mailing list archive at Nabble.com.
Solr Query Elevation Component
The documentation is very unclear (at least to me) around Query Elevation Component and filter queries (fq param) The documentation for Solr 4.9 states: The fq Parameter Query elevation respects the standard filter query (fq) parameter. That is, if the query contains the fq parameter, all results will be within that filter even if elevate.xml adds other documents to the result set. Now when I read this it made me think that only documents that are contained in the result set could be filtered. So when I apply a filter using the fq param that removes a document from the result set it should no longer be elevated. I have tested the elevator component using the elevateId's and elevate.xml and both still elevate documents that have been filtered from the result set using the fq parameter IF they exist in the result set before filtering. I would like to have the elevate component have an optional flag. Something like showFiltered=false where any results that have been filtered from the result set with the fq parameter will no longer be elevated. I have created the following ticket if anybody wants to take a stab at it: https://issues.apache.org/jira/browse/SOLR-6308 -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Query-Elevation-Component-tp4150531.html Sent from the Solr - User mailing list archive at Nabble.com.
CollapseQParserPlugin problem with ElevateComponent
https://issues.apache.org/jira/browse/SOLR-5773 I am having trouble with CollapseQParserPlugin showing duplicate groups when the search results contain a member of a grouped document but another member of that grouped document is defined in the elevate component. I have described the issue in more detail here: https://issues.apache.org/jira/browse/SOLR-5773 Any help is appreciated. Also any hints as to how I can solve this problem myself would be great as I'm having a bit of trouble understanding the code to implement a fix. -- View this message in context: http://lucene.472066.n3.nabble.com/CollapseQParserPlugin-problem-with-ElevateComponent-tp4119596.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: CollapseQParserPlugin problem with ElevateComponent
Hi Joel, Thank you for the reply. I created https://issues.apache.org/jira/browse/SOLR-5773 for this new feature. I was looking at the getBoostDocs() function and if I understand it correctly it iterates through the boosted set that is passed into the function and then iterates over the boosted SetString and casts each element to a BytesRef and stores it in a HashSet. While I'm confused what all the type conversion is actually doing I can follow the logic somewhat. You then traverse the index and retrieve all of the terms for the uniqueid of the schema. You then seek in the localBoosts hashset for the current document and if it is in the index you add it to boostDocs to be returned from the function as well as remove the document from the localBoosts hashset. I don't think the document is actually removed from the result set in this function however. I spent some hours today trying to decipher some of this code. I am very interested in understanding this code so that I can contribute back to this project but I am finding it all a bit daunting. As always your help is greatly appreciated and thank you for the quick response. On Tue, Feb 25, 2014 at 5:38 PM, Joel Bernstein [via Lucene] ml-node+s472066n411966...@n3.nabble.com wrote: Hi David, Just read through your comments on the jira. Feel free to create a jira for this. The way this currently works is that if the elevated document is not the selected group head, then both the elevated document and the group head are in the result set. What you are suggesting is that the elevated document becomes the group head. We can discuss the best way to handle this on the new ticket. Joel Joel Bernstein Search Engineer at Heliosearch On Tue, Feb 25, 2014 at 1:29 PM, dboychuck [hidden email]http://user/SendEmail.jtp?type=nodenode=4119662i=0 wrote: https://issues.apache.org/jira/browse/SOLR-5773 I am having trouble with CollapseQParserPlugin showing duplicate groups when the search results contain a member of a grouped document but another member of that grouped document is defined in the elevate component. I have described the issue in more detail here: https://issues.apache.org/jira/browse/SOLR-5773 Any help is appreciated. Also any hints as to how I can solve this problem myself would be great as I'm having a bit of trouble understanding the code to implement a fix. -- View this message in context: http://lucene.472066.n3.nabble.com/CollapseQParserPlugin-problem-with-ElevateComponent-tp4119596.html Sent from the Solr - User mailing list archive at Nabble.com. -- If you reply to this email, your message will be added to the discussion below: http://lucene.472066.n3.nabble.com/CollapseQParserPlugin-problem-with-ElevateComponent-tp4119596p4119662.html To unsubscribe from CollapseQParserPlugin problem with ElevateComponent, click herehttp://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4119596code=ZGJveWNodWNrQGJ1aWxkLmNvbXw0MTE5NTk2fDE3MjM1MzAyMTk= . NAMLhttp://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- *David Boychuck* Software Engineer Search, Team Lead Build.com, Inc. http://corp.build.com/ Smarter Home Improvement(tm) P.O. Box 7990 Chico, CA 95927 *P*: 800.375.3403 *F*: 530.566.1893 dboych...@build.com | Network of Storeshttp://www.build.com/index.cfm?page=help:networkstoressource=emailSignature -- View this message in context: http://lucene.472066.n3.nabble.com/CollapseQParserPlugin-problem-with-ElevateComponent-tp4119596p4119680.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Cloud error with shard update
I have created Jira issue here: https://issues.apache.org/jira/browse/SOLR-5551 -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Cloud-error-with-shard-update-tp4106260p4106448.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Error when creating collection in Solr 4.6
Where did you add that directive? I am having the same problem. -- View this message in context: http://lucene.472066.n3.nabble.com/Error-when-creating-collection-in-Solr-4-6-tp4103536p4106248.html Sent from the Solr - User mailing list archive at Nabble.com.
Solr Cloud error with shard update
I am running a data import and it is throwing all kinds of errors. I am upgrading to 4.6 from 4.5.1 with the exact schema and solrconfig and dih configs. Here is the error I am getting: org.apache.solr.common.SolrException: ERROR: [doc=k-690kohler!670614] Error adding field 'weight'='java.math.BigDecimal:9.28' msg=For input string: java.math.BigDecimal:9.28 at org.apache.solr.update.DocumentBuilder.toDocument(DocumentBuilder.java:167) at org.apache.solr.update.AddUpdateCommand.getLuceneDocument(AddUpdateCommand.java:77) at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:215) at org.apache.solr.update.processor.RunUpdateProcessor.processAdd(RunUpdateProcessorFactory.java:69) at org.apache.solr.update.processor.UpdateRequestProcessor.processAdd(UpdateRequestProcessor.java:51) at org.apache.solr.update.processor.DistributedUpdateProcessor.doLocalAdd(DistributedUpdateProcessor.java:569) at org.apache.solr.update.processor.DistributedUpdateProcessor.versionAdd(DistributedUpdateProcessor.java:705) at org.apache.solr.update.processor.DistributedUpdateProcessor.processAdd(DistributedUpdateProcessor.java:435) at org.apache.solr.update.PeerSync.handleUpdates(PeerSync.java:482) at org.apache.solr.update.PeerSync.handleResponse(PeerSync.java:330) at org.apache.solr.update.PeerSync.sync(PeerSync.java:260) at org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:387) at org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:244) Caused by: java.lang.NumberFormatException: For input string: java.math.BigDecimal:9.28 at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1241) at java.lang.Float.parseFloat(Float.java:452) at org.apache.solr.schema.TrieField.createField(TrieField.java:593) at org.apache.solr.schema.TrieField.createFields(TrieField.java:650) at org.apache.solr.update.DocumentBuilder.addField(DocumentBuilder.java:47) at org.apache.solr.update.DocumentBuilder.toDocument(DocumentBuilder.java:118) ... 12 more It looks like there is a problem with the readJavaFormat() function on a tried field? -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Cloud-error-with-shard-update-tp4106260.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Cloud error with shard update
Here is the output from the logs of the server running the import: 598413 [updateExecutor-1-thread-62] ERROR org.apache.solr.update.StreamingSolrServers – error org.apache.solr.common.SolrException: Bad Request request: http://solr-shard-5.sys.id.build.com:8080/solr/productindex/update?update.distrib=FROMLEADERdistrib.from=http%3A%2F%2Fsolr-shard-4.sys.id.build.com%3A8080%2Fsolr%2Fproductindex%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:240) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2598413 [updateExecutor-1-thread-63] ERROR org.apache.solr.update.StreamingSolrServers – error org.apache.solr.common.SolrException: Bad Request request: http://solr-shard-6.sys.id.build.com:8080/solr/productindex/update?update.distrib=FROMLEADERdistrib.from=http%3A%2F%2Fsolr-shard-4.sys.id.build.com%3A8080%2Fsolr%2Fproductindex%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:240) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2598449 [updateExecutor-1-thread-63] ERROR org.apache.solr.update.StreamingSolrServers – error org.apache.solr.common.SolrException: Bad Request request: http://solr-shard-5.sys.id.build.com:8080/solr/productindex/update?update.distrib=FROMLEADERdistrib.from=http%3A%2F%2Fsolr-shard-4.sys.id.build.com%3A8080%2Fsolr%2Fproductindex%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:240) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2598449 [updateExecutor-1-thread-62] ERROR org.apache.solr.update.StreamingSolrServers – error org.apache.solr.common.SolrException: Bad Request request: http://solr-shard-6.sys.id.build.com:8080/solr/productindex/update?update.distrib=FROMLEADERdistrib.from=http%3A%2F%2Fsolr-shard-4.sys.id.build.com%3A8080%2Fsolr%2Fproductindex%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:240) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2598493 [updateExecutor-1-thread-63] ERROR org.apache.solr.update.StreamingSolrServers – error org.apache.solr.common.SolrException: Bad Request request: http://solr-shard-6.sys.id.build.com:8080/solr/productindex/update?update.distrib=FROMLEADERdistrib.from=http%3A%2F%2Fsolr-shard-4.sys.id.build.com%3A8080%2Fsolr%2Fproductindex%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:240) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2598494 [updateExecutor-1-thread-62] ERROR org.apache.solr.update.StreamingSolrServers – error org.apache.solr.common.SolrException: Bad Request request: http://solr-shard-5.sys.id.build.com:8080/solr/productindex/update?update.distrib=FROMLEADERdistrib.from=http%3A%2F%2Fsolr-shard-4.sys.id.build.com%3A8080%2Fsolr%2Fproductindex%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:240) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2598538 [updateExecutor-1-thread-63] ERROR org.apache.solr.update.StreamingSolrServers – error org.apache.solr.common.SolrException: Bad Request request: http://solr-shard-6.sys.id.build.com:8080/solr/productindex/update?update.distrib=FROMLEADERdistrib.from=http%3A%2F%2Fsolr-shard-4.sys.id.build.com%3A8080%2Fsolr%2Fproductindex%2Fwt=javabinversion=2 at org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:240) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at
Re: Solr Cloud error with shard update
And here are the logs of one of the replicas: 2286617 [Thread-146] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286627 [Thread-147] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286638 [Thread-159] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286641 [Thread-160] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286643 [Thread-158] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286645 [Thread-154] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286647 [Thread-155] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286648 [Thread-157] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286650 [Thread-152] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286652 [Thread-150] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286654 [Thread-151] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286655 [Thread-148] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2286657 [Thread-156] WARN org.apache.solr.cloud.RecoveryStrategy – Stopping recovery for zkNodeName=core_node2core=productindex 2290696 [RecoveryThread] ERROR org.apache.solr.update.PeerSync – PeerSync: core=productindex url=http://solr-shard-5.sys.id.build.com:8080/solr Error applying updates from [Ljava.lang.String;@6c8cbe52 ,update=[1, 1454173058518482944, SolrInputDocument(fields: [productAddDate=Fri Aug 17 12:03:00 PDT 2007, keywords_84_txtws=[K-690, Vinnata], InstallationType_string=Deck Mounted, InstallationAvailable_boolean=true, popularity_82_i=98960, pricebook_26_fs=[700.88, 483.64, 630.30], keywords_15_txtws=[K-690, Vinnata], keywords_33_txtws=[K-690, Vinnata], keywords_5_txtws=[K-690, Vinnata], uniquePricebook_28_f=700.88, PulloutSpray_boolean=true, pricebook_28_fs=[700.88, 483.64, 630.30], uniquePricebook_27_f=700.88, type_string=faucet, popularity_84_i=97124, uniquePricebook_29_f=700.88, popularity_85_i=3940, productid=k-690, masterFinish=[Chromes, Nickel Tones, Chromes, Bronze Tones, Nickel Tones, Bronze Tones], description=pem**Note: This faucet is extremely large please see specification sheet below for dimensions. If you are looking for this same faucet but a little smaller. nbsp;Please check out the K-691./em/p pstrongProduct Features:/strong/p ul liFully covered under Kohler's limited lifetime warranty/li liAll-metal faucet body and handle construction/li liSuperior finishing process - faucet finish covered under lifetime warranty/li liIncludes cover plate (escutcheon) for sinks with 3-holes (8 centers)/li liInsulated pullout spray faucet head and retractable hose/li liVinnata kitchen faucets not only boast good looks, but superior functionality as well/li liFeaturing a MasterClean spray face that resists hard water build-up/li liSpout swivels 360 degrees to allow for unobstructed sink access/li liHigh-arch gooseneck spout further allows for unobstructed sink access/li /ul pstrongProduct Specifications:/strong/p ul liOverall Height: 16-5/8 (measured from counter top to highest point of faucet)/li liSpout Height: 10 (measured from counter top to faucet outlet)/li liSpout Reach: 9-1/2 (measured from center of faucet base to center of faucet outlet)/li liNumber of installation holes required: 1/li li2.2 gallons-per-minute flow rate/li liMaximum Deck Thickness: 1-3/8/li li1 handle included/li liADA compliant/li liLow lead compliant - complies with federal and state regulations for lead content/li liDesigned to easily connect to standard U.S. plumbing supply bibs/li liSecure mounting assembly/li liAll necessary mounting hardware included/li /ul pstrongVariations:/strong/p ul listrongK-690:/strong This model/li listrongK-691:/strong Bar (smaller) version of this model/li /ul pstrongAbout Kohler:/strong/p pGracious living is characterized by qualities of charm, good taste, generosity of spirit and the enhancement of nature. It is Kohlerrsquo;s mission that you can improve your sense of gracious living with every experience you have with a Kohler product or service./p pWith everything that Kohler does it lives on the leading edge of design and technology, while maintaining a constant level of quality regardless of price. Kohler sets the standard of excellence in its field, and yet is constantly striving to improve./p pFrom sustainable products in the kitchen and bath, to engines for lawn tractors and
Re: solr 4.3 solrj generating search terms that return no results
Thanks Shawn! That makes sense now. I appreciate the response. -- View this message in context: http://lucene.472066.n3.nabble.com/solr-4-3-solrj-generating-search-terms-that-return-no-results-tp4077137p4099615.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr 4.3 solrj generating search terms that return no results
I'm having the same issue with solrJ 4.5.1 If I use the escapeQueryChars() function on a string like a b c it is escaping it to a\+b\+c which returns 0 results using edismax query parser. However a b c returns results. -- View this message in context: http://lucene.472066.n3.nabble.com/solr-4-3-solrj-generating-search-terms-that-return-no-results-tp4077137p4099524.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Error with CollapsingQParserPlugin when trying to use tagging
The following unit test in TestCollapseQParserPlugin.java illustrates the
bug
ModifiableSolrParams params = new ModifiableSolrParams();
params.add(q, *:*);
params.add(fq, {!collapse field=group_s});
params.add(defType, edismax);
params.add(bf, field(test_ti));
params.add(fq,{!tag=test_ti}test_ti:5);
params.add(facet,true);
params.add(facet.field,{!ex=test_ti}test_ti);
assertQ(req(params), *[count(//doc)=1],
//doc[./int[@name='test_ti']='5'])
On Thu, Oct 31, 2013 at 6:46 PM, dboychuck [via Lucene]
ml-node+s472066n4098710...@n3.nabble.com wrote:
Here is an example URL that gives the error:
solr/productindex/productQuery?fq={!collapse%20field=groupid}fq=discontinued:falsefq={!tag=manufacturer_string}manufacturer_string:(%22delta%22%20OR%20%22kohler%22)fq=siteid:82sort=score%20descfacet=truestart=0rows=48fl=productid,manufacturer,uniqueFinish,uniqueid,productCompositeid,scorefacet.query={!ex=onSale}onSale:truefacet.query={!ex=rating}rating:[4%20TO%20*]facet.query={!ex=rating}rating:[3%20TO%20*]facet.query={!ex=rating}rating:[2%20TO%20*]facet.query={!ex=rating}rating:[1%20TO%20*]facet.query={!ex=MadeinAmerica_boolean}MadeinAmerica_boolean:yesfacet.query={!ex=inStock}inStock:truefacet.query={!ex=PulloutSpray_string}PulloutSpray_string:yesfacet.query={!ex=HandlesIncluded_string}HandlesIncluded_string:yesfacet.query={!ex=Electronic_string}Electronic_string:yesfacet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[0%20TO%201]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[1%20TO%202]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[2%20TO%203]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[4%20TO%205]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[3%20TO%204]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[5%20TO%20*]facet.query={!ex=ADA_string}ADA_string:yesfacet.query={!ex=WaterSenseCertified_string}WaterSenseCertified_string:yesfacet.query={!ex=WaterfallFaucet_boolean}WaterfallFaucet_boolean:yesfacet.query={!ex=InstallationAvailable_string}InstallationAvailable_string:yesfacet.query={!ex=LowLeadCompliant_string}LowLeadCompliant_string:yesfacet.query={!ex=DrainAssemblyIncluded_string}DrainAssemblyIncluded_string:yesfacet.query={!ex=EscutcheonIncluded_string}EscutcheonIncluded_string:yesfacet.field=NumberOfHandles_numericfacet.field=pricebook_1_fsfacet.field=SpoutReach_numericfacet.field=SpoutHeight_numericfacet.field=FaucetCenters_numericfacet.field=OverallHeight_numericfacet.field=FaucetHoles_numericfacet.field=HandleStyle_stringfacet.field=masterFinish_stringfacet.field={!ex=manufacturer_string}manufacturer_stringfacet.field=HandleMaterial_stringfacet.field=ValveType_stringfacet.field=Theme_stringfacet.field=MountingType_stringqt=/productQueryqf=sku^9.0%20upc^9.1%20keywords_82_txtws^1.9%20uniqueid^9.0%20series^2.8%20productTitle^1.2%20productid^9.0%20manufacturer^4.0%20masterFinish^1.5%20theme^1.1%20categoryNames_82_txt^0.2%20finish^1.4pf=keywords_82_txtws^2.1%20productTitle^1.5%20manufacturer^4.0%20finish^1.9bf=linear(popularity_82_i,1,2)^3.0q.alt=categories_82_is:108503
Taking out tagging I do not receive the error:
/solr/productindex/productQuery?fq={!collapse%20field=groupid}fq=discontinued:falsefq=manufacturer_string:(%22delta%22%20OR%20%22kohler%22)fq=siteid:82sort=score%20descfacet=truestart=0rows=48fl=productid,manufacturer,uniqueFinish,uniqueid,productCompositeid,scorefacet.query={!ex=onSale}onSale:truefacet.query={!ex=rating}rating:[4%20TO%20*]facet.query={!ex=rating}rating:[3%20TO%20*]facet.query={!ex=rating}rating:[2%20TO%20*]facet.query={!ex=rating}rating:[1%20TO%20*]facet.query={!ex=MadeinAmerica_boolean}MadeinAmerica_boolean:yesfacet.query={!ex=inStock}inStock:truefacet.query={!ex=PulloutSpray_string}PulloutSpray_string:yesfacet.query={!ex=HandlesIncluded_string}HandlesIncluded_string:yesfacet.query={!ex=Electronic_string}Electronic_string:yesfacet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[0%20TO%201]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[1%20TO%202]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[2%20TO%203]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[4%20TO%205]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[3%20TO%204]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[5%20TO%20*]facet.query={!ex=ADA_string}ADA_string:yesfacet.query={!ex=WaterSenseCertified_string}WaterSenseCertified_string:yesfacet.query={!ex=WaterfallFaucet_boolean}WaterfallFaucet_boolean:yesfacet.query={!ex=InstallationAvailable_string}InstallationAvailable_string:yesfacet.query={!ex=LowLeadCompliant_string}LowLeadCompliant_string:yesfacet.query={!ex=DrainAssemblyIncluded_string}DrainAssemblyIncluded_string:yesfacet.query={!ex=EscutcheonIncluded_string}EscutcheonIncluded_string:yesfacet.field=NumberOfHandles_numericfacet.field=pricebook_1_fsfacet.field=SpoutReach_numericfacet.field=SpoutHeight_numericfacet.field=FaucetCenters_numericfacet.field=OverallHeight_numericfacet.field
Re: Error with CollapsingQParserPlugin when trying to use tagging
I've created the following tracker for the issue: https://issues.apache.org/jira/browse/SOLR-5416 -- View this message in context: http://lucene.472066.n3.nabble.com/Error-with-CollapsingQParserPlugin-when-trying-to-use-tagging-tp4098709p4098862.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Error with CollapsingQParserPlugin when trying to use tagging
Here is an example URL that gives the error:
solr/productindex/productQuery?fq={!collapse%20field=groupid}fq=discontinued:falsefq={!tag=manufacturer_string}manufacturer_string:(%22delta%22%20OR%20%22kohler%22)fq=siteid:82sort=score%20descfacet=truestart=0rows=48fl=productid,manufacturer,uniqueFinish,uniqueid,productCompositeid,scorefacet.query={!ex=onSale}onSale:truefacet.query={!ex=rating}rating:[4%20TO%20*]facet.query={!ex=rating}rating:[3%20TO%20*]facet.query={!ex=rating}rating:[2%20TO%20*]facet.query={!ex=rating}rating:[1%20TO%20*]facet.query={!ex=MadeinAmerica_boolean}MadeinAmerica_boolean:yesfacet.query={!ex=inStock}inStock:truefacet.query={!ex=PulloutSpray_string}PulloutSpray_string:yesfacet.query={!ex=HandlesIncluded_string}HandlesIncluded_string:yesfacet.query={!ex=Electronic_string}Electronic_string:yesfacet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[0%20TO%201]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[1%20TO%202]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[2%20TO%203]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[4%20TO%205]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[3%20TO%204]facet.query={!ex=FlowRateGPM_numeric}FlowRateGPM_numeric:[5%20TO%20*]facet.query={!ex=ADA_string}ADA_string:yesfacet.query={!ex=WaterSenseCertified_string}WaterSenseCertified_string:yesfacet.query={!ex=WaterfallFaucet_boolean}WaterfallFaucet_boolean:yesfacet.query={!ex=InstallationAvailable_string}InstallationAvailable_string:yesfacet.query={!ex=LowLeadCompliant_string}LowLeadCompliant_string:yesfacet.query={!ex=DrainAssemblyIncluded_string}DrainAssemblyIncluded_string:yesfacet.query={!ex=EscutcheonIncluded_string}EscutcheonIncluded_string:yesfacet.field=NumberOfHandles_numericfacet.field=pricebook_1_fsfacet.field=SpoutReach_numericfacet.field=SpoutHeight_numericfacet.field=FaucetCenters_numericfacet.field=OverallHeight_numericfacet.field=FaucetHoles_numericfacet.field=HandleStyle_stringfacet.field=masterFinish_stringfacet.field={!ex=manufacturer_string}manufacturer_stringfacet.field=HandleMaterial_stringfacet.field=ValveType_stringfacet.field=Theme_stringfacet.field=MountingType_stringqt=/productQueryqf=sku^9.0%20upc^9.1%20keywords_82_txtws^1.9%20uniqueid^9.0%20series^2.8%20productTitle^1.2%20productid^9.0%20manufacturer^4.0%20masterFinish^1.5%20theme^1.1%20categoryNames_82_txt^0.2%20finish^1.4pf=keywords_82_txtws^2.1%20productTitle^1.5%20manufacturer^4.0%20finish^1.9bf=linear(popularity_82_i,1,2)^3.0q.alt=categories_82_is:108503
Taking out tagging I do not receive the error:
Error with CollapsingQParserPlugin when trying to use tagging
I ran into an error with the CollapsingQParserPlugin when trying to use it in
tandem with tagging
I get the following error whenever I use {!tag} in the same request as
{!collapse field=groupid}
Oct 31, 2013 6:43:56 PM org.apache.tomcat.util.http.Cookies
processCookieHeader
INFO: Cookies: Invalid cookie. Value not a token or quoted value
Note: further occurrences of Cookie errors will be logged at DEBUG level.
121624 [http-bio-8080-exec-1] ERROR org.apache.solr.core.SolrCore –
java.lang.NullPointerException
at
org.apache.solr.search.CollapsingQParserPlugin$CollapsingScoreCollector.collect(CollapsingQParserPlugin.java:409)
at
org.apache.solr.search.SolrIndexSearcher.getDocSet(SolrIndexSearcher.java:910)
at
org.apache.solr.request.SimpleFacets.parseParams(SimpleFacets.java:219)
at
org.apache.solr.request.SimpleFacets.getFacetFieldCounts(SimpleFacets.java:549)
at
org.apache.solr.request.SimpleFacets.getFacetCounts(SimpleFacets.java:265)
at
org.apache.solr.handler.component.FacetComponent.process(FacetComponent.java:78)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:208)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1859)
at
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:703)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:406)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1008)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
121635 [http-bio-8080-exec-1] ERROR
org.apache.solr.servlet.SolrDispatchFilter –
null:java.lang.NullPointerException
at
org.apache.solr.search.CollapsingQParserPlugin$CollapsingScoreCollector.collect(CollapsingQParserPlugin.java:409)
at
org.apache.solr.search.SolrIndexSearcher.getDocSet(SolrIndexSearcher.java:910)
at
org.apache.solr.request.SimpleFacets.parseParams(SimpleFacets.java:219)
at
org.apache.solr.request.SimpleFacets.getFacetFieldCounts(SimpleFacets.java:549)
at
org.apache.solr.request.SimpleFacets.getFacetCounts(SimpleFacets.java:265)
at
org.apache.solr.handler.component.FacetComponent.process(FacetComponent.java:78)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:208)
at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
at org.apache.solr.core.SolrCore.execute(SolrCore.java:1859)
at
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:703)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:406)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
Solr 4.5.1 Overseer error
I am upgrading from 4.4 to 4.5.1 I used to just upload my configurations to zookeeper and then install solr with no default core Solr would give me an error that no cores were created when I tried to access until I ran the collections API create command to make a collection however now when I try to install solr with no default core I get a generic error about path cannot end with / and I can't create the cores using the collections api when I manually copy the files over and create the core through the interface it all works as expected any help would be appreciated Here is the error i'm seeing http://pastebin.com/cEfpSEqe here's my solr.xml http://pastebin.com/kBLv9Vvt and here are my startup arguments http://pastebin.com/7tCrSpX9 -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-5-1-Overseer-error-tp4098160.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Cloud Distributed IDF
I am indexing documents using the domin:id format ex id = k-690kohler!670614 This ensures that all k-690kohler documents are indexed to the same shard. This does cause numDocs that are not perfectly distributed across shards probably even worse than the default sharding algorithm. Here is the search on Solr Cloud http://solrsolr/productindex/productQuery?q=categories_82_is:108996bf=linear(popularity_82_i,1,2)^3debugQuery=true And on Solr 3.6 http://solr-2-build.sys.id.build.com:8080/solr-build/select?q.alt=categoryId:108996qt=dismaxbf=linear(popularity,1,2)^3debugQuery=truefl=id,productID,manufacturer Here is the debug output from Solr Cloud lst name=explain str name=921rusticware!1210842 48481.992 = (MATCH) sum of: 4.7323933 = (MATCH) weight(categories_82_is:`#8;#0;#6;SD in 248779) [DefaultSimilarity], result of: 4.7323933 = score(doc=248779,freq=1.0 = termFreq=1.0 ), product of: 0.8745785 = queryWeight, product of: 5.411056 = idf(docFreq=3181, maxDocs=262058) 0.16162805 = queryNorm 5.411056 = fieldWeight in 248779, product of: 1.0 = tf(freq=1.0), with freq of: 1.0 = termFreq=1.0 5.411056 = idf(docFreq=3181, maxDocs=262058) 1.0 = fieldNorm(doc=248779) 48477.26 = (MATCH) FunctionQuery(1.0*float(int(popularity_82_i))+2.0), product of: 99977.0 = 1.0*float(int(popularity_82_i)=99975)+2.0 3.0 = boost 0.16162805 = queryNorm /str str name=4706baldwin!1223898 48380.168 = (MATCH) sum of: 4.7323933 = (MATCH) weight(categories_82_is:`#8;#0;#6;SD in 67238) [DefaultSimilarity], result of: 4.7323933 = score(doc=67238,freq=1.0 = termFreq=1.0 ), product of: 0.8745785 = queryWeight, product of: 5.411056 = idf(docFreq=3181, maxDocs=262058) 0.16162805 = queryNorm 5.411056 = fieldWeight in 67238, product of: 1.0 = tf(freq=1.0), with freq of: 1.0 = termFreq=1.0 5.411056 = idf(docFreq=3181, maxDocs=262058) 1.0 = fieldNorm(doc=67238) 48375.438 = (MATCH) FunctionQuery(1.0*float(int(popularity_82_i))+2.0), product of: 99767.0 = 1.0*float(int(popularity_82_i)=99765)+2.0 3.0 = boost 0.16162805 = queryNorm /str str name=yb5405moen!1748274 48278.34 = (MATCH) sum of: 4.7323933 = (MATCH) weight(categories_82_is:`#8;#0;#6;SD in 123982) [DefaultSimilarity], result of: 4.7323933 = score(doc=123982,freq=1.0 = termFreq=1.0 ), product of: 0.8745785 = queryWeight, product of: 5.411056 = idf(docFreq=3181, maxDocs=262058) 0.16162805 = queryNorm 5.411056 = fieldWeight in 123982, product of: 1.0 = tf(freq=1.0), with freq of: 1.0 = termFreq=1.0 5.411056 = idf(docFreq=3181, maxDocs=262058) 1.0 = fieldNorm(doc=123982) 48273.61 = (MATCH) FunctionQuery(1.0*float(int(popularity_82_i))+2.0), product of: 99557.0 = 1.0*float(int(popularity_82_i)=99555)+2.0 3.0 = boost 0.16162805 = queryNorm /str str name=bp53005amerock!1721790 48262.008 = (MATCH) sum of: 4.7675867 = (MATCH) weight(categories_82_is:`#8;#0;#6;SD in 108146) [DefaultSimilarity], result of: 4.7675867 = score(doc=108146,freq=1.0 = termFreq=1.0 ), product of: 0.8758082 = queryWeight, product of: 5.4436426 = idf(docFreq=3131, maxDocs=266484) 0.16088642 = queryNorm 5.4436426 = fieldWeight in 108146, product of: 1.0 = tf(freq=1.0), with freq of: 1.0 = termFreq=1.0 5.4436426 = idf(docFreq=3131, maxDocs=266484) 1.0 = fieldNorm(doc=108146) 48257.24 = (MATCH) FunctionQuery(1.0*float(int(popularity_82_i))+2.0), product of: 99982.0 = 1.0*float(int(popularity_82_i)=99980)+2.0 3.0 = boost 0.16088642 = queryNorm /str str name=bp29340amerock!1721865 48208.918 = (MATCH) sum of: 4.7675867 = (MATCH) weight(categories_82_is:`#8;#0;#6;SD in 108031) [DefaultSimilarity], result of: 4.7675867 = score(doc=108031,freq=1.0 = termFreq=1.0 ), product of: 0.8758082 = queryWeight, product of: 5.4436426 = idf(docFreq=3131, maxDocs=266484) 0.16088642 = queryNorm 5.4436426 = fieldWeight in 108031, product of: 1.0 = tf(freq=1.0), with freq of: 1.0 = termFreq=1.0 5.4436426 = idf(docFreq=3131, maxDocs=266484) 1.0 = fieldNorm(doc=108031) 48204.15 = (MATCH) FunctionQuery(1.0*float(int(popularity_82_i))+2.0), product of: 99872.0 = 1.0*float(int(popularity_82_i)=99870)+2.0 3.0 = boost 0.16088642 = queryNorm /str str name=bp53001amerock!1314101 48176.516 = (MATCH) sum of: 4.7323933 = (MATCH) weight(categories_82_is:`#8;#0;#6;SD in 47622) [DefaultSimilarity], result of: 4.7323933 = score(doc=47622,freq=1.0 = termFreq=1.0 ), product of: 0.8745785 = queryWeight, product of: 5.411056 = idf(docFreq=3181, maxDocs=262058) 0.16162805 = queryNorm 5.411056 = fieldWeight in 47622, product of: 1.0 = tf(freq=1.0), with freq of: 1.0 = termFreq=1.0 5.411056 = idf(docFreq=3181, maxDocs=262058) 1.0 = fieldNorm(doc=47622) 48171.785 = (MATCH) FunctionQuery(1.0*float(int(popularity_82_i))+2.0), product of: 99347.0 = 1.0*float(int(popularity_82_i)=99345)+2.0 3.0 = boost 0.16162805 = queryNorm /str And here is the debug output from Solr 3.6 lst name=explain str name=bp53005amerock 15421.395 = (MATCH) sum of: 1.6594616 = (MATCH) weight(categoryId:`#8;#0;#6;SD in 45538), product of: 0.29207912 = queryWeight(categoryId:`#8;#0;#6;SD), product of:
Solr facet field counts not correct
I am running a simple query in a non-distributed search using grouping. I am getting incorrect facet field counts and I cannot figure out why. Here is the query you will notice that the facet field and facet query counts are not the same. The facet query counts are correct. Any help is appreciated. This XML file does not appear to have any style information associated with it. The document tree is shown below. response lst name=responseHeader int name=status0/int int name=QTime18/int /lst lst name=grouped lst name=groupid int name=matches89/int int name=ngroups74/int arr name=groups lst str name=groupValueuc101cadet/str result name=doclist numFound=2 start=0 doc str name=productiduc101/str arr name=finish strWhite/str strBlack/str /arr str name=uniqueFinishBlack/str str name=manufacturercadet/str int name=productCompositeid736388/int int name=uniqueid1545116/int /doc /result /lst lst str name=groupValuerm162cadet/str result name=doclist numFound=1 start=0 doc str name=productidrm162/str arr name=finish strN/A/str /arr str name=uniqueFinishN/A/str str name=manufacturercadet/str int name=productCompositeid667690/int int name=uniqueid1545089/int /doc /result /lst lst str name=groupValuecs202cadet/str result name=doclist numFound=1 start=0 doc str name=productidcs202/str arr name=finish strN/A/str /arr str name=uniqueFinishN/A/str str name=manufacturercadet/str int name=productCompositeid460865/int int name=uniqueid1545142/int /doc /result /lst lst str name=groupValuecs152cadet/str result name=doclist numFound=1 start=0 doc str name=productidcs152/str arr name=finish strN/A/str /arr str name=uniqueFinishN/A/str str name=manufacturercadet/str int name=productCompositeid458740/int int name=uniqueid1545141/int /doc /result /lst lst str name=groupValue65201cadet/str result name=doclist numFound=1 start=0 doc str name=productid65201/str arr name=finish strWhite/str /arr str name=uniqueFinishWhite/str str name=manufacturercadet/str int name=productCompositeid773769/int int name=uniqueid1999873/int /doc /result /lst lst str name=groupValuermc202cadet/str result name=doclist numFound=1 start=0 doc str name=productidrmc202/str arr name=finish strWhite/str /arr str name=uniqueFinishWhite/str str name=manufacturercadet/str int name=productCompositeid667929/int int name=uniqueid1545122/int /doc /result /lst lst str name=groupValuerbf101cadet/str result name=doclist numFound=1 start=0 doc str name=productidrbf101/str arr name=finish strChrome/str /arr str name=uniqueFinishChrome/str str name=manufacturercadet/str int name=productCompositeid663553/int int name=uniqueid1820328/int /doc /result /lst lst str name=groupValuerm202cadet/str result name=doclist numFound=1 start=0 doc str name=productidrm202/str arr name=finish strN/A/str /arr str name=uniqueFinishN/A/str str name=manufacturercadet/str int name=productCompositeid667551/int int name=uniqueid1545088/int /doc /result /lst lst str name=groupValuesl151tcadet/str result name=doclist numFound=1 start=0 doc str name=productidsl151t/str arr name=finish strWhite/str /arr str name=uniqueFinishWhite/str str name=manufacturercadet/str int name=productCompositeid710375/int int name=uniqueid1545153/int /doc /result /lst lst str name=groupValueuc102cadet/str result name=doclist numFound=2 start=0 doc str name=productiduc102/str arr name=finish strWhite/str strBlack/str /arr str name=uniqueFinishWhite/str str name=manufacturercadet/str int name=productCompositeid736389/int int name=uniqueid1820349/int /doc /result /lst /arr /lst /lst lst name=facet_counts lst name=facet_queries int name=HeatingArea_numeric:[0 TO *]23/int /lst lst name=facet_fields lst name=HeatingArea_numeric int name=128.020/int int name=250.06/int int name=500.06/int int name=250.06/int int name=500.06/int int name=250.06/int int name=500.06/int int name=375.03/int int name=375.03/int int name=374.03/int int name=125.02/int int name=200.02/int int name=125.02/int int name=200.02/int int name=125.02/int int name=200.02/int int name=32.02/int int name=175.01/int int name=300.01/int int name=400.01/int int name=550.01/int int name=175.01/int int name=300.01/int int name=400.01/int int name=550.01/int int name=175.01/int int name=300.01/int int name=400.01/int int name=548.01/int int name=512.01/int int name=100.00/int int name=220.00/int int name=420.00/int int name=610.00/int int name=640.00/int int name=710.00/int int name=720.00/int int name=750.00/int int name=770.00/int int name=835.00/int int name=850.00/int int name=860.00/int int name=870.00/int int name=900.00/int int name=910.00/int int name=920.00/int int name=930.00/int int name=940.00/int int name=950.00/int int name=1000.00/int int name=1010.00/int int name=1015.00/int int name=1020.00/int int name=1040.00/int int name=1050.00/int int name=1070.00/int int name=1090.00/int int name=1100.00/int int name=1150.00/int int name=1175.00/int int name=1200.00/int int name=1250.00/int int name=1300.00/int int name=1330.00/int int name=1360.00/int int
Re: Solr facet field counts not correct
Here is my query String: /solr/singleproductindex/productQuery?fq=siteid:82q=categories_82_is:109124facet=truefacet.query=HeatingArea_numeric:[0%20TO%20*]facet.field=HeatingArea_numericdebugQuery=true Here is my schema for that field: dynamicField name=*_numeric type=tfloatindexed=true stored=false multiValued=true/ Here is my request handler definition: requestHandler name=/productQuery class=solr.SearchHandler lst name=defaults str name=dftext/str str name=defTypeedismax/str float name=tie0.01/float str name=qf sku^9.0 upc^9.1 keywords_82_txtws^1.9 series^2.8 productTitle^1.2 productid^9.0 manufacturer^4.0 masterFinish^1.5 theme^1.1 categoryNames_82_txt^0.2 finish^1.4 uniqueFinish^1 /str str name=pf keywords_82_txtws^2.1 productTitle^1.5 manufacturer^4.0 finish^1.9 /str str name=bf linear(popularity_82_i,1,2)^3.0 /str str name=fl uniqueid,productCompositeid,productid,manufacturer,uniqueFinish,finish /str str name=mm 3lt;-1 5lt;-2 6lt;90% /str bool name=grouptrue/bool str name=group.fieldgroupid/str bool name=group.ngroupstrue/bool bool name=group.facettrue/bool int name=ps100/int int name=qs3/int str name=spellcheck.count10/str str name=spellcheck.alternativeTermCount5/str str name=spellcheck.maxResultsForSuggest5/str str name=spellcheck.collatetrue/str str name=spellcheck.collateExtendedResultstrue/str str name=spellcheck.maxCollationTries10/str str name=spellcheck.maxCollations5/str /lst arr name=last-components strspellcheck/str /arr /requestHandler -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-facet-field-counts-not-correct-tp4097305p4097306.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr facet field counts not correct
if I do group=falsegroup.facet=false the counts are what they should be for the ungrouped counts... seems like group.facet isn't working correctly -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-facet-field-counts-not-correct-tp4097305p4097314.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr facet field counts not correct
Hoss created: https://issues.apache.org/jira/browse/SOLR-5383 -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-facet-field-counts-not-correct-tp4097305p4097346.html Sent from the Solr - User mailing list archive at Nabble.com.
Solr Cloud Distributed IDF
I recently moved an index from 3.6 non-distributed to Solr Cloud 4.4 with three shards. My company uses a boosting function with a value assigned to each document. This boosting function no longer works dependably and I believe the cause is that IDF is not distributed. This seems like it should be a high priority for Solr Cloud. Does anybody know the status of this feature? I understand that the elevate component does work for Solr Cloud in version 4.5 but unfortunately it would be a pretty big leap for how we are currently using our index and our boosting function for relevancy scoring. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Cloud-Distributed-IDF-tp4097127.html Sent from the Solr - User mailing list archive at Nabble.com.
solr 4.3 solrj generating search terms that return no results
I'm having trouble with solrj generating a query like q=kohler%5C+k for the
search term 'Kohler k'
I am using Solr 4.3 in cloud mode. When I remove the %5C everything is fine.
I'm not sure why the %5C is being added when I call
solrQuery.setQuery('Kohler k');
Any help is appreciated.
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-4-3-solrj-generating-search-terms-that-return-no-results-tp4077137.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr 4.3 solrj generating search terms that return no results
solrQuery.setQuery(ClientUtils.escapeQueryChars(keyword)); It looks like using the solrj ClientUtils.escapeQueryChars function is escaping any spaces with %5C+ which returns 0 results at search time. -- View this message in context: http://lucene.472066.n3.nabble.com/solr-4-3-solrj-generating-search-terms-that-return-no-results-tp4077137p4077141.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Problems with documents that are added not showing up in index Solr 3.5
Yes I confirmed in the logs. I have also committed manually several times using the updatehandler /update?commit=true -- View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-documents-that-are-added-not-showing-up-in-index-Solr-3-5-tp4043539p4043716.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Problems with documents that are added not showing up in index Solr 3.5
numdocs is wrong and they will not show up when I search by uniqueid On Thu, Feb 28, 2013 at 10:45 AM, Upayavira [via Lucene] ml-node+s472066n4043724...@n3.nabble.com wrote: What do you mean by 'will not show up'? Is numdocs wrong? They don't show in queries? Upayavira On Thu, Feb 28, 2013, at 06:07 PM, dboychuck wrote: Yes I confirmed in the logs. I have also committed manually several times using the updatehandler /update?commit=true -- View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-documents-that-are-added-not-showing-up-in-index-Solr-3-5-tp4043539p4043716.html Sent from the Solr - User mailing list archive at Nabble.com. -- If you reply to this email, your message will be added to the discussion below: http://lucene.472066.n3.nabble.com/Problems-with-documents-that-are-added-not-showing-up-in-index-Solr-3-5-tp4043539p4043724.html To unsubscribe from Problems with documents that are added not showing up in index Solr 3.5, click herehttp://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4043539code=ZGJveWNodWNrQGJ1aWxkLmNvbXw0MDQzNTM5fDE3MjM1MzAyMTk= . NAMLhttp://lucene.472066.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- *David Boychuck* Software Engineer Build.com, Inc. http://corp.build.com/ Smarter Home Improvement™ P.O. Box 7990 Chico, CA 95927 *P*: 800.375.3403 *F*: 530.566.1893 dboych...@build.com | Network of Storeshttp://www.build.com/index.cfm?page=help:networkstoressource=emailSignature -- View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-documents-that-are-added-not-showing-up-in-index-Solr-3-5-tp4043539p4043727.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Problems with Solr 3.6 and Magento
I noticed that Magento is using the overwritePending commit directive but I can't find any documentation on this. Does the overwritePending directive purge any added docs since the last commit? Any help would be appreciated. -- View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-Solr-3-6-and-Magento-tp4043492p4043510.html Sent from the Solr - User mailing list archive at Nabble.com.
solr spellchecker hogging all of my memory
before I optimize (build my spellchecker index) my solr instance running in tomcat uses about 2 gigs of memory as soon as I optimize it jumps to about 5 gigs http://d.pr/i/oUQI it just doesn't seem right http://pastebin.com/6Cg7F0dK is there anything wrong with my configuration? when i dump the heap I can see that spellchecker is using a majority of the memory -- View this message in context: http://lucene.472066.n3.nabble.com/solr-spellchecker-hogging-all-of-my-memory-tp3997353.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Import Handler Custom Transformer not working
Thank you for your input. With your help I was able to solve my problem.
Although I could find no good example of how to handle multivalued fields
with a custom transformer online your comments helped me to find a solution.
Here is the code that handles both multi-valued and single valued fields.
package org.build.com.solr;
/**
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the License); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
import org.apache.solr.handler.dataimport.Context;
import org.apache.solr.handler.dataimport.Transformer;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
public class FacetsTransformer extends Transformer {
public Object transformRow(MapString, Object row, Context context) {
Object tf = row.get(facets);
if (tf != null) {
if (tf instanceof List) {
List list = (List) tf;
String tempKey = ;
for (Object o : list) {
String[] arr = ((String) o).split(=);
if (arr.length == 3) {
tempKey = arr[0].replaceAll([^A-Za-z0-9], ) + _ +
arr[1];
if (row.containsKey(tempKey))
{
ListString tempArrayList =
(ArrayListString)row.get(tempKey);
tempArrayList.add(arr[2]);
row.put(tempKey, tempArrayList );
} else {
ListString tempArrayList = new ArrayListString();
tempArrayList.add(arr[2]);
row.put(tempKey, tempArrayList);
}
}
}
} else {
String[] arr = ((String) tf).split(=);
if (arr.length == 3) row.put(arr[0].replaceAll([^A-Za-z0-9],
) + _ + arr[1], arr[2]);
}
row.remove(facets);
}
return row;
}
}
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Import-Handler-Custom-Transformer-not-working-tp3978746p3983704.html
Sent from the Solr - User mailing list archive at Nabble.com.
Data Import Handler with Dynamic Fields
I am trying to import data through my db but I have dynamic fields that I
don't always know the names of. Can someone tell me why something like this
doesn't work.
entity name=dynamicfield processor=CachedSqlEntityProcessor
datasource=database query=select optionname, datatype, optionvalue FROM
mmc.dbo.product_specs WITH (NOLOCK) WHERE optionName='Category' AND
productId='K-690' AND manufacturer='Kohler'
field column=optionvalue
name=${dynamicfield.optionname}_${dynamicfield.datatype}/
/entity
--
View this message in context:
http://lucene.472066.n3.nabble.com/Data-Import-Handler-with-Dynamic-Fields-tp3978419.html
Sent from the Solr - User mailing list archive at Nabble.com.
Solr Import Handler Custom Transformer not working
I have created a custom transformer for dynamic fields but it doesn't seem to
be working correctly and I'm not sure how to debug it with a live running
solr instance.
Here is my transformer
package org.build.com.solr;
import org.apache.solr.handler.dataimport.Context;
import org.apache.solr.handler.dataimport.Transformer;
import java.util.List;
import java.util.Map;
public class FacetsTransformer extends Transformer {
public Object transformRow(MapString, Object row, Context context) {
Object tf = row.get(facets);
if (tf != null) {
if (tf instanceof List) {
List list = (List) tf;
for (Object o : list) {
String[] arr = ((String)
o).split(=);
if (arr.length == 3)
row.put(arr[0].replaceAll([^A-Za-z0-9], ) +
_ + arr[1], arr[2]);
}
} else {
String[] arr = ((String) tf).split(=);
if (arr.length == 3)
row.put(arr[0].replaceAll([^A-Za-z0-9], ) +
_ + arr[1], arr[2]);
}
row.remove(facets);
}
return row;
}
}
Seems pretty standard. Here is the data contained in the facet row:
ADA=boolean=Yes|Category=string=Kitchen Faucets|Category=string=Pullout
Kitchen Faucets|Country of Origin=string=USA|Eco
Friendly=boolean=No|Escutcheon Included=boolean=Yes|Faucet
Centers=numeric=0|Faucet Holes=numeric=1|Filtering=boolean=No|Flow Rate
(GPM)=numeric=2.20|Handle Style=string=Metal Lever|Handles
Included=boolean=Yes|Height=numeric=16.63|Hose
Length=numeric=33|Installation Type=string=Deck Mounted|Low Lead
Compliant=Boolean=Yes|MasterFinish=String=Bronze
Tones|MasterFinish=String=Chromes|MasterFinish=String=Nickel
Tones|Material=string=Metal|Max Deck Thickness=numeric=1.38|Number Of
Handles=numeric=1|Pre Rinse=boolean=No|Pullout
Spray=boolean=Yes|Sidespray=boolean=No|Soap Dispenser
Included=boolean=No|Spout Height=numeric=10.00|Spout
Reach=numeric=9.50|Spout Swivel=numeric=360|Spout Type=string=Swivel|Sub
Category=string=Pullout Spray Faucets#x0D;
|Theme=string=Traditional / Classic|Valve Type=string=Ceramic
Disc|Width=numeric=10.5|
here is my import config file
entity name=mainProductData
transformer=RegexTransformer,org.build.com.solr.FacetsTransformer
query=select facets from blah
field column=facets splitBy=|/
/entity
But for some reason none of the facets are showing up in my index. The
transformer is being used because there are no class not found errors. Can
anybody lend a hand as to what might be going wrong here?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Import-Handler-Custom-Transformer-not-working-tp3978746.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Import Handler Custom Transformer not working
Also here is my schema dynamicField name=*_string type=facetstring indexed=true stored=false multiValued=true/ dynamicField name=*_numeric type=tfloat indexed=true stored=false multiValued=true/ dynamicField name=*_boolean type=boolean indexed=true stored=false/ -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Import-Handler-Custom-Transformer-not-working-tp3978746p3978748.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr dismax not returning expected results
Adding autoGeneratePhraseQueries=true to my field definitions has solved the problem -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-dismax-not-returning-expected-results-tp3891346p3891594.html Sent from the Solr - User mailing list archive at Nabble.com.
default fq in dismax request handler being overridden
I have a dismax request handler with a default fq parameter. requestHandler name=dismax class=solr.DisMaxRequestHandler lst name=defaults str name=echoParamsexplicit/str float name=tie0.01/float str name=qf sku^9.0 upc^9.1 searchKeyword^1.9 series^2.8 productTitle^1.2 productID^9.0 manufacturer^4.0 masterFinish^1.5 theme^1.1 categoryName^2.0 finish^1.4 /str str name=pf searchKeyword^2.1 text^0.2 productTitle^1.5 manufacturer^4.0 finish^1.9 /str str name=bqisTopSeller:true^1.30/str str name=bflinear(popularity,1,2)^3.0/str str name=flproductID,manufacturer/str str name=mm3-1 5-2 690%/str int name=ps100/int int name=qs3/int str name=fqdiscontinued:false/str /lst /requestHandler I understand that when I send a search post ex. /select?qt=dismaxq=f-0sort=score%20descfq=type_string:faucet What I would like to know is if there is a way to always include the fq that is defined in the query handler and not have it be overridden but appended automatically to any solr searches that use the query handler. -- View this message in context: http://lucene.472066.n3.nabble.com/default-fq-in-dismax-request-handler-being-overridden-tp3768735p3768735.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: default fq in dismax request handler being overridden
Think I answered my own question... I need to use an appends list -- View this message in context: http://lucene.472066.n3.nabble.com/default-fq-in-dismax-request-handler-being-overridden-tp3768735p3768817.html Sent from the Solr - User mailing list archive at Nabble.com.
