Filtered search term suggestions via Facet Prefixing or NGrams

Hi, we've successfully implemented suggestion of search terms using facet prefixing with Solr 4.0. However, with lots of unique index terms we've encountered performance problems (long running queries) and even exceptions: Too many values for UnInvertedField faceting on field textbody. We

Re: Filtered search term suggestions via Facet Prefixing or NGrams

Hi, can somebody help, please? Maybe you can at least answer parts of my question? I'd expect that somebody at least knows the limitations of faceting with UninvertedField? Thank you, Andreas Andreas Hubold wrote on 04.04.2013 13:30: Hi, we've successfully implemented suggestion

Number of unique terms in a field

Hi, in previous versions of Solr (at least with 1.4.1) the admin page displayed the number of unique terms in the index / in a field. I cannot find this on the new admin page anymore (Solr 4.0.0). Can somebody please give me a pointer or is this info not available anymore? Thank you, Andreas

Re: Number of unique terms in a field

:33 PM, Andreas Hubold wrote: Hi, in previous versions of Solr (at least with 1.4.1) the admin page displayed the number of unique terms in the index / in a field. I cannot find this on the new admin page anymore (Solr 4.0.0). Can somebody please give me a pointer or is this info not available

Index compatibility from 4.0 to 4.3

Hi, we are planning to update Solr installations from 4.0 to 4.3 and want to avoid reindexing. But solrconfig.xml contains the following comment for luceneMatchVersion: ... Generally, you want to use the latest version to get all bug fixes and improvements. It is highly recommended that you

Re: Index compatibility from 4.0 to 4.3

Thank you both for your answers. I really like the idea of explaining the changes for luceneMatchVersion in more detail. Maybe this could even go into the release notes? Thanks, Andreas Shawn Heisey wrote on 10.05.2013 15:27: On 5/10/2013 5:11 AM, Jan Høydahl wrote: Hi, The fastest way to

dismax query does not match with additional field in qf

Hi, I ran into a problem with the Solr dismax query parser. We're using Solr 4.10.0 and the field types mentioned below are taken from the example schema.xml. In a test we have a document with rather strange content in a field named name_tokenized of type text_general: abc_iframe

Re: dismax query does not match with additional field in qf

Andreas Hubold wrote on 09/30/2014 05:14 PM: I ran into a problem with the Solr dismax query parser. ... I'd expect that an additional field in the qf parameter would not lead to fewer matches. Okay, the above example is a rather crude test but I'd like to understand it. Is this a bug in Solr

Re: dismax query does not match with additional field in qf

won't happen since only the full string is indexed. Generally, you need to escape all special characters in a query. Then hopefully your string field will match. -- Jack Krupansky -Original Message- From: Andreas Hubold Sent: Tuesday, September 30, 2014 11:14 AM To: solr-user

Re: dismax query does not match with additional field in qf

as a phrase of contiguous terms. -- Jack Krupansky -Original Message- From: Andreas Hubold Sent: Tuesday, October 7, 2014 12:08 PM To: solr-user@lucene.apache.org Subject: Re: dismax query does not match with additional field in qf Okay, sounds reasonable. However I didn't expect this when

create new core based on named config set using the admin page

Hi, I'm trying to use named config sets with a standalone Solr server (4.10.1). But it seems there's no way to create a new core based on a named config set using the Solr admin page. Or did I miss something? Should I open a JIRA issue? Regards, Andreas

Re: create new core based on named config set using the admin page

in context: http://lucene.472066.n3.nabble.com/create-new-core-based-on-named-config-set-using-the-admin-page-tp4167850p4167860.html Sent from the Solr - User mailing list archive at Nabble.com. -- Andreas Hubold Software Architect tel +49.40.325587.519 fax +49.40.325587.999 andreas.hub

solr.xml coreRootDirectory relative to solr home

