Re: Error Adding a Replica to SOLR Cloud 8.2.0

We finally got this fixed by temporarily disabling any updates to the SOLR index. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error on searches containing specific character pattern

Thanks David, I'll set up  the techproducts schema and see what happens. Kind regards, Andy On 4/09/20 4:09 pm, David Smiley wrote: Hi, I looked at the code at those line numbers and it seems simply impossible that an ArrayIndexOutOfBoundsException could be thrown there because it's guarded b

Re: Error on searches containing specific character pattern

Hi, I looked at the code at those line numbers and it seems simply impossible that an ArrayIndexOutOfBoundsException could be thrown there because it's guarded by a condition ensuring the array is of length 1. https://github.com/apache/lucene-solr/blob/2752d50dd1dcf758a32dc573d02967612a2cf1ff/luce

Re: Error from server at http://localhost:8983/solr/search: Expected mime type application/octet-stream but got text/html

Hi, There were few discussions about similar issues these days. A JIRA issue was created https://issues.apache.org/jira/browse/SOLR-14768 Regards Dominique Le jeu. 27 août 2020 à 15:00, Divino I. Ribeiro Jr. < divinoirj.ib...@gmail.com> a écrit : > Hello everyone! > When I run an query to Sol

Re: Error when trying to create a core in solr

