Re: I cannot get nested objects to index - with image links
Hi Matthew
The (pseudo-)field in which you want to put the nested documents ("content"
in your example) should not be added to the schema. The actual fields of
the nested document (id, stuff1, stuff2) need to match an explicit field
definition or a dynamicField definition in your schema though.
Thomas
Op ma 24 okt. 2022 om 23:48 schreef Matthew Castrigno :
> Hello Community, Thank you for taking the time to read my message.
>
> I am attempting to index (update) a document with a nested object.
>
> In reading the documentation is seems to state that the fields of the
> nested object do not need to be and should not be added
>
> to schema.xml. I am getting error that the field of the nested object is
> undefined, and I am not sure what I am doing wrong.
>
> Any insights appreciated. Thank you
>
> https://i.postimg.cc/25GtB1Mc/update.png
>
> https://i.postimg.cc/SKk5s6TY/schema.png
>
> --
> "This message is intended for the use of the person or entity to which it
> is addressed and may contain information that is confidential or
> privileged, the disclosure of which is governed by applicable law. If the
> reader of this message is not the intended recipient, you are hereby
> notified that any dissemination, distribution, or copying of this
> information is strictly prohibited. If you have received this message by
> error, please notify us immediately and destroy the related message."
>
Re: Solr 9 Custom ibraries
Hi, Can you be more specific on what libraries you try to use, and how you added them in Solr 8? The reference guide may help you: https://solr.apache.org/guide/solr/latest/configuration-guide/solr-plugins.html Jan > 24. okt. 2022 kl. 23:51 skrev Ed K : > > Hello everyone, > Wondering if anyone who has migrated to Solr 9.0 is using the custom > libraries ? I have some custom libraries that I've used with 8.11.2 but not > seeing that functionality on Solr 9. > Any info is greatly appreciated. > Thanks~ed
[ANNOUNCE] Solr Docker images now pin the Linux release
Solr 9 was released on May 12th, using the eclipse-temurin:17-jre base image. Thus, we are pinned to Java 17 and Solr's Docker image will thus always use an updated Java 17 version. If you pull the docker image from time to time that is. However, the base image tag 17-jre did not give us pinning to a specific Ubuntu Linux major release. At the time of Solr 9 release on May 12th it would pull Ubuntu 20.04 (Focal Fossa), but at the end of May, it was auto upgraded to the brand new Ubuntu 22.04 (Jammy Jellyfish). This was not our desire, and we have learnt that due to this, our image is no longer compatible with Docker client versions before 20.10.16. Having a "floating" linux release like this can also break the image in other subtle ways, as well as breaking downstream images using us as a base image. We therefore decided to start pinning not only Java release, but also Linux release in our official Docker images. This means that Solr 9.0 is once again based on Ubuntu 20.04 Focal, i.e. a downgrade. Note that our images will still receive important Linux bug fixes from time to time, but you won't get them unless you re-pull the image. When we upgrade Linux major version in the future, it will be a deliberate decision and not by accident. Read this news on the web page: https://solr.apache.org/news.html#solr-docker-images-now-pin-the-linux-release
[ANNOUNCE] Java 17 bug affecting Solr
Several users running Solr in production on OpenJDK 17 or later have experienced JVM crashes due to a known bug in the JDK. Read more about the bug in SOLR-16463[1]. Known mitigations are to either downgrade to JDK 11 or to start Solr with a Java startup flag that avoids the failure condition. Here is how to manually apply the flag: Edit your solr.in.sh or solr.in.cmd file to set the SOLR_OPTS environment variable as follows: Linux: SOLR_OPTS=-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put Windows: SET SOLR_OPTS=-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put Alternatively, you can inject the same flag with the -a argument, e.g: bin/solr -a "-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put" If you run Solr 9 with the official Docker image, we have already pushed an updated Docker image to Docker Hub that will inject the flag for you. Just pull the image again to get it. The Docker image uses the -a option to set this java flag when running Solr, so if you are using the -a option you will need to provide the JVM flag mentioned above in addition to the other flags you are setting. [1]: https://issues.apache.org/jira/browse/SOLR-16463 Read this news on the web page: https://solr.apache.org/news.html#java-17-bug-affecting-solr
Re: Cannot get nested objects to index
Your images are not showing, and clicking through doesn't get me anything other than 404. The list settings strip out images, and images are not searchable when the message gets archived anyway. Images are usually harder to work with (they often don't look good if reading mail from a phone for example). If you can share the specific page of the reference guide you are looking at, and example updates that don't seem to work (as text) that will help folks help you. On Mon, Oct 24, 2022 at 5:35 PM Matthew Castrigno wrote: > Images I tried to add to original post. > > [url= > https://postimg.cc/944b6QWZ][img]https://i.postimg.cc/25GtB1Mc/update.png[/img][/url > ] > [url= > https://postimg.cc/WdYSYkPs][img]https://i.postimg.cc/SKk5s6TY/schema.png[/img][/url > ] > > From: Matthew Castrigno > Sent: Monday, October 24, 2022 2:10 PM > To: users@solr.apache.org > Subject: Cannot get nested objects to index > > Hello Community, Thank you for taking the time to read my message. I am > attempting to index (update) a document with a nested object. In reading > the documentation is seems to state that the fields of the nested object do > not need to be and > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside the St. Luke's email system. > > ZjQcmQRYFpfptBannerEnd > Hello Community, Thank you for taking the time to read my message. > > I am attempting to index (update) a document with a nested object. In > reading the documentation is seems to state that the fields of the nested > object do not need to be and should not be added to schema.xml. I am > getting error that the field of the nested object is undefined, and I am > not sure what I am doing wrong. Any insights appreciated. Thank you. > > [cid:8383c74f-7d38-4694-8eb8-bf71f699027a] > [cid:c6791e41-de3d-460e-b193-500a5ade35ad] > > "This message is intended for the use of the person or entity to which it > is addressed and may contain information that is confidential or > privileged, the disclosure of which is governed by applicable law. If the > reader of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution, or copying of this > information is strictly prohibited. If you have received this message by > error, please notify us immediately and destroy the related message." > > -- > "This message is intended for the use of the person or entity to which it > is addressed and may contain information that is confidential or > privileged, the disclosure of which is governed by applicable law. If the > reader of this message is not the intended recipient, you are hereby > notified that any dissemination, distribution, or copying of this > information is strictly prohibited. If you have received this message by > error, please notify us immediately and destroy the related message." > -- http://www.needhamsoftware.com (work) http://www.the111shift.com (play)
Re: How to return location name in search result?
This is a good question, but I'm not sure you are going to be able to do this easily. For any "which part of my document matched the query" questions we generally suggest the highlighting component: https://solr.apache.org/guide/solr/latest/query-guide/highlighting.html However, you want to return another field that relates to the part of the document that matches your query, so I don't think highlighting will do that for you. If you do not have a lot of data, I would recommend denormalizing your data if this feature is necessary. This means breaking up your current documents and duplicating them such that each document only holds one location (the field would be single-valued). That way whenever you get a document that matches, you can easily just return the string value of that location. The downside of this method is that your index will get bigger (but depending on the size right now this might not actually matter), and you need to update multiple documents anytime you want to change shared metadata. - Houston On Mon, Oct 24, 2022 at 1:01 PM Gurmit Teotia wrote: > I've defined following field in my schema to store latitude and longitude- > > stored="true" sortMissingLast="true" multiValued="true"/> > > and "location" is of following field type > docValues="true"/> > > I'm storing multiple latitude and longitude pairs in loc_coords field and > using a "geofilt" filter successfully able to retrieve the documents close > to a given point. I'm looking for your advice on how I can store the > location names, corresponding to latitude/longitude pairs and return them > in search result e.g. if "loc_coords" has following lat/long coordinates > for "London" and "New York" > > ["51.5072,0.1276", "40.7128,74.0060"] > > In my search query when I'm looking for documents *near *to "New York" then > the above document will be returned and in the search result I also want > to return the location name "New York". > > I'm considering following two approaches to store location names and return > them in search result- > > 1. Store location names in a string array field ( call it location_names) > in the same order as lng/lat pair in location_coords field and somehow find > the index of matching lng/lat pair and use the index on location_names > field to retrieve the location name. This is just logical thinking. I'm not > sure how I can achieve it in Solr. > > 2. Store the data as GeoJson in solr because GeoJson allows to store extra > information along with coordinates as mentioned here- https://geojson.org/ > . > But I'm not sure how I'm going to get the location name of matching > coording in the search result. > > Thank you for the help. > > GS >
Error when building suggester
My collection in solr contains ~8 millions documents, I tried to build the
suggester and I get an error message attached to this email
LexisNexis is a trading name of RELX (UK) LIMITED - Registered office - 1-3
STRAND, LONDON WC2N 5JR
Registered in England - Company No. 02746621
{
"responseHeader": {
"zkConnected": true,
"status": 500,
"QTime": 854
},
"error": {
"msg": "input automaton is too large: 1001",
"trace": "java.lang.IllegalArgumentException: input automaton is too
large: 1001\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1298)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\tat
org.apache.lucene.util.automaton.Operations.topoSortStatesRecurse(Operations.java:1306)\n\t
