Re: org.apache.lucene.util.fst.FST taking up lot of Java Heap Memory

2020-08-07 Thread sanjay dutt
Best explanation I found so far. Will migrate to LatLonPointSpatialField and try to share the benchmark data here. Thanks again David. Cheers,Sanjay Sent from Yahoo Mail on Android On Sat, Aug 8, 2020 at 3:31 AM, David Smiley wrote: Since you have a typical use-case (point data, queries

RE: solr startup

2020-08-07 Thread Schwartz, Tony
suggester? what do i need to look for in the configs? Tony Sent from my Verizon, Samsung Galaxy smartphone Original message From: Dave Date: 8/7/20 18:23 (GMT-05:00) To: solr-user@lucene.apache.org Subject: Re: solr startup It sounds like you have suggester indexes

Re: solr startup

2020-08-07 Thread Dave
It sounds like you have suggester indexes being built on startup. Without them they just come up in a second or so > On Aug 7, 2020, at 6:03 PM, Schwartz, Tony wrote: > > I have many collections. When I start solr, it takes 30 - 45 minutes to > start up and load all the collections. My

solr startup

2020-08-07 Thread Schwartz, Tony
I have many collections. When I start solr, it takes 30 - 45 minutes to start up and load all the collections. My collections are named per day. During startup, solr loads the collections in alpha-numeric name order. I would like solr to load the collections in the descending order. So the

Re: org.apache.lucene.util.fst.FST taking up lot of Java Heap Memory

2020-08-07 Thread David Smiley
Since you have a typical use-case (point data, queries that are rectangles), I strongly encourage you to migrate to LatLonPointSpatialField: https://builds.apache.org/job/Solr-reference-guide-master/javadoc/spatial-search.html#latlonpointspatialfield It's based off an internal "BKD" tree index

Re: wt=xml not defaulting the results to xml format

2020-08-07 Thread Shawn Heisey
On 8/7/2020 9:30 AM, yaswanth kumar wrote: solr/PROXIMITY_DATA_V2/select?q=pkey:223_*=true=country_en=country_en What ever I am trying is not working other than sending wt=xml as a parameter while hitting the url. I tried your solrconfig.xml addition and a URL similar to yours out on

Re: Solrj client 8.6.0 issue special characters in query

2020-08-07 Thread Chris Hostetter
: Hmm, setting -Dfile.encoding=UTF-8 solves the problem. I have to now check : which component of the application screws it up, but at the moment I do NOT : believe it is related to Solrj. You can use the "forbidden-apis" project to analyze your code and look for uses of APIs that depend on the

RE: Getting rid of Master/Slave nomenclature in Solr

2020-08-07 Thread Jamie Gruener
Marcus, Thank you for tackling this. I'm not a developer, just a user, so my ability to help is limited to moral support. And I support your efforts 100%. Thank you, --Jamie -Original Message- From: Marcus Eagan Sent: Monday, August 3, 2020 12:15 PM To: solr-user@lucene.apache.org

Re: wt=xml not defaulting the results to xml format

2020-08-07 Thread Alexandre Rafalovitch
You have echoParams set to all. What does that return? Regards, Alex On Fri., Aug. 7, 2020, 11:31 a.m. yaswanth kumar, wrote: > Thanks for looking into this Erick, > > > solr/PROXIMITY_DATA_V2/select?q=pkey:223_*=true=country_en=country_en > > that's what the url I am hitting, and also I

Re: Add custom comparator for field(s) for Sorting.

2020-08-07 Thread Erick Erickson
You can sort by function, see: https://lucene.apache.org/solr/guide/6_6/function-queries.html. Not quite sure what the function would look like though. What I would do rather than a custom sort or sort by function is normalize these into a different field at index time and just sort on that.

Add custom comparator for field(s) for Sorting.

2020-08-07 Thread Pushkar Raste
Hi, Is it possible to add a custom comparator to a field for sorting. e.g. let's say I have field 'name' and following documents { id : "doc1", name : "1" } { id : "doc2", name : "S1" } { id : "doc2", name : "S2" } if I sort using field 'name', the order would be : ["doc1",

Re: Solr + Parquets

2020-08-07 Thread Jörn Franke
DIH is deprecated and it will be removed from Solr. You may though still be able to install it as a plug-in. However, AFAIK nobody maintains it. Do not use it anymore You can write a custom Spark data source that writes to Solr or does it in a spark Map step using SolrJ . In both cases do not

Solr + Parquets

2020-08-07 Thread Kevin Van Lieshout
Hi, Is there any assistance around writing parquets from spark to solr shards or is it possible to customize a DIH to import a parquet to a solr shard. Let me know if this is possible, or the best work around for this. Much appreciated, thanks Kevin VL

Re: copyField from empty multivalue

2020-08-07 Thread matthew sporleder
Nevermind I think we found this was caused by a bug in our (new) custom indexer On Thu, Aug 6, 2020 at 4:11 PM matthew sporleder wrote: > > I have a copyField: > > > > But sometimes preview ( indexed="true" stored="true" multiValued="true" />) is not populated. > > It appears that the

Re: wt=xml not defaulting the results to xml format

2020-08-07 Thread yaswanth kumar
Thanks for looking into this Erick, solr/PROXIMITY_DATA_V2/select?q=pkey:223_*=true=country_en=country_en that's what the url I am hitting, and also I made sure that initParams is all commented like this and also I made sure that there is no uncommneted section defined for initParams. Also from

Re: wt=xml not defaulting the results to xml format

2020-08-07 Thread Erick Erickson
Please show us the _exact_ URL you’re sending as well as the response header, particularly the echoed params. This is a long shot, but also take a look at any “initParams” sections in solrconfig.xml. The “wt” parameter you’ve specified in your select handler should override anything in the

Re: Replication of Solr Model and feature store

2020-08-07 Thread krishan goyal
Hi Monica, Replication is working fine for me. You just have to add the _schema_feature-store.json and _schema_model-store.json to confFiles under /replication in solrconfig.xml I think the issue you are seeing is where the model is referencing a feature which is not present in the feature

Re: wt=xml not defaulting the results to xml format

2020-08-07 Thread yaswanth kumar
Thanks Shawn, for looking into this. I did make sure that no explicit parameter wt is being sent and also verified the logs and even that's not showing up any extra parameters. But it's always taking json as a default, unless I pass it explicitly as wt=xml which I don't want to do it here. Is

Re: Cybersecurity Incident Report

2020-08-07 Thread Jan Høydahl
If you suspect a new vulnerability in the product, please report as detailed on our security page: https://lucene.apache.org/solr/security.html For these existing ones, you may first check whether upgrades are already done in 8.5 or 8.6, and if not, check if there is an open JIRA issue about

Re: Solrj client 8.6.0 issue special characters in query

2020-08-07 Thread Andy Webb
hi Jörn - something's decoding a UTF8 sequence using the legacy iso-8859-1 character set: Jörn is J%C3%B6rn in UTF8 J%C3%B6rn misinterpreted as iso-8859-1 is Jörn Jörn is J%C3%83%C2%B6rn in UTF8 I hope this helps track down the problem! Andy On Fri, 7 Aug 2020 at 12:08, Jörn Franke wrote: >

Re: Solrj client 8.6.0 issue special characters in query

2020-08-07 Thread Jörn Franke
Hmm, setting -Dfile.encoding=UTF-8 solves the problem. I have to now check which component of the application screws it up, but at the moment I do NOT believe it is related to Solrj. On Fri, Aug 7, 2020 at 11:53 AM Jörn Franke wrote: > Dear all, > > I have the following issues. I have a Solrj

Solrj client 8.6.0 issue special characters in query

2020-08-07 Thread Jörn Franke
Dear all, I have the following issues. I have a Solrj Client 8.6 (but it happens also in previous versions), where I execute, for example, the following query: Jörn If I look into Solr Admin UI it finds all the right results. If I use Solrj client then it does not find anything. Further,

Re: wt=xml not defaulting the results to xml format

2020-08-07 Thread Shawn Heisey
How are you sending the query request that doesn't come back as xml? I suspect that the request is being sent with an explicit wt parameter set to something other than xml. Making a query with the admin ui would do this, and it would probably default to json. When you make a query, assuming