Re: Upgrade Solr 8.0.0 issue

Usually I will create the collection again since I will re-index after the upgrade. If I create the collection again, the new core.properties will be created. If you plan to use the same schema.xml, have to check if there are class that have become deprecated, as usually some old class will get

How to implement security for solr admin page

Hi Team, Working solR search. Able to create schema and query and get results. Problem: Any one having admin url would be able to read and write to solR. There by looking for some mechanism like access_key/userid/password etc to prevent unauthorized users to admin url. Would you please suggest

Re: Upgrade Solr 8.0.0 issue

i will re-index with clean after the solr 8.0.0 upgrade.Is it necessary to change the core.properties? In solr 6.0.0 i wrote only name,shard and collection in core.properties i didn't write coreNodeName and collection.configName. For starting solr, first i delete the zoo_data version-2 folder

Re: Solr unable to start up after setting up SSL in Solr 7.4.0

Hi, Regarding the issue with jetty-ssl.xml which I have mentioned previously, seems that the issue still exists in Solr 8.0.0 if I use the jetty-ssl.xml that comes with Solr 8.0.0. Regards, Edwin On Fri, 24 Aug 2018 at 09:19, Zheng Lin Edwin Yeo wrote: > Thanks for the advice. > > Regards, >

Re: Upgrade Solr 8.0.0 issue

Hi Vishal, There could be problem with your index if you upgrade directly from Solr 6.1.0 to Solr 8.0.0, which is two major version, as Solr only supports upgrade for one major version. Regards, Edwin On Thu, 28 Mar 2019 at 21:30, vishal patel wrote: > Hi > > I am upgrading solr 6.1.0 to

Re: Problem with white space or special characters in function queries

Thanks Jan, I was not aware of this, appreciate your help. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: security.json "all" predefined permission

There was some other issues with the "all" permission as well lately, see https://issues.apache.org/jira/browse/SOLR-13344 Order matters in permissions, the first permission matching is used, but I don't know how that would change anything

Re: Problem with white space or special characters in function queries

Functions can never contain spaces. Try to substitute the term with a variable, i.e. a request parameter, e.g. bf=if(termfreq(ADSKFeature,$myTerm),log(CaseCount),sqrt(CaseCount))=CUI+(Command) -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 28. mar. 2019 kl. 18:51

security.json "all" predefined permission

Hi all, Diving into the RuleBasedAuthorizationPlugin for the first time in awhile, and found that the predefined permission "all" isn't behaving the way I'd expect it to. I'm trying to figure out whether it doesn't work the way I think, whether I'm just making a dumb mistake, or whether it's

Re: Problem with white space or special characters in function queries

Ahemad, I don't think its related to the field definition, rather looks like an inherent bug. For the time being, I created a copyfield which uses a custom regex to remove whitespace and special characters and use it in the function. I'll debug the source code and confirm if it's bug, will raise a

Spell check support for CJK?

Hello, This is probably a basic question, but I can't find any definitive answer. Does CJK (Chinese, Japanese or Korean language analyzer/tokenizer) support spell-check or did-you-mean functionality? I can get Latin languages working fine for spell check, but not CJK. Basic search is working

Re: Solr 8.0.0 coreNodeName

This seems related to https://issues.apache.org/jira/browse/SOLR-11503? On Thu, Mar 28, 2019 at 2:14 AM vishal patel wrote: > > Hi > > I am upgrading the solr 8.0.0 from 6.1.0. Before I can not add the > coreNodeName in core.properties and its working fine for me. But when i > start the solr

Re: SolrCore Initialization Failures in Solr 8.0.0

I know that need to reindex of collection when upgrading from 6 to 8. Is it necessary to create a collection using admin GUI for solr 8.0.0? Can I copy of collection Folder excluding data from solr 6.1.0 and upconfig? My collection Folder like --- product --- conf ---

Re: SolrCore Initialization Failures in Solr 8.0.0