Hi, I'm trying to configure a different core discovery root directory in solr.xml with the coreRootDirectory setting as described in https://cwiki.apache.org/confluence/display/solr/Format+of+solr.xml I'd like to just set it to a subdirectory of solr home (a cores directory to avoid

Re: Schemaless configuration using 4.10.2/API returning 404

Hi, it might be a silly question, but are you sure that a Solr core collection1 exists? Or does it have a different name? At least you would get a 404 if no such core exists. Regards, Andreas nbosecker wrote on 11/05/2014 09:12 PM: Hi all, I'm working on updating legacy Solr to 4.10.2 to

How to dynamically create Solr cores with schema

Hi, I have a use-case where Java applications need to create Solr indexes dynamically. Schema fields of these indexes differ and should be defined by the Java application upon creation. So I'm trying to use the Core Admin API [1] to create new cores and the Schema API [2] to define fields.

Re: How to dynamically create Solr cores with schema

-tabpanel#comment-13711098 This would have been a perfect fit for me but it seems the idea got rejected. Thank you, Andreas Andreas Hubold wrote on 11/06/2014 04:04 PM: Hi, I have a use-case where Java applications need to create Solr indexes dynamically. Schema fields of these indexes differ

Re: How to dynamically create Solr cores with schema

://www.solr-start.com/ and @solrstart Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 On 6 November 2014 10:04, Andreas Hubold andreas.hub...@coremedia.com wrote: Hi, I have a use-case where Java applications need to create Solr indexes dynamically. Schema fields

How to specify a property for all cores

Hi, I'm using Solr 4.10.1 with the new solr.xml format (auto-discovered cores). I'm trying to set a property that I can reference in solrconfig.xml files of all cores. I know I can use JVM system properties or add the property to each core's core.properties file. Is there another

Re: create new core based on named config set using the admin page

://issues.apache.org/jira/browse/SOLR-6703 https://issues.apache.org/jira/browse/SOLR-6084 On Wed, Nov 5, 2014 at 11:57 PM, Andreas Hubold andreas.hub...@coremedia.com wrote: Hi, Solr 4.8 introduced named config sets with https://issues.apache.org/jira/browse/SOLR-4478. You can create a new core

soft commit and deletions

Hi, I've read about soft commits in Erick Erickson's excellent blog article [1]: The thing to understand most about soft commits are that they will make documents visible But I'm still not totally sure. Does a soft commit also make deleted documents invisible? In a test with an

Re: soft commit and deletions

. Or if you do open a new searcher and any autowarming hasn't completed you'll still see the snapshot before the commit. Best, Erick On Wed, Nov 26, 2014 at 8:16 AM, Shawn Heisey apa...@elyograg.org wrote: On 11/26/2014 8:18 AM, Andreas Hubold wrote: But I'm still not totally sure. Does a soft

Batch updates and separate update request processor chain for atomic document updates

Hi, we're using a SolrJ client which either adds (or overwrites) existing documents or updates some meta-data fields of existing documents. Our default update request processor chain is configured with a processor for language detection. To avoid setting a wrong language, we're using a

Re: Dismax and StandardTokenizer: OR queries despite mm=100%

at client side. Ahmet On Wednesday, September 23, 2015 10:00 PM, Andreas Hubold <andreas.hub...@coremedia.com> wrote: Hi, we're using Solr 4.10.4 and the dismax query parser to search across multiple fields. One of the fields is configured with a StandardTokenizer (type "text_gener

Dismax and StandardTokenizer: OR queries despite mm=100%

Hi, we're using Solr 4.10.4 and the dismax query parser to search across multiple fields. One of the fields is configured with a StandardTokenizer (type "text_general"). I set mm=100% to only get hits that match all terms. This does not seem to work for queries that are split into multiple

Re: Core Admin API: Create Solr core if it does not exist

patchFilter.java:729) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:258) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207) Cheers, Andreas Andreas Hubold schrieb am 16.06.2016 um 16:09: Hi, we're still using Solr 4.10

Core Admin API: Create Solr core if it does not exist

Hi, we're still using Solr 4.10.4 without SolrCloud and create cores dynamically using the Core Admin API. We have multiple applications that access a core and create it if it doesn't exist. To this end, we use the STATUS action to see if a required core exists and if it doesn't, create it

faceting on correlated multi-valued fields?

Hi, I'm thinking about indexing articles with tags in a denormalized way as follows multiValued="true"/> stored="false" multiValued="true"/> An article can have multiple tags. Each tag has a description and an ID. The multi-valued fields tagIds and tagDescriptions have the same length

facet on two multi-valued fields

Hi, my schema looks like this multiValued="true"/> stored="false" multiValued="true"/> I'd like to get the tagIds of documents with a certain tagDescription (and text). However tagIds contains multiple ids in the same order as tagDescription and simple faceting would return all. Is there

Re: facet on two multi-valued fields

docs and show some queries (do you query the tagDescription field?) and wanted facet output? There may be several ways to solve the task, depending on the exact use case. One solution could be to use child documents. -- Jan Høydahl, search solution architect Cominvent AS - www.cominv

Wrong comments in example schema about DocValues requirements

Hi, there are comments in the example schema files of Solr 6.4.1 about field requirements for DocValues. For example, in server/solr/configsets/basic_configs/conf/managed-schema: docValues: [...] they might require the field to be single-valued, be required or have a default

Solr 6.6 UNLOAD core broken?

Hi, I just tried to update from Solr 6.5.1 to Solr 6.6.0 and observed a changed behaviour with regard to unloading cores in Solr standalone mode. After unloading a core using the CoreAdmin API (e.g. via Admin UI), I still get search results for that core. It seems, the search request

Re: SolrJ does not use HTTP proxy anymore in 7.5.0 after update from 6.6.5

ces are not closed automatically by HttpSolrClient. Cheers, Andreas Michael Joyner schrieb am 12.10.2018 um 17:36: Would you supply the snippet for the custom HttpClient to get it to honor/use proxy? Thanks! On 10/10/2018 10:50 AM, Andreas Hubold wrote: Thank you, Shawn. I'm now using a cus