Hi Erick, I probably should have included information about the config directory. As part of the setup, I had copied the config directory as follows: $ cp -r /usr/share/solr-8.5.1/server/solr/configsets/_default/* . Note that the copy was from solr-8.5.1 because I could not find a '_default' dir

Re: Error when trying to create a core in solr

You need the entire config directory for a start, not just the schema file. And there’s no need to copy things around, just path to the nutch-provided config directory and you can leave off the “conf” since the upload process automatically checks for it and does the right thing. Best, Erick > On

Re: "Error creating core. No system property or default value specified for X"

Screenshots do not come through, the mail server pretty aggressively strips them. Ok, this is weird. There’s no way you should be getting results from an index that has only a write.lock file. So the fact that you were suggests that you are looking. at one thing and Solr is looking at another.

Re: Error while updating: java.lang.NumberFormatException: empty String

On Thu, Jan 16, 2020 at 3:10 PM Edward Ribeiro wrote: > Hi, > > There is a status_code in the JSON snippet and it is going as a string with > single space. Maybe it is an integer? > > Best, > Edward > > Oh wow, yes you are right. When I adjusted the status_code to not be a space, it fixed everyth

Re: Error while updating: java.lang.NumberFormatException: empty String

Hi, There is a status_code in the JSON snippet and it is going as a string with single space. Maybe it is an integer? Best, Edward On Thu, Jan 16, 2020 at 2:06 PM rhys J wrote: > While updating my Solr core, I ran into a problem with this curl statement. > > When I looked up the error, the on

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

This setting is pretty dangerous. It’ll build the suggester every time the Solr instance starts. The DocumentDictionaryFactory will read _every_ document in your index to extract the stored “suggest” field and create the dictionary. But this points to the fact that you hadn’t built the dictionar

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

It's working now that I changed the solrconfig.xml to mySuggester FreeTextLookupFactory DocumentDictionaryFactory suggest 3 text_en_splitting *true* On Wed, Nov 6, 2019 at

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

What's the command to build it On Wed, Nov 6, 2019 at 3:06 PM Mikhail Khludnev wrote: > Hello, > > Have you build suggester before requesting? > > On Wed, Nov 6, 2019 at 12:50 PM Tyrone Tse wrote: > > > Solr version 8.1.1 > > > > My schema > > > > > multiValued="false" indexed="true"/> > > >

Re: Error with Solr Suggester using lookupIml = FreeTextLookupFactory

Hello, Have you build suggester before requesting? On Wed, Nov 6, 2019 at 12:50 PM Tyrone Tse wrote: > Solr version 8.1.1 > > My schema > > multiValued="false" indexed="true"/> > > > solconfig.xml > > > > mySuggester > FreeTextLookupFactory >

Re: Error in Initializing plugin

There is very little information to go on here. What is the full stack trace from the Solr log file for this? Best, Erick > On Oct 17, 2019, at 5:36 AM, Shubham Goswami > wrote: > > Hi Community > > I am working with currencies and exchange rates and getting this following > error. > error:

Re: Error 401 and 404 while Solr product search.

Those are two different collections. Have you tried solving the easier one (non secure), by accessing /solr/master_doterraUSContent_Index/select in the browser? Seems to be the collection is not there or named differently. So, that would be the first step to check. Regards, Alex. On Thu, 27 Ju

Re: Error in last_modified for open documents formats

Solr requires a very precise format, the one you’re sending has both too many zeros to the right of the decimal point and is missing the terminating ‘Z’. See: https://lucene.apache.org/solr/guide/6_6/working-with-dates.html The output you’re getting is from Tika, which is used by Solr. You’ll ha

Re: Error when merging segments ("terms out of order")

Hello, I installed it with the openjdk-11-jdk package from Ubuntu 18.04 repository with apt-get... For the moment, no more problem with openjdk-8... I don't know the exact reason of problems with openjdk-11 32bit (?). I will go on a 64bit system when possible (server is installed as 32bit si

Re: Error when merging segments ("terms out of order")

On 5/8/2019 10:47 AM, Alméras Yannick wrote: The problem of segments merging seems to be solved when I replace Java 11 32bit with Java 8 32bit on my prod Ubuntu server... (On my dev archlinux computer, no problem with Java 11 64bit...). It is strongly recommended to run a 64-bit version of Java

Re: Error when merging segments ("terms out of order")

Hello ! The problem of segments merging seems to be solved when I replace Java 11 32bit with Java 8 32bit on my prod Ubuntu server... (On my dev archlinux computer, no problem with Java 11 64bit...). Hope this will be the real solution... "I cross my fingers" (from french "je croise les doigts

Re: Error when merging segments ("terms out of order")

Hello ! I'm going deeper into the mystery... There is something wrong in my configuration or with solr because segments merging never work as it should. Example (step by step) : * I clear my index. * I had entries one by one. No problem when looking at items ; all fields are ok -if no segmen

Re: Error when merging segments ("terms out of order")

Hello ! (sorry for my last double post... I thought there was a problem with my other mail address). Le mardi 7 mai 2019, 15:25:13 CEST Shawn Heisey a écrit : > On 5/7/2019 5:28 AM, Alméras Yannick wrote: > > I don't understand a problem on my ubuntu 18.04 solr server (version > > 7.6.0)... > >

Re: Error when merging segments ("terms out of order")

On 5/7/2019 5:28 AM, Alméras Yannick wrote: I don't understand a problem on my ubuntu 18.04 solr server (version 7.6.0)... When merge of segments is called, there is an error and then, the index is not writable. The logs of a failed segments merging are at the end of this message (here, I forced

Re: Error getting replica locations : unable to get autoscaling policy session when creating collection

I run the following command to allow Solr and ZooKeeper to communicate via https. Without this, they are still trying to communicate via http. zkcli.bat -zkhost localhost:2181 -cmd clusterprop -name urlScheme -val https Another issue which may cause this issue is that you have not created the SS

RE: ERROR: Error CREATEing SolrCore 'nutch': Unable to create core [nutch] Caused by: invalid boolean value:

Hi Sid, 1. Does folder/configuration actually exist (ie: Did you copy the folder to /opt/solr/server/solr/nutch/conf/ )? Yes the configuration does exist 2. I noticed you wrote that you are using Nutch 1.5. Is that a typo for Nutch 1.15? It was a typo. I am using Nutch 1.15 3. Have you tr

RE: ERROR: Error CREATEing SolrCore 'nutch': Unable to create core [nutch] Caused by: invalid boolean value:

Hey Vishal, 1. Does folder/configuration actually exist (ie: Did you copy the folder to /opt/solr/server/solr/nutch/conf/ )? 2. I noticed you wrote that you are using Nutch 1.5. Is that a typo for Nutch 1.15? 3. Have you tried rolling back to a 7.x version? (It is possible that the Nutch 1.15 c

Re: Error getting replica locations : unable to get autoscaling policy session when creating collection

I encountered the same error, how did you resolve this? -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error on text field

On 3/26/2019 10:56 AM, Dave Beckstrom wrote: I'm using Nutch to crawl and index some content. It failed on a SOLR field defined as a text field when it was trying to insert the following value for the field: What precisely does "failed" mean? Can you share the complete error? It will likely

Re: Error when trying to create a collection with SolrCloud and Zookeeper Ensemble

Hi, How is your setup like? Which version of Solr and ZooKeeper are you using? And are you enabling Basic Authentication and SSL in your Solr? Regards, Edwin On Wed, 6 Mar 2019 at 13:37, maimuna ambareen wrote: > I received the below error when i tried to create a collection with > SolrCloud >

Re: Error getting replica locations : unable to get autoscaling policy session when creating collection

Hi, I have found that the issue is due to the https clusterprop configuration is not correctly loaded to zookeeper. As such, they are still communicating on http, when Solr is already configured to use https. Regards, Edwin On Sat, 2 Feb 2019 at 13:49, Zheng Lin Edwin Yeo wrote: > Hi, > > I am

Re: Error using collapse parser with /export

I checked again and looks like all documents with the same "id_field" reside on the same shard, in which case I would expect collapse parser to work. Here is my complete query: http://localhost:8983/solr/mycollection/stream/?expr=search(mycollection ,sort="field1 asc,field2 asc",fl="fileld1,field2

Re: Error using collapse parser with /export

Hi Joel, Thanks for responding to the query. Answers to your questions: 1) After collapsing is it not possible to use the /select handler? - The collapsing itself is causing the failure (or did I not understand your question right?) 2) After exporting is it possible to unique the records using t

Re: Error when configuring reclaimDeletesWeight in TieredMergedPolicyFactory

see: https://issues.apache.org/jira/browse/LUCENE-8263 On Thu, Jan 24, 2019 at 11:23 PM Zheng Lin Edwin Yeo wrote: > > Hi, > > I am using Solr 7.5.0, and I came across this presentation ( > https://www.slideshare.net/sematext/solr-search-engine-optimize-is-not-bad-for-you) > on Solr Search Engine

Re: Error using collapse parser with /export

I haven't had time to look into the details of this issue but it's not clear that these two features will be able to be used together. Although that it would be nice if the could. A couple of questions about your use case: 1) After collapsing is it not possible to use the /select handler? 2) Afte

Re: Error using collapse parser with /export

Hello, Following up on my query. I know this might be too specific an issue. But I just want to know that it's a legitimate bug and the supported operation is allowed with the /export handler. If someone has an idea about this and could confirm, that would be great. Thanks, Rahul On Thu, Jan 17,

Re: Error at import data from SQL Server 2017 (Solr 7.5.0)

@lucene.apache.org Subject: Re: Error at import data from SQL Server 2017 (Solr 7.5.0) Can you post the part of schema.xml where the fields are defined. The error seems to be an incompatibility between your schema and what your are trying to import. By the way, I think you should have further

Re: Error at import data from SQL Server 2017 (Solr 7.5.0)

t;, > "statusMessages": { > "Total Requests made to DataSource": "1", > "Total Rows Fetched": "1", > "Total Documents Processed": "0", > "Total Documents Skipped": "0", > "

Re: Error at import data from SQL Server 2017 (Solr 7.5.0)

Started": "2018-12-15 04:46:50", "Total Documents Failed": "1", "Time taken": "0:0:0.34" } } But Solr does not create the document and the log shows: Error creating document : SolrInputDocument(fields: [rut=61.601.000-k,​ idLabora

Re: Error at import data from SQL Server 2017 (Solr 7.5.0)

Images and the like are aggressively stripped by the e-mail server, so there's no error information in your post. Exactly _how_ are you importing? Data Import Handler? If so, please show your config as well. Best, Erick On Fri, Dec 14, 2018 at 4:19 PM Alexis Aravena Silva wrote: > > Hello, > >

Re: Error waiting for SolrCore to be created

So I don't know what to recommend except rebooting. Solr (actually, Lucene) would _not_ delete that file without replacing it. There is a great deal of care taken to insure that the index is consistent and I haven't heard of the segments file disappearing by itself, some external process is very l

Re: Error waiting for SolrCore to be created

@Erick Erickson Thanks for your feedback and support. segments* file is missing from /solr/solr-6.4.1/server/solr/coreStore_shard1_replica1/data/index directory. Erick: Is that directory the one you expect for that replica? This is a sanity check, as there's no reason it would change magically.

Re: Error waiting for SolrCore to be created

Caused by: org.apache.lucene.index.IndexNotFoundException: no segments* file found in LockValidatingDirectoryWrapper(MetricsDirectory(NRTCachingDirectory(MMapDirectory@/solr/solr-6.4.1/server/solr/coreStore_shard1_replica1/data/index segments* is what's used to indicate what segments are available

Re: ERROR When uploading configset

https://zookeeper.apache.org/doc/r3.4.6/zookeeperAdmin.html See the jute.maxbuffer sysvar. That said, having 6M of synonym file is suspect. Remember that each and every core will have to download this file on startup. Solr intentionally limited the defalut value here so that you have to override

Re: Error when loading configset

It’s also documented in the Solr Ref Guide: https://lucene.apache.org/solr/guide/7_5/setting-up-an-external-zookeeper-ensemble.html#increasing-the-file-size-limit Even if you

Re: Error when loading configset

By the default, ZooKeeper's znode maximum size limit is 1MB. If you try to send more than this then an error occurs. You can increase this size limit but it has to be done both on server (ZK) and client (Solr) side. See this discussion for more details: http://lucene.472066.n3.nabble.com/How-to-s

Re: Error while indexing Thai core with SolrCloud

Thank you. Will check all options and let you know. From: Alexandre Rafalovitch Sent: Sunday, October 21, 2018 8:09:34 PM To: solr-user Subject: Re: Error while indexing Thai core with SolrCloud Ok, That may have been a bit too much :-) However, it was useful

Re: Error while indexing Thai core with SolrCloud

Ok, That may have been a bit too much :-) However, it was useful. There seem to have several possible avenues: 1) You are using SolrJ and your SolrJ version is not the same as the version of the Solr server. There was a bunch of things that could trigger, especially in combination with Unicode bu

Re: Error while indexing Thai core with SolrCloud

Hi, Thank you. Full stacktrace below "core_node_name":"172.19.218.201:8082_solr_core_th"}DEBUG - 2018-10-19 02:13:20.343; org.apache.zookeeper.ClientCnxn$SendThread; Reading reply sessionid:0x200b5a04a770005, packet:: clientPath:null serverPath:null finished:false header:: 356,1 replyHeader

Re: Error while indexing Thai core with SolrCloud

gt; > > From: Alexandre Rafalovitch > Sent: Sunday, October 21, 2018 5:18:24 PM > To: solr-user > Subject: Re: Error while indexing Thai core with SolrCloud > > I would check if the Byte-order mark is the cause: > https://urldefense.proofpoi

Re: Error while indexing Thai core with SolrCloud

Hi Alexandre, Thank you. How this explain the issue exists only with SolrCloud and not standalone? Moshe From: Alexandre Rafalovitch Sent: Sunday, October 21, 2018 5:18:24 PM To: solr-user Subject: Re: Error while indexing Thai core with SolrCloud I would

Re: Error while indexing Thai core with SolrCloud

I would check if the Byte-order mark is the cause: https://en.wikipedia.org/wiki/Byte_order_mark The error message does not seem to be a perfect match to this issue, but a good thing to check anyway. That symbol (right at the file start) is usually invisible and can trip Java XML parsers for some

Re: Error casting to PointField

Thanks Shawn and Erick. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error while creating a new solr core

"When used in combination with the RSA JSSE and RSA JCE providers, this crypto module provides a FIPS-compliant (FIPS 140-2) implementation. " This is written in the oracle website so I suppose JsafeJCE provides a FIPS-compliant JSSE. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-Use

Re: Error casting to PointField

On 9/11/2018 10:15 PM, Zahra Aminolroaya wrote: Thanks Erick. We used to use TrieLongField for our unique id and in the document it is said that all Trie* fieldtypes are casting to *pointfieldtypes. What would be the alternative solution? I've never heard of Trie casting to Point. Point is the

Re: Error casting to PointField

People usually just use a string field in place of longs etc.. On Tue, Sep 11, 2018 at 9:15 PM Zahra Aminolroaya wrote: > > Thanks Erick. We used to use TrieLongField for our unique id and in the > document it is said that all Trie* fieldtypes are casting to > *pointfieldtypes. What would be the a

Re: Error casting to PointField

Thanks Erick. We used to use TrieLongField for our unique id and in the document it is said that all Trie* fieldtypes are casting to *pointfieldtypes. What would be the alternative solution? Best, Zahra -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: error render solr data spatial from geoserver

Hi, Which version of Solr are you using? And are your different shard on the same machine or different machine? Regards, Edwin On Tue, 4 Sep 2018 at 18:04, tkg_cangkul wrote: > Hi i wanna try to rendering solr data spatial from geoserver layer. > when i try to render it from single shard solr

Re: Error while creating a new solr core

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Shalvak, On 9/11/18 01:51, Shalvak Mittal (UST, ) wrote: > I have recently installed solr 7.2.1 in my ubuntu 16.04 system. > While creating a new core, the solr logging shows an error saying > > > " Caused by: org.apache.solr.common.SolrException:

Re: Error while creating a new solr core

On 9/10/2018 11:51 PM, Shalvak Mittal (UST, ) wrote: I have recently installed solr 7.2.1 in my ubuntu 16.04 system. While creating a new core, the solr logging shows an error saying " Caused by: org.apache.solr.common.SolrException: fips module was not loaded." I have never heard of a module

Re: Error casting to PointField

point-based fields cannot be used for , see: https://issues.apache.org/jira/browse/SOLR-10829 This should be documented better in the ref guide On Tue, Sep 11, 2018 at 5:53 AM Zahra Aminolroaya wrote: > > We read that in Solr 7, Trie* fields are deprecated, so we decided to change > all of ou

Re: Error with plugin in Solrcloud

Thanks Shawn. I wrote my own filter. I attached my jar in hear. I found your answer in hear: http://lucene.472066.n3.nabble.com/How-to-load-plugins-with-Solr-4-9-and-SolrCloud-td4312113.html Based on your answer, is it possible that blob Api does not work for my own filter jar? norm.jar

Re: Error with plugin in Solrcloud

On 8/18/2018 11:03 PM, Zahra Aminolroaya wrote: Thanks Shawn. For Solr mode I should include all dependencies in lib, so I thought for Solr Cloud mode I should include the dependencies too. Even for standalone mode, you don't want those dependency jars in the lib folder.  The same problems can

Re: Error with plugin in Solrcloud

Thanks Shawn. For Solr mode I should include all dependencies in lib, so I thought for Solr Cloud mode I should include the dependencies too. The error is as follows: Caused by: org.apache.solr.common.SolrException: Unable to reload core [textd_shard1_replica2] at org.apache.solr.cor

Re: Error with plugin in Solrcloud

Thanks Shawn. For Solr mode I should include all dependencies in lib, so I thought for Solr Cloud mode I should include the dependencies too. The error is as follows: java.util.concurrent.ExecutionException: org.apache.solr.common.SolrException: Unable to create core [gettingstarted_shard1_repl

Re: Error with plugin in Solrcloud

On 8/18/2018 4:16 AM, Zahra Aminolroaya wrote: My plugin works correctly in Solr. Now I want to have my plugin in solrCloud mode: I have a main jar file named "norm" and I have other jar files that my "norm" is dependent on them: "lucene-analyzers-common-6.6.1","lucene-core-6.6.1","slf4j-api-1.7

Re: error on health check from command line

Additional information: Using solr-6.3.0 Also tried, no luck: ./bin/solr healthcheck -c poi -z host1:2181,host2:2181,host3:2181 SOLR_AUTH_TYPE=“basic” SOLR_AUTHENTICATION_OPTS="-Dbasicauth=username:password" On Tue, Jul 10, 2018 at 9:09 AM Satya Marivada wrote: > Hi, > > How do I supply the ba

Re: Error in solr Plugin

Thanks Andrea and Erick -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error in solr Plugin

bq. The lucene-core7 had some useful functions like incrementToken which I could not find in previous versions because of that I used this version. Do not do this. You simply cannot mix jar versions because there was a function in the old version that you want to use. The support for that functi

Re: Error in solr Plugin

Hi, I mean you should use Maven which would pickup, starting from a number (e.g. 6.6.1), all the correct dependencies you need for developing the plugin. Yes, the "top" libraries (e.g. Solr and Lucene) should have the same version but on top of that, the plugin could require some other direct

Re: Error in solr Plugin

Thanks Andrea. Do you mean all of my jar file versions should be 6.6.1? The lucene-core7 had some useful functions like incrementToken which I could not find in previous versions because of that I used this version. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error in solr Plugin

Hi Zahra, I think your guessing it's right: I see some mess in libraries versions. If I got you * the target platform is Solr 6.6.1 * the compile classpath includes solr-core-4.1.0, 1.4.0 (!) and lucene 7.4.0? If that is correct, with a ClassCastException you're just scraping the surface

Re: Error deleting copy field

Ikenna, Can you please create a JIRA issue[1], and if possible include your schema? Thanks. -- Steve www.lucidworks.com [1] https://wiki.apache.org/solr/HowToContribute#JIRA_tips_.28our_issue.2Fbug_tracker.29 > On Jun 6, 2018, at 5:16 PM, Ikenna Okonkwo wrote: > > Hi Steve, > > I didn't us

Re: Error deleting copy field

Hi Steve, I didn't use a dynamic field. It was an exact match. -- Ikenna Okonkwo Senior Front End Developer, WMX Project Phone: (905) 821-2111 (Ext: 78847) Mobile: (437) 922-9004 ikenna.okon...@walmart.com Walmart Canada Corp. 1940 Argentia Road Mississauga, Ontario L5N 1P9 Save money. Live bet

Re: Error deleting copy field

Hi Ikenna, If the source field(s) are dynamic fields, then you have to give the same spelling you used when you created the copy field. E.g. for ‘item_desc_en’, if the source field in the copy field directive is ‘*_desc_en’, then you have to use that when you issue the delete. You can find ou

Re: Error using multiple terms in function query

Problems like this are usually caused by the whole query not even making it to Solr due to bad HTTP param encoding. For example, if you're using curl with request parameters in the URL, you need to manually encode spaces as either "+" or "%20" -Yonik On Tue, May 15, 2018 at 7:41 PM, Shamik Bando

Re: Error when indexing against a specific dynamic field type

Steve's comment is much more germane. KeywordTokenizer, used in alphaOnlySort last I knew is not appropriate at all. Do you really want single tokens that consist of the entire document for sorting purposes? Wouldn't the first 1K be enough? It looks like this was put in in 4.0, so I'm guessing you

Re: Error when indexing against a specific dynamic field type

Erick, thanks for the response. I have a number of documents in our database where solr is throwing the same exception against *_tsing types. However, when I index against the same document with our solr 4.7, it is successfully indexed. So, I assume something is different between 4.7 and 7.3. I wa

Re: Error when indexing against a specific dynamic field type

On 5/1/2018 8:40 AM, THADC wrote: > I get the following exception: > > *Exception writing document id FULL_36265 to the index; possible analysis > error: Document contains at least one immense term in > field="gridFacts_tsing" (whose UTF8 encoding is longer than the max length > 32766), all of whic

Re: Error when indexing against a specific dynamic field type

The input in the error message starts “lorem ipsum”, so it contains spaces, but the alphaOnlySort field type (in Solr’s example schemas anyway) uses KeywordTokenizer, which tokenizes the entire input as a single token. As Erick implied, you maybe should not be doing that with this kind of data -

Re: Error when indexing against a specific dynamic field type

You're sending it a huge term. My guess is you're sending something like base64-encoded data or perhaps just a single unbroken string in your field. Examine your document, it should jump out at you. Best, Erick On Tue, May 1, 2018 at 7:40 AM, THADC wrote: > Hello, > > We are migrating from solr

Re: Error when starting standalone zookeeper instance

sorry, I found the zookeeper group and got my question answered there. I will be more careful in the future. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error when starting standalone zookeeper instance

ok, I made a couple of changes, however I don't think the server is starting. When I invoke the start: *$ ./bin/zkServer.sh start ZooKeeper JMX enabled by default Using config: /c/Users/thclotworthy/DevBase/zookeeper/zookeeper-3.4.10/bin/../conf/zoo.cfg Starting zookeeper ... STARTED* , it says i

Re: Error when starting standalone zookeeper instance

On 4/27/2018 10:48 AM, THADC wrote: I am new to zookeeper. created my zoo.cfg and attempted starting instance (DOS shell). my command is: .\bin\zkServer.cmd start zoo.cfg and getting following error: "C:\Users\thclotworthy\DevBase\zookeeper\zookeeper-3.4.10\bin\..\build\classes;C:\Users\thclot

Re: Error when starting standalone zookeeper instance

Hi, Look in the "data" folder - there has to be a file named "myid". In this file, the ID of your zookeeper has to be defined. Start by 1. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error when starting standalone zookeeper instance

Thanks for responding, below is the zoo.cfg file contents. I took this directly from the solr ref guide 7.0, for setting up an external zookeeper (https://lucene.apache.org/solr/guide/7_0/setting-up-an-external-zookeeper-ensemble.html#setting-up-an-external-zookeeper-ensemble). It did not specify t

Re: Error when starting standalone zookeeper instance

What do your ZooKeeper configurations look like? My guess is that the "myid" field isn't formed correctly or is absent. Best, Erick On Fri, Apr 27, 2018 at 9:48 AM, THADC wrote: > Hi, > > I am new to zookeeper. created my zoo.cfg and attempted starting instance > (DOS shell). my command is: > >

Re: Error configuring Spell Checker

James, That was it! Many, many thanks! Gene On Tue, Apr 17, 2018 at 8:57 AM, Dyer, James wrote: > (moving to solr-user@lucene.apache.org) > > Gene, > > I can reproduce your problem if I misspell the "spellcheck.dictionary" > parameter in my query. But I see your query has "direct" which m

RE: Error configuring Spell Checker

(moving to solr-user@lucene.apache.org) Gene, I can reproduce your problem if I misspell the "spellcheck.dictionary" parameter in my query. But I see your query has "direct" which matches the "name" element of one of your spellcheckers. I think the actual problem in your case might be that y

Re: Error when running ant package in solr 7.2.1 from source

On 3/27/2018 7:36 PM, C F wrote: I'm unable to run the ant package target in solr-7.2.1-src.tgz. Any ideas? Is git required now? This is not a new requirement.  When the official repository was in subversion, that target required svn -- it couldn't be built if the checkout was done from githu

Re: Error in indexing JSON with space in value

Thanks for the input. I have got this to work by using cygwin. Regards, Edwin On 23 March 2018 at 07:04, Chris Hostetter wrote: > : > : Ah, there's the extra bit of context: > : > PS C:\curl> .\curl ' > : > : You're using Windows perhaps? If so, it's probably a shell issue > : getting all of

Re: Error in indexing JSON with space in value

Yes, I'm running this on Windows, using Windows Powershell "curl" command. Will try out other tools like cygwin. Thanks you. Regards, Edwin On 23 March 2018 at 06:52, Yonik Seeley wrote: > Ah, there's the extra bit of context: > > PS C:\curl> .\curl ' > > You're using Windows perhaps? If so

Re: Error in indexing JSON with space in value

: : Ah, there's the extra bit of context: : > PS C:\curl> .\curl ' : : You're using Windows perhaps? If so, it's probably a shell issue : getting all of the data to the "curl" command. Yep.. and you cna even see in the trace output that curl thinks the entire JSON payload you want to send is 2

Re: Error in indexing JSON with space in value

Ah, there's the extra bit of context: > PS C:\curl> .\curl ' You're using Windows perhaps? If so, it's probably a shell issue getting all of the data to the "curl" command. Something like cygwin or WSL (Windows Subsystem for Linux) may make your life easier. -Yonik On Thu, Mar 22, 2018 at 6:45

Re: Error in indexing JSON with space in value

Thanks for your reply. This is the curl command that I run, with the "--trace -" output. PS C:\curl> .\curl 'http://localhost:8983/solr/collection1/update/json/docs? split=/|/orgs ' -H 'Content-type:application/j son' -d ' {

Re: Error in indexing JSON with space in value

Thanks for your reply. PS C:\curl> .\curl ' http://localhost:8983/edm/emails6/update/json/docs?split=/|/orgs' -H 'Content-type:application/j son' -d ' { "id":"1", "name_s": "Joe Smith", "phone_s": 876876687, "orgs": [ { "name1_s": "Microsoft", "city_s": "Seattle",

Re: Error in indexing JSON with space in value

It looks like a curl globbing issue from the curl error message you included: "curl: (3) [globbing] bad range specification in column 39" You can try turning off curl globbing with the -g param. That may not be the only issue though, as the command shown shouldn't have triggered curl globbing. Pe

Re: Error in indexing JSON with space in value

On 3/22/2018 9:48 AM, Zheng Lin Edwin Yeo wrote: > I am trying to index the following JSON, in which there is a space in the > name "Joe Smith". > > .\curl 'http://localhost:8983/solr/collection/update/json/docs?split=/|/orgs > ' > -H 'Content-type:application/json' -d ' > { > "id":"1", > "

Re: Error in indexing JSON with space in value

I can't reproduce the problem you described -- using 7.2.1 and the techproducts example i can index a JSON string w/white space just fine... $ bin/solr -e techproducts $ curl 'http://localhost:8983/solr/techproducts/update/json/docs' -H 'Content-type:application/json' -d ' { "id":"1", "nam

Re: Error when indexing with SolrJ HTTP ERROR 405

On 3/18/2018 9:46 PM, Khalid Moustapha Askia wrote: SolrClient client = new HttpSolrClient.Builder(" http://localhost:8983/solr/#/corename";).build(); When I remove the "#" It throws a NullPointerException URLs with # in them will ONLY work in a browser.  They will not work for SolrJ.  T

Re: Error when indexing with SolrJ HTTP ERROR 405

Regarding the # in the Solr Url, I found that I also have the # that appears automatically in the Solr URL when I'm at the Solr Admin UI. Even when I correct it to remove it, it will appear again. How can we remove the #? Regards, Edwin On 19 March 2018 at 17:36, Vincenzo D'Amore wrote: > Pay

Re: Error when indexing with SolrJ HTTP ERROR 405

Pay attention to # in the Solr Url http://localhost:8983/solr/#/corename Try to correct it into http://localhost:8983/solr/corename On Mon, Mar 19, 2018 at 8:47 AM, Shamik Sinha wrote: > You need to send binary content instead of html. Atleast that is what the > error shows. > > I also think

  1   2   3   4   5   6   7   >