Is it needed to create collection again in Solr 8.0.0 if its already created in Solr 6.1.0 ? When i upgraded Solr 6.1.0 from 5.2.0, i just copied collection and changed the solrconfig.xml as per solr 6.1.0. upconfig using below command zkcli.bat -cmd bootstrap -solrhome

Re: Stopwords param of edismax parser not working

and to say anything about your particular situation we need to see the field definitions from the schema for the field you expect stopwrods to be removed from and the stopwords file for those fields. But Walter’s comment is germane. Stopwords lead to a number of incongruities and are best just

Re: Stopwords param of edismax parser not working

Why are you removing stopwords? That hack made sense in the 1950s, but I haven’t removed stopwords for the last twenty years. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Mar 28, 2019, at 2:47 AM, Ashish Bisht wrote: > > Hi, > > We are trying

Upgrade Solr 8.0.0 issue

Hi I am upgrading solr 6.1.0 to 8.0.0. In solr 6.0.0 my folder structure below ---product ---conf ---schema.xml ---solrconfig.xml ---core.properties ---solr.xml core.properties contains name=product shard=shard1 collection=product upconfig command : zkcli.bat -cmd bootstrap

Re: Using copyFields

Thanks. Adding default field in solrconfig.xml worked. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Problem with white space or special characters in function queries

Hi,Did you find any solution for this, I tried adding analyzers with keyword tokenizer and reversewildcardfilterfactory but was not working.  It's working when I don't include spaces when I am doing wildcard search but not giving the result when I have whitespaces and do wildcard search using *

Re: Using copyFields

On Thu, 2019-03-28 at 05:03 -0700, Sharmadha wrote: > I created my own field named "cfield1" of type text_general and added > a copyField with src = "*" and dest = "cfield1". Posted the films > data. After this , on typing "comedy" in query field , the query > doesn't fetch results. You need to

Re: Using copyFields

As mentioned in https://lucene.apache.org/solr/guide/7_7/solr-tutorial.html#create-a-catchall-copy-field , instead of having a copyField on src="*" ,dest ="_text_" , I added a copyField with src="*" ,dest ="cfield". when I did copyField on src="*" ,dest ="_text_" , on firing query=comedy , it

Re: Using copyFields

What do you mean does not fetch results? It returns the found documents, but not the text content? In this case you need to store the field. Is comedy a stop word defined by you? > Am 28.03.2019 um 13:03 schrieb Sharmadha : > > Following solr tutorial , >

Using copyFields

Following solr tutorial , https://lucene.apache.org/solr/guide/7_7/solr-tutorial.html#create-a-catchall-copy-field ,without adding copyField with src = "*" and dest = "_text_" , I created my own field named "cfield1" of type text_general and added a copyField with src = "*" and dest = "cfield1".

Re:Intervals vs Span guidance

For anyone interested, Alan Woodward responded to the copy of this that I posted in the dev mailing list. https://lists.apache.org/thread.html/e0c8f97211efa1c7445ac2514d4ff0570953ded4a723c81338b41b94@%3Cdev.lucene.apache.org%3E

post command not working on non-file arguments when run from crontab

I'm working with a script where I want to send a command to delete all elements in an index; notably, /opt/solr/bin/post -c -d "*:*" When run interactively, this works fine. However, when run automatically as a cron job, it gives this interesting output: Unrecognized argument: "*:*" If

Stopwords param of edismax parser not working

Hi, We are trying to remove stopwords from analysis using edismax parser parameter.The documentation says *stopwords A Boolean parameter indicating if the StopFilterFactory configured in the query analyzer should be respected when parsing the query. If this is set to false, then the

Solr 8.0.0 coreNodeName

Hi I am upgrading the solr 8.0.0 from 6.1.0. Before I can not add the coreNodeName in core.properties and its working fine for me. But when i start the solr 8.0.0 with same core.properties it will give ERROR 2019-03-25 09:01:18.704 ERROR