Re: SolrJ does not use HTTP proxy anymore in 7.5.0 after update from 6.6.5

/1/2018 6:54 AM, Andreas Hubold wrote: Is there some other way to configure an HTTP proxy, e.g. with HttpSolrClient.Builder? I don't want to create an Apache HttpClient instance myself but the builder from Solrj (HttpSolrClient.Builder). Unless you want to wait for a fix for SOLR-12848, you have

SolrJ does not use HTTP proxy anymore in 7.5.0 after update from 6.6.5

Hi, SolrJ 6.6.5 used org.apache.http.impl.client.SystemDefaultHttpClient under the hood, which took system properties for HTTP proxy config into account (http.proxyHost and http.proxyPort). The deprecated SystemDefaultHttpClient class was replaced as part of SOLR-4509. And with Solr 7.5.0

Storing PID below /run

Hi, we'd like to store the PID file for the Solr service in a directory below the /run directory (CentOS 7.5). I've set "SOLR_PID_DIR=/run/solr" in solr.in.sh. But if /run is mounted as tmpfs, the directory /run/solr will not exist after boot and the pid file cannot be stored in that

DocValues or stored fields to enable atomic updates

Hi, I have a question on schema design: If a single-valued StrField is just used for filtering results by exact value (indexed=true) and its value isn't needed in the search result and not for sorting, faceting or highlighting - should I use docValues=true or stored=true to enable atomic

Re: Solr 7.7 UpdateRequestProcessor broken

ength(), maxFieldValueChars); +if (content instanceof CharSequence) { + docSize += Math.min(((CharSequence) content).length(), maxFieldValueChars); } } -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 14. feb. 2019 kl. 16:0

Solr 7.7 UpdateRequestProcessor broken

Hi, while trying to update from Solr 7.6 to 7.7 I run into some unexpected incompatibilites with UpdateRequestProcessors. The SolrInputDocument passed to UpdateRequestProcessor#processAdd does not return Strings for string fields anymore but instances of

Re: Solr dependencies with security issues (CVEs)

xplain a new vulnerability on open mailing lists. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 24. jan. 2019 kl. 13:10 skrev Andreas Hubold : Hi, in our project, we're checking JAR dependencies with the OWASP dependency check [1] for security issues for which CV

Solr dependencies with security issues (CVEs)

Hi, in our project, we're checking JAR dependencies with the OWASP dependency check [1] for security issues for which CVEs have been reported. There are CVEs for some of Solr's third-party dependencies in version 7.6.0, and I wonder if you have plans to update these to unaffected versions.

Sort field values by client-specified order

Hi, we have a fixed number of values in a String field (up to around 100), that should be used for sorting query results. Is there some way to let the client specify the sort order as part of its query? I was thinking about using a function query. Is it possible to specify the order of

termfreq and IntPointField

Hi, we changed our int fields from TrieIntField to IntPointField when we upgraded from Solr 7.7 to 8.1.1. We're using the termfreq function to order results and this worked with Solr 7.7 and TrieIntField but does not work with IntPointField and Solr 8.1.1 anymore. The field is defined as

Solr LockObtainFailedException and NPEs for CoreAdmin STATUS

Hi, we're running tests on a stand-alone Solr instance, which create Solr cores from multiple applications using CoreAdmin (via SolrJ). Lately, we upgraded from 8.4.1 to 8.6.3, and sometimes we now see a LockObtainFailedException for a lock held by the same JVM, after which Solr is broken

Re: Atomic update wrongly deletes child documents

Hi, I was able to work around the issue. I'm now using a custom UpdateRequestProcessor that removes undefined fields, so that I was able to remove the catch-all dynamic field "ignored" from my schema.. Of course, one has to be careful to not remove fields that are used for nested documents in the

Re: Atomic update wrongly deletes child documents

Thank you, I've created https://issues.apache.org/jira/browse/SOLR-15018 now. Regards, Andreas Erick Erickson wrote on 24.11.20 13:29: Sure, raise a JIRA. Thanks for the update... On Nov 24, 2020, at 4:12 AM, Andreas Hubold wrote: Hi, I was able to work around the issue. I'm now using

How to get the config set name of Solr core

Hi, is there a way to get the name of the config set for an existing Solr core from a stand-alone Solr server (not SolrCloud)? I need the name of the config set to create another core with the same config. The actual use case here is to have a script that creates cores of the same config on

Re: How to get the config set name of Solr core

Hi, I was able to add the config set to the STATUS response by implementing a custom extended CoreAdminHandler. However, it would be nice if this could be added in Solr itself. I've create a JIRA for this: https://issues.apache.org/jira/browse/SOLR-15034 Kind regards, Andreas -- Sent from:

Atomic update wrongly deletes child documents

Hi, when I try to atomically update a single field of a parent/root document, all of its nested child documents disappear (Solr 8.6.3). I've tracked the problem down to the reconstruction of the original document in DistributedUpdateProcessor#getUpdatedDocument. Solr correctly finds